Design Guide for Cisco Unity Release 5.x Revised May 6, 2008 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S Preface ix Audience ix Document Conventions ix Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and Software Support Policy for Optional Third-Party Software x Obtaining Documentation, Obtaining Support, and Security Guidelines Cisco Product Security Overview xi CHAPTER 1 Design Guide Overview CHAPTER 2 Cisco Unity Concepts x xi 1-1 2-1 How Cisco Unity Works 2-1 Characteristics of Unified Messaging and Voice Messaging Systems Unified Mess
Contents Some Subscriber Information and Configuration Settings Are Stored on the Cisco Unity Server Some Configuration Settings Are Stored in the Registry 2-10 CHAPTER 3 Network Infrastructure Requirements 2-10 3-1 Availability of Network Resources 3-1 Name Resolution 3-1 Domain Controller Access and Availability 3-2 Availability of Message Store Servers 3-2 Using Firewalls with Cisco Unity 3-3 Sizing and Scaling Cisco Unity Servers 3-3 Maximum Number of Users on Dedicated Domino or Exchange Serve
Contents Windows Domains and Domino Domains 5-5 Server Placement 5-5 Active Directory Accounts and Permissions 5-6 Authentication 5-6 Domino Permissions 5-7 Cisco Unity Subscribers and Domino Users 5-7 Domino Clusters 5-7 Message Routing 5-8 Notes Client on the Cisco Unity Server 5-8 Client Access Licenses 5-8 Backing Up and Restoring Data 5-8 Migrating from Cisco Unity for Exchange 5-8 Cisco Unity and the Domino Address Book 5-8 Unified Messaging Configurations 5-9 Unified Messaging, No Domino Cluster 5
Contents Cisco Unified Communications Manager Authentication and Encryption for Cisco Unity Voice Messaging Ports (SCCP Integrations Only) 6-12 Packetization (SCCP Integrations Only) 6-17 Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) 6-17 Multiple Cisco Unified Communications Manager Express Version Support 6-18 Multiple Cisco Unified Communications Manager Express Routers Integrating with a Single Cisco Unity Server 6-19 Integrating Cisco Unity with Cisco Survivable
Contents Installing Exchange 2003 on the Cisco Unity Primary Server in a Standby Redundancy Configuration 7-3 Diagram of a Standby Redundancy Configuration 7-5 CHAPTER 8 Voice-Recognition Access to Cisco Unity CHAPTER 9 Migrating to Cisco Unity from Another Voice-Messaging System 8-1 9-1 INDEX Design Guide for Cisco Unity Release 5.
Contents Design Guide for Cisco Unity Release 5.
Preface See the following sections: • Audience, page ix • Document Conventions, page ix • Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and Software, page x • Support Policy for Optional Third-Party Software, page x • Obtaining Documentation, Obtaining Support, and Security Guidelines, page xi Audience The Design Guide for Cisco Unity Release 5.x is intended for anyone responsible for the design or configuration of a Cisco Unity system.
Preface Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and Software For descriptions and the URLs of Cisco Unity documentation on Cisco.com, see the Documentation Guide for Cisco Unity. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.ht ml.
Preface Obtaining Documentation, Obtaining Support, and Security Guidelines For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.
Preface Design Guide for Cisco Unity Release 5.
CH A P T E R 1 Design Guide Overview The following table lists the feature areas that affect the design of a Cisco Unity system and, for each area, the location where you will find more information (either in this guide or in other Cisco Unity documentation). Note that for some features, documentation that covers only system design is not available; therefore, the location listed is for feature documentation.
Chapter 1 Product Area Interoperating with or migrating from other voice-messaging systems Design Guide Overview Design or Feature Documentation • For information on interoperating with Avaya voice-messaging systems, see the following documents: – The Design Guide for Cisco Unity Bridge at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_implementati on_design_guides_list.html. – The applicable Networking Guide for Cisco Unity Bridge at http://www.cisco.
Chapter 1 Design Guide Overview Design Guide for Cisco Unity Release 5.
Chapter 1 Design Guide Overview Design Guide for Cisco Unity Release 5.
CH A P T E R 2 Cisco Unity Concepts • How Cisco Unity Works, page 2-1 • Characteristics of Unified Messaging and Voice Messaging Systems, page 2-2 • Hardware Components of a Cisco Unity System, page 2-3 • Software Components of a Cisco Unity System, page 2-6 • Where Cisco Unity Stores Data, page 2-6 How Cisco Unity Works Cisco Unity is a unified messaging system that can also be a voice messaging system, and it requires a dedicated messaging infrastructure.
Chapter 2 Cisco Unity Concepts Characteristics of Unified Messaging and Voice Messaging Systems Note This is true unless the MWI had already been activated because of a prior message arrival, in which case it simply remains activated.
Chapter 2 Cisco Unity Concepts Hardware Components of a Cisco Unity System The message store contains only Cisco Unity voice messages, not e-mails or faxes. Exchange can be installed either on the Cisco Unity server or on a separate server, depending on the number of subscribers that need to be supported by Cisco Unity. Domino must be installed on a separate server. • Subscribers check messages: – With Domino or Exchange, by using the phone or Cisco Personal Communicator.
Chapter 2 Cisco Unity Concepts Hardware Components of a Cisco Unity System Cisco Unity can also be integrated with multiple telephone systems. For more information, see the Multiple Telephone System Integrations Guide for Cisco Unity 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_g uides_list.html.
Chapter 2 Cisco Unity Concepts Hardware Components of a Cisco Unity System information). All voice cards must be installed in the expansion chassis; they cannot be split between the server and the expansion chassis, because all of the cards must be connected to one another by using a single H.100 cable.
Chapter 2 Cisco Unity Concepts Software Components of a Cisco Unity System • Give subscribers access to Cisco Unity by using the Cisco Unity Assistant, the Cisco Unity Inbox, an IMAP e-mail client, or Cisco Personal Communicator. • Install Exchange on a separate server. For a system with a large number of Cisco Unity subscribers, installing Exchange on a separate server is required. Note • Give the Cisco Unity server access to network utilities such as virus checking and backup.
Chapter 2 Cisco Unity Concepts Where Cisco Unity Stores Data currently supported by DUC for Cisco, see the “Domino Requirements—Message Store” section of System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. Cisco Unity can service subscribers on multiple Domino servers. You specify one Domino server (the partner Domino server) through which Cisco Unity communicates with the other Domino servers.
Chapter 2 Cisco Unity Concepts Where Cisco Unity Stores Data • Reliability: Because subscriber data is stored on the Cisco Unity server, Cisco Unity can answer calls, let outside callers look up subscriber extensions, and take messages even when the Domino or Exchange network is down. (When the Domino or Exchange network is unavailable, new messages are stored on the Cisco Unity server, and subscribers have access to those messages.
Chapter 2 Cisco Unity Concepts Where Cisco Unity Stores Data The directory replicates the information to all Domino servers in the domain (for Domino) or domain controllers and global catalog servers in the forest (for Exchange), which ensures that Cisco Unity has the required access to information. For detailed information on adding two or more Cisco Unity servers to the same Domino domain or Active Directory forest, see the Networking Guide for Cisco Unity at http://www.cisco.
Chapter 2 Cisco Unity Concepts Where Cisco Unity Stores Data Because this information can be stored and changed in multiple locations, it must be regularly synchronized. Cisco Unity includes separate directory monitors for Domino and for Active Directory that keep the directory synchronized with the SQL Server 2000 database. Every few minutes, the directory monitor checks for new, changed, and deleted objects, and replicates the information.
CH A P T E R 3 Network Infrastructure Requirements See the following sections: • Availability of Network Resources, page 3-1 • Using Firewalls with Cisco Unity, page 3-3 • Sizing and Scaling Cisco Unity Servers, page 3-3 • Audio Codecs, page 3-5 Availability of Network Resources The following network resources must be available at all times and in close physical proximity to Cisco Unity (over a local area network, not a wide area network), or Cisco Unity functionality will be impaired: • All name
Chapter 3 Network Infrastructure Requirements Availability of Network Resources • Administrators access the Cisco Unity Administrator from other servers, which is primarily done when using the administrative web interfaces. Typically, if a server name is used instead of an IP address, the server name must be resolved to an IP address before access can occur over the network. • Subscribers access the Cisco Unity Assistant or the Cisco Unity Inbox.
Chapter 3 Network Infrastructure Requirements Using Firewalls with Cisco Unity during installation. If Cisco Unity subscribers are homed on servers other than the partner Exchange server or the Domino mail drop server, all voice messages from outside callers pass through the partner server or the mail drop server on their way to the home servers for Cisco Unity subscribers.
Chapter 3 Network Infrastructure Requirements Sizing and Scaling Cisco Unity Servers Maximum Number of Users on Dedicated Domino or Exchange Servers You should not allow the Domino or Exchange servers to service the maximum number of Domino or Exchange users that IBM Lotus or Microsoft allow.
Chapter 3 Network Infrastructure Requirements Audio Codecs In some cases you might find that an existing voice messaging system has more ports than the current maximum number of voice ports on a Cisco Unity system. In this case, the customer can purchase additional Cisco Unity servers and connect them by using Cisco Unity Digital Networking. Audio Codecs An audio codec is an algorithm that encodes and decodes (and compresses or decompresses) audio data.
Chapter 3 Network Infrastructure Requirements Audio Codecs Table 3-1 Voice Message File Sizes and Audio Quality Ratings Audio Codec Approximate File Size, 1-Minute Message Quality Rating G.711 Mu-Law and A-Law 480 KB Excellent G.726 32 Kbps 240 KB Fine OKI ADPCM 8 kHz 240 KB Fine OKI ADPCM 6 kHz 180 KB Fine GSM 6.10 98 KB Good G.
CH A P T E R 4 Designing a Cisco Unity System with Exchange as the Message Store This chapter focuses on using Exchange as the message store and Active Directory as the directory for Cisco Unity. All references to Exchange apply to the currently supported versions of Exchange—Exchange 2007 and Exchange 2003—unless specified otherwise. Exchange 2000 is supported only for upgrades from Cisco Unity 4.x and is, therefore, not discussed in this design guide.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Deployment Models Unified Messaging with Customer-Provided Infrastructure Revised May 6, 2008 For the Cisco Unity Unified Messaging configurations, Cisco Unity installs into an existing infrastructure, is a part of the messaging environment, services subscribers who are homed on existing Exchange e-mail servers, and uses existing DC/GCs.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Deployment Models • Each Voice Messaging subscriber requires a separate Exchange mailbox that holds only Cisco Unity voice messages on a separate, dedicated Exchange server that homes only Cisco Unity voice messages. The advantages of this model include the following: • The customer does not need to extend the Active Directory schema in the existing forest.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Physical Placement and Network Infrastructure When all Cisco Unity servers will be in the same Active Directory forest and the customer wants subscribers to be able to send voice messages across servers, use Cisco Unity Digital Networking to connect them. The messaging functionality across Cisco Unity servers is the same as the messaging functionality on a single Cisco Unity server.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Customer-Provided Infrastructure For detailed firewall requirements, see the following sections in the System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Customer-Provided Infrastructure For general information on Cisco Unity and Active Directory, see the applicable Cisco Unity Data and the Directory white paper, also at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Customer-Provided Infrastructure Exchange Considerations (All Versions) Note the following Exchange considerations when a Cisco Unity implementation will use customer-provided Exchange infrastructure: • When Cisco Unity is installed, the installer chooses a partner Exchange server, which is the home of several default Cisco Unity mailboxes, including: – The Cisco Unity system mailbox (alias: Unity_)
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Customer-Provided Infrastructure • In a Voice Messaging configuration, to help prevent Exchange transaction logs from filling the hard disk, a wizard in Cisco Unity Setup prompts the installer to change the circular-logging setting for any message store in the forest for which circular logging is turned off.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Cisco-Provided, Dedicated Infrastructure Considerations for Cisco-Provided, Dedicated Infrastructure Note the following considerations when a Cisco Unity implementation will use Cisco-provided, dedicated Exchange and Active Directory infrastructure: • Ensure that the servers selected for Cisco Unity and for Exchange are able to handle the proposed number of users.
Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store Considerations for Cisco-Provided, Dedicated Infrastructure Design Guide for Cisco Unity Release 5.
CH A P T E R 5 Designing a Cisco Unity System with Domino as the Message Store This chapter focuses on using IBM Lotus Domino as the message store and a Domino address book as the directory for Cisco Unity.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes • Domino Clusters, page 5-7 • Message Routing, page 5-8 • Notes Client on the Cisco Unity Server, page 5-8 • Client Access Licenses, page 5-8 • Backing Up and Restoring Data, page 5-8 • Migrating from Cisco Unity for Exchange, page 5-8 Maximum Number of Cisco Unity Subscribers Cisco Unity for Domino deployments are limited to one Cisco Unity server or one pair of failover se
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes • csAdmin, the administration component of DUC for Cisco, must be installed on the Domino server that pushes directory information out to the other Domino servers. You install csAdmin only once for the domain. In addition, DUC for Cisco client software must be installed on the client workstation of each Notes user who will be a Cisco Unity subscriber.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes Changes That csClient Makes to the Mail File When csClient software is installed on a client workstation, the elements in Table 5-2 are added to the mail file. If csClient is uninstalled, these elements are removed from the mail file.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes – A secondary address book is an address book from which subscribers can be imported but that does not home default Cisco Unity accounts. You can choose a secondary address book, if any, in the Cisco Unity Administrator. – Monitored address books may be needed when there are multiple Cisco Unity servers that will be set up for Digital Networking.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes For additional firewall requirements, see the section “Network Requirements” in the System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Overview of Cisco Unity with Domino and Notes Domino Permissions Before Cisco Unity is installed, the Cisco Unity installer or a qualified Domino administrator needs to: • Create a group for Cisco Unity servers named UnityServers, and grant the group Editor permissions for Admin4.nsf and Editor with Delete Documents permissions for Names.nsf.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Cisco Unity and the Domino Address Book Message Routing Cisco Unity voice messages are routed to Domino mailboxes by Domino. When a caller leaves a voice message (whether an outside caller or a subscriber), Cisco Unity submits the messages to Mail.box on the mail drop server. The mail drop server determines the routing path to the mail file of the recipient.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Unified Messaging Configurations Cisco Unity requires Editor with Delete Documents permission for the address book that Cisco Unity monitors. A Cisco Unity server can monitor the address books for one domain, including Names.nsf and any secondary address book that may be supporting proxy/remote users (users who do not have mail files in the Domino domain).
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Voice Messaging Configuration Table 5-3 Server Requirements and Recommendations for a Unified Messaging Configuration (continued) Servers Requirements and Recommendations Cisco Unified Communications The Cisco Unified Communications Manager (CM) Express (formerly known as Cisco Manager Express Unified CallManager Express) and Cisco Unity servers must be connected by a LAN.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Deploying Cisco Unity for Lotus Domino • A Cisco Unity server can service mailboxes on up to a recommended maximum of ten Domino servers or clusters in a single physical site. • A Cisco Unity server can service a single Domino address book (directory or Names.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Deploying Cisco Unity for Lotus Domino Administrative Access and Control To manage administrative access to the Cisco Unity server and its resources, the customer may want different levels of access for different operations, for example, backing up the server or gathering performance information for trending.
Chapter 5 Designing a Cisco Unity System with Domino as the Message Store Deploying Cisco Unity for Lotus Domino • Create a group for Cisco Unity servers, and grant the group Editor permissions for Admin4.nsf, and Editor with Delete Documents permissions for Names.nsf. • Install DUC for Cisco components on the applicable Domino servers. • Define the level of access to the local Cisco Unity server necessary for an administrator.
Chapter 5 Feature Parity Between Cisco Unity for Domino and Cisco Unity for Exchange Designing a Cisco Unity System with Domino as the Message Store Feature Parity Between Cisco Unity for Domino and Cisco Unity for Exchange Cisco Unity 5.0 for Domino does not support: • Cisco Unity reports. • The Cisco Unity Inbox. • Using an IMAP e-mail client to access Cisco Unity voice messages. • The secure messaging feature.
CH A P T E R 6 Integrating Cisco Unity with the Phone System See the following sections: • Overview, page 6-1 • How an Integration Works, page 6-2 • Sample Path for a Call from the Phone System to a Subscriber, page 6-8 • General Integration Issues, page 6-9 • Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP), page 6-10 • Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP), page 6-17 • Integrating by Using SIP, page 6-22 • Integrat
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works Cisco Unity can integrate with one or more phone systems at the same time. For details, see 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_g uides_list.html.
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works Lines and Cables to Make Physical Connections Depending on the type of integration, different combinations of lines and cables are used to connect the phone system and Cisco Unity. Integration with Cisco Unified Communications Manager Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager) and SIP proxy servers use network connections that carry all communication to and from Cisco Unity.
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works DTMF Integration with Analog PIMG Units The phone system sends call information, MWI requests, and voice connections through the analog lines, which connect the phone system to the PIMG units. The PIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initiation Protocol (SIP). Figure 6-3 shows the connections for a DTMF integration by using analog PIMG units.
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works Serial (SMDI, MCI, or MD-110) Integration with Analog PIMG Units The phone system sends call information and MWI requests through the data link, which is an RS-232 serial cable that connects the phone system and the master PIMG unit. Voice connections are sent through the analog lines between the phone system and the PIMG units.
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works Figure 6-5 Connections for an Integration by Using TIMG Units Additional slave TIMG units as needed Slave TIMG unit (calls only) LAN/WAN Cisco Unity server T1 digital lines (one or more) RS-232 serial cable Network connections 190676 Phone system Master TIMG unit (SMDI data and calls) DTMF Integration with Voice Cards The circuit-switched phone systems use analog lines to carry voice connections, call information, an
Chapter 6 Integrating Cisco Unity with the Phone System How an Integration Works Connections for a Serial Integration by Using Voice Cards Phone system Cisco Unity server RS-232 serial cable Analog lines 55423 Figure 6-7 Settings in the Phone System and in Cisco Unity For an integration to be successful, Cisco Unity and the phone system must know the connections to use (for example, cables, IP addresses, and channels) and the expected method of communication (for example, IP packets, serial packets,
Chapter 6 Integrating Cisco Unity with the Phone System Sample Path for a Call from the Phone System to a Subscriber If the phone system sends the necessary information and if Cisco Unity is configured correctly, an integration can provide the following integration functionality: • Call forward to personal greeting • Call forward to busy greeting • Caller ID • Easy message access (a subscriber can retrieve messages without entering an ID because Cisco Unity identifies the subscriber based on the e
Chapter 6 Integrating Cisco Unity with the Phone System General Integration Issues The corresponding step for circuit-switched phone systems, when an external call arrives via the PSTN, TI/PRI, DID or LS/GS analog trunks, is for the call to be routed through the phone system to the Cisco Unity voice mail pilot number. 2. The phone system routes the call to an available Cisco Unity extension (a voice messaging port). 3. Cisco Unity answers the call and plays the opening greeting. 4.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) • Circuit-switched phone systems that connect to voice cards and that use an RS-232 serial cable for the integration must be within 50 feet of the Cisco Unity server. For serial cable specifications, see the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuratio n_guides_list.html.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) For information on the compatibility of Cisco Unity and Cisco Unified CM versions with the Cisco Unity-CM TSP and the SIP trunk, see the following documents at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) Integrating Cisco Unity with Multiple Cisco Unified Communications Manager Clusters To integrate Cisco Unity with more than one Cisco Unified CM cluster, you can just re-run the Cisco Unity Telephony Integration Manager, or UTIM. Note the options and considerations detailed in Table 6-2.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) Note • Identity theft of the Cisco Unity voice messaging port, in which a non-Cisco Unity device presents itself to Cisco Unified CM as a Cisco Unity voice messaging port. • Identity theft of the Cisco Unified CM server, in which a non-Cisco Unified CM server presents itself to Cisco Unity voice messaging ports as a Cisco Unified CM server.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) Table 6-3 Cisco Unified Communications Manager Security Features That Are Used by Cisco Unity (continued) Security Feature Description Signaling encryption Uses cryptographic methods to protect (through encryption) the confidentiality of all SCCP signaling messages that are sent between the Cisco Unity voice messaging ports and Cisco Unified CM.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) The process of authentication and encryption of Cisco Unity voice messaging ports is as follows: 1. Each Cisco Unity voice messaging port connects to the TFTP server, downloads the CTL file, and extracts the certificates for all Cisco Unified CM servers. 2.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) Table 6-4 Cisco Unified Communications Manager Cluster Security Mode Settings for Voice Messaging Ports Setting Effect Authenticated The integrity of call-signaling messages will be ensured because they will be connected to Cisco Unified CM through an authenticated TLS port.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) Packetization (SCCP Integrations Only) The Real-Time Transport Protocol (RTP) is used to send and receive audio packets over the IP network. Each discrete packet has a fixed-size header, but the packets themselves can vary in size, depending on the size of the audio stream to be transported (which varies by codec) and the packetization setting.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) Table 6-5 Differences Between SCCP and SIP Integration Methods Feature SCCP SIP Communication method Cisco Unity-CM TSP SIP trunk Failover Supported Not supported Use of SCCP and SIP phones Supported Some SCCP phones may require use of a media termination point (MTP) Support for Cisco Unified CM versions All versions Versions 5.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) Multiple Cisco Unified Communications Manager Express Routers Integrating with a Single Cisco Unity Server A single, centralized Cisco Unity server can be used by multiple Cisco Unified CM Express routers.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) Figure 6-10 IP Cisco Unified Communications Manager Fallback with BRI or PRI SRST Gateway CM Gateway BRI/PRI IP Cisco CallManager WAN AN F Failure Voice-Mail Server WAN 88981 IP When the WAN is down and Cisco Unity has foreign exchange office (FXO) or foreign exchange station (FXS) access connect to a public switched telephone network (PSTN), Cisco Unity
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) Call forward to internal greeting When the Cisco Unified SRST router uses FXO/FXS connections to the PSTN and a call is forwarded from a branch office to Cisco Unity, the internal greeting cannot play. Because the PSTN provides the calling number of the FXO line, the caller is not identified as a subscriber.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating by Using SIP Integrating Cisco Unity with Cisco Unified Communications Manager Express in SRST Mode Cisco Unity supports a topology with centralized call processing and distributed messaging, in which your Cisco Unity server is located at a remote site or branch office and registered with the Cisco Unified CM at a central site. When the WAN link fails, the phones fall back to the Cisco Unified CM Express-as-SRST device.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating by Using SIP • A unique SIP address, which is similar to an e-mail address and uses the format sip:@. The user ID can be either a user name or an E.164 address. When a user initiates a call, a SIP request typically goes to a SIP server (either a proxy server or a redirect server). The request includes the caller’s address (From) and the address of the called party (To).
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units Cisco Unity can integrate with circuit-switched phone systems by using the Dialogic Media Gateway (PIMG or TIMG units) between circuit-switched phone systems and IP networks.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units DTMF Integration with Analog PIMG Units The phone system sends call information, MWI requests, and voice connections through the analog lines, which connect the phone system to the PIMG units. The PIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initiation Protocol (SIP).
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units Figure 6-14 Connections for a Serial (SMDI, MCI, or MD-110) Integration by Using Analog PIMG Units Additional slave PIMG units as needed Slave PIMG unit (calls only) LAN/WAN Analog lines RS-232 serial cable Network connections Note Cisco Unity server 153567 Phone system Master PIMG unit (SMDI data and calls) When you use multiple PIMG units, one PIMG unit must be de
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units Figure 6-15 Connections for an Integration by Using TIMG Units Additional slave TIMG units as needed Slave TIMG unit (calls only) LAN/WAN T1 digital lines (one or more) RS-232 serial cable Network connections Cisco Unity server 190676 Phone system Master TIMG unit (SMDI data and calls) Setup and Configuration For PIMG/TIMG setup and configuration, the installer does t
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units When older versions of Cisco Unity integrated with a circuit-switched phone system by using a serial integration, if the phone system did not use standard serial packets (such as SMDI or MCI), it was possible to adjust the serial packet definitions by using Cisco Unity .avd files.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units The connections for a PIMG integration with Cisco Unity failover are shown in Figure 6-16.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Multiple Phone Systems Assuming there are four phone systems from four different manufacturers (for example, Nortel, Avaya, NEC, and Siemens), four different integrations will be created on the Cisco Unity server to support the four phone systems. Across those four integrations, Cisco Unity can support 144 ports. For example: • At the Seattle site, 15 PIMG units can be stacked to support 122 ports.
Chapter 6 Integrating Cisco Unity with the Phone System Integrating with Multiple Phone Systems Requirements for Integrations with Multiple Phone Systems Cisco Unity has the following requirements for multiple phone system integrations: • All phone system and Cisco Unity server requirements have been met. See the applicable Cisco Unity integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuratio n_guides_list.html.
Chapter 6 Integrating Cisco Unity with the Phone System Optional Integration Features Optional Integration Features See the following sections: • Alternate Extensions, page 6-32 • Alternate MWIs, page 6-33 Alternate Extensions In addition to the primary extension that you specify for each subscriber, you can assign a subscriber up to nine alternate extensions.
Chapter 6 Integrating Cisco Unity with the Phone System Optional Integration Features – A minimum extension length for the extensions entered in the Cisco Unity Assistant. See the Administration—Set the Minimum Length for Subscriber-Defined Alternate Extensions setting. See the Advanced Settings Tool Help for details on using the settings. • You can control whether subscribers can use the Cisco Unity Assistant to view the alternate extensions that you specify in the Cisco Unity Administrator.
Chapter 6 Integrating Cisco Unity with the Phone System Centralized Voice Messaging • The unique subscriber extensions on the non-integrated phone system to forward on no answer to the corresponding phantom extensions on Cisco Unified CM. • The Switch.ini file (phone system configuration file) to enable Cisco Unity access through the serial cable for turning alternate MWIs on and off.
Chapter 6 Integrating Cisco Unity with the Phone System Centralized Voice Messaging For a centralized voice messaging configuration to exist, a suitable inter-phone system networking protocol must exist to deliver a minimum level of feature support, such as: • Message waiting indication (MWI). • Transfer, which ensures that the correct calling/called party ID is delivered to the voice messaging system.
Chapter 6 Integrating Cisco Unity with the Phone System Centralized Voice Messaging Design Guide for Cisco Unity Release 5.
CH A P T E R 7 Cisco Unity Failover and Standby Redundancy See the following sections: • Comparison of Cisco Unity Failover and Standby Redundancy, page 7-1 • Failover, page 7-1 • Standby Redundancy, page 7-2 Comparison of Cisco Unity Failover and Standby Redundancy Cisco Unity failover provides system-malfunction failover within a data center. Failover consists of two servers, a primary and a secondary.
Chapter 7 Cisco Unity Failover and Standby Redundancy Standby Redundancy Configuring Failover When Cisco Unity Servers Are Separated by a Firewall Revised May 6, 2008 When Exchange is the message store, you can separate Cisco Unity primary and secondary servers by a firewall. When IBM Lotus Domino is the message store, the primary and secondary servers cannot be separated by a firewall.
Chapter 7 Cisco Unity Failover and Standby Redundancy Standby Redundancy – Sufficient bandwidth for call traffic to the data center in which the secondary server is installed. • Automatic failover must be disabled when Cisco Unity standby redundancy is configured. Therefore, if the primary server becomes unavailable, the customer must manually make the secondary server active before it begins taking calls.
Chapter 7 Cisco Unity Failover and Standby Redundancy Standby Redundancy • Both Cisco Unity servers must appear on the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html and must belong to the same platform overlay. • There must be a connection of 100 Mbps between the primary and secondary Cisco Unity servers.
Chapter 7 Cisco Unity Failover and Standby Redundancy Standby Redundancy Diagram of a Standby Redundancy Configuration Figure 7-1 shows one possible configuration for a Cisco Unity standby redundancy system.
Chapter 7 Cisco Unity Failover and Standby Redundancy Standby Redundancy Design Guide for Cisco Unity Release 5.
CH A P T E R 8 Voice-Recognition Access to Cisco Unity The Cisco Unity voice-recognition feature lets users navigate the Cisco Unity conversation and manage voice messages by using spoken commands, either by saying the number associated with a menu option or by saying a word or phrase, for example, “play new messages” or “reply to all.” For more information, see the following documentation: • System requirements for voice recognition servers are listed in System Requirements for Cisco Unity Release 5.
Chapter 8 Voice-Recognition Access to Cisco Unity Design Guide for Cisco Unity Release 5.
CH A P T E R 9 Migrating to Cisco Unity from Another Voice-Messaging System When the customer is replacing another voice messaging system with Cisco Unity, consider the following: • How do users interact with each system? For example, the options offered by the Cisco Unity standard conversation (the telephone user interface, or TUI), and the key presses used to accomplish tasks, may be different from what users are accustomed to using.
Chapter 9 • Migrating to Cisco Unity from Another Voice-Messaging System The supporting infrastructure (for example, message store servers), whether dedicated to Cisco Unity or being used by Cisco Unity, must be evaluated for availability and responsiveness. This can be accomplished by helping a customer understand the dependencies Cisco Unity has on the infrastructure, and how Cisco Unity performance or functionality can be affected by loss of connectivity to any of the external dependencies.
I N D EX A alternate extensions alternate MWIs 6-32 2-9 voice messages 2-6 domain controller, access and availability 6-33 3-2 Domino audio codecs Active Directory accounts and permissions affect on file size overview synchronization 3-5 address book 3-5 5-8 address book server 5-4 address book terminology authentication C centralized voice messaging authentication and encryption client access licenses 6-12 integrating Cisco Unity with multiple clusters 6-12 5-7 5-10 deployment
Index E N Exchange name resolution Active Directory considerations considerations network connections 4-5 2-5 network resources, availability 4-7 considerations with Exchange 2007 deployment models 3-1 4-8 4-1 mixed Unified Messaging and Voice Messaging Multi-site WAN with distributed messaging network infrastructure 3-1 4-3 4-2 P phone integration 4-4 alternate extensions 6-32 Unified Messaging with customer-provided infrastructure 4-2 alternate MWIs Voice Messaging with Cisco-prov
Index speech access to Cisco Unity 8-1 standby redundancy compared to failover diagram 7-1 7-5 requirements 7-2 with Exchange 2003 7-3 U Unified Messaging description 2-2 V Voice Messaging description voice recognition 2-2 8-1 Design Guide for Cisco Unity Release 5.
Index Design Guide for Cisco Unity Release 5.