Thursday 5 September 2013

Links


MGCP Gateway Integration with CUCM and PSTN Service Provider

https://supportforums.cisco.com/docs/DOC-22421

=======================================================================

Cisco Unified Mobility: Single Number Reach & Call flows

https://supportforums.cisco.com/docs/DOC-23053

=======================================================================

 Configuring Call Manager Voice Gtewayes

http://jeffreycmiller.com/download/3814551-Configuring-CallManager-Voice-Gateways.pdf

=====================================================================


http://www.ciscopress.com/articles/article.asp?p=2021962&seqNum=7

=======================================================================

Managing the Phone System Integrations
 
 
=======================================================================
 
Unity Connection


===============================================

Media Termination point (MTP)

http://rsccievoice.wordpress.com/2012/06/18/media-termination-point-mtp/

=============================================

https://www.ciscolive365.com/connect/sessionDetail.ww?SESSION_ID=4447

==============================================

Configuring ISDN PRI


Wednesday 24 July 2013

Transferring Incoming (DID calls ) to Different number.

Transferring Incoming (DID calls ) to Different number.

Login to Voice Gateway.

Create the below rule:

num-exp 62220700 1234

Where 622207000 is incoming DID number.
 and 1234 is local directory number.

Crate a dummy DN and enable call-forward all to external number or mobile.

ephone-dn  1
 number 1234
call-forward all 9987654321


Regards,
MMM

Friday 5 July 2013

Configuring Extensions and Phones on CME (Call Manager Express)

Before configuring a IP phone on Cisco CallManager Express (CCME), we need first to
understand the concepts of ephone and ephone-dn.
In CCME, “ephone” (short for Ethernet Phone) refers to the physical IP phone device, and is
configured with the Ethernet MAC address of the IP phone.The ephone directory number
(ephone-dn) refers to the phone lines that are associated with the ephone device.
Dual Line: A dual line uses for features such as call transfer ,call waiting and conferencing
A dual line configuration uses one line with two channels so that a second call to the same
line can be put in call waiting mode or a transfer.

-->Assigning Extensions to IP Phones –line 1
ephone-dn 10 dual-line
number 500
label ABC AYZ
description ABC XYZ
name ABC XYZ

-->Assigning Extensions to IP Phones –line 2

ephone-dn 11 dual-line
number 501
label ABC XYZ
description ABC XYZ
name Hiroaki Hamasaka

-->Configure the 7940 phone and assign ephone-dn numbers to buttons 1 and 2

ephone 1
mac-address A4BA.DBCC.467B
ephone-template 1
type 7940
button 1:10 2:11

-->Resetting IP Phone
#ephone 1
#restart
#


Links:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/gui/user/guide/cmegui_user.pdf
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configuration_example
09186a008037f2a9.shtml

Regards,
MMM

Thursday 14 March 2013

When the user clicks the "Start Voice Monitor" button in CSD, an error pops up



Configuration in CUCM


Please go to agent's phone, the ones that you are going to monitor and record and check these parameters:
1) Span PC port --> should be enabled. If it is disabled, please enable it and “RESTART” the phone.
2) Advertise G722 codec --> MUST be Disabled



3) The agents extension should be Unique on Call Manager, the lines that are going to be monitored or recorded can't be shared lines.
Note:  You can go to the physical phone -> Settings -> Device configuration -> Ethernet configuration and confirm Span to PC Port says “Yes”.
SpanToPCport.png

Configuration in UCCX


1) From the Navigation bar please Select “Cisco Desktop Administrator”
2) Then go to Services Configuration --> Multiline, Monitoring and Recording --> VOIP Monitoring Device
Make sure that default "Monitor Service" is selected and "Desktop Monitoring" is enabled for each agent

Configuration in Agent’s PC


1) The phone should be daisy chain. (Computer --- connected to--> IP Phone -- connect to ---> Network)
2) On C:\Program Files\Cisco\Desktop\bin ---> PostInstall.exe -> This should have the correct IP address of the NIC card that the computer is using. (If the computer is using 2 NIC cards (Wireless and Lan), one of them should be disabled. So, if they leave the LAN NIC enable, they should be using that IP address on Postinstall.exe
3) Make sure that Windows firewall is disabled (It could be blocking UDP traffic). Sometimes antivirus could block this kind of traffic too, so disabled it and test.


