Table Of Contents

Cisco Unity Messaging Integration

System Requirements

Integration Description

Cisco Unity Cisco CallManager Integrated Mailbox Configuration

Securing the Voice-Mail Port

Cisco Unity Configuration Checklist

Where to Find More Information

Cisco Unity Messaging Integration

---

Cisco Unity comprises a Windows 2000-based communications solution that delivers voice messaging and unified messaging in a unified environment.

Unified messaging means that users can manage all message types from the same Inbox. Cisco Unity works in concert with an Exchange server or (for Cisco Unity 4.0(x) and later) a Domino server to collect and store all messages—both voice and e-mail—in one message facility. Users can then access voice and e-mail messages on a computer, through a touchtone phone, or over the Internet.

For complete, step-by-step instructions on how to integrate Cisco CallManager with the Cisco Unity messaging system, refer to the Cisco CallManager 4.1 Integration Guide for Cisco Unity 4.0.

This section covers the following topics:

•System Requirements

•Integration Description

•Cisco Unity Cisco CallManager Integrated Mailbox Configuration

•Securing the Voice-Mail Port

•Cisco Unity Configuration Checklist

•Where to Find More Information

System Requirements

The following lists provide requirements for your phone system and the Cisco Unity server. For specific version information, refer to the Cisco Unity Integration Guide for Cisco Unity.

Phone System

•Cisco CallManager software that is running on a Cisco IP telephony applications server

•Cisco licenses for all phone lines, IP phones, and other H.323-compliant devices or software (such as Cisco Virtual Phone and Microsoft NetMeeting clients) that will be connected to the network, as well as one license for each Cisco Unity port

•IP phones for the Cisco CallManager extensions

•A LAN connection in each location where you will plug an IP phone into the network

Cisco Unity Server

•Cisco Unity system that was installed and made ready for the integration as described in the Cisco Unity Installation Guide.

•A system key with the integration type set to "TAPI" and with the appropriate number of voice-messaging ports enabled (for Cisco Unity 3.1(x) and earlier). If you are integrating Cisco Unity with two phone systems (Cisco CallManager and a second, non-IP phone system), you must set the integration type on the system key to "Multiple Integrations."

•A license that enables the appropriate number of voice-messaging ports

Integration Description

The integration uses the LAN to connect Cisco Unity and Cisco CallManager. The gateway provides connections to the PSTN. Figure 28-1 shows the connections.

Figure 28-1 Connections Between the Phone System and Cisco Unity

The following steps give an overview of the path that an external call takes through the Cisco AVVID network.

1. When an external call arrives, the Cisco gateway sends the call over the LAN to the machine on which Cisco CallManager is installed.

2. For Cisco CallManager lines that are configured to route calls to Cisco Unity, Cisco CallManager routes the call to an available Cisco Unity extension.

3. Cisco Unity answers the call and plays the opening greeting.

4. During the opening greeting, the caller enters either the name of a subscriber or an extension; for example, 1234.

5. Cisco Unity notifies Cisco CallManager that it has a call for extension 1234.

6. At this point, the path of the call depends on whether Cisco Unity is set up to perform supervised transfers or release transfers. Refer to the Cisco CallManager 4.1 Integration Guide for Cisco Unity 4.0 for more information.

Cisco Unity Cisco CallManager Integrated Mailbox Configuration

When Cisco CallManager release 4.1 integrates with Cisco Unity version 4.0(4) (or later) with Microsoft Exchange, Cisco CallManager administrators can create Cisco Unity subscriber voice mailboxes, one at a time, from the Directory Number Configuration or User Configuration windows.

Requirements

•Cisco CallManager release 4.1

•Cisco Unity release 4.0(4) or later with Microsoft Exchange

•Cisco CallManager Integrated Voice Mailbox asp page (installed on the Cisco CallManager server from the Cisco Unity server)

•RIS Data Collector service that is activated on Cisco CallManager server

Restrictions

•After a mailbox is created, no automatic synchronization of mailbox data happens between Cisco Unity and Cisco CallManager. All changes get synchronized manually on both systems.

•The system does not support creation of Internet, VPIM, AMIS, Bridge, or Domino subscriber mailboxes from Cisco CallManager Administration.

•The system does not support bulk or batch import of Cisco Unity mailboxes by using the Bulk Administration Tool (BAT).

•Creation of Cisco Unity mailbox creates a Cisco Unity subscriber account directly in SQL, so new subscribers can be viewed and updated on the Cisco Unity Administrator when the create mailbox transaction completes.

•A log file records Cisco Unity mailbox transactions that are made by using Cisco CallManager Administration on the Cisco Unity server.

•The system writes associated diagnostic logs to a log file.

