cc/td/doc/product/access/sc/nirvdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Overview of the Cisco EGW 2200 Solution Interfaces


Overview of the Cisco EGW 2200 Solution Interfaces


The various interfaces between the devices that comprise this solution are illustrated in Figure 1.

Figure 1 Cisco EGW 2200 Solution Interfaces

The table below identifies the interfaces that connect the devices that are used to create this solution.

Table 1 Device Connections and their Interfaces 

Device Connection
Interfaces

Cisco EGW to/from client browser

A world-wide web interface is provided using HTTP.

Cisco EGW to Cisco CallManager cluster

AVVID XML (AXL)/Simple Object Access Protocol (SOAP)—Used for database lookups to get device names and call forwarding information.

Quick Buffer Encoding (QBE)—Used to query and monitor line states, and to query information about devices for computer telephony integration (CTI) route point data.

eXtensible Markup Language (XML)—Used to update the IP phone display for the Call Back feature.

H.323—

Cisco EGW to/from Cisco Unity (may include a Cisco SIP Proxy Server)

Session Initiation Protocol (SIP) (Cisco SIP Proxy Server is optional)

Cisco EGW to a gatekeeper and/or Cisco CallManager cluster

In Gatekeeper Mode, the H.225 Registration, Admission, and Status (RAS) protocol message set is used for call admission control, bandwidth allocation, and dial pattern resolution (call routing) between Cisco CallManager clusters and H.323 networks.

In Direct Mode, the interface to the Cisco CallManager cluster is handled directly through the H.323, CTI, AXL, or XML interfaces in the Cisco EGW system without any RAS protocol messaging.

Cisco EGW to/from Digital Private Networking Signaling System (DPNSS)/Q Signaling (QSIG) private branch exchange (PBX) or Cisco CallManager voice-enabled media gateway (MGW)

Media Gateway Controller Protocol (MGCP)—Used for bearer channel control. It defines the path from the Cisco EGW to the DPNSS/QSIG PBX/Cisco CallManager voice-enabled MGW.

DPNSS User Adaptation (DUA) and SCTP—Defines the path from the DPNSS PBX/Cisco CallManager voice-enabled MGW to the Cisco EGW for backhauling DPNSS call control messaging.

Session Manager (SM) and Reliable User-Datagram Protocol (RUDP)—Used to backhaul Q.931 call control messaging from the QSIG PBX/Cisco CallManager voice-enabled MGW to the Cisco EGW

Cisco Unity to Cisco CallManager cluster

Skinny Call Connection Protocol (SCCP)

Cisco Unity to DPNSS/QSIG PBX voice-enabled MGW

RTP

DPNSS/QSIG PBX voice-enabled MGW to/from DPNSS/QSIG PBX

E1 interface (DPNSS or QSIG depending on PBX)

PSTN voice-enabled MGW to/from Cisco EGW

MGCP—Used for bearer channel control. It defines the path from the Cisco EGW to the PSTN voice-enabled MGW.

SM and RUDP—Used to backhaul Q.931 call control messaging from PSTN MGW to Cisco EGW

PSTN MGW to PSTN

Primary Rate Interface (PRI) ISDN trunk—Cisco EGW serves as a media gateway controller to the PSTN). Available when a Cisco 5x00 series access server is used as the PSTN MGW.

SIP Proxy Server to/from DPNSS/QSIG PBX voice-enabled MGW

RTP



hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Mar 31 14:54:18 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.