Managing the Phone System Integrations in Cisco Unity Connection 9.x

NoteYou can manage the phone system integrations by adding or deleting phone systems, port groups, ports, phone system trunks, and servers. You can also change the settings for existing phone systems, port groups, ports, phone system trunks, and servers.

Managing Phone Systems in Unity Connection

The phone system pages in Cisco Unity Connection Administration identify the phone systems that Unity Connection integrates with. In Unity Connection Administration, a phone system has one or more port groups, which in turn have voice messaging ports. You can manage the phone systems to meet the changing needs of your system.

Step 2 On the Search Phone Systems page, under Phone System Search Results, select Add New . The New Phone System page appears.

Step 3 On the New Phone System page, in the Phone System Name field, enter a descriptive name for the phone system and select Save .

Step 4 On the Phone System Basics page, enter the applicable settings and select Save .

Deleting a Phone System Integration

You can delete a phone system when the phone system is no longer used by Unity Connection. Before you can delete a phone system, you must delete or reassign to another phone system all of the following objects that are associated with the phone system that you want to delete:

Step 2 On the Search Phone Systems page, under Phone System Search Results, check the check box next to the name of the phone systems that you want to delete.

Step 3 Select Delete Selected .

Step 4 When prompted to confirm that you want to delete the phone systems, select OK .

Changing Phone System Settings

You can change the settings for a phone system after it is integrated with Unity Connection. The phone system settings identify the phone system that Unity Connection integrates with and regulate certain phone system features. (Integration configuration settings are located in the port groups that belong to the phone system.)

Step 2 On the Search Phone Systems page, select the display name of the phone system.

Step 3 On the Phone System Basics page, on the Edit menu, select Phone System Associations .

Step 4 On the Phone System Associations page, the list of users who are associated with the phone system is displayed.

Disabling the Use of the Same Port for Turning On and Off an MWI

If you created the phone system integration to use the same voice messaging port to turn on and off an MWI (the Use Same Port for Enabling and Disabling MWIs field was checked), you can do the following procedure to disable this configuration without leaving MWIs on when there are no voice messages for the user.

For Cisco Unified Communications Manager integrations, Phone View allows users to see search results on the LCD screens of their Cisco IP phones when they use the Find Message or the Display Message menu. Phone View requires that Cisco Unified CM also be configured. For details, see the “Setting Up Phone View in Cisco Unity Connection 9.x” chapter.

Step 2 On the Search Phone Systems page, select the display name of the phone system.

Step 3 On the Phone System Basics page, under Phone View Settings, enter the applicable settings and select Save .

Changing Call Loop Detection Settings

Calls that Unity Connection forwards (for example, to notify a user that a message has been received) are sometimes forwarded back to Unity Connection. When call loop detection is enabled, Unity Connection detects when a call loop has occurred and rejects the call.

You can change the call loop detection settings to enable or disable the types of calls that are checked, to set the fourth-column DTMF tone that Unity Connection uses, and to set the guard time.

The call loop detection settings should not be changed without understanding the effect that they have on calls that Unity Connection forwards.

Step 11 In the Name column, select the name of the Cisco Unity Connection server.

Step 12 On the Application Server Configuration page, in the Available Application User field, select the Cisco Unified CM application user that you used in Step 7 and select the Down arrow to move it to the Selected Application User field.

Managing Port Groups in Unity Connection

Port groups hold most of the integration configuration settings and some or all of the voice messaging ports for Unity Connection.

While most phone system integrations need only one port group, multiple port groups may be needed in the following circumstances:

For integrations with phone systems through PIMG/TIMG units, each PIMG/TIMG unit is connected to one port group with the applicable voice messaging ports. For example, a system that uses five PIMG units requires five port groups, one port group for each PIMG unit.

For integrations with other phone systems, an additional port group with its own voice messaging ports may be used for testing a new configuration or for troubleshooting.

Adding a Port Group

You can add multiple port groups, each with its own integration configuration settings and its own voice messaging ports.

Cisco Unified Communications Manager Business Edition (CMBE) only: Before you can add a port group, you must have existing voice messaging ports in Cisco Unified CM Administration that do not belong to a port group.

Other configurations: For integrations with phone systems through PIMG/TIMG units, one port group is required for each PIMG/TIMG unit. For example, a system that uses five PIMG units requires five port groups, one port group for each PIMG unit.

NoteUnity Connection enables you to create a maximum of 90 port groups if you are using only TUI (touchtone conversation) and VUI (voice-recognition) features. However, if you are using all the features of Unity Connection, you are allowed to create a maximum of 60 port groups.

Step 4 On the Edit Codec Advertising page, select the Up and Down arrows to change the order of the codecs or to move codecs between the Advertised Codec box and the Unadvertised Codecs box.

