Overview
Issue 2.1 June 2006 1041
Chapter 7: Converting PNs to IP-PNC
This chapter contains modules that describe how to convert some or all port networks (PNs) in
an Avaya communications system from fiber-PNC to IP-PNC. These procedures assume that
an S8500 or S8700-series media server running release 3.0 or later of Communication
Manager controls the communications system.
This chapter includes the following conversion modules:
● Converting some or all direct-connect port networks to IP-connect on page 1047
● Converting some or all CSS port networks to IP-PNC on page 1079
● Converting some or all ATM port networks to IP-PNC on page 1115
!
Important:
Important: Avaya recommends that you perform a traffic analysis when changes from a
fiber-PNC configuration to a mixed configuration that includes both fiber-PNC
and IP-PNC PNs. A traffic analysis helps you understand Inter-PN bearer traffic
and determine the correct number of media processor resources, other network
parameters such as the use of network regions, codec sets, and VLANs. For
more information, see Avaya Application Solutions: IP Telephony Deployment
Guide (555-245-600) and Administration for Network Connectivity (555-233-504).
Overview
The modules in this chapter provide procedures to convert fiber-PNC port networks (PNs) to
IP-PNC PNs in an S8500 or an S8700-series communications system. Fiber-PNC PNs use the
circuit-switched (TDM) protocol to transport bearer traffic (voice, fax, video) between PNs over
fiber-optic cables. IP-PNC PNs use the packet-switched Internet Protocol (IP) to transport
bearer traffic over Ethernet cables.
Note:
Note: The term fiber-PNC (fiber port network connectivity) is used in this document with
almost the same meaning as the term multiconnect. Multiconnect implies a
dedicated control network and fiber-PNC PNs that carry the bearer traffic. The
term fiber-PNC applies to configurations with either a dedicated or a
nondedicated control network.
To Next Page
Loading...
Need help?
General
