Cisco CallManager System Guide, Release 3.1(1) - Cisco DPA Integration [Cisco Unified Communications Manager (CallManager)]

Table Of Contents

Cisco DPA Integration

Understanding the DPA 7630/7610

How the DPA 7630/7610 Works

Why is the DPA 7630/7610 Needed?

Can I Just Use SMDI?

What If I Cannot Use SMDI?

Where to Find More Information

Cisco DPA Integration

The Cisco DPA 7630 and 7610 Voice Mail Gateways (DPA 7630/7610) let you integrate Cisco CallManager systems with Octel voice mail systems, which might also be connected to either Lucent Definity G3 (Definity) or Meridian 1 (Meridian 1) PBX systems. The DPA 7630/7610 lets you use your existing third-party telephony systems along with your Cisco IP telephony system.

For example, you can ensure that features such as message-waiting indicators (MWI) for Octel voice messages are properly set on Cisco IP phones (connected to Cisco CallManager) and traditional telephony phones (connected to Definity or Meridian 1 PBX systems).

Using the DPA 7630/7610, you can integrate the following systems:

•Cisco CallManager 3.0(1) or higher

•Octel 200 and 300 voice messaging systems (using APIC/NPIC integration)

•Octel 250 and 350 voice messaging systems (using FLT-A/FLT-N integration)

•Lucent Definity G3 PBX systems (DPA 7630 only)

•Nortel Meridian 1 PBX systems (DPA 7610 only)

These sections provide you with an overview of the DPA 7630/7610 and its interactions with the other components in traditional and IP telephony networks:

•Understanding the DPA 7630/7610

•How the DPA 7630/7610 Works

Understanding the DPA 7630/7610

The DPA 7630/7610 functions as a gateway between Cisco CallManager and an Octel system (which may be connected to a PBX system), performing these tasks:

•Determines the call type from Cisco CallManager and sends display, light, and ring messages to the Octel system.

•Determines when the Octel system is attempting to transfer, set message waiting indicators (MWI) and so on, and sends the appropriate messages to Cisco CallManager.

•Converts dual-tone multi-frequency (DTMF) tones to Skinny Client Control Protocol (SCCP) messages.

•Provides companding-law transcoding, and voice compression.

•Performs Real-Time Transport Protocol (RTP) encapsulation of the voice message.

How the DPA 7630/7610 Works

With the Cisco DPA 7630/7610, you can integrate your existing Octel voice mail with Cisco CallManager and either a Definity PBX system or a Meridian 1 PBX system. If you have a Definity PBX, use the DPA 7630; if you have a Meridian 1 system, use the DPA 7610.

The DPA 7630/7610 functions by emulating digital phone or PBX systems. This capability allows it to appear like these devices to Cisco CallManager, Octel, Definity, and Meridian 1 systems.

Figure 25-1 illustrates the Cisco DPA.

Figure 25-1 Cisco DPA

Why is the DPA 7630/7610 Needed?

If you want to migrate your telephony system from a Definity G3 PBX or a Meridian 1 PBX to Cisco CallManager, you must decide whether to do a complete cutover to Cisco CallManager or to migrate slowly. If you do a complete cutover to Cisco CallManager and Cisco voice-mail solution, you do not need the DPA 7630/7610. However, if you are slowly migrating your systems, you might want to maintain some phones on the Definity or Meridian 1 PBX while installing new phones on the Cisco CallManager system. You might want to use your existing Octel voice-mail system with your Cisco CallManager system. In these cases, the DPA 7630/7610 can assist your migration to Cisco CallManager.

Can I Just Use SMDI?

Migration presents one difficulty because voice-mail systems such as Octel were designed to integrate to only one PBX at a time. To resolve this difficulty, you can use Simple Message Desk Interface (SMDI), which was designed to enable integrated voice-mail services to multiple clients.

However, to use SMDI, your voice mail system must meet several qualifications:

•It must have sufficient database capacity to support two PBX systems simultaneously and to associate each mailbox with the correct PBX in order to send MWI information on the correct link.

•It must be possible to physically connect the IP network to the voice messaging system while maintaining the existing physical link to the PBX.

•It must support analog integration. SMDI exists primarily as an analog technology.

Additionally, SMDI requires reconfiguration of your existing telephony network.

What If I Cannot Use SMDI?

SMDI might not be an option for you, particularly if you are using a digital interface on your Octel systems. Octel systems with digital line cards emulate digital phones, appearing to the PBX as digital extensions, referred to as per-port or PBX integration cards (PIC). On PIC systems, the voice and data streams (for setting MWI) use the same path. The system sets and clears the MWIs via feature access codes on dedicated ports. Because these PIC ports use proprietary interfaces, you cannot use standard interfaces to connect them to the Cisco CallManager system.

However, the DPA 7630/7610 can translate these interfaces to enable communication among the Cisco CallManager, Octel, and Definity or Meridian 1 systems. Depending on the needs of your network, you can choose among several different integration methods.

Where to Find More Information

Related Topics

•SMDI Voice Mail Integration

Additional Cisco Documentation

•Cisco DPA 7630/7610 Voice Mail Gateways Administration Guide

	Cisco CallManager System Guide, Release 3.1(1)
	Cisco DPA Integration