If only one codec is in the Advertised Codecs box, Unity Connection sends the media stream in that audio format. The phone system transcodes if it does not use this audio format.

If two or more codecs are in the Advertised Codecs box, Unity Connection advertises its preference for the first codec in the list but sends the media stream in the audio format from the list that the phone system selects.

Step 5 Select Save .

Step 6 (All integrations except SCCP) If you want to change the packet size that is used by the advertised codecs, on the Port Group Basics page, under Advertised Codec Settings, select the applicable packet setting for each codec and select Save .

Step 7Select Next .

Step 8 Repeat Step 3 through Step 7 for all remaining port groups that belong to the phone system integration for which you want to change the audio format of the media stream.

Changing MWI Settings

Messaging waiting indicators (MWIs) control whether Unity Connection sets MWIs for users and how retries for MWI requests are handled.

Adding Secondary Cisco Unified Communications Manager Servers

For Cisco Unified Communications Manager integrations, Related Links helps you create the integration only with one Cisco Unified CM server. The secondary Cisco Unified CM servers in the cluster must be added after the integration is created.

NoteYou can selectPing to verify the IP address (or host name) of the SIP server.

Managing PIMG/TIMG Units

For integrations with phone systems through PIMG/TIMG units, each PIMG/TIMG unit is in a separate port group. For example, a system that uses five PIMG units requires five port groups, one port group for each PIMG unit. You can add, change, or delete PIMG/TIMG units after the phone system integration has been created.

NoteCisco Unified Communications Manager Business Edition (CMBE) does not support integrations with PIMG/TIMG units.

Enabling or Disabling Normalization

Normalization controls automatic volume adjustments for recording messages. We recommend that you leave normalization enabled and that you not change the value of the Target Decibel Level for Recordings and Messages field on the System Settings > General Configuration page.

NoteWith Unity Connection 9.0(1) and later releases, the ports do not require any specific license to be installed on your system. You can configure the ports based on your hardware profile.

Adding a Port

Voice messaging ports provide the connections for calls between Unity Connection and the phone system. You can add voice messaging ports after the phone system has been created.

Cisco Unified Communications Manager Business Edition (CMBE) only: Before you can add ports, you must have existing voice messaging ports in Cisco Unified CM Administration that do not belong to a port group.

NoteWe recommend you to create a maximum of 90 port groups if you are using only TUI (touchtone conversation) and VUI (voice-recognition) features of Unity Connection. However, if you are using all the features of Unity Connection, you are allowed to create a maximum of 60 port groups.

Step 2 On the Search Ports page, under Port Search Results, check the check box next to the voice messaging ports that you want to delete.

Step 3 Select Delete Selected .

Step 4 For the remaining voice messaging ports in the port group, change the settings as necessary so that there are an appropriate number of voice messaging ports set to answer calls and an appropriate number of voice messaging ports set to dial out.

Changing Port Settings

Voice messaging ports provide the connections for calls between Unity Connection and the phone system. You can change the voice messaging port settings after the phone system integration has been created.

Depending on the phone system integration, some or all of the fields in Table 30-3 appear.

Table 30-3 Port Basics Page Settings

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.

Server Name

(not available for PIMG/TIMG integrations)

(For Unity Connection redundancy only) Select the name of the Unity Connection server that you want to handle this port.

Assign an equal number of answering and dial-out voice messaging ports to the Unity Connection servers so that they equally share the voice messaging traffic.

Extension

(available for PIMG/TIMG integrations only)

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 outside 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

(not used by serial integrations)

Check this check box to designate the port for turning MWIs on and off. Assign Send MWI Requests to the least busy ports.

For serial integrations, uncheck this check box. Otherwise, the integration may not function correctly.

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

(not available for SIP integrations)

Enter the priority order in which Cisco Unity Connection uses 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, Unity Connection uses the port that has been idle the longest.

Security Mode

(available for Cisco Unified CM SCCP integrations only)

Select the applicable security mode:

Non-secure —The integrity and privacy of call-signaling messages are not ensured because call-signaling messages are sent as clear (unencrypted) text and are connected to Cisco Unified Communications Manager through a non-authenticated port rather than an authenticated TLS port. In addition, the media stream is not encrypted.

Authenticated —The integrity of call-signaling messages are ensured because they are connected to Cisco Unified CM through an authenticated TLS port. However, the privacy of call-signaling messages are not ensured because they are sent as clear (unencrypted) text. In addition, the media stream are not encrypted.

Encrypted —The integrity and privacy of call-signaling messages are ensured on this port because they are connected to Cisco Unified CM through an authenticated TLS port, and the call-signaling messages are encrypted. In addition, the media stream is encrypted.