•Audit log and diagnostic files do not record the transmission of credentials across the network.

Securing the Voice-Mail Port

When you configure security for Cisco CallManager voice mail ports and Cisco Unity SCCP devices, a TLS connection (handshake) opens for authenticated devices after each device accepts the certificate of the other device; likewise, the system sends SRTP streams between devices; that is, if you configure the devices for encryption.

When the device security mode equals authenticated or encrypted, the Cisco Unity TSP connects to Cisco CallManager through the Cisco CallManager TLS port. When the security mode equals nonsecure, the Cisco Unity TSP connects to Cisco CallManager through the Cisco CallManager SCCP port.

For interactions, restrictions, and procedures on how to configure security, refer to the Cisco CallManager Security Guide.

Cisco Unity Configuration Checklist

Table 28-1 provides steps to configure the Cisco Unity voice-messaging system.

Table 28-1 Cisco Unity Configuration Checklist 

Configuration Steps		Procedures and Related Topics
Step 1	Ensure that you have met the system requirements for Cisco CallManager and Cisco Unity.	System Requirements Cisco CallManager 4.1 Integration Guide for Cisco Unity 4.0
Step 2	Add voice-mail ports (directory numbers) for each port that you are connecting to Cisco Unity.	Cisco Voice-Mail Port Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 3	Add a voice-mail pilot number for the voice-mail ports.	Cisco Voice-Mail Pilot Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 4	Specify MWI and voice-mail extensions.	Service Parameters Configuration, Cisco CallManager Administration Guide Message Waiting Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 5	Add the Voice Mail Port DNs to a line group.	Adding a Line Group, Cisco CallManager Administration
Step 6	Add the line group that contains the Voice Mail Port DNs to a hunt list.	Adding a Route List, Cisco CallManager Administration
Step 7	Associate the hunt list that contains the line group with a hunt pilot. Note The hunt pilot must match the voice-mail pilot that is configured and used by the voice-mail profiles.	Adding a Route Pattern, Cisco CallManager Administration Guide
Step 8	Set up the voice-mail profile.	Voice-Mail Profile Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 9	Set up the voice-mail service parameters.	Service Parameters Configuration, Cisco CallManager Administration Guide. Cisco CallManager Integration Guide for Cisco Unity
Step 10	Set up voice-mail ports, so incoming calls are forwarded only to answering ports in Cisco Unity.	Cisco Voice-Mail Port Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 11	For multiple clusters of Cisco CallManager, set up MWI ports.	Message Waiting Configuration, Cisco CallManager Administration Guide Cisco CallManager Integration Guide for Cisco Unity
Step 12	Enable the DTMF relay feature in the gateways.	Cisco CallManager Integration Guide for Cisco Unity
Step 13	Install, configure, and test the TAPI service provider [for Cisco Unity 3.1(x) and earlier].	Cisco CallManager Integration Guide for Cisco Unity
Step 14	Configure Cisco Unity for the integration [for Cisco Unity 3.1(x) and earlier]. Create a new integration between Cisco Unity and Cisco CallManager.	Cisco CallManager Integration Guide for Cisco Unity
Step 15	Test the integration.	Cisco CallManager Integration Guide for Cisco Unity Cisco Unity Troubleshooting Guide Refer to the installation guide for the phone system.
Step 16	Integrate the secondary server for Cisco Unity failover (use when Cisco Unity failover is installed).	Cisco CallManager Integration Guide for Cisco Unity Cisco Unity Failover Guide
Step 17	If using Cisco CallManager Administration to configure voice mail subscribers, perform the following steps [requires Cisco Unity 4.0(4) or later]: •Copy the voicemailbox.asp file to the Cisco CallManager server. •Set up the Cisco Unity Cisco CallManager Integrated Mailbox Configuration administrator account. (This step is required for the failover server if subscribers will be created on the failover server.) •Create a Cisco Unity voice mailbox.	Cisco CallManager Integration Guide for Cisco Unity Configuring Directory Numbers, Cisco CallManager Administration Guide Adding a New User, Cisco CallManager Administration Guide

Where to Find More Information

Additional Cisco Documentation

•Cisco Voice-Mail Port Configuration, Cisco CallManager Administration Guide

•Service Parameters Configuration, Cisco CallManager Administration Guide

•Configuring Directory Numbers, Cisco CallManager Administration Guide

•Creating a Cisco Unity Voice Mailbox, Cisco CallManager Administration Guide

•Cisco CallManager Integration Guide for Cisco Unity

•Cisco Unity Installation Guide

•Cisco Unity Troubleshooting Guide

•Cisco CallManager 4.1 Integration Guide for Cisco Unity 4.0