See the following sections in this chapter:
•Integrations with Multiple Phone Systems
The Cisco Unified Communications Manager (CM) Express (formerly known as Cisco Unified CallManager Express) SCCP integration uses a LAN to connect Cisco Unity Connection and the phone system. The Cisco Unified Communications Manager Express router also provides connections to the PSTN. Figure 1-1 shows the connections for a system with a single Cisco Unified CM Express router.
Figure 1-1 Connections Between a Single Cisco Unified Communications Manager Express Router and Cisco Unity Connection
Figure 1-2 shows the connections for a system with multiple Cisco Unified CM Express router and a single Cisco Unity Connection server. One Cisco Unified CM Express router acts as the SIP MWI server, and the remaining Cisco Unified CM Express routers act as 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.
Figure 1-2 Connections Between Multiple Cisco Unified Communications Manager Express Routers and a Single Cisco Unity Connection Server
For a list of supported versions of Cisco Unified CM Express that are qualified to integrate with Cisco Unity Connection by Skinny Call Control Protocol (SCCP), see 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.
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 CM.
The phone system sends the following information with forwarded calls:
•The extension of the called party
•The extension of the calling party (for internal calls) or the phone number of the calling party (if it is an external call and the system uses caller ID)
•The reason for the forward (the extension is busy, does not answer, or is set to forward all calls)
Cisco Unity Connection uses this information to answer the call appropriately. For example, a call forwarded to Cisco Unity Connection is answered with the personal greeting of the user. If the phone system routes the call to Cisco Unity Connection without this information, Cisco Unity Connection answers with the opening greeting.
The Cisco Unified CM Express SCCP integration with Cisco Unity Connection provides the following features:
•Call forward to personal greeting
•Call forward to busy greeting
•Easy message access (a user can retrieve messages without entering an ID; Cisco Unity Connection identifies a user based on the extension from which the call originated; a password may be required)
•Identified user messaging (Cisco Unity Connection automatically identifies a user who leaves a message during a forwarded internal call, based on the extension from which the call originated)
•Message waiting indication (MWI)
These integration features are not available to analog phones connected through FXS ports on the Cisco Unified CM Express phone system. Analog phones connected to ATA, however, support all integration features, except MWIs (MWI lamps will not light, though the stutter dial tone will sound).
Integrations with Multiple Phone Systems
When 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 cannot be integrated with multiple phone systems at one time.
When Cisco Unity Connection is not installed as Cisco Unified CMBE, Cisco Unity Connection can be integrated with two or more phone systems at one time. For information on and instructions for integrating Cisco Unity Connection with multiple phone systems, refer to the Multiple Phone System Integration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.