Cisco CallManager System Guide, Release 3.1(1) Index Preface Introduction Cisco IP Telephony Overview System Configuration Overview System-Level Configuration Settings Clustering Redundancy Call Admission Control Cisco TFTP Device Support Services Auto-Registration Partitions and Calling Search Spaces Understanding Route Plans Understanding the LDAP Directory Managing User Directory Information Media Resource Management Conference Bridges Transcoders Music On Hold Media Termination Points Catalyst DSP Resources for Transcoding and Conferencing SMDI Voice Mail Integration Cisco Unity Messaging Integration Cisco uOne Voice Messaging Integration Cisco DPA Integration Call Park Call Pickup and Group Call Pickup Cisco IP Phone Services Extension Mobility and Phone Login Features Understanding Cisco WebAttendant Custom Phone Rings Understanding Voice Gateways Cisco IP Phones Computer Telephony Integration Administrative Tools Overview Administrative Accounts and Passwords	Download this chapter Cisco DPA Integration Download the complete book PDF Version of Entire Book (PDF - 5 MB) Feedback Table Of Contents Cisco DPA Integration Understanding the DPA 7630/7610 How the DPA 7630/7610 Works Why is the DPA 7630/7610 Needed? Can I Just Use SMDI? What If I Cannot Use SMDI? Where to Find More Information Cisco DPA Integration The Cisco DPA 7630 and 7610 Voice Mail Gateways (DPA 7630/7610) let you integrate Cisco CallManager systems with Octel voice mail systems, which might also be connected to either Lucent Definity G3 (Definity) or Meridian 1 (Meridian 1) PBX systems. The DPA 7630/7610 lets you use your existing third-party telephony systems along with your Cisco IP telephony system. For example, you can ensure that features such as message-waiting indicators (MWI) for Octel voice messages are properly set on Cisco IP phones (connected to Cisco CallManager) and traditional telephony phones (connected to Definity or Meridian 1 PBX systems). Using the DPA 7630/7610, you can integrate the following systems: •Cisco CallManager 3.0(1) or higher •Octel 200 and 300 voice messaging systems (using APIC/NPIC integration) •Octel 250 and 350 voice messaging systems (using FLT-A/FLT-N integration) •Lucent Definity G3 PBX systems (DPA 7630 only) •Nortel Meridian 1 PBX systems (DPA 7610 only) These sections provide you with an overview of the DPA 7630/7610 and its interactions with the other components in traditional and IP telephony networks: •Understanding the DPA 7630/7610 •How the DPA 7630/7610 Works Understanding the DPA 7630/7610 The DPA 7630/7610 functions as a gateway between Cisco CallManager and an Octel system (which may be connected to a PBX system), performing these tasks: •Determines the call type from Cisco CallManager and sends display, light, and ring messages to the Octel system. •Determines when the Octel system is attempting to transfer, set message waiting indicators (MWI) and so on, and sends the appropriate messages to Cisco CallManager. •Converts dual-tone multi-frequency (DTMF) tones to Skinny Client Control Protocol (SCCP) messages. •Provides companding-law transcoding, and voice compression. •Performs Real-Time Transport Protocol (RTP) encapsulation of the voice message. How the DPA 7630/7610 Works With the Cisco DPA 7630/7610, you can integrate your existing Octel voice mail with Cisco CallManager and either a Definity PBX system or a Meridian 1 PBX system. If you have a Definity PBX, use the DPA 7630; if you have a Meridian 1 system, use the DPA 7610. The DPA 7630/7610 functions by emulating digital phone or PBX systems. This capability allows it to appear like these devices to Cisco CallManager, Octel, Definity, and Meridian 1 systems. Figure 25-1 illustrates the Cisco DPA. Figure 25-1 Cisco DPA Why is the DPA 7630/7610 Needed? If you want to migrate your telephony system from a Definity G3 PBX or a Meridian 1 PBX to Cisco CallManager, you must decide whether to do a complete cutover to Cisco CallManager or to migrate slowly. If you do a complete cutover to Cisco CallManager and Cisco voice-mail solution, you do not need the DPA 7630/7610. However, if you are slowly migrating your systems, you might want to maintain some phones on the Definity or Meridian 1 PBX while installing new phones on the Cisco CallManager system. You might want to use your existing Octel voice-mail system with your Cisco CallManager system. In these cases, the DPA 7630/7610 can assist your migration to Cisco CallManager. Can I Just Use SMDI? Migration presents one difficulty because voice-mail systems such as Octel were designed to integrate to only one PBX at a time. To resolve this difficulty, you can use Simple Message Desk Interface (SMDI), which was designed to enable integrated voice-mail services to multiple clients. However, to use SMDI, your voice mail system must meet several qualifications: •It must have sufficient database capacity to support two PBX systems simultaneously and to associate each mailbox with the correct PBX in order to send MWI information on the correct link. •It must be possible to physically connect the IP network to the voice messaging system while maintaining the existing physical link to the PBX. •It must support analog integration. SMDI exists primarily as an analog technology. Additionally, SMDI requires reconfiguration of your existing telephony network. What If I Cannot Use SMDI? SMDI might not be an option for you, particularly if you are using a digital interface on your Octel systems. Octel systems with digital line cards emulate digital phones, appearing to the PBX as digital extensions, referred to as per-port or PBX integration cards (PIC). On PIC systems, the voice and data streams (for setting MWI) use the same path. The system sets and clears the MWIs via feature access codes on dedicated ports. Because these PIC ports use proprietary interfaces, you cannot use standard interfaces to connect them to the Cisco CallManager system. However, the DPA 7630/7610 can translate these interfaces to enable communication among the Cisco CallManager, Octel, and Definity or Meridian 1 systems. Depending on the needs of your network, you can choose among several different integration methods. Where to Find More Information Related Topics •SMDI Voice Mail Integration Additional Cisco Documentation •Cisco DPA 7630/7610 Voice Mail Gateways Administration Guide
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks