Administering Network Connectivity on Avaya Aura ......Administering Network Connectivity on Avaya...

Administering Network Connectivity on Avaya Aura™ Communication Manager

555-233-504Issue 14

May 2009

© 2009 Avaya Inc.All Rights Reserved.

NoticeWhile reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.For full legal page information, please see the documents, Avaya Support Notices for Software Documentation, 03-600758, andAvaya Support Notices for Hardware Documentation, 03-600759.These documents can be accessed on the documentation CD and on the Web site, http://www.avaya.com/support. On the Web site, search for the document number in the Search box.

Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.

WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site:http://www.avaya.com/support.

CopyrightExcept where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support.

http://www.avaya.com/supporthttp://www.avaya.com/supporthttp://www.avaya.com/support/

Issue 14 May 2009 3

Contents

Chapter 1: Networking overview . . . . . . . . . . . . . . . . . . . . . . 11About “network” terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About digital telephone calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About network regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Establishing inter-switch trunk connections . . . . . . . . . . . . . . . . . . . . 13

Interconnecting port networks . . . . . . . . . . . . . . . . . . . . . . . . . . 13Networking branch offices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Control networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Enabling spanning tree protocol (STP) . . . . . . . . . . . . . . . . . . . . . 14Inter-Gateway Alternate Routing (IGAR) . . . . . . . . . . . . . . . . . . . . . 15Dial Plan Transparency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Network quality management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About VoIP-transmission hardware . . . . . . . . . . . . . . . . . . . . . . . . . 16

Processor Ethernet (PE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Support for Processor Ethernet and Port Networks on an ESS server . . 17Firmware for optimal performance . . . . . . . . . . . . . . . . . . . . . . 18

Providing LAN security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Connection Preservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Session refresh handling . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Connection Preserving Migration . . . . . . . . . . . . . . . . . . . . . . . . 20

H.248 and H.323 Link Recovery . . . . . . . . . . . . . . . . . . . . . . . . 20Auto fallback to primary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Local Survivable Processor (LSP) . . . . . . . . . . . . . . . . . . . . . . 21Enterprise Survivable Server (ESS) . . . . . . . . . . . . . . . . . . . . . 21Standard Local Survivability (SLS) . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2: Port network configurationswith S8500-series and S8700-series Servers. . . . . . . . . 23

Fiber-PNC and IP-PNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

S8500-series Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24S8700-series Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

S8500-series IP-PNC (single control network) . . . . . . . . . . . . . . . . . . 26Duplicated TN2602AP circuit packs in IP-PNC PNs . . . . . . . . . . . . . 27

S8500-series direct-connect (single control network) . . . . . . . . . . . . . 29TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 31Rules for TN570B circuit pack placement with SCC1/MCC1 Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents

4 Administering Network Connectivity on Avaya Aura™ Communication Manager

S8700-series IP-PNC (single control network) . . . . . . . . . . . . . . . . . . 33S8700-series IP-PNC (duplicated control network) . . . . . . . . . . . . . . . 36S8700-series IP-PNC (duplicated control and duplicated bearer network) . . 38S8700-series direct-connect (single control network) . . . . . . . . . . . . . 40

TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 42S8700-series direct-connect (duplicated control network) . . . . . . . . . . . 44S8700-series direct-connect (duplicated control and bearer networks) . . . . 46

Rules for TN570B circuit pack placement with SCC1/MCC1 Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

S8700-series Center Stage Switch (single control network) . . . . . . . . . . 50TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 52

S8700-series Center Stage Switch (duplicated control network) . . . . . . . . 55TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 55

S8700-series Center Stage Switch (duplicated control and bearer networks) 58TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 58

S8700-series ATM Switch (single control network) . . . . . . . . . . . . . . . 61TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 61

S8700-series ATM Switch (duplicated control networks) . . . . . . . . . . . . 66TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 66

S8700-series ATM Switch (duplicated control and bearer networks) . . . . . 69TN2602AP circuit packs for duplicated bearer. . . . . . . . . . . . . . . . 69

Distance options with fiber-optic connections . . . . . . . . . . . . . . . . . 72Fiber connections up to 200 feet (61 meters) . . . . . . . . . . . . . . . . 72Fiber connections up to 22 miles (35.4 kilometers) . . . . . . . . . . . . . 74Fiber connection up to 200 miles . . . . . . . . . . . . . . . . . . . . . . . 76Metallic cable for intracabinet connections . . . . . . . . . . . . . . . . . 77

Configurations with both IP-PNC and fiber-PNC PNs . . . . . . . . . . . . . . . . 78Possibilities for combining IP-PNC and fiber-PNC PNs in a configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Media gateway combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Options for multiple levels of reliability . . . . . . . . . . . . . . . . . . . . . 82

Administering an S8700-series Server for duplicated and single control networks . . . . . . . . . . . . . . . . . . . . . . . . . 82

Dedicated and non-dedicated control networks. . . . . . . . . . . . . . . . . 82Requirements for using both IP-PNC and fiber-PNC PNs. . . . . . . . . . . . 82

TN2602AP circuit packs in fiber-PNC PNs . . . . . . . . . . . . . . . . . . 84Examples of combining IP-PNC and fiber-PNC PNs . . . . . . . . . . . . . . 84

Example of combining direct- and IP-PNC PNs . . . . . . . . . . . . . . . 84Example of IP-PNC PNs with different reliability levels . . . . . . . . . . . 86Example of combining IP- and fiber-PNC PNs with different reliability levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Contents

Issue 14 May 2009 5

Example of combining IP- and ATM-connected PNs and different reliability levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

MCC1 Media Gateway with IP-PNC PNs or a combination of IP-and fiber-PNC PNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Options for IP-PNC PNs in an MCC1 Media Gateway . . . . . . . . . . . . 94Options for combined IP- and fiber-PNC PNs in an MCC1 MediaGateway (single control network) . . . . . . . . . . . . . . . . . . . . . . 95

Options for combined IP- and fiber-PNC PNs in an MCC1 MediaGateway (duplicated control networks) . . . . . . . . . . . . . . . . . . . 95

Options for combined IP- and fiber-PNC PNs in an MCC1 MediaGateway (duplicated control and bearer networks) . . . . . . . . . . . . 96

Example of MCC1 IP-PNC . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Example of MCC1 with IP- and fiber-PNC PNs . . . . . . . . . . . . . . . . 99

ESS support for combined IP- and fiber-PNC PNs . . . . . . . . . . . . . . . 102

Chapter 3: Control Networks for S8700-Series and S8500-series Servers 103Combining fiber-PNC and IP-PNC in a single configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Layer 2 connectivity options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Layer 3 connectivity options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Control network C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

CNC configuration: Multi-site private CNA, CNB, with remote PNs on the enterprise LAN . . . . . . . . . . . . . . . . . . . . 109

Control network on customer LAN (CNOCL) . . . . . . . . . . . . . . . . . . . . 111CNOCL configuration — not recommended . . . . . . . . . . . . . . . . . . . . . 117

Network administration for Figure 32. . . . . . . . . . . . . . . . . . . . . 118Preferred CNOCL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Network administration for Figure 33. . . . . . . . . . . . . . . . . . . . . 120

Chapter 4: Administering converged networks . . . . . . . . . . . . . . 121About Voice over IP converged networks . . . . . . . . . . . . . . . . . . . . . . 121

Providing a network assessment . . . . . . . . . . . . . . . . . . . . . . . . . 122Setting up VoIP hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

About Universal DS1 circuit packs andMM710 T1/E1Media Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Working with echo cancellation . . . . . . . . . . . . . . . . . . . . . . . 123Administering echo cancellation on the DS1 circuit packor MM710 media module . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Administering echo cancellation on trunks . . . . . . . . . . . . . . . . . 126About the TN799DP Control LAN . . . . . . . . . . . . . . . . . . . . . . . . 128

Physical addressing for the C-LAN board . . . . . . . . . . . . . . . . . . 128

Contents


IP addressing techniques for the C-LAN board . . . . . . . . . . . . . . . 129Installing the TN799DP C-LAN . . . . . . . . . . . . . . . . . . . . . . . . 129Administering the C-LAN bus bridge (Avaya DEFINITY Server csi only) . 129Installing C-LAN cables to a hub or ethernet switch . . . . . . . . . . . . 130Assigning IP node names . . . . . . . . . . . . . . . . . . . . . . . . . . 131Defining a LAN default gateway . . . . . . . . . . . . . . . . . . . . . . . 132Setting up Alternate Gatekeeper andC-LAN load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

About the TN2302AP IP Media Processor . . . . . . . . . . . . . . . . . . . . 134Improving theTN2302AP transmission interface . . . . . . . . . . . . . . 135Supporting TN2302AP hairpinning . . . . . . . . . . . . . . . . . . . . . . 135Testing TN2302AP ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Enabling a survivable remote EPN . . . . . . . . . . . . . . . . . . . . . . 135

About the TN2602AP IP Media Resource 320 . . . . . . . . . . . . . . . . . . 135Load balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Bearer duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Combining duplication and load balancing . . . . . . . . . . . . . . . . . 137Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Firmware download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138I/O adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

About the TN2312BP IP Server Interface (IPSI) . . . . . . . . . . . . . . . . . 139Detailed description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Firmware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140IP Server Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 140Communication Manager alarm on settings mismatch . . . . . . . . . . . 141Default settings of IPSI QoS parameters . . . . . . . . . . . . . . . . . . . 142Backward compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

About the MM760 VoIP Media Module . . . . . . . . . . . . . . . . . . . . . . 143MM760 Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Voice compression on the MM760 . . . . . . . . . . . . . . . . . . . . . . 143TN8400AP Server circuit pack . . . . . . . . . . . . . . . . . . . . . . . . 144TN8412AP S8400 server IP Interface . . . . . . . . . . . . . . . . . . . . . 144

Administering Avaya gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Administering IP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Administering SIP trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Administering H.323 trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Setting up H.323 trunks for administration . . . . . . . . . . . . . . . . . 147Completing H.323 trunk administration . . . . . . . . . . . . . . . . . . . 159Dynamic generation of private/public calling party numbers. . . . . . . . 167

Administering Avaya phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Contents

Issue 14 May 2009 7

Administering IP Softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Administering a Telecommuter phone . . . . . . . . . . . . . . . . . . . . 169Administering a Road-warrior phone. . . . . . . . . . . . . . . . . . . . . 171

Installing and administering Avaya IP telephones . . . . . . . . . . . . . . . 172About the 4600-series IP telephones . . . . . . . . . . . . . . . . . . . . . 173About the 9600-series IP telephones . . . . . . . . . . . . . . . . . . . . . 173About the 1600-series IP telephones . . . . . . . . . . . . . . . . . . . . . 174About IP telephone hardware/software requirements. . . . . . . . . . . . 174Administering Avaya IP telephones . . . . . . . . . . . . . . . . . . . . . 176

About hairpinning and shuffling . . . . . . . . . . . . . . . . . . . . . . . . . 177What hardware and endpoints are required . . . . . . . . . . . . . . . . . 178About shuffled audio connections . . . . . . . . . . . . . . . . . . . . . . 178Examples of shuffling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179About hairpinned audio connections. . . . . . . . . . . . . . . . . . . . . 181Example of a hairpinned call . . . . . . . . . . . . . . . . . . . . . . . . . 182

Hairpinning and shuffling administration interdependencies . . . . . . . . . 184About Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . 185

What are the types of NAT . . . . . . . . . . . . . . . . . . . . . . . . . . 186What are the issues between NAT and H.323 . . . . . . . . . . . . . . . . 187About the Communication Manager NAT Shuffling feature . . . . . . . . 187

Administering hairpinning and shuffling. . . . . . . . . . . . . . . . . . . . . 188Choosing how to administer hairpinning and shuffling. . . . . . . . . . . 188Administering hairpinning and shuffling at the system-level. . . . . . . . 189Administering hairpinning and shuffling in network regions. . . . . . . . 191Administering H.323 trunks for hairpinning and shuffling . . . . . . . . . 194Administering IP endpoints for hairpinning and shuffling . . . . . . . . . 195

Administering FAX, modem, TTY, and H.323 clear channel calls over IP Trunks . 198What is relay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198What is pass-through mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Overview of steps to administer FAX, TTY, modem, and clear channel calls over IP trunks . . . . . . . . . . . . . . . . . . . . . 200

FAX, TTY, modem, and clear channel transmission modes and speeds . . . 202Considerations for administering FAX, TTY, modem, and clear channel transmission . . . . . . . . . . . . . . . . . . . . . . . . . 205

Bandwidth for FAX, modem, TTY, and clear channel calls over IP networks . 208Media encryption for FAX, modem, TTY, and clear channel . . . . . . . . . . 209

SRTP media encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Administering SRTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Contents


Chapter 5: Voice and Network quality administration . . . . . . . . . . 213About factors causing voice degradation . . . . . . . . . . . . . . . . . . . . . . 214

Packet delay and loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Echo cancellers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Echo cancellation plans (TN464HP/TN2464CP circuit packs) . . . . . . . 217Echo cancellation plans (TN464GP/TN2464BP circuit packs) . . . . . . . 218

Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

About Quality of Service (QoS) andvoice quality administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Layer 3 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222RSVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Layer 2 QoS: 802.1p/Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Using VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Administering IP CODEC sets . . . . . . . . . . . . . . . . . . . . . . . . . . 226Administering IP network regions . . . . . . . . . . . . . . . . . . . . . . . . 234

Defining an IP network region . . . . . . . . . . . . . . . . . . . . . . . . 236Call Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Setting up Inter-Gateway Alternate Routing (IGAR) . . . . . . . . . . . . . 247Setting up Dial Plan Transparency . . . . . . . . . . . . . . . . . . . . . . 248Network Region Wizard (NRW) . . . . . . . . . . . . . . . . . . . . . . . . 251Manually interconnecting the network regions . . . . . . . . . . . . . . . 252Administering inter-network region connections . . . . . . . . . . . . . . 253Pair-wise administration of IGAR between network regions . . . . . . . . 254Port network to network region mapping for boards other than IP boards 256Status of inter-region usage . . . . . . . . . . . . . . . . . . . . . . . . . 257Reviewing the network region administration . . . . . . . . . . . . . . . . 258

Setting network performance thresholds . . . . . . . . . . . . . . . . . . . . 258Enabling spanning tree protocol (STP). . . . . . . . . . . . . . . . . . . . 260

Adjusting jitter buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Configuring UDP ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

About Media Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263What is Media Encryption? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263What are the limitations of Media Encryption? . . . . . . . . . . . . . . . . . 264What types of media encryption are available? . . . . . . . . . . . . . . . . . 264Is there a license file requirement?. . . . . . . . . . . . . . . . . . . . . . . . 267Is Media Encryption currently enabled? . . . . . . . . . . . . . . . . . . . . . 267Administering Media Encryption . . . . . . . . . . . . . . . . . . . . . . . . . 268

Contents

Issue 14 May 2009 9

Administering Media Encryption for IP Codec Sets . . . . . . . . . . . . . 268Administering Media Encryption for signaling groups . . . . . . . . . . . 270Viewing encryption status for stations and trunks . . . . . . . . . . . . . 272

About legal wiretapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272About possible failure conditions . . . . . . . . . . . . . . . . . . . . . . . . 272How does Media Encryption interact with other features? . . . . . . . . . . . 273

Network recovery and survivability . . . . . . . . . . . . . . . . . . . . . . . . . 274About network management . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Monitoring network performance . . . . . . . . . . . . . . . . . . . . . . . 274Controlling QoS policies . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

About H.248 link loss recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 277Auto fallback to primary controller for H.248 media gateways . . . . . . . 277Basic feature operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279G250 interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280G350 interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280G700 interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Older media gateway loads . . . . . . . . . . . . . . . . . . . . . . . . . . 281Administering auto fallback to primary . . . . . . . . . . . . . . . . . . . 281

Administrable IPSI Socket Sanity Timeout. . . . . . . . . . . . . . . . . . . . 288Enterprise Survivable Servers (ESS) . . . . . . . . . . . . . . . . . . . . . . . 289Improved Port Network Recovery from Control Network Outages. . . . . . . 291Port Network Recovery Rules screen . . . . . . . . . . . . . . . . . . . . . . 292

No Service Time Out Interval . . . . . . . . . . . . . . . . . . . . . . . . . 293Field description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293PN Cold Reset Delay Timer (sec) . . . . . . . . . . . . . . . . . . . . . . . 293

Configuration impacts on availability . . . . . . . . . . . . . . . . . . . . . . . . 293Survivability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Contents


Issue 14 May 2009 11

Chapter 1: Networking overview

This chapter provides background information to help you understand and use the information in this book. Telephony delivered over digital networks capitalizes on the flexibility of technology itself, and can be implemented in a variety of ways. Users might find that they need to reference only a portion of the information in this book. Other readers might need most of its information before understanding how to tailor a telephony network to suit their needs.

About “network” terminologyThe Communication Manager network can contain multiple interconnected servers and all of the equipment, including data networking devices, controlled by those servers. Such equipment may be geographically dispersed among a variety of sites, and the equipment at each site may be segregated into distinct logical groupings, referred to as network regions. A single server system has one or more network regions. Each network region is a logical grouping of endpoints, including stations, trunks, and media gateways. In cases where one server is insufficient for controlling all of the equipment, multiple systems can be networked together. So, one or more network region(s) comprise a site, and one or more sites comprise a system, which in turn is a component of a network.For the purposes of this book and to clarify what we mean by the word, consider these uses of the word “network”:

● Businesses often have a “corporate network,” meaning a Local Area Network (LAN) or a Wide Area Network (WAN), over which they distribute E-mail, data files, run applications, access the Internet, and send and receive fax and modem calls.

We use non-dedicated to describe this type of network and the traffic that it bears. This means that the network is a heterogeneous mix of data types.

● When a non-dedicated network carries digitized voice signals along with other data types, we call this a converged network, because it is a confluence of voice and non-voice data.

● Network segments that exclusively carry telephony traffic are dedicated, since they carry only telephony-related information.

● When a digital network carries telephony and non-telephony data in a packet-switched (TCP/IP), instead of a circuit-switched (TDM) environment, we call this an IP network.

Networking overview


About digital telephone callsA digital phone call consists of voice (bearer) data and call-signaling messages. Some transmission protocols require sending signaling data over a separate network, virtual path, or “channel,” from the voice data. The following list describes the data that are transmitted between switches during a phone call:

● Voice (bearer) data — digitized voice signals

● Call-signaling data — control messages

- Set up the call connection

- Maintain the connection during the call

- Tear down the connection when the call is finished

● Distributed Communications System (DCS) signaling data — an Avaya DEFINITY® Server proprietary signaling protocol also supported by Avaya IP Telephony Systems.

Distributed Communications System (DCS) allows two or more communications switches to be configured as if they were a single switch. DCS provides attendant and voice-terminal features between these switch locations. DCS simplifies dialing procedures and allows transparent use of some Communication Manager features. Feature transparency means that features are available to all users on DCS regardless of the switch location.

About network regionsA network region is a group of IP endpoints that share common characteristics and resources. Every IP endpoint on the Communication Manager system belongs to a network region.By default, all IP endpoints are in network region 1. If left that way, all IP endpoints would all share the same characteristics defined by network region 1 and use the same resources. But in many cases, this is not sufficient to allow for certain differences that may be based upon location or network characteristic, and therefore multiple network regions should be configured.The most common of these cases are:

● One group of endpoints requires a different CODEC (COder-DECoder) set than another group.

This could be based on requirements related to bandwidth or encryption.

● Calls between separate groups of endpoints require a different codec set than calls within a single group of endpoints, again based on requirements related to bandwidth or encryption.

● Specific C-LAN or MedPro or other resources must be accessible to only a specific group of endpoints.

Establishing inter-switch trunk connections


● One group of endpoints requires a different UDP port range or QoS parameters than another group.

● One group of endpoints reports to a different VoIP Monitoring Manager server than another group.

Somewhat related to network regions is the concept of locations. The location parameter is used to identify distinct geographic locations, primarily for call routing purposes. In other words, the location parameter is used primarily to ensure that calls access the proper trunks, based on the origin and destination of each call.

Establishing inter-switch trunk connectionsConnected switches enable people within an enterprise to communicate easily with one another, regardless of their physical location or the particular communications server they use. Inter-switch connections also provide shared communications resources such as messaging and Call Center services. Switches communicate with each other over trunk connections. There many types of trunks that provide different sets of services. Commonly-used trunk types are:

● Central Office (CO) trunks that provide connections to the public telephone network through a central office.

● H.323 trunks that transmit voice and fax data over the Internet to other systems with H.323 trunk capability.

H.323 trunks that support DCS+ and QSIG signaling.

● Tie trunks that provide connections between switches in a private network.

These and other common trunk types are described in the Administering Avaya Aura™ Communication Manager, 03-300509.

Interconnecting port networks

Note:Note: See Chapter 2: Port network configurations with S8500-series and S8700-series

Servers on page 23 for detailed examples of IP-connected (IP-PNC) and fiber-connected (fiber-PNC) port networks.

Avaya systems with more than three fiber-connected port networks (fiber-PNC, formerly called "Multi-Connect") must use a center stage switch (CSS) or an ATM configuration to interconnect the port networks.

Networking overview


Networking branch officesFor Communication Manager environments, The MultiVOIP™ voice over IP gateways (Multi-Tech Systems, Inc.) provide distributed networking capabilities to small branch offices of large corporations. MultiVOIP extends the call features of a centralized Avaya Server and provides local office survivability to branch offices of up to 15 users using analog or IP phones.For more information, see: http://www.multitech.com/PARTNERS/Alliances/Avaya/.

Control networksControl networks are the networks over which servers, such as the S8700-series or S8500-series Servers, exchange signaling data with the port networks through the IPSI circuit packs.With Communication Manager 3.0 and later, Avaya extends “Control Network on Customer LAN” functionality to simplify network configuration by allowing both IP-PNC and fiber-PNC port networks in a single configuration. With this combined port network functionality, enterprises can attach IP-connected, ATM-connected, or center-stage-connected port networks to their S8700-series or S8500-series servers. To support combined port networks, Avaya has enhanced the flexibility of control networks for port network attachment. In addition to private control networks A and B, Avaya allows the “Customer LAN” Ethernet interface to be used as a third, public control network, control network C.

Note:Note: See Chapter 3: Control Networks for S8700-Series and S8500-series Servers on

page 101 for more information about control networks.

Enabling spanning tree protocol (STP)Spanning Tree Protocol (STP) is a loop avoidance protocol. If you don't have loops in your network, you don't need STP. The "safe" option is to always leave STP enabled. Failure to do so on a network with a loop (or a network where someone inadvertently plugs the wrong cable into the wrong ports) can lead to a complete cessation of all traffic. However, STP is slow to converge after a network failure, and slow to allow a new port into the network (~50 sec by default). A modified version of STP, Rapid Spanning Tree converges faster than the earlier STP, and enables new ports much faster (sub-second) than the older protocol. Rapid Spanning Tree works with all Avaya equipment, and is recommended by Avaya.

http://www.multitech.com/PARTNERS/Alliances/Avaya/

Network quality management


Inter-Gateway Alternate Routing (IGAR)For single-server systems that use the IP-WAN to connect bearer traffic between port networks or media gateways, Inter-Gateway Alternate Routing (IGAR) provides a means of alternately using the PSTN when the IP-WAN is incapable of carrying the bearer connection. IGAR may request that bearer connections be provided by the PSTN under the following conditions:

● The number of calls allocated or bandwidth allocated via Call Admission Control- Bandwidth Limits (CAC-BL) has been reached.

● VoIP RTP resource exhaustion in a MG/PN is encountered.

● A codec set is not specified between a network region pair.

● Forced redirection between a pair of network regions is configured.

IGAR takes advantage of existing public and private-network facilities provisioned in a network region. Most trunks in use today can be used for IGAR. Examples of the better trunk facilities for use by IGAR would be:

● Public or Private ISDN PRI/BRI

● R2MFC

IGAR provides enhanced Quality of Service (QoS) to large distributed single-server configurations.

Dial Plan TransparencyDial Plan Transparency (DPT) preserves the dial plan when a media gateway registers with an LSP or when a port network registers with an ESS due to the loss of contact with the primary controller. DPT establishes a trunk call and reroutes the call over the PSTN to connect endpoints that can no longer connect over the corporate IP network.

Network quality managementA successful Voice over Internet Protocol (VoIP) implementation involves quality of service (QoS) management that is impacted by three major factors:

● Delay: Significant end-to-end delay may result in echo and talker overlap.

● Packet Loss: Under peak network loads and periods of congestion, voice data packets may be dropped.

● Jitter (Delay Variability): Jitter results when data packets arrive at their destination at irregular intervals as a result of variable transmission delay over the network.

Networking overview


Note:Note: For more information about these QOS factors and network quality management,

see:

- Chapter 5: Voice and Network quality administration on page 213

- Avaya Application Solutions: IP Telephony Deployment Guide, 555-245-600

About VoIP-transmission hardwareThe following circuit packs are essential in an Avaya telecommunications network. For more information about these and other Avaya hardware devices, see Avaya Aura™ Communication Manager Hardware Description and Reference, 555-245-207.For information about the administration tasks for this equipment, see Setting up VoIP hardware on page 123.

● TN799DP control LAN (C-LAN) interface

The TN799DP control LAN (C-LAN) interface provides TCP/IP connectivity over Ethernet between servers and gateways or Point to Point Protocol (PPP) between servers and adjuncts.

● TN2312BP IP Server Interface (IPSI)

The IPSI provides for the transport of control messages between servers and port networks.

● TN2302AP IP Media Processor and TN2602AP IP Media Resource 320

The TN2302AP and TN2602AP provide high-capacity VoIP audio access to the switch for local stations and outside trunks.

● TN8400AP Server circuit pack

The TN8400 Server circuit pack is the hardware platform for an S8400 Server, which is a Linux-based server that occupies a single slot in a standard TN carrier.

● TN8412AP S8400 server IP Interface (SIPI)

The SIPI is used in an S8400-based system to provide transport of control messages between the S8400 Server and the port network (PN) using direct connections.

● H.248 media gateways

The H.248 media gateways include the G700, G250, G350, G430, G450, and IG550.

The H.248 media gateways provide:

- Extension of Communication Manager telephony features to branch offices when controlled by a remote server.

- Standalone telephony systems when controlled by an embedded S8300 Server.

About VoIP-transmission hardware


- Local Survivable Processor (LSP) backup for a remote server.

● MM760 VoIP Media Module

The MM760 VoIP Media Module is a clone of the G700 motherboard VoIP engine. The MM760 provides an additional 64 VoIP channels in the G700.

Processor Ethernet (PE)Much like a C-LAN board, Processor Ethernet provides connectivity to IP endpoints, gateways, and adjuncts. The PE interface is a logical connection in the Communication Manager software that uses a port on the NIC in the server (that is, the s-called “native NIC”). No additional hardware is needed to implement PE. Processor Ethernet uses the PROCR IP-interface type.During the configuration of a server, the PE is assigned to a Computer Ethernet (CE). The PE and the CE share the same IP address, but are very different in nature. The CE interface is a native computer interface while the PE interface is the logical appearance of the CE interface within Communication Manager software. The interface that is assigned to the PE can be a control network or a corporate LAN. The interface that is selected determines which physical port the PE uses on the server. For more information on how to configure the server, see Administering Avaya Aura™ Communication Manager, 03-300509.An LSP or an ESS server enables the Processor Ethernet interface automatically. On an LSP, the H.248 and the H.323 fields default to a yes on the IP Interface Procr screen, to allow the registration of H.248 gateways and H.323 endpoints using the Processor Ethernet interface. In Communication Manager release 5.2 and later, H.248 Media Gateway and H.323 endpoint registration on an ESS server is allowed if you administer the Enable PE for H.248 Gateways and Enable PE for H.323 Endpoints fields on the Survivable Processor screen on the main server. Therefore the H.248 and H.323 fields on the IP Interface Procr screen of the ESS server display the values that you administered.

! Important:Important: Both the ESS server and the LSP require the use of the Processor Ethernet

interface to register to the main server. Do not disable the Processor Ethernet interface on an ESS server or an LSP.

Support for Processor Ethernet and Port Networks on an ESS server

In Communication Manager Release 5.2 and later, the capabilities of ESS servers are enhanced to support connection of IP devices to the Processor Ethernet interface as well as to C-LAN interfaces located in G650 (port network) gateways.An Enterprise Survivable Server (ESS) can use its Processor Ethernet interface to support IP devices such as H.248 Media Gateways, H.323 Media Gateways, IP Adjuncts, IP telephones, IP trunks, and SIP trunks. The ESS can optionally control port networks (G650 Media Gateways) through IPSI at the same time. When there are no port networks in the configuration,

Networking overview


ESS may provide the equivalent benefit of an LSP. The ESS can be duplicated, providing additional redundancy to the survivability of the system.For Processor Ethernet on duplex servers to work, you must assign the Processor Ethernet interface to the PE Active Server IP Address (IP-alias) and not the server unique address. The NIC assigned to the Processor Ethernet interface must be on a LAN connected to the main server.

● If the LSP or ESS registers to the C-LAN on the main server, the C-LAN must have IP connectivity to the LAN assigned to the NIC used for Processor Ethernet on the ESS.

● If the LSP or ESS registers to the Processor Ethernet on the main server, the Processor Ethernet on the main server must have IP connectivity to the LAN assigned to the NIC used for Processor Ethernet on the ESS.

Firmware for optimal performance

Processor Ethernet on duplex servers works effectively only when the H.248 gateways and IP telephones are on the most current release of firmware. Avaya recommends that you use the following IP telephone models to ensure optimal system performance when you use Processor Ethernet on duplex servers:

● 9610, 9620, 9630, 9640, and 9650 telephones with firmware 3.0 or later; any future 96xx models that support TTS (Time to Service) will work optimally.

● 4601+, 4602SW+, 4610SW, 4620SW, 4621SW, 4622SW, and 4625SW Broadcom telephones with firmware R 2.9 SP1 or later, provided the 46xx telephones are not in the same subnet as the servers

All other IP telephone models will re-register in case of server interchange. The 46xx telephones will re-register if they are in the same subnet as the servers.To ensure that you have the most current versions, go to the Avaya Support web site, http://avaya.com/support. Click Downloads and select the product.

Providing LAN securitySome customers are concerned that a user could access the switch using the INADS line, gain access to C-LAN, and then access to the customer’s LAN. The Avaya architecture prevents access to the customer’s LAN as depicted in Figure 1: Security-related system architecture on page 19, which shows a high-level switch schematic with a TN799 (C-LAN) circuit pack.

http://avaya.com/supporthttp://avaya.com/support

Connection Preservation


Figure 1: Security-related system architecture

Logins through the INADS line terminate in software; software communicates with firmware over an internal bus through a limited message set. There are two main reasons why a user cannot access a customer’s LAN through the INADS line:

● A user logging into software cannot obtain direct access to the C-LAN firmware.

The user can only enter SAT commands that request C-LAN information or to configure C-LAN connections.

● The C-LAN application TFTP is currently disabled and cannot be enabled by Communication Manager.

TELNET only interconnects C-LAN Ethernet clients to the system management application on the switch. FTP exists only as a server, is used only for firmware downloads, and it cannot connect to the client network.

Connection PreservationCommunication Manager supports connection preservation and call presentation for handling SIP calls. Any SIP telephone connected through a SIP Enablement Server with Communication Manager can use this feature. SIP connection preservation and call preservation are always active.

Networking overview


● Call preservation and connection preservation during LAN failure:When near-end failure is detected, the SIP signaling group state is placed into Out-of-service state. The SIP-trunk in the trunk group is in a deactivated state and cannot be used either for incoming or outgoing calls. Stable or active calls on the SIP-trunk are not dropped and are kept in In-service/active state. When the active connection is dropped, SIP-trunk changes to Out-of-service state.When far-end failure is detected, the SIP signaling group is placed into the Far-end-bypass state. Stable or active calls are not dropped and the SIP-trunk changes to pending-busyout state. When the active connection is dropped, SIP-trunk changes into Out-Of-Serivce/FarEnd-idle state.

● Call preservation and connection preservation when LAN connectivity is revived:When near-end failure is ended, SIP signaling group state changes to In-service. Stable or active calls on the SIP-trunk are kept in In-service/active state.When far-end failure ends, the SIP signaling group state changes to In-service. State of Stable or active calls on the SIP-trunk changes from pending-busyout to In-service/active state.

Session refresh handling

When SIP session refresh handling fails, the SIP call is set to connection preservation and a net-safety timer starts to keep the call active for 2 hours. After 2 hours the call drops, unless the user ends the call before time.

Connection Preserving MigrationThe Connection Preserving Migration (CPM) feature preserves existing bearer (voice) connections while an H.248 media gateway migrates from one Communication Manager server to another because of network or server failure. However, users on connection-preserved calls cannot use such features as Hold, Conference, or Transfer, etc. In addition to preserving the audio voice paths, CPM extends the time period for recovery operations and functions during Avaya’s complementary recovery strategies.

H.248 and H.323 Link Recovery

H.248 Link Recovery is an automated way in which the media gateway reacquires the H.248 link when it is lost from either a primary call controller or an LSP. The H.248 link between a server running Communication Manager and a media gateway, and the H.323 link between a media gateway and an H.323-compliant IP endpoint, provide the signaling protocol for:

● Call setup

● Call control (user actions such as Hold, Conference, or Transfer) while the call is in progress

● Call tear-down

Connection Preservation


If the link goes down, Link Recovery preserves any existing calls and attempts to re-establish the original link. If the gateway/endpoint cannot reconnect to the original server/gateway, then Link Recovery automatically attempts to connect with alternate TN799DP (C-LAN) circuit packs within the original server’s configuration or to a Local Survivable Processor (LSP).

Auto fallback to primary

The intent of the auto fallback to primary controller feature is to return a fragmented network, in which a number of H.248 Media Gateways are being serviced by one or more LSPs (Local Survivable Processors), to the primary server in an automatic fashion. This feature is targeted towards all H.248 media gateways. By migrating the media gateways back to the primary automatically, the distributed telephony switch network can be made whole sooner without human intervention.

Local Survivable Processor (LSP)

Either an S8300 or S8500-series Server can act as survivable call-processing servers for remote or branch customer locations. As an LSP, the S8300 Server carries a complete set of Communication Manager features, and its license file allows it to function as a survivable call processor. If the link between the remote media gateways—G700, G450, G430, G350, or G250 and the primary controller is broken, the telephones and media gateways designated to receive backup service from the LSP register with the LSP. The LSP will provide control to those registered devices in a license error mode (see Avaya Aura™ Communication Manager Hardware Description and Reference, 555-245-207).

Note:Note: The LSP, in contrast to the Standard Local Survivability (SLS) feature on the

G250, G350, G430, and G450 Media Gateways, is also known as ELS, or Enhanced Local Survivability.

Enterprise Survivable Server (ESS)

The Enterprise Survivable Server (ESS) feature provides survivability to port networks by allowing backup servers to be placed in various locations in the customer’s network. The backup servers supply service to port networks in the case where the Avaya S8500-series Server, or S8700-series Server pair fails, or connectivity to the main Communication Manager server(s) is lost. Servers for ESS can be either S8500-series or S8700-series servers, and offer full Communication Manager functionality when in survivable mode, provided sufficient connectivity exists to other Avaya components (for example, endpoints, gateways, and messaging servers).

Standard Local Survivability (SLS)

Standard Local Survivability (SLS) consists of a module built into the G250 Media Gateway to provide partial backup media gateway controller functionality, in the event that the connection

Networking overview


with the primary controller is lost. This feature allows a G250, with no S8300 installed locally, to provide a degree of Communication Manager functionality when no link is available to an external controller. It is configured on a system-wide basis, or, alternatively, it can be configured on an individual G250 using the CLI.


Chapter 2: Port network configurationswith S8500-series and S8700-series Servers

The S8500-series and S8700-series Servers can control call processing of port networks in a large variety of ways. Control networks can be established using Ethernet connections only or a combination of Ethernet connections and fiber connections (direct-connect, CSS, or ATM). Voice, fax, TTY, and modem can be transmitted over the LAN/WAN connections, fiber connections, or both. Reliability with the S8700-series Server can include single control and bearer networks (standard reliability), duplicated control networks (high reliability), duplicated control and bearer networks (critical reliability), or a combination of reliabilities.

Each of the following configurations show how the various options can be used. Configurations with both IP-PNC and fiber-PNC PNs on page 78 describes the possibilities and considerations when fiber-PNC options are combined with IP-PNC options.

Fiber-PNC and IP-PNCFiber port network connectivity (fiber-PNC) uses fiber connections and/or DS1-C connections between port networks (PNs) for:

● Voice bearer transmission

● Control signaling from the server to PNs that do not have a control TN2312BP IPSI circuit pack

● Sharing of Touch-tone Receiver (TTR) and media processor resources. If these resources are not available in one fiber-PNC PN, the resources on another fiber-PNC PN can be used across the fiber links.

Fiber-PNC includes Direct Connect, Center Stage Switch (CSS), and ATM configurations. One or more PNs in the CSS or ATM configurations have an IPSI connection to the server for control signaling. Only one PN in a Direct Connect configuration has an IPSI connection.

IP port network connectivity (IP-PNC) uses LAN/WAN connections exclusively between port networks for bearer transmission and control signaling from the server. Each PN must have either one or two control ISPI circuit packs for control signaling.

An S8500-series or S8700-series Server can support both types of port network connectivity simultaneously within a single Communication Manager configuration.

Port network configurations with S8500-series and S8700-series Servers


ReliabilityReliability is the ability of a Communication Manager configuration to maintain service when components such as Ethernet switches, circuit packs, or gateways within the configuration fail. The available reliability levels and their precise definitions depend on whether the port networks use IP-PNC or fiber-PNC and whether the server is an S8500-series or S8700-series Server.

S8500-series Server

An S8500-series Server has several reliability options, and the implementation of reliability levels differs somewhat between fiber-PNC and IP-PNC.

Fiber-PNC● Standard reliability

For fiber-PNC, an S8500-series Server supports only Direct Connect with up to 3 fiber-PNC PNs. This configuration supports a single control IPSI in one of the fiber-PNCs. IPSIs in other PNs serve only as tone clocks and do not carry control signaling. There can be only a single fiber connection between each of the fiber PNs.

IP-PNC● Standard reliability

For IP-PNC, an S8500-series Server supports a single IPSI for control in every IP-PNC PN. TN2302BP or TN2602AP circuit packs are used for the bearer network. However, TN2602AP circuit packs are implemented in load-balancing mode only.

● Duplicated bearer reliability

For IP-PNC, an S8500-series Server does not support duplicated control. However, any or all IP-PNC PNs may have duplicated TN2602AP circuit packs to duplicate the bearer connections. Control signaling to a PN with duplicated TN2602AP circuit packs always occurs over a direct IPSI connection to the server. Duplicated bearer using TN2602AP circuit packs is implemented for individual PNs and does not require uniform implementation for all PNs within the configuration.

S8700-series Server

An S8700-series Server has multiple levels of reliability, and the implementation of reliability levels differs somewhat between fiber-PNC and IP-PNC.

Fiber-PNCAll port networks that use fiber-PNC within a single Communication Manager configuration must have the same level of reliability and may be one of the following:


● Standard duplex reliability — The standard S8700-series Server configuration includes duplicated servers. A single IPSI circuit pack for control resides in one or more PNs. A single fiber interface connects all fiber-PNC PNs.

● High reliability — The high reliability S8700-series Server configuration includes the standard duplicated servers and, in addition, duplicated IPSIs in one or more PNs. A single fiber interface connects all fiber-PNC PNs.

● Critical Reliability — The standard reliability S8700-series Server configuration includes the following:- Standard duplicated servers- Duplicated control IPSIs in one or more PNs.- Duplicated fiber interfaces connect all fiber-PNC PNs.

IP-PNCReliability for PNs that use IP-PNC within a single Communication Manager configuration is implemented for individual PNs and does not require uniform implementation for other IP-PNC PNs within the configuration. In addition, duplicated bearer and duplicated control can be implemented independently of each other. Duplicated control is not required for a PN to have duplicated bearer reliability.

An IP-PNC PN can have one of the following reliability levels:

● Standard duplicated servers

A single IPSI provides control signaling between the PN and the server. Only single or load-balancing TN2302BP or TN2602AP circuit pack pairs.

● Duplicated control

In addition to the standard duplicated servers, duplicated IPSIs for control reside in each PN. The PN contains only single or load balancing TN2302BP or TN2602AP circuit pack pairs.

● Single control and duplicated bearer

In addition to the standard duplicated servers, duplicated TN2602AP circuit packs reside in each PN to provide duplicated bearer.

Note:Note: Duplicated IPSI control is recommended, but not required, for duplicated bearer

for IP-PNC PNs.

● Duplicated control and bearer

In addition to the standard duplicated servers, duplicated IPSIs for control reside in each PN and duplicated TN2602AP circuit packs reside in each PN to provide duplicated bearer.



S8500-series IP-PNC (single control network)In this configuration, the S8500-series Server uses IP connections to control call processing on the port networks (PNs) and to send voice between PNs over an IP network. An existing VoIP-ready IP infrastructure can be used. This solution saves customers the cost of building a separate telephony network. In this type of configuration, all PNs are connected to the server and to each other over the customer’s network. Up to 64 PNs can be configured in an IP-PNC network. Depending on the type of Ethernet switches used to connect PNs, the number of PNs, and the PN locations in the LAN and WAN, the network may require multiple Ethernet switches to support the PNs.

Only the G650 media gateway is available for new installations. However, because different migrations from older systems are supported, the following media gateways can be used in an IP-PNC network:

● G650 media gateway

A G650 PN can consist of one to five G650 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:

- TN2312BP IPSI circuit pack


A PN can consist of one to four G600 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:

- TN2312AP/BP IPSI circuit pack

Note:Note: The TN2314 Processor and TN744E Call Classifier and Tone Detector circuit

packs, needed for the S8100 model, are not used and must be removed if the G600 is being migrated from an S8100 Server. All gateways are port gateways, though the bottom gateway (serving as control cabinet A) contains the IPSI circuit pack.

● CMC1 media gateway

A PN can consist of one to three CMC1 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:


Note:Note: The TN795 processor board, needed for the CSI model, is not used and must be

removed if the CMC1 is being migrated from a DEFINITY server. The CMC1 or CMC1 stack may not be used with additional PNs.


IP/TDM conversion resource: Each PN must contain at least one TN2302AP IP Media Interface or TN2602AP IP Media Resource 320 circuit pack. The TN2302AP or TN2602AP circuit pack provides IP-TDM voice processing of endpoint connections between PNs. These circuit packs can be inserted in any gateway in the PN. Each PN may optionally house a TN799DP C-LAN circuit pack for control of the G150 Media Gateway, the H.248 media gateways (G700, G450, G430, G350, G250), IP endpoints, adjunct systems such as messaging, and firmware downloads.

Ethernet connections. In the IP-PNC configuration, the S8500-series Server connects to the media gateways through a single Ethernet switch. Each PN also has a connection to the S8500 Server through a local Ethernet switch. As a result, remote PNs in an IP-PNC configuration over a WAN, which normally requires routers to complete the connection, may require their own Ethernet switches, in addition to the Ethernet switch that supports the S8500-series Server. IP connections to the S8500-series Server may be administered as dedicated private LAN connections or connections over the customer LAN.

Duplicated TN2602AP circuit packs in IP-PNC PNs

For an S8500-series Server, any individual IP-PNC PN can contain load-balancing or duplicated TN2602AP circuit packs. However, TN2602AP circuit packs do not need to be implemented uniformly within the system. Thus, some PNs may have a single TN2602AP circuit pack, some PNs may have load-balancing TN2602AP circuit packs, and some PNs may have duplicated TN2602AP circuit packs. Thus, an S8500-series Server can have duplicated bearer connections, even though it does not support duplicated control.



Figure 2: S8500 IP-PNC

Figure notes: S8500 IP-PNC

1. S8500C or S8500B Server

2. Ethernet Switch. For local LAN connections, the same Ethernet switch can connect both the servers and the media gateways. For remote LAN/WAN connections the remote gateway(s) must have an Ethernet switches at the remote location.

3. PNs (G650 Media Gateway or stack [shown in figure]). May also be a G600 or CMC1 Media Gateway or stack from an S8100 or DEFINITY Server CSI migration, an MCC1 Media Gateway from a DEFINITY Server SI or R migration, or an SCC1 Media Gateway.

4. PN control gateway in the A position in the gateway stack which contains: ● A TN2312AP/BP IPSI circuit pack for IP connection to server.

NOTE: For the G650 Media Gateway, the BP version of the TN2312 is required in order to provide environmental maintenance.

5. IPSI-to-server control network connection via Ethernet switch

1 of 2


S8500-series direct-connect (single control network)In this configuration, one PN is connected to the server over an Ethernet connection. Fiber links connect up to two additional PNs to each other. This configuration also requires either a dual-NIC card in the S8500-series Server or an interim Ethernet switch so that the S8500-series Server can have an Ethernet port to the customer LAN and a dedicated Ethernet connection to the media gateways.

IPSI-connected PNOnly the G650 media gateway is available for new installations. However, because different migrations from older systems are supported, the PN connected to the S8500-series Server can consist of one of three gateways:




● SCC1 media gateway

An SCC1 PN can consist of one to four SCC1 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:


Note:Note: The TN2404 and TN2401 processor circuit packs, needed for the SI model, are

not used and must be removed if the SCC1 is being migrated from a DEFINITY server.

6. LAN connections of TN2302AP IP Media Interface or TN2602AP IP Media Resource 320 for IP-TDM voice processing and optional TN799DP C-LAN for control of IP endpoints

NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs may be inserted into a port gateway (shown in figure) or the PN control gateway.

7. Customer LAN/WAN

8. LAN connections of servers for remote administration

Figure notes: S8500 IP-PNC (continued)

2 of 2



● MCC1 media gateway

An MCC1 PN has from one to five carriers in an MCC1 gateway connected by a TDM/LAN bus cables. One carrier, serving as control carrier in position A in the middle of the stack, contains the following:


Note:Note: The control carrier for a DEFINTY Server SI or R is not used and must be

removed and replaced with an expansion control carrier if the MCC1 is being migrated. The processor circuit packs, needed for the SI or R models, are not used and must be removed. Other PNs can also be MCC1 Gateways.

PNs not IPSI-connectedIn a S8500-series direct-connect configuration, additional PNs (up to two only) may be connected using fiber optic cable. The additional PNs connect to the IPSI-connected PN using fiber optic cable between external interface (EI) TN570B (version 7 or later) circuit packs. The cables are connected to the circuit packs using short-range or long-range multi-mode transceivers, or single-mode transceivers, depending on the distance between PNs.

The TN570B circuit packs reside in the control carrier (MCC1) or control gateway (G650 or SCC1) of each PN. The control carrier or gateway in each additional PN also must contain a TN2182C Tone Clock circuit pack (SCC1 or MCC1) or a maintenance-only TN2312BP IPSI circuit pack (G650).

Note:Note: Straight fiber connections between TN570B circuit packs may be up to 200 feet

(61 meters) (see TN570B Expansion Interface PN connections up to 200 ft. on page 73). If the distance between PNs is greater, Light guide interface units (LIUs) must also be used to connect the fiber cables or the connection must use TN1654 DS1 converters. Lengths of fiber, including connections through LIUs or DS1 converters, are:

- 4900 feet (1493.5 meters) (see TN570B Expansion Interface PN connections up to 4900/25000 ft. and 22 miles. on page 75)

- 25,000 feet (7620 meters) in multimode (see TN570B Expansion Interface PN connections up to 4900/25000 ft. and 22 miles. on page 75)

- 21.7 miles (34.9 kilometers) in single mode (see TN570B Expansion Interface PN connections up to 4900/25000 ft. and 22 miles. on page 75)

- 200 miles (322 kilometers) (see TN1654 DS1 Converter/TN570B Expansion Interface PN connections up to 200 miles. on page 77)

Note:Note: You cannot connect additional PNs that contain CMC1 or G600 Media Gateways.


TN2602AP circuit packs for duplicated bearer

For an S8500-series Server, any individual fiber-PNC PN can contain load-balancing or duplicated TN2602AP circuit packs. However, TN2602AP circuit packs do not need to be implemented uniformly within the system. Thus, some PNs may have no TN2602AP circuit pack, some PNs may have load-balancing TN2602AP circuit packs, and some PNs may have duplicated TN2602AP circuit packs. Thus, an S8500-series Server can have duplicated bearer connections, even though it does not support duplicated control.

Rules for TN570B circuit pack placement with SCC1/MCC1 Media Gateways

Fiber-PNC MCC1 and SCC1 Media Gateways have rules on the placement of TN570B External Interface circuit packs in direct connect configurations. See Rules for TN570B circuit pack placement with SCC1/MCC1 Media Gateways on page 48. However, for MCC1/SCC1 Media Gateways configured with an S8500-series Server, only the rules that apply to single control networks apply.



Figure 3: S8500 direct-connect

Figure notes: S8500 direct-connect

1. S8500C or S8500B Server

2. LAN connections of server for remote administration

3. IPSI-connected PN (G650 Media Gateway or G650 stack [shown in figure], MCC1 Media Gateway or SCC1 Media Gateway or SCC1 stack).

NOTE: G600 or CMC1 Media Gateways can be used in IP-PNC configurations only.

4. Media gateway (G650) or expansion port network (EPN) control gateway (SCC1) or carrier (MCC1), in the A position, which contains:

● A TN2312AP/BP IPSI circuit pack for IP connection to server.


● Two TN570B EI circuit packs for bearer and control network connections to the other two PNs (if any).

5. PN (G650 Media Gateway or G650 stack [shown in figure], MCC1 Media Gateway, or SCC1 Media Gateway or SCC1 stack).

1 of 2


S8700-series IP-PNC (single control network)In this configuration, the S8700-series Servers connect to one or more PNs over an Ethernet connection using either an interim Ethernet switch and a dedicated LAN connection or the customer’s LAN. Each PN is connected to the Ethernet switch or LAN with a CAT5 cable to a TN2312AP/BP IP Server Interface (IPSI) card.

This solution saves customers the cost of building a separate telephony network. In this type of configuration, all PNs are connected to the customer’s network and call control from the S8700-series Server is also sent over the customer’s network. Up to 64 PNs can be configured in an IP-PNC network.

Only the G650 media gateway is available for new installations. However, because different migrations from older systems are supported, the following media gateways can be used in an IP-PNC network:




6. PN control gateway or carrier, which contains two TN570B EI circuit packs for bearer and control network connections to the other two PNs.

NOTE: One TN2182C Tone Clock circuit pack must also be present per PN if the PN(s) consist of SCC1 or MCC1 Media Gateways. One maintenance-only TN2312BP IPSI circuit pack must be present per PN if the PN(s) consist of G650 Media Gateways.

The control gateway or carrier is always in the A position in the MCC1 or gateway stack.

7. IPSI-to-server control network connection. Requires dual NIC card on the server.

8. TN 570B/570B fiber connections between PNs.

9. Customer LAN.

10. LAN connections, if any, of optional TN2302AP IP Media Interface or TN2602AP IP Media Resource 320 for IP-TDM voice processing.

NOTE: Optionally, at least one TN799DP C-LAN can be present for the system for control of IP endpoints, adjunct systems such as messaging, and firmware downloads.

NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs are optional for PNs in a direct-connect network and may be inserted into a port carrier (shown in figure) or the PN control carrier. However, the C-LAN circuit pack is required for downloads of firmware updates.

11. LAN connection.

Figure notes: S8500 direct-connect (continued)

2 of 2




A PN can consist of one to four G600 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:


Note:Note: The TN2314 Processor and TN744E Call Classifier and Tone Detector circuit

packs, needed for the S8100 model, are not used and must be removed if the G600 is being migrated from an S8100 Server. All gateways are port gateways, though the bottom gateway (serving as control cabinet A) contains the IPSI circuit pack.

● CMC1 media gateway

A PN can consist of one to three CMC1 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:


Note:Note: The TN795 processor board, needed for the CSI model, is not used and must be

removed if the CMC1 is being migrated from a DEFINITY server. The CMC1 or CMC1 stack may not be used with additional PNs.

IP/TDM conversion resource: Each PN must contain at least one TN2302AP IP Media Interface or TN2602AP IP Media Resource 320 circuit pack. The TN2302AP or TN2602AP circuit pack provides IP-TDM voice processing of endpoint connections between PNs. Optionally, one or more TN799DP C-LAN circuit pack can be present for control of the G150 Media Gateway, the H.248 media gateways (G700, G450, G430, G350, G250), IP endpoints, adjunct systems such as messaging, and firmware downloads. These circuit packs may be inserted in any gateway in the PN.

Ethernet connections. In the IP-PNC configuration, the S8700-series Server connects to the media gateways through a single Ethernet switch. Each PN also has a connection to the network or the S8700-series Server through a local Ethernet switch. As a result, remote PNs in an IP-PNC configuration over a WAN, which normally requires routers to complete the connection, may require their own Ethernet switches in addition to the Ethernet switch that supports the S8700-series Server. IP connections to the S8700-series Server may be administered as dedicated private LAN connections or connections over the customer LAN.


Figure 4: S8700-series IP-PNC single control network

Figure notes: S8700-series IP-PNC single control network

1. S8700-series Server

2. Ethernet Switch. For local LAN connections, the same Ethernet switch can connect both the servers and the media gateways. For remote LAN/WAN connections, the remote gateway(s) must have an Ethernet switches at the remote location.

3. PNs (G650 Media Gateway or stack [shown in figure]). May also be a G600 or CMC1 Media Gateway or stack from an S8100 or DEFINITY Server CSI migration, an MCC1 Media Gateway from a DEFINITY Server SI or R migration, or an SCC1 Media Gateway.

4. PN control gateway, in the A position, which contains: ● A TN2312AP/BP IPSI circuit pack for IP connection to server.



1 of 2



S8700-series IP-PNC (duplicated control network)The S8700-series Server IP-PNC high reliability configuration is the same as the standard reliability configuration, except for the following differences:

● There are duplicated Ethernet switches, with each server connected to each Ethernet switch

● Each PN has duplicated TN2312AP/BP IPSI circuit packs. One IPSI circuit pack in each PN is connected through one Ethernet switch and the other IPSI circuit pack is connected through the other Ethernet switch


NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs may be inserted into a port gateway (shown in figure) or the PN control gateway.

7. Customer LAN/WAN


9. Duplicated server links, including the link for translations memory duplication and the link for control data sharing. The link for memory duplication is implemented through the DAL2 board or (for the S8720 and S8730 Server) through software duplication.

Figure notes: S8700-series IP-PNC single control network (continued)

2 of 2


Figure 5: S8700-series IP-PNC duplicated control network

Figure notes: S8700-series IP-PNC duplicated control network


2. Ethernet Switch. For local LAN connections, the same pair of Ethernet switches can connect both the servers and the media gateways. For remote LAN/WAN connections, the remote gateway(s) must have a pair of Ethernet switches at the remote location.

3. PNs (G650 Media Gateway or stack [shown in figure]). May also be an SCC1 stack or MCC1 Media Gateway from a DEFINITY Server SI or R migration.



5. Duplicated expansion control gateway, in the B position, which contains: ● A TN2312AP/BP IPSI circuit pack for IP connection to control network.



NOTE: The number of TN2302AP, TN2602AP, and TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs may be inserted into a port carrier (shown in figure), the PN control carrier, or the duplicated control carrier.

1 of 2



S8700-series IP-PNC (duplicated control and duplicated bearer network)

The S8700-series Server IP-PNC critical reliability configuration (duplicated control and duplicated bearer network) is the same as the high reliability configuration, except for the following differences:

● Each PN has duplicated TN2602AP IP Media Resource 320 circuit packs. One TN2602 circuit pack in each PN is connected through one Ethernet switch and the other TN2602 circuit pack is connected through the other Ethernet switch.

● A TN771DP Maintenance Test circuit pack must also be installed in each PN that has duplicated control and bearer network connections.

8. Customer LAN


10. Duplicated server links, including the link for translations memory duplication and the link for control data sharing. The link for memory duplication is implemented through the DAL2 board or (for the S8720 and S8730 Server) through software duplication.

Figure notes: S8700-series IP-PNC duplicated control network (continued)

2 of 2


Figure 6: S8700-series IP-PNC duplicated control and duplicated bearer network

Figure notes: S8700-series IP-PNC duplicated control and duplicated bearer network


2. Ethernet Switch. For local LAN connections, the same pair of Ethernet switches can connect both the servers and the media gateways. For remote LAN/WAN connections, the remote gateway(s) must have a pair of Ethernet switches at the remote location.

3. PNs (G650 Media Gateway or stack [shown in figure]). May also be an SCC1 stack or MCC1 Media Gateway from a DEFINITY Server SI or R migration.



● A TN2602AP IP Media Resource 320 for PN bearer connections over the LAN

NOTE: The TN2602AP circuit pack may be placed in any gateway in the PN. However, the pair of TN2602 circuit packs should be separated between two different gateways whenever possible.

5. Duplicated expansion control gateway, in the B position, which contains: ● A TN2312AP/BP IPSI circuit pack for IP connection to control network.

● A TN2602AP IP Media Resource 320 for PN bearer connections over the LAN

NOTE: The TN2602AP circuit pack may be placed in any gateway in the PN. However, the pair of TN2602 circuit packs should be separated between two different gateways whenever possible.

1 of 2



S8700-series direct-connect (single control network)In this configuration, one PN is connected to the server over an Ethernet connection. Fiber links connect up to two additional PNs to each other. This configuration also requires either a dual-NIC card in the S8700-series Server or an interim Ethernet switch.

IPSI-connected PNOnly the G650 media gateway is available for new installations. However, because different migrations from older systems are supported, the PN connected to the S8700-series Server can consist of one of three gateways:




● SCC1 media gateway

An SCC1 PN can consist of one to four SCC1 gateways in a stack connected by a TDM/LAN bus cable. One gateway, serving as control gateway in position A at the bottom of the stack, contains the following:


Note:Note: The TN2404 and TN2401 processor circuit packs, needed for the SI model, are

not used and must be removed if the SCC1 is being migrated from a DEFINITY server.


7. LAN connection of the TN799DP C-LAN for control of IP endpointsNOTE: The number of TN799DP circuit packs varies, depending on the number of IP endpoints, PNs, and adjunct systems. These circuit packs may be inserted into a port carrier (shown in figure), the PN control carrier, or the duplicated control carrier.

8. LAN connections of TN2602AP IP Media Resource 320 circuit packs for IP-TDM voice processing

9. Customer LAN


11. Duplicated server links, including the link for translations memory duplication and the link for control data sharing. The link for memory duplication is implemented through the DAL2 board or (for the S8720 and S8730 Server) through softw

Date post:	18-Jul-2020
Category:	Documents
Author:	others
View:	4 times
Download:	1 times

Administering Network Connectivity on Avaya Aura ......Administering Network Connectivity on Avaya...

Documents

Avaya Aura CM SIP Integration - …distributors.innovationtw.com/support/downloads/Avaya Aura CM SIP... · Avaya Aura CM SIP Integration ... 4 6 9 4 a SIP connection to Avaya Aura(R)

Avaya Aura®

Avaya Aura Commuincicaions Manger

Avaya Aura™ Application Enablement - CRINJ · Implementation notes on Integration of Avaya Aura Application Enablement ... Avaya Aura® Application Enablement Services Implementation

Avaya Aura® Virtualized Environment...Avaya Aura Virtualized Environment is the Avaya solution for supporting Avaya Aura core applications on any VMware-based IT data center. The

Administering Avaya Aura™ System Platform

Administering Avaya Aura Communication Manager as a ...

Avaya Aura System Manager

The Avaya Aura Platform - AVAD GmbH · Avaya Aura Suite Licenses Avaya Aura Suite Licensing offers a simpler approach to creating solution-oriented options for Avaya Aura customers.

Using Avaya Aura Messaging

Using Avaya Aura Messaging - Michigan State Universityipf.msu.edu/_files/pdfs/user-guides/avaya-aura-messaging-user... · Using Avaya Aura ® Messaging ... Email client (Outlook)

Avaya Aura - Config Guide

and Avaya Aura Session Manager - Spectralink Supportsupport.spectralink.com/sites/default/files/resource_files/721... · Avaya Aura Communication Manager and Avaya Aura Session Manager

Avaya Aura™ - ONE Corp · • Avaya Aura System Manager, a common ... Avaya Aura System Platform technology gives developers the flexibility, test and development environments to

Business Talk & BTIP for Avaya AURA · conferencing, tones and announcements. ... Avaya Aura Communication Manager 8.0.1 FP1 822.0-25031 ... Avaya Aura Session Border Controller for

Application Notes for Valcom PagePro IP with Avaya Aura® Communication Manager … · 2020. 9. 30. · Aura® Communication Manager and Avaya Aura® Session ... Avaya Aura® System

Avaya 1400 Series Digital Deskphones for Avaya Aura ...

Administering Avaya Proactive Contact