| Introduction
Key Features
Application Summaries
Introduction
Cisco EGW 2200 Enterprise
Gateway supports a group of enterprise business
applications that allow you to migrate from legacy
TDM-based voice networks to IP-based telephony
(IPT). Using the Cisco EGW 2200 Enterprise Gateway,
you can:
- Interwork
DPNSS PBXs with Cisco CallManager—The
Cisco EGW 2200 allows you to transition DPNSS
PBX networks to IPT
with Cisco CallManager by interworking signaling
and features between the TDM and IP-based voice
networks. Multiple Cisco CallManager clusters
are supported.
- Attach
Cisco Unity voice messaging to legacy DPNSS
or QSIG PBXs—You can attach
Cisco Unity to DPNSS or QSIG PBXs, allowing
you to take advantage of its advanced messaging
services. The Cisco EGW 2200 interworks the
TDM-based signaling with Cisco Unity's SIP interface,
providing auto-attendant and message waiting
indicator services to end users with QSIG or
DPNSS PBXs.
- Provide
Tandem Signaling and Toll Bypass Services—You
can replace a legacy DPNSS or QSIG TDM mesh
network with an IP communications network. Doing
so permits you to take advantage of the cost
savings provided by toll bypass networks, and
can offer important services such as policy-based
routing, centralized dial plan provisioning,
and tandem PBX replacement. All DPNSS and QSIG
features are supported transparently.
These applications can be implemented
individually or in combination (see Figure 1 below).
Optionally, any business application can include
a centralized PSTN
interconnect to the public switched
telephone network (PSTN) through a PRI ISDN trunk.
Note: The illustration
shows the use of a gatekeeper and the registration,
admission, and status protocol for the H.323 interface
between Cisco EGW 2200 and Cisco CallManager.
The gatekeeper is optional; small networks can
use H.323 direct mode without a gatekeeper.
Figure 1. Combination of IP PBX,
Cisco Unity Voice Messaging, and PSTN Interconnect
Applications
|
Return to top
Key Features
The Cisco EGW 2200 provides the following
key features:
- The Cisco EGW 2200 applications
run on select Intel-based Cisco platforms Media Convergence
Servers (Cisco MCS). These are the same platforms
used by other AVVID products.
- Simplified installation, provisioning,
and management of key components on the Cisco EGW
2200 through use of Cisco's network appliance model:
- Software is preloaded and configured on first
use through configuration wizards.
- Provisioning and administration are done using
browser-accessible applications.
- Upgrades are browser-accessible
with electronic notification of new releases.
- Support for the most commonly
used DPNSS calling features (based on BTNR188 Issue
5):
- Add-on Conference
- Basic call
- Call Back When Free
- Call Back When Next Used
- Call Forward
- Call Hold
- Call Offer
- Call Redirection
- Call Waiting
- Calling Name Display
- Centralized Operator
- Diversions
- Extension Status
- Loop Avoidance
- Message Waiting Indicator
- Night Service
- Non-Specified Field
- Route Optimization
- Three Party Service: Shuttle,
Transfer, and Add-on
Note:
When DPNSS features are interworked between a legacy
DPNSS PBX network and Cisco CallManager, the implementation
of those features mimics the implementation of the features
in a DPNSS network. For details and any exceptions,
see Overview
of DPNSS Features .
The Cisco EGW 2200 also provides these
other capabilities:
- Call routing and number analysis
- Call limiting, so that you can
specify a call limit (maximum number of calls) on
the media gateway, H.323 interface to Cisco CallManager,
or the Unity SIP interface
- Policy-based routing including:
- Direct routing
- Time-of-day routing
- Holiday routing
- Percentage-based routing
- Attachment of Cisco Unity unified
messaging products to DPNSS and QSIG PBXs, providing
Auto Attendant and Message Waiting Indication services.
- Ability to serve as a centralized
access point to the PSTN using Cisco AS5000-series
gateways
- Availability in single or continuous
service dual (active/standby) configurations
- Standards that conform to best
practices recommended for PBX to IP migration
Application Summaries
IP PBX—Interwork
DPNSS PBXs with Cisco CallManager
This application provides a
transition to IP telephony by adding an IP PBX Cisco
CallManager cluster that can interwork with your existing
DPNSS PBXs.
>>
More details and illustration
Cisco
Unity Voice Messaging—Attach
Cisco Unity to Legacy DPNSS or QSIG PBXs
Cisco Unity advanced voice messaging
(voice mail, unified messaging, and auto attendant )
can be added to DPNSS or QSIG TDM PBXs. The Cisco EGW
provides signaling interworking between Unity's Session
Initiation Protocol (SIP) interface and the TDM PBXs.
TDM PBXs can be either DPNSS or QSIG, but not a mix.
You can also add Cisco Unity messaging
to your IP PBX application. In the case of the IP PBX,
the Cisco EGW provides signaling interworking for Unity's
SIP interface and for the Cisco CallManager's H.323
interface to the DPNSS or QSIG PBXs.
>>
More details and illustration
Tandem
Signaling and Toll Bypass—Deploy
TDM PBXs over IP network
In this application, TDM PBXs are
IP-enabled through use of a voice-enabled router referred
to as a DPNSS or QSIG media gateway. For TDM PBX-to-PBX
calling, signaling is backhauled to the Cisco EGW which
performs call setup. Unlike applications with TDM and
IP PBXs, this application does not require DPNSS or
QSIG interworking between the TDM and IP worlds. Instead,
it uses transparent transmission of the signaling from
one PBX to another over the IP network. The Cisco EGW
performs call control between the TDM PBXs on the IP
network, and can provide advanced centralized call routing
that simplifies PBX network dial plans. All DPNSS and
QSIG features are supported transparently.
Using the IP communications network
provides improved, simplified central call control and
toll bypass.
TDM PBXs can be DPNSS or QSIG, but
not a mix.
>>
More details and illustration
(Optional
with Any Application) PSTN Interconnect—Add
PSTN Access
You can provide PSTN access for the
PBXs by having the Cisco EGW serve as a gateway to the
PSTN through a PRI ISDN trunk. The trunk is terminated
on a separate media gateway (referred to as a PRI gateway).
Return
to top
|