In this post, let’s see what the configuration parameters would be if we are using a CME router in the headquarters location and wanted to set up Unity voice mail support when the Unified Communication Managers are offline to continue voice mail operations.
As a review on how ports are created in CUCM, one would navigate to Voice Mail –> Voice Mail Ports in order to use this with Cisco Unity. In CUCM, you create voice mail port numbers and voice port name prefixes. This is accomplished using two distinct methods in CME.
Let’s illustrate a CME configuration which will add four voice mail ports for inbound and outbound, and one dedicated outbound port using the SCCP protocol to which will allow Unity to register it’s ports with CME.
First we create ephone-dn‘s to represent each individual port. To prevent confusion with other directory number configurations in CME, you should place a description or name for documentation purposes. Let’s see what the running configuration will look like for the ephone-dn’s created to represent each SCCP port into Unity. As a reminder, when you create the directory numbers ensure you set them up as dual-lines which will be needed for Unity to execute call consult transfers using its auto attendant feature.
TampaCME# show running-config ephone-dn 14 dual-line number 80030 name VoiceMail_1 preference 1 no hunt stop ephone-dn 15 dual-line number 80030 name VoiceMail_2 preference 2 no hunt stop ephone-dn 16 dual-line number 80030 name VoiceMail_3 preference 3 no hunt stop ephone-dn 17 dual-line number 80030 name VoiceMail_4 preference 4 hunt stop
Note: Secondary 9 may appear in your configuration under preference which indicates preference 9 for a secondary number configuration which is not configured in this running configuration
Below is a dedicated Cisco Unity Port configuration in CME. We purposely use a DN beginning with a number range which is not reachable by any IP Phone key pad.
Ephone-dn 18 number D4 preference 0 secondary 9 huntstop
Notice dual-line not required since it is used only for outdialing with Unity for MWI, TRAP, AMIS etc..
Next is to create the ephone’s which will represent each of the prefix names that will be configured in Cisco Unity to pass to CME for port registration. That part of the running configuration would appear as follows:
Ephone 10 vm-device-id TPAUM1-VI1 button 1:14 Ephone 11 vm-device-id TPAUM1-VI2 button 1:15 Ephone 12 vm-device-id TPAUM1-VI3 button 1:16 Ephone 13 vm-device-id TPAUM1-VI4 button 1:17 Ephone 14 vm-device-id TPAUM1-VI5 button 1:18
As an important point, keep the device prefix name less than 13 bytes. This issue is with Unity which will not allow you to add a prefix name greater than 13 bytes in the Unity Integration Telephony Manager or UTIM. So try to keep the prefix name as short as possible with a meaningful naming structure. In this example this is used for a CME configuration with a local Unity in Tampa Florida i.e. TPA which represents the Airport code value for the area.
The last piece for the CME configuration would be for MWI support. First we need to configure the IP Phone message button so when it is depressed on the Cisco IP Phone, it will route to one of the assigned voice mail ports configured in the hunt. This is done in the telephone service configuration as depicted below:
TampaCME#show running-config Telephony-Service Voice-mail 80030
The last component would be to add the actual MWI using the ephone-dn command as follows:
ephone-dn 20 number 7070 mwi on ! ephone-dn 21 number 7071 mwi off !
Notice we must carefully keep our MWI phone numbers from overlapping other numbers in CME to prevent interdigit timeout issues.
Next time we will look at the Unity setup to support this configuration and address some important CME troubleshooting commands in case Unity fails to register with the local CME.
Author: Joe Parlas