Avaya 555-245-600 Benutzerhandbuch
Evolution from circuit-switched to IP
120 Avaya Application Solutions IP Telephony Deployment Guide
With the S8700 fiber-PNC solution, Avaya is delivering a high-capacity server and a migration
path from DEFINITY. The S8700-series Server uses an industry-standard Linux operating
system on an industry-standard server, which enables all endpoints to use Communication
Manager. This solution allows customers to migrate to IP Telephony and to a higher
performance processor without sacrificing the reliability of the G3r platform.
path from DEFINITY. The S8700-series Server uses an industry-standard Linux operating
system on an industry-standard server, which enables all endpoints to use Communication
Manager. This solution allows customers to migrate to IP Telephony and to a higher
performance processor without sacrificing the reliability of the G3r platform.
There are three stages to upgrading from a DEFINITY G3r to an Avaya Communication
Manager IP PBX:
Manager IP PBX:
1. Replace the G3r processor with industry-standard S8700-series Servers.
2. Add IP circuit packs (C-LAN and Media Processor board) to support IP endpoints.
3. Consolidate multiple systems into a single system to simplify administration. Support
network or processor failure conditions with LSPs deployed at remote sites.
Steps 1 and 2 can be reversed. The next five diagrams show the migration from circuit-switched
DEFINITY to an IP-enabled S8700 fiber-PNC system with server consolidation and LSP
survivability at a remote site.
DEFINITY to an IP-enabled S8700 fiber-PNC system with server consolidation and LSP
survivability at a remote site.
Migration from DEFINITY
Server R to S8700 fiber-PNC
Server R to S8700 fiber-PNC
Phase 1: Processor replacement
This section explains how an existing non-IP Avaya Communication Manager PBX can evolve
to an IP Telephony-based solution. We will examine the case of an existing system that is based
on the traditional PPN/EPN architecture, which will be applicable to all the G3 platforms.
When designing S8700 fiber-PNC systems, there are two options for setting up the call control
network. The control network can be set up on the enterprise LAN or on a private network that is
isolated from the enterprise LAN. See
to an IP Telephony-based solution. We will examine the case of an existing system that is based
on the traditional PPN/EPN architecture, which will be applicable to all the G3 platforms.
When designing S8700 fiber-PNC systems, there are two options for setting up the call control
network. The control network can be set up on the enterprise LAN or on a private network that is
isolated from the enterprise LAN. See
for more information
on setting up an IP network that can support IP Telephony.
The S8700-series Server controls Media Gateways in a different manner than DEFINITY
controlled Port Networks. With DEFINITY, the control path signaling shared the same transport
media as the bearer channels. In a fiber-PNC system, call control signaling is established from
the S8700-series Server over an Ethernet connection to the TN2312BP IP Server Interface
(IPSI) in the IPSI-connected Media Gateway. Non-IPSI connected Port Networks get their
control information from the servers through the Center Stage Switch to one of the Port
Networks that does contain an IPSI. An IPSI can support up to five Port Networks.
The S8700-series Server controls Media Gateways in a different manner than DEFINITY
controlled Port Networks. With DEFINITY, the control path signaling shared the same transport
media as the bearer channels. In a fiber-PNC system, call control signaling is established from
the S8700-series Server over an Ethernet connection to the TN2312BP IP Server Interface
(IPSI) in the IPSI-connected Media Gateway. Non-IPSI connected Port Networks get their
control information from the servers through the Center Stage Switch to one of the Port
Networks that does contain an IPSI. An IPSI can support up to five Port Networks.