Table Of Contents
Setting Up a Cisco Unified CallManager 3.3 SCCP Integration with Cisco Unity
Task List to Create the Integration by SCCP
Requirements
Programming the Cisco Unified CallManager Phone System for Integrating with Cisco Unity
Creating a New Integration with Cisco Unified CallManager
Creating an Integration with an Additional Cisco Unified CallManager Cluster
Setting Up a Cisco Unified CallManager 3.3 SCCP Integration with Cisco Unity
For detailed instructions for setting up a Cisco Unified CallManager 3.3 SCCP integration with Cisco Unity, see the following sections in this chapter:
•
Task List to Create the Integration by SCCP
•Requirements
•Programming the Cisco Unified CallManager Phone System for Integrating with Cisco Unity
•Creating a New Integration with Cisco Unified CallManager
Note Cisco Unified CallManager authentication and encryption of voice messaging ports are not available for Cisco Unified CallManager 3.3.
If you are configuring MWI relay across trunks in a distributed phone system, you must refer to the Cisco Unified CallManager documentation for requirements and instructions. Configuring MWI relay across trunks does not involve Cisco Unity settings.
Task List to Create the Integration by SCCP
Before doing the following tasks to integrate Cisco Unity with Cisco Unified CallManager by Skinny Call Control Protocol (SCCP), confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the applicable Cisco Unity installation guide. If you are installing a new Cisco Unity server by using the applicable Cisco Unity installation guide, you may have already completed some of the following tasks.
1. Review the system and equipment requirements to confirm that all phone system and Cisco Unity server requirements have been met. See the "Requirements" section.
2. Plan how the voice messaging ports will be used by Cisco Unity. See Chapter 2, "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity."
3. Program Cisco Unified CallManager. See the "Programming the Cisco Unified CallManager Phone System for Integrating with Cisco Unity" section.
4. Create the integration. See the "Creating a New Integration with Cisco Unified CallManager" section.
5. Test the integration. See Chapter 11, "Testing the Integration."
6. If you have a secondary server for Cisco Unity failover, integrate the secondary server. See Chapter 12, "Integrating a Secondary Server for Cisco Unity Failover with a Cisco Unified Communications Manager Integration."
Requirements
The Cisco Unified CallManager SCCP integration supports configurations of the following components:
Phone System
•Cisco Unified CallManager 3.3(x).
•SCCP phones for the Cisco Unified CallManager extensions.
•A LAN connection in each location where you will plug an IP phone into the network.
•For multiple Cisco Unified CallManager clusters, the capability for users to dial an extension on another Cisco Unified CallManager cluster without having to dial a trunk access code or prefix.
Cisco Unity Server
•The applicable version of Cisco Unity. For details on compatible versions of Cisco Unity, refer to the SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.
•Cisco Unity installed and ready for the integration, as described in the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
•The applicable Cisco Unity-CM TSP, installed. For details on compatible versions of the TSP, refer to the SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.
•A license that enables the applicable number of voice messaging ports.
Centralized Voice Messaging
Cisco Unity supports centralized voice messaging by supporting various inter-phone system networking protocols including, for example, proprietary protocols such as Avaya DCS, Nortel MCDN, or Siemens CorNet, and standards-based protocols such as QSIG or DPNSS. For details, see the "Centralized Voice Messaging" section in the "Integrating Cisco Unity with the Phone System" chapter of the Design Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/design/guide/5xcudgx.html.
Programming the Cisco Unified CallManager Phone System for Integrating with Cisco Unity
After Cisco Unified CallManager software is installed, do the procedures in this section to program Cisco Unified CallManager to work with Cisco Unity:
•When configuring voice mail ports for a Cisco Unity server without failover, or the primary server with failover, do all the procedures in this section.
•When configuring voice mail ports for a secondary server with failover, do only the "To Add Voice Mail Ports to Cisco Unified CallManager" procedure.
To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports
Step 1 In Cisco Unified CallManager Administration, click Route Plan > Partition.
Step 2 Click Add a New Partition.
Step 3 Enter the name and description you want for the partition that will contain all voice mail port directory numbers except for the first voice mail port, which will be assigned the voice mail pilot number. For example, enter "VMRestrictedPT, Partition for voice mail port directory numbers." For a diagram of the configuration, see Figure 3-1. For a diagram of the configuration with Cisco Unity failover, see Figure 3-2.
Step 4 Click Insert.
Step 5 Click Add a New Partition.
Step 6 Enter the name and description you want for the partition that will contain the directory number of the first voice mail port, which will be assigned the voice mail pilot number. For example, enter "VMPilotNumberPT, Partition for the voice mail pilot number." For a diagram of the configuration, see Figure 3-1. For a diagram of the configuration with Cisco Unity failover, see Figure 3-2.
Step 7 Click Insert.
Step 8 Click Route Plan > Calling Search Space.
Step 9 Click Add a New Calling Search Space.
Step 10 In the Calling Search space Name field, enter a name for the calling search space that will include the partition created in Step 2 through Step 4. For example, enter "VMRestrictedCSS."
Step 11 Optionally, in the Description field, enter a description of the calling search space. For example, enter "Voice mail port directory numbers."
Step 12 In the Available Partitions field, double-click the name of the partition created in Step 2 through Step 4. For example, double-click "VMRestrictedPT." For a diagram of the configuration, see Figure 3-1. For a diagram of the configuration with Cisco Unity failover, see Figure 3-2.
The name of the partition appears in the Selected Partitions field.
Step 13 Click Insert.
Step 14 Click Back to Find/List Calling Search Spaces.
Step 15 Click the name of the calling search space that is used by subscriber phones.
Step 16 In the Available Partitions field, double-click the name of the partition created in Step 5 through Step 7. For example, double-click "VMPilotNumberPT." For a diagram of the configuration, see Figure 3-1. For a diagram of the configuration with Cisco Unity failover, see Figure 3-2.
Caution If the partition that contains the voice mail pilot number is not in the calling search space that is used by subscriber phones, the phones will not be able to dial the Cisco Unity server.
Step 17 Click Update.
Step 18 Repeat Step 15 through Step 17 for each remaining calling search space that needs to access Cisco Unity.
Figure 3-1 Partitions for Voice Mail Port Directory Numbers
Figure 3-2 Partitions for Voice Mail Port Directory Numbers with Cisco Unity Failover
To Add a Device Pool for the Voice Mail Ports
Step 1 In Cisco Unified CallManager Administration, click System > Device Pool.
Step 2 On the Find and List Device Pools page, click Add a New Device Pool.
Step 3 On the Device Pool Configuration page, enter the following device pool settings.
Table 3-1 Settings for the Device Pool Configuration Page
Field
|
Setting
|
Device Pool Name
|
Enter Cisco Unity Voice Mail Ports or other description for this device pool.
|
Cisco CallManager Group
|
Click the Cisco CallManager group to assign to the voice mail ports in this device pool.
|
Date/Time Group
|
Click the date/time group to assign to the voice mail ports in this device pool.
|
Region
|
Click the Cisco Unified CallManager region to assign to the voice mail ports in this device pool.
|
Softkey Template
|
Click the softkey template to assign to the voice mail port in this device pool.
|
SRST Reference
|
If applicable, click the survivable remote site telephony (SRST) reference to assign to the voice mail ports in this device pool.
|
Network Hold MOH Source
|
Click None.
|
User Hold MOH Audio Source
|
Click None.
|
Step 4 Click Insert.
In the following procedure, add a voice mail port to Cisco Unified CallManager for each voice mail port that you will connect to Cisco Unity.
To Add Voice Mail Ports to Cisco Unified CallManager
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port Wizard.
Step 2 Click Create a New Cisco Voice Mail Server and Add Ports to It, and click Next.
Step 3 The name of the voice mail server appears. We recommend that you accept the default name for the voice mail server. If you must use a different name, however, the name must have no more than nine characters.
Caution If Cisco Unity is configured for failover, the name of the voice mail server and voice mail ports that serve the secondary server must be different from the name of the voice mail server and voice mail ports that serve the primary server. Otherwise, the secondary server cannot function correctly.
Step 4 Click Next.
Step 5 Enter the number of voice mail ports that you want to add (which must not be more voice mail ports than the Cisco Unity license enables), then click Next.
If you will integrate Cisco Unity with multiple clusters of Cisco Unified CallManager, the number you enter here cannot bring the total number of ports on all clusters integrated with Cisco Unity to more than the number of ports enabled by the Cisco Unity license.
Step 6 Enter the following voice mail device settings.
Table 3-2 Settings for the Voice Mail Devices
Field
|
Setting
|
Description
|
Enter Cisco Voice Mail Port or another description for the voice mail device.
|
Device Pool
|
Click the name of the device pool you created for the voice mail ports. For example, click Cisco Unity Voice Mail Ports.
|
Calling Search Space
|
Click the name of a calling search space that allows calls to the subscriber phones and any required network devices.
This calling search space must include partitions that contain all devices Cisco Unity needs to access (for example, during call transfers, message notifications, and MWI activations).
|
Location
|
Accept the default of None.
|
Step 7 Click Next.
Step 8 Enter the following voice mail directory number settings.
Table 3-3 Settings for the Voice Mail Directory Numbers
Field
|
Setting
|
Pilot Number
|
Enter the pilot number for the voice mail ports.
The pilot number is the extension number of the first voice mail port and is the number subscribers enter to listen to their voice messages.
If Cisco Unity is configured for failover and you are adding voice mail ports for the secondary server, the pilot number is the extension number of the first voice mail port on the secondary server, but it is not the number subscribers enter to listen to their voice messages.
|
Partition
|
Click the name of the partition that you set up for all voice mail port directory numbers except the first voice mail port. For example, click "VMRestrictedPT."
|
Calling Search Space
|
Click the name of a calling search space that you set up to contain the partition with all voice mail port directory numbers except the first voice mail port, as set in Step 9 of the "To Add Partitions and a Calling Search Space to Contain the Voice Mail Ports" procedure. For example, click "VMRestrictedCSS."
Because this calling search space is not used by subscriber phones, subscribers cannot dial any voice mail ports except the voice mail pilot number.
|
Display
|
Accept the default of Voicemail. (This text appears on the phone when the pilot number is dialed.)
Caution If Cisco Unity is configured for failover, do not change the default setting for this field, Otherwise, the integration will not function correctly.
|
Step 9 Click Next.
Step 10 Enter the operator number or the number you want the last port to forward to when busy, if applicable, and click Next.
Step 11 The settings for the new ports appear. Click Finish.
Step 12 Click Go to Cisco Voice Mail Ports Page.
Note If Cisco Unity is configured for failover and you are setting voice mail ports for the secondary server, skip the remaining procedures in this section and continue to the "Creating a New Integration with Cisco Unified CallManager" section. For further instructions on configuring the voice mail ports, see Chapter 12, "Integrating a Secondary Server for Cisco Unity Failover with a Cisco Unified Communications Manager Integration."
To Set the Partition for the First Voice Mail Port
Step 1 On the Cisco Voice Mail Port Configuration page, in the Cisco Voice Mail Ports list, click the first voice mail port, which is assigned the voice mail pilot number.
Step 2 Under Directory Number Information, in the Partition field, click the partition that you set up to contain the first voice mail port. For example, click "VMPilotNumberPT."
Step 3 Click Update.
To Specify MWI Directory Numbers
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Message Waiting.
Step 2 In the Message Waiting Directory Numbers list of the Message Waiting Configuration page, click Add a New Directory Number.
Step 3 Enter the following settings for turning MWIs on.
Table 3-4 Settings for Turning MWIs On
Field
|
Setting
|
Directory Number
|
Enter the unique extension that turns MWIs on.
|
Message Waiting Indicator
|
Click On.
|
Partition
|
Click the name of the partition that you set up for the first voice mail port. For example, click "VMPilotNumberPT."
|
Calling Search Space
|
Click a calling search space that is used by subscriber phones.
|
Step 4 Click Insert.
Step 5 In the Message Waiting directory Numbers list, click Add a New Directory Number.
Step 6 Enter the following settings for turning MWIs off.
Table 3-5 Settings for Turning MWIs Off
Field
|
Setting
|
Directory Number
|
Enter the unique extension that turns MWIs off.
|
Message Waiting Indicator
|
Click Off.
|
Partition
|
Click the name of the partition that you set up for the first voice mail port. For example, click "VMPilotNumberPT."
|
Calling Search Space
|
Click a calling search space that is used by subscriber phones.
|
Step 7 Click Insert.
In the following procedure, you will add the voice mail pilot number, which is the extension that you dial to listen to your voice messages. Your Cisco IP phone automatically dials the voice mail pilot number when you press the Messages button.
To Add a Voice Mail Pilot Number for the Voice Mail Ports
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Voice Mail Pilot.
Step 2 In the Voice Mail Pilot Numbers List of the Voice Mail Pilot Configuration page, click Add a New Voice Mail Pilot Number.
Step 3 Enter the following voice mail pilot number settings.
Table 3-6 Settings for the Voice Mail Pilot Number
Field
|
Setting
|
Voice Mail Pilot Number
|
Enter the pilot number for the voice mail ports. This number must be the same pilot number that you entered when adding voice mail ports earlier.
The pilot number is typically the extension number of the first voice mail port and is the number subscribers will dial to listen to their voice messages.
|
Description
|
Enter Cisco Unity Pilot or another description.
|
Calling Search Space
|
Click the calling search space that includes partitions containing the subscriber phones and the partition you set up for the first voice mail port.
|
Make This the Default Voice Mail Pilot for the System
|
Check this check box. When this check box is checked, this voice mail pilot number replaces the current default pilot number.
|
Step 4 Click Insert.
To Set Up the Voice Mail Profile
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Voice Mail Profile.
Step 2 On the Find and List Voice Mail Profiles page, click Add a New Voice Mail Profile.
Step 3 On the Voice Mail Profiles Configuration page, enter the following voice mail profile settings.
Table 3-7 Settings for the Voice Mail Profile
Field
|
Setting
|
Voice Mail Profile Name
|
Enter a name to identify the voice mail profile.
|
Description
|
Enter Cisco Unity Profile or another description.
|
Voice Mail Pilot
|
Click one of the following:
•The applicable voice mail pilot number that you defined on the Voice Mail Pilot Configuration page
•None (to use the default voice mail pilot number)
|
Voice Mail Box Mask
|
When multitenant services are not enabled on Cisco Unified CallManager, leave this field blank.
When multitenant services are enabled, each tenant uses its own voice mail profile and must create a mask to identify the extensions (directory numbers) in each partition that is shared with other tenants. For example, one tenant can use a mask 972813XXXX, while another tenant can use the mask 214333XXXX. Each tenant also uses its own translation patterns for MWIs.
|
Make This the Default Voice Mail Profile for the System
|
Check this check box to make this voice mail profile the default.
When this check box is checked, this voice mail profile replaces the current default voice mail profile.
|
Step 4 Click Insert.
To Set Up the Voice Mail Server Service Parameters
Step 1 In Cisco Unified CallManager Administration, click Service > Service Parameters.
Step 2 On the Service Parameters Configuration page, in the Server field, click the name of the voice mail server that you created earlier.
Step 3 In the Service list, click Cisco CallManager. The list of parameters appears.
Step 4 Scroll down the list until you locate the parameters listed in Table 8.
Table 3-8 Settings for the Service Parameters
Service Parameter to Configure
|
Setting
|
Voice Mail Maximum Hop Count
|
Used together with AdvancedCallForwardHopFlag, the maximum number of voice mail ports skipped to find the next available voice mail port. Specify a value that is three less than the number of Cisco Unified CallManager ports that are connected to the Cisco Unity server. For example, if you have a 48-port Cisco Unity system, enter 45 for this setting.
If you have configured failover for Cisco Unity, specify a value that is three less than the total number of Cisco Unified CallManager ports that are connected to both Cisco Unity servers. For example, if the primary and secondary Cisco Unity servers each have 48 ports, enter 93 for this setting.
|
Multiple Tenant MWI Modes
|
Enables multitenant MWI notification. When set to True, Cisco Unified CallManager uses any configured translation patterns to convert voice mail extensions into directory numbers when turning on or off an MWI.
|
H225 DTMF Duration
|
Specifies the duration (in milliseconds) of outbound DTMF digits for H.323 devices.
If you will use the Cisco Unity Bridge or AMIS to connect Cisco Unified CallManager and Cisco Unity to a supported third-party voice messaging system, confirm that this parameter is set to 100.
|
Advanced CallForward Hop Flag
|
Enables Cisco Unified CallManager to skip busy or unregistered voice mail ports when searching for an available voice mail port. Set to True.
|
Step 5 Click Update to save the settings.
Step 6 Click Select Another Service at the top of the page.
Step 7 In the Services list, click Cisco Messaging Interface. The list of parameters appears.
Step 8 Confirm that the VoiceMailDn parameter setting is blank.
Step 9 If you changed the parameter setting to blank, click Update to save the setting.
Step 10 Shut down and restart the Cisco Unified CallManager server.
If the plan for voice mail ports in Cisco Unity (see Chapter 2, "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity") includes ports that do not answer calls (for example, ports that only dial out to set MWIs), do the following procedure so that incoming calls are not forwarded to these ports.
To Set Up Voice Mail Ports So Incoming Calls Are Forwarded Only to Answering Ports
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port.
Step 2 In the Cisco Voice Mail Ports list of the Cisco Voice Mail Port Configuration page, click the name of the last voice mail port that answers calls in Cisco Unity.
Step 3 Set the Forward Busy and Forward No Answer fields to forward to the first voice mail port that answers calls in Cisco Unity.
Step 4 Click Update.
Step 5 In the Cisco Voice Mail Ports list, click the name of a the first voice mail port that does not answer calls in Cisco Unity.
Step 6 Under Call Forwarding Information, delete the extensions in the Forward Busy field, and set the Forward No Answer field to forward to the first voice mail port that answers calls in Cisco Unity.
Step 7 Click Update.
Step 8 Repeat Step 5 through Step 7 for all remaining voice mail ports that do not answer calls in Cisco Unity.
If the Cisco Unity server services multiple clusters of Cisco Unified CallManager, do the following procedure to enable MWIs to be activated on extensions in each cluster.
To Set Up MWI Voice Mail Ports for Multiple Clusters of Cisco Unified CallManager
Step 1 In Cisco Unity Administrator, select at least one voice mail port per cluster to be dedicated for sending MWIs to each cluster. For example, if the system has four clusters, dedicate at least four ports to send only MWIs, one port from each cluster.
Step 2 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port.
Step 3 In the Cisco Voice Mail Ports list of the Cisco Voice Mail Port Configuration page, click the name of the port before the first dedicated MWI port.
Step 4 Under Call Forwarding Information, change the extensions to the number of the first voice mail port or of the operator.
Step 5 Click Update.
Step 6 In the Cisco Voice Mail Ports list, click the name of a dedicated MWI port.
Step 7 Under Call Forwarding Information, delete the extensions so that the fields are empty and call forwarding for this port is disabled.
Step 8 Click Update.
Step 9 Repeat Step 6 through Step 8 for all remaining dedicated MWI ports.
Creating a New Integration with Cisco Unified CallManager
After ensuring that Cisco Unified CallManager and Cisco Unity are ready for the integration, do the following procedures to set up the integration and to enter the port settings.
Note the following:
•Multiple clusters—If you are integrating with multiple clusters of Cisco Unified CallManager and you have already created the integration with the first cluster, you must integrate Cisco Unity with each additional cluster. Skip to the "To Add a UTIM Cluster to a Cisco Unified CallManager Integration" procedure.
•MWI relay across trunks—If you are configuring MWI relay across trunks in a distributed phone system, you must refer to the Cisco Unified CallManager documentation for requirements and instructions. Configuring MWI relay across trunks does not involve Cisco Unity settings.
To Create an Integration
Step 1 If UTIM is not already open, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 2 In the left pane of the UTIM window, click Cisco Unity Server.
Step 3 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 4 On the Welcome page, click SCCP (CUCM/CCM and CUCME/CCME only) and click Next.
Step 5 On the Name CUCM/CCM Integration and Cluster page, enter the following settings, then click Next.
Table 3-9 Settings for the CUCM/CCM Integration and Cluster Page
Field
|
Setting
|
Integration Name
|
Enter the name you will use to identify this Cisco Unified CallManager integration. Accept the default name or enter another name.
|
Cluster Name
|
Enter the name you will use to identify this Cisco Unified CallManager cluster. Accept the default name or enter another name.
|
Step 6 On the Enter CUCM/CCM IP Address and Port page, enter the following settings, then click Next.
Table 3-10 Settings for the Enter CUCM/CCCP IP Address and Port Page
Field
|
Setting
|
IP Address/Name
|
Enter the IP address (or DNS name) of the Cisco Unified CallManager server that you are connecting to Cisco Unity. If you are connecting to a Cisco Unified CallManager cluster, we recommend entering the IP address (or DNS name) of a subscriber Cisco Unified CallManager server.
|
TCP Port
|
Enter the TCP port of the Cisco Unified CallManager server that you are connecting to Cisco Unity. We recommend using the default setting.
|
You can click Ping Server to confirm that the IP address is correct.
Step 7 On the Enter Secondary Server Settings for Failover page, in the IP Address/Name field, enter the IP address (or DNS name) and port of all remaining subscriber Cisco Unified CallManager servers in the cluster and of the publisher Cisco Unified CallManager server. Then click Add after entering each so that the IP addresses of all secondary servers appear in the list. If there is only one Cisco Unified CallManager server in the cluster, leave this page blank.
The IP addresses of the subscriber Cisco Unified CallManager servers must appear in descending order, so that the subscriber Cisco Unified CallManager server at the top of the list is the first to take over call processing functions during failover, and the publisher Cisco Unified CallManager server is the last.
You can click Ping Servers to confirm that the IP addresses are correct.
Step 8 If you want Cisco Unity to automatically reconnect to the primary Cisco Unified CallManager server after failover has been corrected, check the Reconnect to Primary CUCM/CCM Server check box.
Step 9 Click Next.
Step 10 On the Enter CUCM/CCM MWI Extensions page, enter the following settings, then click Next.
Table 3-11 Settings for the Enter CUCM/CCM MWI Extensions Page
Field
|
Setting
|
MWI On Extension
|
Enter the extension you specified in Cisco Unified CallManager Administration for turning MWIs on.
|
MWI Off Extension
|
Enter the extension you specified in Cisco Unified CallManager Administration for turning MWIs off.
|
Step 11 On the Set Number of Voice Messaging Ports page, enter the following settings, then click Next.
Table 3-12 Settings for the Set Number of Voice Messaging Ports Page
Field
|
Setting
|
Number of Ports
|
Enter the number of voice messaging ports connecting Cisco Unity to the Cisco Unified CallManager server; if Cisco Unity is connected to a single Cisco Unified CallManager server, this number cannot be more than the number of ports set up on Cisco Unified CallManager. If Cisco Unity is connected to multiple clusters of Cisco Unified CallManager, this number cannot be more than the number of ports set up on the Cisco Unified CallManager cluster, and the total number of ports on all clusters connected to Cisco Unity cannot be more than the number of ports enabled by the Cisco Unity license.
|
CUCM/CCM Device Name Prefix
|
Enter the prefix Cisco Unified CallManager adds to the device name for voice messaging ports. This prefix must match the prefix used by Cisco Unified CallManager.
Caution If Cisco Unity is configured for failover, the CUCM/CCM Device Name Prefix setting for the secondary server must be different from the CUCM/CCM Device Name Prefix setting for the primary server. Otherwise, the secondary server cannot function correctly.
|
You can click Verify to confirm that the CUCM/CCM device name prefix is correct.
Note If Cisco Unified CallManager ports are set up for authentication or encryption, the confirmation will fail because the Cisco Unity voice messaging ports are not yet set up for authentication or encryption.
Step 12 If other integrations already exist, the Enter Trunk Access Code page appears. Enter the extra digits that Cisco Unity must use to transfer calls through the gateway to extensions on the other phone systems with which it is integrated. Then click Next.
Step 13 On the Reassign Subscribers page, any subscribers whose phone system integration has been deleted and who are not currently assigned to a phone system integration will appear in the list.
If no subscribers appear in the list, click Next and continue to Step 14.
Otherwise, select the subscribers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting subscribers.
Table 3-13 Selection Controls for the Reassign Subscribers Page
Selection Control
|
Effect
|
Check All
|
Checks the check boxes for all subscribers in the list.
|
Uncheck All
|
Unchecks the check boxes for all subscribers in the list.
|
Toggle Selected
|
For the subscribers highlighted in the list, toggles between checking and unchecking the check boxes.
If some highlighted subscriber check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.
|
Step 14 On the Reassign Call Handlers page, any call handlers whose phone system integration has been deleted and that are not currently assigned to a phone system integration will appear in the list.
If no call handlers appear in the list, click Next and continue to Step 15.
Otherwise, select the call handlers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting call handlers.
Table 3-14 Selection Controls for the Reassign Call Handlers Page
Selection Control
|
Effect
|
Check All
|
Checks the check boxes for all call handlers in the list.
|
Uncheck All
|
Unchecks the check boxes for all call handlers in the list.
|
Toggle Selected
|
For the call handlers highlighted in the list, toggles between checking and unchecking the check boxes.
If some highlighted call handler check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.
|
Step 15 On the Completing page, verify the settings you entered, then click Finish.
Step 16 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.
Alternatively, you can restart the Cisco Unity services in UTIM on the Tools menu by clicking Restart Cisco Unity.
To Enter the Voice Messaging Port Settings for the Integration
Step 1 After the Cisco Unity services restart, on the View menu, click Refresh.
Step 2 In the left pane of the UTIM window, expand the phone system integration that you are creating.
Step 3 In the left pane, click the name of the cluster.
Step 4 In the right pane, click the Ports tab.
Step 5 Enter the settings shown in Table 3-15 for the voice messaging ports.
We strongly recommend and consider it a best practice to configure most voice messaging ports to only answer calls and the remaining ports to only dial out or perform MWI functions. This configuration eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes that port off-hook to dial out.
Caution In programming Cisco Unified CallManager, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.
Table 3-15 Settings for the Voice Messaging Ports
Field
|
Considerations
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
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.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.
|
Dialout MWI
|
Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.
|
AMIS Delivery
(available with the AMIS licensed feature only)
|
Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.
|
TRAP Connection
|
Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.
|
Step 6 Click Save.
Step 7 Repeat Step 3 through Step 6 for all remaining clusters if any.
Creating an Integration with an Additional Cisco Unified CallManager Cluster
You can integrate Cisco Unity with an additional Cisco Unified CallManager cluster through UTIM by using the options and considerations described in Table 3-16.
Table 3-16 Options and Considerations for Integrating with Another Cisco Unified CallManager Cluster
Option
|
Consideration
|
Add a cluster in UTIM to an existing Cisco Unified CallManager integration for each new Cisco Unified CallManager cluster. For instructions see the "To Add a UTIM Cluster to a Cisco Unified CallManager Integration" procedure.
|
•You must assign at least one MWI port dedicated to each Cisco Unified CallManager cluster that you add.
•The first cluster in UTIM will handle all calls and direct them to the Cisco Unified CallManager cluster on which the subscriber is homed.
•You can create an unlimited number of clusters in UTIM to a Cisco Unified CallManager integration.
•Multiple UTIM clusters can be used with multiple Cisco Unified CallManager integrations on the Cisco Unity server.
|
Create a new Cisco Unified CallManager integration for each new Cisco Unified CallManager cluster. For instructions, see the "Creating a New Integration with Cisco Unified CallManager" procedure".
|
•Each Cisco Unified CallManager integration handles the MWIs for the cluster. Dedicated MWI ports for each Cisco Unified CallManager cluster is necessary only if the Cisco Unified CallManager integration has multiple clusters in UTIM.
•Cisco Unity sends each MWI request directly to the Cisco Unified CallManager cluster on which the subscribers is homed.
•The number of Cisco Unified CallManager integrations is limited only by number of licensed voice messaging ports on the Cisco Unity server, as described in the Multiple Phone System Integration Guide for Cisco Unity 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.
•Multiple Cisco Unified CallManager integrations can be used with multiple UTIM clusters on a Cisco Unity server.
|
To Add a UTIM Cluster to a Cisco Unified CallManager Integration
Step 1 In the left pane of the UTIM window, click the Cisco Unified CallManager integration.
Step 2 On the Cluster menu, click New. The Add Server dialog box appears.
Step 3 Enter the following settings.
Table 3-17 Settings for the Add Server Dialog Box
Field
|
Setting
|
IP Address or Host Name
|
Enter the IP address (or DNS name) of a subscriber Cisco Unified CallManager server.
|
Port
|
Enter the TCP port of the Cisco Unified CallManager server that you are connecting to Cisco Unity. We recommend using the default setting.
|
TLS Port
|
Enter the secure port that Cisco Unified CallManager uses for secure call-signaling messages. This setting is used only when the CUCM/CCM Cluster Security Mode is set to Authenticated or Encrypted.
|
Step 4 Click OK.
Step 5 When prompted to enter the remaining settings for the cluster, click OK.
Step 6 Click the Servers tab, and, in the Display Name field, enter Cisco Unified CallManager Cluster 02 or another name you will use to identify this Cisco Unified CallManager cluster.
Step 7 If there are no additional Cisco Unified CallManager servers in this cluster, continue to Step 13.
If there are additional Cisco Unified CallManager servers in this cluster, click Add. The Add Server dialog box appears.
Step 8 Enter the following settings.
Table 3-18 Settings for the Add Server Dialog Box
Field
|
Setting
|
IP Address or Host Name
|
Enter the IP address (or DNS name) of a subscriber Cisco Unified CallManager server.
|
Port
|
Enter the TCP port of the Cisco Unified CallManager server that you are connecting to Cisco Unity. We recommend using the default setting.
|
TLS Port
|
Enter the secure port that Cisco Unified CallManager uses for secure call-signaling messages. This setting is used only when the CUCM/CCM Cluster Security Mode is set to Authenticated or Encrypted.
|
Step 9 Click OK.
Step 10 Repeat Step 7 through Step 9 for all remaining Cisco Unified CallManager servers in the cluster.
Step 11 Enter the following settings.
Table 3-19 Settings for the Servers Tab
Field
|
Setting
|
CUCM/CCM Device Name Prefix
|
Enter the prefix Cisco Unified CallManager adds to the device name for voice messaging ports. This prefix must match the prefix used by the Cisco Unified CallManager cluster.
Caution If Cisco Unity is configured for failover, the CUCM/CCM Device Name Prefix setting for the secondary server must be different from the CUCM/CCM Device Name Prefix setting for the primary server. Otherwise, the secondary server cannot function correctly.
|
CUCM/CCM Cluster Security Mode
|
Accept the default setting of Non-secure.
|
Reconnect to the Primary CUCM/CCM server
|
Check this check box if you want Cisco Unity to automatically reconnect to the primary Cisco Unified CallManager server in the cluster after failover has been corrected.
|
Step 12 Click Verify Servers to confirm that the Cisco Unified CallManager server information is correct.
Step 13 Click the MWI tab, and enter the following settings.
Table 3-20 Settings for the MWI Tab
Field
|
Setting
|
On Extension
|
Enter the extension you specified in Cisco Unified CallManager Administration of the cluster for turning MWIs on.
|
Off Extension
|
Enter the extension you specified in Cisco Unified CallManager Administration of the cluster for turning MWIs off
|
Step 14 Click the Ports tab, and click Add Port.
Step 15 In the Add Port dialog box, enter the number of voice messaging ports on Cisco Unity that you want to connect to the Cisco Unified CallManager cluster, and click OK.
This number cannot be more than the number of ports set up on the Cisco Unified CallManager cluster. This number cannot bring the total number of port installed on the Cisco Unity server to more than the number of ports enabled by the Cisco Unity license.
Step 16 Enter the settings shown in Table 3-21 for the voice messaging ports.
We strongly recommend and consider it a best practice to configure most voice messaging ports to only answer calls and the remaining ports to only dial out or perform MWI functions. This configuration eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes that port off-hook to dial out.
Caution In programming Cisco Unified CallManager, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.
Table 3-21 Settings for the Voice Messaging Ports
Field
|
Considerations
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
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.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.
|
Dialout MWI
|
Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.
|
AMIS Delivery
(available with the AMIS licensed feature only)
|
Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.
|
TRAP Connection
|
Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.
|
Step 17 Click the RTP tab, and confirm that the Automatically Assign option is selected.
Step 18 In the UTIM window, click Save.
Step 19 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.
Alternatively, you can restart the Cisco Unity services in UTIM on the Tools menu by clicking Restart Cisco Unity.
Step 20 After the Cisco Unity services restart, in the left pane of the UTIM window, click the Cisco Unified CallManager integration.
Step 21 Repeat Step 1 through Step 20 for all remaining Cisco Unified CallManager clusters.
If the number of voice messaging ports on the Cisco Unity server is 72 or more, and the Cisco Unity server is running Windows Server 2003 or Exchange is the message store, do the following procedure.
To Adjust the Advanced Settings for 72 or More Voice Messaging Ports
Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Tools Depot.
Step 2 In the Tools Depot window, in the left pane, expand Administration Tools and double-click Advanced Settings Tool.
Step 3 If the Cisco Unity server is running Windows Server 2003, do the following substeps. Otherwise, continue to Step 4.
a. In the Cisco Unity Advanced Settings window, in the left pane, click Messaging - 72 or More Voice Ports - Enable Low-Fragmentation Heap.
b. In the New Value drop-down box, click 1 and click Set.
c. When prompted that the value has been set, click OK.
Step 4 If Exchange is the message store, do the following substeps. Otherwise, continue to Step 5.
a. In the Cisco Unity Advanced Settings window, in the left pane, click Messaging - 72 or More Voice Ports - Number of MAPI Sessions Per Exchange Server.
b. In the New Value drop-down box, click the applicable setting, then click Set.
Number of Voice Messaging Ports
|
Setting
|
72 to 83
|
Click 2.
|
84 to 95
|
Click 3.
|
96 to 119
|
Click 4.
|
120 to 143
|
Click 5.
|
144
|
Click 6.
|
c. When prompted that the value has been set, click OK.
Step 5 Close the Tools Depot window.
Step 6 Restart the Cisco Unity server.
