Help   |   Feedback   |   About   |  
    Deploying and Operating Cisco EGW 2200 Applications
Home Planning Installing Configuring Operating Troubleshooting Reference
  
You Are Here: Planning Cisco Unity Messaging
 
Planning TOC
Getting Started with Planning
Planning Tasks

Assessing the Readiness of Your Network

Identifying the Components You Need
(Compatibility Matrix)
Planning Redundancy
Planning Installation
Planning Provisioning
Concepts for Planning
Cisco EGW Applications Overview
Cisco EGW 2200 Overview
Interwork DPNSS PBXs with Cisco CallManager
Cisco Unity Voice Messaging
Tandem Signaling and Toll Bypass
Overview of DPNSS
Overview of QSIG
Other Documentation
Acronyms
 
 
Cisco Unity Voice Messaging

Introduction
Key Features
How This Application Works

Component List


Introduction

The Cisco EGW 2200 permits DPNSS or QSIG PBXs to take advantage of Cisco Unity's advanced messaging services by providing the necessary signaling and feature interworking between Cisco Unity and the DPNSS or QSIG PBX.

The Cisco EGW 2200 can support one or more Cisco Unity servers and multiple TDM PBXs. The PBXs can be DPNSS or QSIG, but not a mix.

A Cisco SIP Proxy Server may be used between Cisco Unity and the Cisco EGW 2200. In this case, you configure the Cisco EGW interface to the proxy server instead of to the Cisco Unity server; the proxy server is then configured to manage one or more Cisco Unity servers.

There are two generic architectures to be considered when attaching the Cisco Unity to TDM-based networks:

  • Cisco Unity only attachment to a DPNSS or QSIG-based PBX network, shown in Figure 1
  • Cisco Unity and Cisco CallManager integration in a DPNSS or QSIG-based network, shown in Figure 2

Figure 1 depicts the generic architecture for Cisco Unity only attachment to a DPNSS or QSIG-based network. The DPNSS or QSIG PBX interfaces with the IP network through one of the supported access routers (Cisco 2600, 3600, or 3700 class). The access router provides the PBX the physical E1 interface(s) to the IP network, voice packetization, call control through the Cisco EGW 2200 using MGCP and DPNSS or QSIG signaling backhaul over IP from the PBX to the Cisco EGW 2200 and vice versa.

Figure 2 shows a high-level architecture of Cisco Unity and Cisco CallManager integration in a DPNSS or QSIG-based network. As in the previous example, the DPNSS or QSIG PBX interfaces with the IP network through one of the supported access routers (Cisco 2600 or 3700 class). The access router provides the PBX a physical E1 interface to the IP network, voice packetization, call control through the Cisco EGW 2200 using MGCP and DPNSS or QSIG signaling backhaul over IP from the PBX to the Cisco EGW 2200 and vice versa.

The Cisco EGW 2200 performs the following functions:

  • DPNSS or QSIG to SIP signaling interworking
  • Call control across the IP network
  • Feature interworking such as Message Waiting Indicator
  • Centralized policy-based call routing and dial plan management if required
  • Access to advanced voice messaging features such as Auto Attendant

When integrated into a QSIG-based PBX network, it is expected that Cisco CallManager will interface with the QSIG PBX(s) through the QSIG interface on Cisco CallManager. The Unity platform will interoperate with Cisco CallManager using Skinny Client Control Protocol (SCCP). In this scenario, the Cisco EGW 2200 plays no role in signaling interworking between Cisco CallManager and Cisco Unity.

Figure 1. Cisco Unity Messaging Application

For more information on a component in the illustration, point to it. To go to a detailed description, click on it. Click a connector line for information on the interfaces and connections between components.

Figure 2. Cisco Unity and Cisco CallManager Integration in a DPNSS or QSIG-based Network

