Table Of Contents
Setting Up a Cisco Unified CallManager Express SCCP Integration with Cisco Unity Connection
Integration Tasks
Requirements
Programming the Cisco Unified CallManager Express Phone System for Integrating with Cisco Unity Connection
Programming a Single Cisco Unified CallManager Express Router to Integrate with a Single Cisco Unity Connection Server
Programming Multiple Cisco Unified CallManager Express Routers to Integrate with a Single Cisco Unity Connection Server
Creating a New Integration with Cisco Unified CallManager Express
Setting Up a Cisco Unified CallManager Express SCCP Integration with Cisco Unity Connection
For detailed instructions for setting up a Cisco Unified CallManager Express Skinny Call Control Protocol (SCCP) integration with Cisco Unity Connection, see the following sections in this chapter:
•
Integration Tasks
•Requirements
•Programming the Cisco Unified CallManager Express Phone System for Integrating with Cisco Unity Connection
•Creating a New Integration with Cisco Unified CallManager Express
This document does not apply to the configuration in which Cisco Unity Connection is installed as Cisco Unified Communications Manager Business Edition (CMBE)—on the same server with Cisco Unified Communications Manager.
Cisco Unity Connection can integrate with Cisco Unified CM Express in SRST mode. For details, see the Integrating Cisco Unity Connection with Cisco Unified CME-as-SRST application note at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_installation_and_configuration_guides_list.html.
Integration Tasks
Before doing the following tasks to integrate Cisco Unity Connection with Cisco Unified CM Express by SCCP, confirm that the Cisco Unity Connection server is ready for the integration by completing the applicable tasks in the Installation Guide for Cisco Unity Connection.
1. Review the system and equipment requirements to confirm that all phone system and Cisco Unity Connection server requirements have been met. See the "Requirements" section.
2. Plan how the voice messaging ports will be used by Cisco Unity Connection. See Chapter 2, "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity Connection."
3. Program Cisco Unified CM Express. See the "Programming the Cisco Unified CallManager Express Phone System for Integrating with Cisco Unity Connection" section.
4. Create the integration. See the "Creating a New Integration with Cisco Unified CallManager Express" section.
5. Test the integration. See Chapter 4, "Testing the Integration."
6. If this integration is a second or subsequent integration, add the applicable new user templates for the new phone system. See Chapter 5, "Adding New User Template for Multiple Integrations."
Requirements
The Cisco Unified CM Express SCCP integration supports configurations of the following components:
Phone System
•Cisco Unified CM Express.
For details on compatible versions of Cisco Unified CM, refer to the SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.
•The following phones or combinations of phones for the Cisco Unified CM Express extensions:
–Only SCCP phones.
–Both SCCP phones and SIP phones.
For a list of supported Cisco IP phone models, refer to the Specifications document for the applicable version of Cisco Unified CM Express at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.
•A compatible Cisco IOS software version. Refer to the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/prod_installation_guide09186a00805acf50.html.
•Cisco Unified CM Express feature license.
•Cisco IP phone feature licenses, and Cisco licenses for other H.323-compliant devices or software (such as Cisco VirtualPhone and Microsoft NetMeeting clients) that will be connected to the network, as well as one license for each Cisco Unity Connection port.
•Analog phones connected to ATA. (For integration limitations with these phones, see Chapter 1, "Introduction.")
•A LAN connection in each location where you will plug the applicable phone into the network.
Cisco Unity Connection Server
•The applicable version of Cisco Unity Connection. For details on compatible versions of Cisco Unity Connection, refer to the SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.
•Cisco Unity Connection installed and ready for the integration, as described in the Installation Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_installation_guides_list.html.
•A license that enables the applicable number of voice messaging ports.
Programming the Cisco Unified CallManager Express Phone System for Integrating with Cisco Unity Connection
After the Cisco Unified CallManager Express router is installed, do the procedures in the applicable section depending on the number of Cisco Unified CM Express routers that you will integrate with the Cisco Unity Connection server:
•Single Cisco Unified CallManager Express router—see the "Programming a Single Cisco Unified CallManager Express Router to Integrate with a Single Cisco Unity Connection Server" section.
•Multiple Cisco Unified CallManager Express routers—see the "Programming Multiple Cisco Unified CallManager Express Routers to Integrate with a Single Cisco Unity Connection Server" section.
Programming a Single Cisco Unified CallManager Express Router to Integrate with a Single Cisco Unity Connection Server
Note Do the procedures in this section only if you are integrating a single Cisco Unified CM Express router with a single Cisco Unity Connection server. If you are integrating multiple Cisco Unified CM Express routers, see the "Programming Multiple Cisco Unified CallManager Express Routers to Integrate with a Single Cisco Unity Connection Server" section.
To Configure the Message Button Access to Cisco Unity Connection
This procedure configures the Message button on Cisco IP phones to dial the Cisco Unity Connection pilot number when pressed.
Step 1 On the Cisco Unified CM Express router, go into the telephony-service configuration mode by entering the following command:
telephony-service
Step 2 Enter the following command:
voicemail <Cisco Unity Connection pilot number>
Step 3 To exit the telephony-service configuration mode, enter the following command:
exit
The following is an example of the configuration:
To Configure the Router for Cisco Unity Connection
Step 1 Go into the ephone-dn configuration mode and configure the directory number tag for the Cisco IP phone lines by entering the applicable command:
•For ephone-dns that will be used by ports that are dedicated for leaving and retrieving voice messages, enter the following command:
ephone-dn <DN tag> dual-line
•For ephone-dns that will be used only to dial out, enter the following command:
ephone-dn <DN tag>
Step 2 To set the extension number for the voice messaging port, enter the following command:
number <Voice messaging port extension>
Note The voice message port extension must be the Cisco Unity Connection pilot number (configured by the "voicemail" command in the preceding procedure) for all ports dedicated for leaving and retrieving voice messages. Use an extension that cannot be dialed for all ports that are used to dial out by Cisco Unity Connection (for example, use "A01").
Step 3 To set the display name for the port (for example, "Voice Messaging System" or "Dial Out Only"), enter the following command:
name <Display name of voice messaging port>
Step 4 To set the device name for the port (for example, "CUC-VI1" or "CUC-VI1-Dialout"), enter the following command:
description <Device name of voice messaging port>
Step 5 To reserve the second ephone-dn channel for supervised transfers, enter the following command:
huntstop channel
Step 6 To set the dial-peer preference for the extension, enter the following command:
preference <Preference order>
Step 7 Enter the applicable command:
•To disable huntstop, enter the following command:
no huntstop
•To enable huntstop, enter the following command:
huntstop
Step 8 Repeat Step 1 through Step 7 for all remaining ports.
Note The number of voice messaging ports set up to connect to Cisco Unity Connection must be the same as the number of directory number tags for the Cisco IP phone lines set up by the ephone-dn configuration mode.
Step 9 To exit the ephone-dn configuration mode, enter the following command:
exit
The following is an example of the configuration:
name "Voice Messaging System"
name "Voice Messaging System"
name "Voice Messaging System"
description "CUC-Dialout1"
In this example, there are four ephone-dns configured to provide four voice messaging ports. Three of the ephone-dns are configured with the same extension number to provide ports dedicated for leaving and retrieving voice messages. These three ephone-dns are also configured with two channels each (the second channel is reserved for supervised transfers). The fourth ephone-dn is provided for use as an dial-out port. The first three ephone-dns are configured with the same extension number (4001), using preferences 1, 2, and 3 to create a hunt group. If the first port is busy, the call goes to the second port, and so on. Port 4 is configured with the extension number A01 and is used to dial out by Cisco Unity Connection (for example, to set MWIs). Separate ports are required for answering calls and dialing out in order to prevent call-collision problems between incoming calls placed by Cisco Unified CM Express to Cisco Unity Connection, and outgoing calls that Cisco Unity Connection places in the opposite direction.
To Associate the Voice Messaging Port
To associate the actual voice messaging port (vm-device-id) to the phone number, associate the Cisco IP phone with the voice messaging port.
The vm-device-id name uses the following format:
<Cisco Unity Connection device name prefix><Port number>
The vm-device-id name must match the Cisco Unity Connection voice messaging port name that you will use to identify the port in Cisco Unity Connection Administration when you create the integration:
•The Cisco Unity Connection device name prefix part (for example, CUC-VI) must match the Device Name Prefix field on the Telephony Integrations > Port Group > Port Group Basics page of Cisco Unity Connection Administration.
•The port number part (for example, "1") must match the number part of the Cisco Unity Connection Administration voice messaging port name used to identify the port on the Telephony Integrations > Port > Port Basics page of Cisco Unity Connection Administration.
To associate a voice messaging port to the Cisco Unified CM Express router, do the following steps, beginning in ephone configuration mode.
Step 1 Go into the ephone configuration mode and register the Cisco IP phones by entering the following command:
ephone <DN tag>
Step 2 Define the voice messaging port name, by entering the following command:
vm-device-id <Cisco Unity Connection device name prefix><Port number>
For example, if the Cisco Unity Connection device name prefix is CUC-VI, enter CUC-VI1 for the first port, CUC-VI2 for the second port, and so on.
Caution The vm-device-id name used by Cisco Unified CM Express must be the same as the voice messaging port name used by Cisco Unity Connection. Otherwise, the integration will not work.
Step 3 Assign buttons to the Cisco IP phone directory numbers created in the "To Configure the Router for Cisco Unity Connection" procedure by entering the following command:
button <Button number>:<DN tag>
For example, you can use the values 1:1, 2:4, or 3:14. In this example, button 1 corresponds to directory number 1 (ephone-dn 1), button 2 corresponds to directory number 4, and button 3 corresponds to directory number 14. The buttons correspond to the phone lines on the Cisco IP phone.
Step 4 Repeat Step 1 through Step 3 for all remaining voice messaging port names.
Note The number of voice messaging port names configured with the vm-device-id command must be the same as the number of Cisco IP phones registered by the ephone configuration mode.
Step 5 To exit the ephone configuration mode, enter the following command:
exit
Following is an example of the configuration. In this example, the vm-device-id command is used within the ephone configuration in place of the mac-address parameter that is used for configuring a regular Cisco IP phone.
To Configure a Directory Number for MWI Notification
MWI configuration on the Cisco Unified CM Express is performed by dedicating Cisco IP phone directory numbers (ephone-DNs) to process MWI status notification calls originating from Cisco Unity Connection. You must allocate a minimum of one MWI processing ephone-dn for each MWI ephone-dn voice messaging port. The MWI processing ephone-dn extensions are configured to match the MWI extensions configured on Cisco Unity Connection.
Step 1 Go into the ephone-dn configuration mode and configure the directory numbers for the Cisco IP phone lines by entering the following command:
ephone-dn <DN tag>
Step 2 Configure two valid directory numbers for the Cisco IP phone to be used for MWIs—the first number will turn MWIs on, and the second number will turn MWIs off—by entering the following command:
number <MWI on number> secondary <MWI off number>
Note The MWI on and off numbers must match the settings of the MWI On Extension and MWI Off Extension fields you enter in Cisco Unity Connection Administration when you create the integration on Cisco Unity Connection.
Step 3 Configure these two directory numbers to be used for setting MWIs by entering the following command:
mwi on-off
Step 4 To exit the ephone-dn configuration mode, enter the following command:
exit
Following is an example of the configuration.
number 8000 secondary 8001
In this example, Cisco Unity Connection calls extensions 8000 and 8001 to turn MWIs on and off. The DN triggers an MWI ON event when 8000 is called, and an MWI OFF event when 8001 is called.
For extensions associated with analog telephone adaptors (ATAs), the MWI is a lit function button on the ATA and a stutter dial tone on the connected analog phone.
Note After completing the procedures in this section, continue to the "Creating a New Integration with Cisco Unified CallManager Express" section.
Programming Multiple Cisco Unified CallManager Express Routers to Integrate with a Single Cisco Unity Connection Server
A single, centralized Cisco Unity Connection server can be used by multiple Cisco Unified CM Express routers. This configuration requires that one Cisco Unified CM Express router be on the same LAN as the Cisco Unity Connection server, and that this Cisco Unified CM Express router register all Cisco Unity Connection voice messaging ports. This Cisco Unified CM Express router (the SIP MWI server) is a proxy server that relays SIP MWI messages between the Cisco Unity Connection server and all other Cisco Unified CM Express routers (the SIP MWI clients). Note that Cisco Unity Connection voice messaging ports register with only the SIP MWI server (the Cisco Unified CM Express router that is on the same LAN as the Cisco Unity Connection server), not with the SIP MWI clients.
Do the procedures in this section only if you are integrating multiple Cisco Unified CM Express routers with a single Cisco Unity Connection server.
To Configure the Message Button Access to Cisco Unity Connection
Step 1 On the Cisco Unified CM Express router, go into the telephony-service configuration mode by entering the following command:
telephony-service
Step 2 Enter the following command:
voicemail <Cisco Unity Connection pilot number>
Step 3 To exit the telephony-service configuration mode, enter the following command:
exit
The following is an example of the configuration:
To Configure the Router for Cisco Unity Connection
Step 1 Go into the ephone-dn configuration mode and configure the directory number tag for the Cisco IP phone lines by entering the applicable command:
•For ephone-dns that will be used by ports that are dedicated for leaving and retrieving voice messages, enter the following command:
ephone-dn <DN tag> dual-line
•For ephone-dns that will be used only to dial out, enter the following command:
ephone-dn <DN tag>
Step 2 To set the extension number for the voice messaging port, enter the following command:
number <Voice messaging port extension>
Note The voice message port extension must be the Cisco Unity Connection pilot number (configured by the "voicemail" command in the preceding procedure) for all ports dedicated for leaving and retrieving voice messages. Use an extension that cannot be dialed for all ports that are used to dial out by Cisco Unity Connection (for example, use "A01").
Step 3 To set the display name for the port (for example, "Voice Messaging System" or "Dial Out Only"), enter the following command:
name <Display name of voice messaging port>
Step 4 To set the device name for the port (for example, "CUC-VI1" or "CUC-Dialout1"), enter the following command:
description <Device name of voice messaging port>
Step 5 To reserve the second ephone-dn channel for supervised transfers, enter the following command:
huntstop channel
Step 6 To set the dial-peer preference for the extension, enter the following command:
preference <Preference order>
Step 7 Enter the applicable command:
•To disable huntstop, enter the following command:
no huntstop
•To enable huntstop, enter the following command:
huntstop
Step 8 Repeat Step 1 through Step 7 for all remaining ports.
Note The number of voice messaging ports set up to connect to Cisco Unity Connection must be the same as the number of directory number tags for the Cisco IP phone lines set up by the ephone-dn configuration mode.
Step 9 To exit the ephone-dn configuration mode, enter the following command:
exit
The following is an example of the configuration:
name "Voice Messaging System"
name "Voice Messaging System"
name "Voice Messaging System"
description "CUC-Dialout1"
In this example, there are four ephone-dns configured to provide four voice messaging ports. Three of the ephone-dns are configured with the same extension number to provide ports dedicated for leaving and retrieving voice messages. These three ephone-dns are also configured with two channels each (the second channel is reserved for supervised transfers). The fourth ephone-dn is provided for use as a dial-out port. The first three ephone-dns are configured with the same extension number (4001), using preferences 1, 2, and 3 to create a hunt group. If the first port is busy, the call goes to the second port, and so on. Port 4 is configured with the extension number A01 and is used to dial out by Cisco Unity Connection (for example, to set MWIs). Separate ports are required for answering calls and dialing out in order to prevent call-collision problems between incoming calls placed by Cisco Unified CM Express to Cisco Unity Connection, and outgoing calls that Cisco Unity Connection places in the opposite direction.
To Associate the Voice Messaging Port
To associate the actual voice messaging port (vm-device-id) to the phone number, associate the Cisco IP phone with the voice messaging port.
The vm-device-id name uses the following format:
<Cisco Unity Connection device name prefix><Port number>
The vm-device-id name must match the Cisco Unity Connection voice messaging port name you will use to identify the port in Cisco Unity Connection Administration when you create the integration:
•The Cisco Unity Connection device name prefix part (for example, CUC-VI) must match the Device Name Prefix field on the Telephony Integrations > Port Group page.
•The port number part (for example, "1") must match the number part of the Cisco Unity Connection voice messaging port name used to identify the port on the Telephony Integrations > Port page.
To associate a voice mail device with the Cisco Unified CM Express router, do the following steps, beginning in ephone configuration mode.
Step 1 Go into the ephone configuration mode and register the Cisco IP phones by entering the following command:
ephone <DN tag>
Step 2 Define the voice messaging port name, by entering the following command:
vm-device-id <Cisco Unity Connection device name prefix><Port number>
For example, if the Cisco Unity Connection device name prefix is CUC-VI, enter CUC-VI1 for the first port, CUC-VI2 for the second port, and so on.
Caution The vm-device-id name used by Cisco Unified CM Express must be the same as the voice messaging port name used by Cisco Unity Connection. Otherwise, the integration will not work.
Step 3 Assign buttons to the Cisco IP phone directory numbers created in the "To Configure the Router for Cisco Unity Connection" procedure by entering the following command:
button <Button number>:<DN tag>
For example, you can use the values 1:1, 2:4, or 3:14. In this example, button 1 corresponds to directory number 1 (ephone-dn 1), button 2 corresponds to directory number 4, and button 3 corresponds to directory number 14. The buttons correspond to the phone lines on the Cisco IP phone.
Step 4 Repeat Step 1 through Step 3 for all remaining voice messaging port names.
Note The number of voice messaging port names configured with the vm-device-id command must be the same as the number of Cisco IP phones registered by the ephone configuration mode.
Step 5 To exit the ephone configuration mode, enter the following command:
exit
Following is an example of the configuration. In this example, the vm-device-id command is used within the ephone configuration in place of the mac-address parameter that is used for configuring a regular Cisco IP phone.
Do the following procedure.
To Configure the SIP MWI Server
Step 1 Go into the SIP user-agent configuration mode by entering the following command:
sip-ua
Step 2 Configure the IP address (or DNS name) and port for the SIP MWI server by entering the following command:
mwi-server {ipv4:<MWI server IP address> | dns:<MWI server host-name} [expires <Seconds>]
[port <Port number>] [transport {tcp | udp}] [unsolicited]
The SIP MWI server must be in the same LAN as Cisco Unity Connection. This IP address is used in conjunction with the "mwi sip" command in ephone-dn configuration mode to subscribe individual ephone-dn extension numbers to the MWI server notification list. The SIP MWI client runs TCP by default.
This command uses the following keywords:
•ipv4:—Sets the IP address of the SIP MWI server.
•dns:—Sets the DNS name of the SIP MWI server.
•expires—(optional) Subscription expiration time, in seconds. The range is 1 to 999999. The default is 3600.
•transport tcp—The default setting.
•transport udp—Allows you to integrate with the SIP MWI client.
•port—Used to specify the TCP port for the SIP MWI server. The default SIP port number is 5060.
•unsolicited—Allows sending SIP NOTIFY for MWIs without the need to send a SUBSCRIBE from the Cisco Unified CM Express router.
Step 3 To exit the SIP user-agent configuration mode, enter the following command:
exit
Step 4 Go into the telephony-service configuration mode by entering the following command:
telephony-service
Step 5 If you want to keep the default registration with an extension number, continue to Step 6. If you want to register with an E.164 10-digit number, enter the following command:
mwi reg-e164
Step 6 To exit the telephony-service configuration mode, enter the following command:
exit
Step 7 Continue to the next procedure.
To Configure MWIs for Each Directory Number
Step 1 Go into the ephone-dn configuration mode and configure the directory numbers for the Cisco IP phone lines by entering the following command:
ephone-dn <DN tag>
Step 2 Configure a valid directory number for the Cisco IP phone that receives the MWI notification by entering the following command:
number <Directory number>
Step 3 Configure the device name of MWI for the directory number that receives MWI notification by entering the following command:
name MWI
Step 4 Subscribe the extension in a Cisco Unified CM Express to receive MWIs from a SIP MWI server by entering the following command:
mwi sip
This command integrates the Cisco Unified CM Express with the MWI service based on SIP protocol.
Note The "mwi sip-server" command under telephony-service configuration mode or the "mwi-server" command under SIP user-agent configuration mode must be set before enabling the "mwi sip" command in ephone configuration mode.
Step 5 To exit the ephone-dn configuration mode, enter the following command:
exit
To Configure a Directory Number for MWI Notification
MWI configuration on the Cisco Unified CM Express is performed by dedicating Cisco IP phone directory numbers (ephone-DNs) to process MWI status notification calls originating from Cisco Unity Connection. You must allocate a minimum of one MWI processing ephone-dn for each MWI ephone-dn voice messaging port. The MWI processing ephone-dn extensions are configured to match the MWI extensions configured on Cisco Unity Connection.
Step 1 Go into the ephone-dn configuration mode and configure the directory numbers for the Cisco IP phone lines by entering the following command:
ephone-dn <DN tag>
Step 2 Configure two valid directory numbers for the Cisco IP phone to be used for MWIs—the first number will turn MWIs on, and the second number will turn MWIs off—by entering the following command:
number <MWI on number> secondary <MWI off number>
Note The MWI on and off numbers must match the settings of the MWI On Extension and MWI Off Extension fields you enter in Cisco Unity Connection Administration when you create the integration on Cisco Unity Connection.
Step 3 Configure these two directory numbers to be used for setting MWIs by entering the following command:
mwi on-off
Step 4 To exit the ephone-dn configuration mode, enter the following command:
exit
Following is an example of the configuration.
number 8000 secondary 8001
In this example, Cisco Unity Connection calls extensions 8000 and 8001 to turn MWIs on and off. The DN triggers an MWI ON event when 8000 is called, and an MWI OFF event when 8001 is called.
To Configure MWI Relay
MWI relay is required when Cisco Unity Connection is integrated with multiple Cisco Unified CM Express routers. The Cisco Unified CM Express routers use the SIP subscriber and notifier mechanism for MWI relay. The Cisco Unified CM Express router that is the SIP MWI relay server acts as the SIP notifier. The other Cisco Unified CM Express routers (the SIP MWI clients) act as the SIP subscribers.
Step 1 Go into the telephony-service configuration mode by entering the following command:
telephony-service
Step 2 Enable the Cisco Unified CM Express router to relay MWI information to Cisco IP phones on other Cisco Unified CM Express routers by entering the following command:
mwi relay
Step 3 To exit the telephony-service configuration mode, enter the following command:
exit
Step 4 Go into the SIP user-agent configuration mode by entering the following command:
sip-ua
Step 5 Configure the IP address (or DNS name) and port for the SIP MWI server by entering the following command:
mwi-server {ipv4:<MWI server IP address> | dns:<MWI server host-name} [expires <Seconds>]
[port <Port number>] [transport {tcp | udp}] [unsolicited]
The SIP MWI server must be in the same LAN as Cisco Unity Connection. This IP address is used in conjunction with the "mwi sip" command in ephone-dn configuration mode to subscribe individual ephone-dn extension numbers to the MWI server notification list. The SIP MWI client runs TCP by default.
This command uses the following keywords:
•ipv4:—Sets the IP address of the SIP MWI server.
•dns:—Sets the DNS name of the SIP MWI server.
•expires—(optional) Subscription expiration time, in seconds. The range is 1 to 999999. The default is 3600.
•transport tcp—The default setting.
•transport udp—Allows you to integrate with the SIP MWI client.
•port—Used to specify the TCP port for the SIP MWI server. The default SIP port number is 5060.
•unsolicited—Allows sending SIP NOTIFY for MWIs without the need to send a SUBSCRIBE from the Cisco Unified CM Express router.
Step 6 To exit the SIP user-agent configuration mode, enter the following command:
exit
Step 7 Go into the telephony-service configuration mode by entering the following command:
telephony-service
Step 8 If you want to keep the default registration with an extension number, continue to Step 9. If you want to register with an E.164 10-digit number, enter the following command:
mwi reg-e164
Step 9 To exit the telephony-service configuration mode, enter the following command:
exit
To Enable DTMF Relay
In certain situations, DTMF digits are not recognized when processed through VoIP dial-peer gateways. To avoid this problem, certain gateways must be configured to enable DTMF relay. The DTMF relay feature is available in Cisco IOS software version 12.0(5) and later.
Cisco IOS software-based gateways that use H.245 out-of-band signaling (but not the Cisco Unified CM Express routers with which Cisco Unity Connection is integrated) must be configured to enable DTMF relay.
The Catalyst 6000 T1/PRI and FXS gateways enable DTMF relay by default and do not need additional configuration to enable this feature.
Step 1 On a VoIP dial-peer that points to a Cisco Unified CM Express router integrated with Cisco Unity Connection (the dial-peer must have a session target of the Cisco Unified CM Express router, not Cisco Unity Connection), enter the following command:
dtmf-relay h245-signal
Step 2 Create a destination pattern that matches the Cisco Unified CM Express voice mail port numbers. For example, if the system has voice mail ports 1001 through 1016, enter the dial-peer destination pattern 10xx.
Step 3 Repeat Step 1 and Step 2 for all remaining VoIP dial-peers that point to Cisco Unified CM Express routers integrated with Cisco Unity Connection.
Creating a New Integration with Cisco Unified CallManager Express
After ensuring that Cisco Unified CallManager Express and Cisco Unity Connection are ready for the integration, do the following procedure to set up the integration and to enter the port settings.
To Create an Integration
Step 1 Log on to Cisco Unity Connection Administration.
Step 2 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Phone System.
Step 3 On the Search Phone Systems page, on the Phone System menu, click New Phone System. The Phone System Integration Wizard appears.
Step 4 On the Select Phone System Manufacturer page, in the Manufacturer field, click Cisco Systems and click Next.
Step 5 On the Select Phone System Model page, in the Model field, click Cisco Unified Communications Manager and click Next.
Step 6 On the Set Up Phone System page, in the Phone System Name field, accept the default name or enter the descriptive name that you want, and click Next.
Step 7 On the Select Port Group Template page, in the Port Group Template field, click SCCP - Skinny Call Control Protocol and click Next.
Step 8 On the Set Up Port Group page, enter the following settings and click Next.
Table 3-1 Settings for the Set Up Port Group Page
Field
|
Setting
|
Port Group Name
|
Enter a descriptive name for the port group. You can accept the default name or enter the name that you want.
|
Device Name Prefix
|
Enter the prefix that Cisco Unified CM Express uses in the vm-device-id name before the port number. This prefix must match the prefix used by Cisco Unified CM Express.
|
MWI On Extension
|
Enter the MWI on directory number that you specified in the ephone-dn configuration mode of the Cisco Unified CM Express router.
|
MWI Off Extension
|
Enter the MWI off directory number that you specified in the ephone-dn configuration mode of the Cisco Unified CM Express router.
|
Security Mode
|
Click Non-secure.
(Cisco Unified Communications Manager authentication and encryption are not available for Cisco Unified CM Express.)
|
Number of Ports
|
Enter the number of voice messaging ports that you want to create in this port group.
|
IP Address or Host Name
|
Enter the IP address (or host name) of the Cisco Unified CM Express router that you are integrating with Cisco Unity Connection.
|
Test Address
|
Click this button to test the IP address that you entered. The results of the test appear in the field to the right of the button.
Note Even though the integration is successful, the test may fail on networks where the "ping" command is disabled or ignored, or when the Cisco Unified CM Express router is not running.
|
Port
|
Enter the TCP port of the Cisco Unified CM Express router that you are integrating with Cisco Unity Connection. We recommend that you use the default setting.
|
TLS Port
|
Enter the TLS port of the Cisco Unified CM Express router that you are integrating with Cisco Unity Connection. We recommend that you use the default setting.
|
Server Type
|
Click Cisco Unified Communications Manager Express.
|
Step 9 On the Confirm Phone System Settings page, confirm the settings that you have entered and click Finish.
Step 10 On the Phone System Creation Summary page, click Close.
Step 11 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Port Group.
Step 12 On the Search Port Groups page, click the display name of the port group that you created for the Cisco Unified CM Express integration in Step 9.
Note By default, the display name for a port group is composed of the phone system display name followed by an incrementing number.
Step 13 On the Port Group Basics page, on the Edit menu, click Advanced Settings.
Step 14 On the Edit Advanced Settings page, in the Delay Before Opening Greeting field, enter 1000 and click Save.
Step 15 In Cisco Unity Connection Administration, expand Telephony Integrations, then click Port.
Step 16 On the Search Ports page, click the display name of the first voice messaging port that you created for the Cisco Unified CM Express integration.
Note By default, the display names for the voice messaging ports are composed of the port group display name followed by incrementing numbers.
Step 17 On the Port Basics page, set the voice messaging port settings as applicable. The fields in the following table are the ones that you can change.
Table 3-2 Settings for the Voice Messaging Ports
Field
|
Considerations
|
Enabled
|
Check this check box to enable the port. The port is enabled during normal operation.
Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from users.
|
Perform Message Notification
|
Check this check box to designate the port for notifying users of messages. Assign Perform Message Notification to the least busy ports.
|
Send MWI Requests
|
Check this check box to designate the port for turning MWIs on and off. Assign Send MWI Requests to the least busy ports.
|
Allow TRAP Connections
|
Check this check box so that users can use the port for recording and playback through the phone in Cisco Unity Connection web applications. Assign Allow TRAP Connections to the least busy ports.
|
Outgoing Hunt Order
|
Enter the priority order in which Cisco Unity Connection will use the ports when dialing out (for example, if the Perform Message Notification, Send MWI Requests, or Allow TRAP Connections check box is checked). The highest numbers are used first. However, when multiple ports have the same Outgoing Hunt Order number, Cisco Unity Connection will use the port that has been idle the longest.
|
Security Mode
|
Click Non-secure.
(Cisco Unified Communications Manager authentication and encryption are not available for Cisco Unified CM Express.)
|
Step 18 Click Save.
Step 19 Click Next.
Step 20 Repeat Step 17 through Step 19 for all remaining voice messaging ports for the phone system.
Step 21 If another phone system integration exists, in Cisco Unity Connection Administration, expand Telephony Integrations, then click Trunk. Otherwise, skip to Step 25.
Step 22 On the Search Phone System Trunks page, on the Phone System Trunk menu, click New Phone System Trunk.
Step 23 On the New Phone System Trunk page, enter the following settings for the phone system trunk and click Save.
Table 3-3 Settings for the Phone System Trunk
Field
|
Setting
|
From Phone System
|
Click the display name of the phone system that you are creating a trunk for.
|
To Phone System
|
Click the display name of the previously existing phone system that the trunk will connect to.
|
Trunk Access Code
|
Enter the extra digits that Cisco Unity Connection must dial to transfer calls through the gateway to extensions on the previously existing phone system.
|
Step 24 Repeat Step 22 and Step 23 for all remaining phone system trunks that you want to create.
Step 25 If prompted to restart the Connection Conversation Manager service, do the following substeps. Otherwise, continue to Step 26.
a. In the Navigation drop-down list, click Cisco Unity Connection Serviceability and click Go.
b. On the Cisco Unity Connection Serviceability page, on the Tools menu, click Control Center - Feature Services.
c. On the Control Center - Feature Services page, in the Server drop-down list, click the name of the Cisco Unity Connection server and click Go.
d. Under Cisco Unity Connection Services, click Connection Conversation Manager.
e. At the top of the page, click Restart.
f. When prompted to confirm restarting the service, click Yes.
g. In the Navigation drop-down list, click Cisco Unity Connection Administration and click Go.
h. In Cisco Unity Connection Administration, expand Telephony Integrations, then click Phone System.
Step 26 In the Related Links drop-down list, click Check Telephony Configuration and click Go to confirm the phone system integration settings.
If the test is not successful, the Task Execution Results displays one or more messages with troubleshooting steps. After correcting the problems, test the connection again.
Step 27 In the Task Execution Results window, click Close.
Step 28 Log off Cisco Unity Connection Administration.
Feedback