Other things to check


1)     NIC binding should have the NIC used to record as the first one at the Agent and Supervisor PCs.
My Network Places -> right click -> properties -> Advanced -> Advanced settings -> the recording NIC should be the first one at the connection field. If not, correct it and reboot the PC.
2)     Recording Count should NOT be ZERO:
Go to Cisco Unified CCX Administration --> System > System Parameters and set the number of the recording count appropriately.
3)    Please go to UCCX Serviceability from Navigation bar, go to tools --> Control Center and restart the Cisco Desktop Voip Monitor Service. This won’t affect server’s production.


Check if NIC CARD is or not supported


1)    Please run a NICQ test, doing this we will see if your current NIC CARD is or not supported for Monitoring and Recording
·         Go to agent’s computer
·         Go to C:\Program Files\Cisco\Desktop\Bin and look for NICQ.exe
·         Then make a normal call and select option 1. You will see if the NIC works or if there is a failure. If so that means that your NIC CARD is not supported.
As soon you have finished the test, on the same location (C:\Program Files\Cisco\Desktop\Bin) you will see a NICQ_output file, you can open it with notepad.
·         You should see something like this:

Photo.png
Photo_1.png
Please forward me NICQ_output file.

·         Certain NICs are configured by default to strip VLAN tags, which does not allow Desktop Monitoring to work. These NICs have published instructions for how to manually configure them to pass VLAN tags
·         Check NIC Binding
·         Check that QoS RSVP service is up and running (Windows XP)
·         From Local area connection --> configure --> you will see if the NIC has or not the “QoS Packet Tagging”, if it has the option available make sure that It is “ENABLED”.















Certain NICs are configured by default to strip VLAN tags, which does not allow Desktop Monitoring to work. These NICs have published instructions for how to manually configure them to pass VLAN tags

Regards,
MMM

Tuesday 22 January 2013

Mobility :- Remote Destination Profile CUCM



Configuring Single Number Reach on Cisco CUCM.

Cisco CUCM allows you to configure single number reach (also known as mobility) so that a call destined for your desk phone's extension can ring on a number of other devices such as your cellphone, blackberry, home phone, etc.  This feature also allows you to seamlessly transfer an active call from your cellphone to your desk phone and vice versa.  The basic CUCM installation will provide you with basic single number reach.

These are the procedures for configuring single number reach on the Cisco Unified Communications Manager.


A ) Enable Device Mobility Mode on Phone

1. Go to Device->Phone
2. Search for and edit the phone on which you wish to enable Mobility
3. Set Device Mobility Mode to On in Device Information
4. Save settings

B) Enable Mobility on End User

1. Go to User Management->End User
2. Search for and edit the end user for which you wish to enable Mobility
3. Check the box Enable Mobility under Mobility Information
4. Select user's primary phone in Primary User Device
5. Save settings


C) Create Remote Destination Profile

1. Go to Device->Device Settings->Remote Destination Profile
2. Click Add New
3. Enter a name for the profile
4. Select the UserID of the end user
5. Set the Device Pool you wish the profile to have
6. Set the Calling Search Space
7. Set the Rerouting Calling Search Space
8. Save Settings

D) Associate Remote Destination Profile with DN

1. Go to the Remote Destination Profile from the previous steps
2. Click Add a new DN in Association Information
3. Select the DN you wish to associate with this profile
4. Save Settings



5. Go back to End User profile and make sure the Remote Destination Profile is associated with user



E) Associate Remote Destination Profile with Remote Destinations

1. Edit the Remote Destination Profile from the previous steps
2. Click on Add a New Remote Destination
3. Enter a name for the remote destination
4. Enter the destination number as it would be dialed from your your deskphone
5. Select Mobile Phone
6. Select Enable Mobile Connect to select this device for mobile connect (this will allow you to transfer the call from your deskphone)
7. Save settings
8. Checkbox the Line Association box for the lines you want to associate this remote destination with
9. Save settings

Regards,
MMM