Skinny Call Connection Protocol (SCCP)  for Cisco Unity to Cisco CallManager cluster communication The Cisco CallManager is the software-based call-processing component of the Cisco IP telephony solution The Cisco CallManager is the software-based call-processing component of the Cisco IP telephony solution DPNSS or QSIG media gateway provides the E1 interface and signaling backhaul Real-Time Tranport Protocol, protocol for bearer transport between the Cisco Unity and media gateway. The Cisco EGW 2200 provides DPNSS/QSIG to SIP interworking for Unity and DPNSS to H.323 interworking for Cisco CallManager DPNSS or QSIG media gateway provides the E1 interface and signaling backhaul You manage the Cisco EGW through a browser application. A Session Initiation Protocol (SIP) interface supports advanced messaging. Cisco Unity provides voice mail, unified messaging, and auto attendant Cisco Unity provides voice mail, unified messaging, and auto attendant DPNSS User Adaptation (DUA) and Stream Controlled Transmission Protocol (SCTP)  provide the communication path for backhauling of DPNSS call control messaging from the PBX/Cisco CallManager media gateway to the Cisco EGW. Call control messaging is backhauled to the EGW using Session Manager (SM) and Reliable UDP (RUDP). The EGW uses MGCP for bearer control of the gateway. A Cisco CallManager cluster is a set of Cisco CallManagers sharing a single database. The cluster serves as an IP PBX The Cisco CallManager is the software-based call-processing component of the Cisco IP telephony solution Interfaces provide advanced calling features: H.323 (intercluster trunk), CTI message interface, AXL for database lookup, and XML for visual notifications on user IP phones DPNSS or QSIG media gateway provides the E1 interface and signaling backhaul Real-Time Tranport Protocol, protocol for bearer transport between the Cisco Unity and media gateway. The Cisco EGW 2200 provides DPNSS/QSIG to SIP interworking for Unity DPNSS or QSIG media gateway provides the E1 interface and signaling backhaul You manage the Cisco EGW through a browser application. A Session Initiation Protocol (SIP) interface supports advanced messaging. Cisco Unity provides voice mail, unified messaging, and auto attendant Cisco Unity provides voice mail, unified messaging, and auto attendant DPNSS User Adaptation (DUA) and Stream Controlled Transmission Protocol (SCTP)  provide the communication path for backhauling of DPNSS call control messaging from the PBX/Cisco CallManager media gateway to the Cisco EGW. Call control messaging is backhauled to the EGW using Session Manager (SM) and Reliable UDP (RUDP). The EGW uses MGCP for bearer control of the gateway. DPNSS or QSIG interworking provided by the Cisco EGW assures feature transparency between Unity and TDM PBXs.

Key Features

The Cisco EGW 2200 permits QSIG or DPNSS PBXs to take advantage of the following Cisco Unity unified messaging services:

Call forward to personal greeting—When an incoming call is routed to an unanswered extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the personal greeting of the subscriber and can leave a message.

Call forward to busy greeting—When an incoming call is routed to a busy extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the busy greeting (if the subscriber enabled it) and can leave a message.

Caller ID—Cisco Unity receives caller ID information from the phone system (if available). This information appears in the subject line of the message in the desktop messaging application.

Easy message access—A subscriber can retrieve messages without entering an ID. Cisco Unity identifies a subscriber based on the extension from which the call originated. A password may be required.

Identified subscriber messaging—Cisco Unity automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.

Message waiting indicator—When a message is waiting for a subscriber, Cisco Unity notifies the phone system to activate the message waiting indicator (MWI) on the subscriber extension.

Auto attendant—Cisco Unity provides support for Auto Attendant. Cisco EGW 2200 provides the ability to interwork Auto Attendant Release Transfers to phones connected to a DPNSS or QSIG PBX, allowing the Auto Attendant function to transfer an incoming call to a specified extension.

Return to top

How This Application Works

The Cisco EGW 2200 provides the DPNSS or QSIG signaling interworking that allows the TDM PBX to use Cisco Unity unified voice messaging. One Cisco EGW (or pair, for fault tolerance) is used to manage one or more Cisco Unity servers and one or more QSIG or TDM PBXs.

A voice-enabled access router serves as the gateway (DPNSS or QSIG media gateway) between the TDM and IP-based PBX networks. The media gateway is physically connected through one or more of its E1 or T1 interfaces to the QSIG or DPNSS PBX. The media gateway interfaces with the IP network through one (or two, for redundancy) of its Ethernet ports. The media gateway performs two functions in the network: packetizing voice for transmission across the IP network and backhauling the QSIG or DPNSS call control signaling over IP to the Cisco EGW 2200. If desired, multiple media gateways can be used for improved fault tolerance. Support is provided for three codecs: G. 711ulaw, G.711alaw, and G.729a. DTMF (dual-tone multi-frequency) relay is also supported.

The Cisco EGW 2200 uses a SIP signaling interface to communicate with the Cisco Unity server. The SIP signaling interface is used to set up calls between Cisco Unity and the Cisco EGW 2200, and to set the Message Waiting Indicator (MWI) status. A SIP trunk is provisioned from the Cisco EGW 2200 to each Cisco Unity server in the network.

Note: SIP authentication is not supported in Cisco EGW 2200 release 1.1(2).

Components List

This application uses the following components. See the Component Chart for hardware and software specifications and see component details for links to overviews and detailed requirements and recommendations for each component.

  • Cisco EGW 2200, in either a single or dual (active/standby) configuration
  • Cisco Unity—Single or (recommended) a redundant pair
  • At least one Cisco QSIG or DPNSS media gateway
  • Optionally, a Cisco SIP Proxy Server
  • For the application shown in Figure 2, a Cisco CallManager cluster with a minimum of one node

Component Details

Return to top

 

Last updated: 27-Oct-2004 5:08 AM