Step 4If there are no more voice messaging ports for which you want to change the settings, skip to Step 6. Otherwise, select Next .

Step 5 Repeat Step 3 and Step 4 for all remaining voice messaging ports for which you want to change the settings.

Step 6On the Port menu, select Search Ports .

Step 7 On the Search Ports page, confirm that there are an appropriate number of voice messaging ports set to answer calls and an appropriate number of voice messaging ports set to dial out. If necessary, adjust the number of voice messaging ports set to answer calls and an appropriate number of voice messaging ports set to dial out.

Viewing the Port Certificate

Port certificates for voice messaging ports are used only by SCCP integrations with Cisco Unified Communications Manager 4.1 and later, and are required for authentication of the Cisco Unity Connection voice messaging ports. You can view the port certificate to help in troubleshooting authentication and encryption problems.

Step 2 On the Search Ports page, select the display name of the voice messaging port for which you want to see the device certificate.

Step 3 On the Port Basics page, select View Certificate .

Step 4 In the View Port Certificate window, the information from the port device certificate is displayed.

Managing Speech Connect Port in Unity Connection

Speech Connect uses voice-enabled directory handlers that allow both employees and outside callers to speak the name of an employee and instantly get connected, without having to navigate an audio-text tree, and without knowing the extension of the employee. For easy access, you can configure a Speech Connect speed dial on user phones.

Configuring a Speech Connect Port

Step 2 On the Speech Connect Port page, under New Speech Connect Port, select the Unity Connection server from the Connection Server drop down list.

Step 3 In the Number of Ports field, enter the number of Speech Connect ports that you want to configure.

Step 4 Click on the Save option to apply the specified settings.

Managing Phone System Trunks in Unity Connection

When multiple phone systems are integrated with Unity Connection, you may want to set up a phone system trunk so that calls on one phone system can be transferred to extensions on another phone system. Phone system trunks are accessed by dialing extra digits (for example, dialing 9) before dialing the extension.

NoteCisco Unified Communications Manager Business Edition (CMBE) does not support phone system trunks.

Adding a Phone System Trunk

If another phone system integration exists, you can add a phone system trunk to provide access from calls on one phone system to extensions on the other phone system. You can add phone system trunks after the phone system integration has been created.

NoteCisco Unified Communications Manager Business Edition (CMBE) does not support phone system trunks.

Viewing the Unity Connection Root Certificate

The root certificate is used by SCCP integrations with Cisco Unified Communications Manager 4.1 and later and SIP trunk integrations with Cisco Unified CM 7.0 and later, and is required for authentication of the Unity Connection voice messaging ports. You can view the root certificate to help troubleshoot authentication and encryption problems.

Step 2 On the View Root Certificate page, the information from the root certificate is displayed.

Saving the Unity Connection Root Certificate as a File

The root certificate is used by SCCP integrations with Cisco Unified CM 4.1 and later and SIP trunk integrations with Cisco Unified CM 7.0 and later, and is required for authentication of the Unity Connection voice messaging ports.

IPv6 support is disabled by default. When you enable IPv6, you can configure Unity Connection to obtain an IPv6 address either through router advertisement, through DHCP, or by manually configuring an address. You can also configure the mode in which Unity Connection listens for incoming traffic—IPv4, IPv6, or both IPv4 and IPv6.

For SCCP integrations with Cisco Unified CM, if Unity Connection is configured to listen for incoming IPv4 and IPv6 traffic, you can configure the addressing mode that Unity Connection uses for call control signaling for each port group to use either IPv4 or IPv6. (This mode is also used when connecting to a TFTP server.)

For SIP integrations with Cisco Unified CM, if Unity Connection is configured to listen for incoming IPv4 and IPv6 traffic, you can configure the addressing mode that Unity Connection uses for call control signaling for each port group to use either IPv4 or IPv6. (This mode is also used when connecting to a TFTP server.) In addition, you can configure the addressing mode that Unity Connection uses for media for each port group to use either IPv4 or IPv6.

Note the following considerations when deploying IPv6 for Cisco Unified CM integrations:

IPv6 is supported in Cisco Unified CM release 7.1(2) and later.

The CTL file required for security features (authentication and encryption) for SCCP integrations uses IPv4 addressing. Therefore, in order to use authentication and encryption with SCCP secure ports, you must retain the IPv4 address or host name for the Cisco Unified CM server(s) on the port group in Connection.

Some versions of Cisco Adaptive Security Appliance (ASA) do not support application inspection for IPv6 traffic for Unified Communications application servers and endpoints. We recommend not using IPv6 for Unified Communications if you are using a Cisco ASA version that does not provide this support. See the documentation for your version of Cisco ASA to determine whether application inspection is supported in your deployment.