Avaya Aura User Manual

Administering Network Connectivity on
Avaya Aura® Communication Manager

Release 7.1.3

Issue 4

February 2020

©

2017-2020, Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this
document without the obligation to notify any person or organization
of such changes.

Documentation disclaimer

“Documentation” means information published in varying mediums
which may include product information, operating instructions and
performance specifications that are generally made available to users
of products. Documentation does not include marketing materials.
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of Documentation unless
such modifications, additions, or deletions were performed by or on
the express behalf of Avaya. End User agrees 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 End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or Documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.

Warranty

Avaya provides a limited warranty on Avaya hardware and software.
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 to Avaya customers and other parties through the Avaya
Support website:

https://support.avaya.com/helpcenter/
getGenericDetails?detailId=C20091120112456651010 under the link

“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if You acquired the product(s) from an
authorized Avaya Channel Partner outside of the United States and
Canada, the warranty is provided to You by said Avaya Channel
Partner and not by Avaya.

“Hosted Service” means an Avaya hosted service subscription that
You acquire from either Avaya or an authorized Avaya Channel
Partner (as applicable) and which is described further in Hosted SAS
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the
foregoing limited warranty may not apply but You may be entitled to
support services in connection with the Hosted Service as described
further in your service description documents for the applicable
Hosted Service. Contact Avaya or Avaya Channel Partner (as
applicable) for more information.

Hosted Service

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE,

HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER

THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF

YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,

HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,

UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants You a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
applicable. The applicable number of licenses and units of capacity
for which the license is granted will be one (1), unless a different
number of licenses or units of capacity is specified in the
documentation or other materials available to You. “Software” means
computer programs in object code, provided by Avaya or an Avaya
Channel Partner, whether as stand-alone products, pre-installed on
hardware products, and any upgrades, updates, patches, bug fixes,
or modified versions thereto. “Designated Processor” means a single
stand-alone computing device. “Server” means a set of Designated
Processors that hosts (physically or virtually) a software application
to be accessed by multiple users. “Instance” means a single copy of
the Software executing at a particular time: (i) on one physical
machine; or (ii) on one deployed software virtual machine (“VM”) or
similar deployment.

License types

Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only: 1) on a number of
Designated Processors up to the number indicated in the order; or 2)
up to the number of Instances of the Software as indicated in the
order, Documentation, or as authorized by Avaya in writing. Avaya
may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
specific designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this purpose.

Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
so long as only the licensed number of Units are accessing and using
the Software at any given time. A “Unit” means the unit on which
Avaya, at its sole discretion, bases the pricing of its licenses and can
be, without limitation, an agent, port or user, an e-mail or voice mail
account in the name of a person or corporate function (e.g.,
webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Software that permits one user to interface
with the Software. Units may be linked to a specific, identified Server
or an Instance of the Software.

Named User License (NU). You may: (i) install and use each copy or
Instance of the Software on a single Designated Processor or Server
per authorized Named User (defined below); or (ii) install and use
each copy or Instance of the Software on a Server so long as only
authorized Named Users access and use the Software. “Named

User”, means a user or device that has been expressly authorized by
Avaya to access and use the Software. At Avaya’s sole discretion, a
“Named User” may be, without limitation, designated by name,
corporate function (e.g., webmaster or helpdesk), an e-mail or voice
mail account in the name of a person or corporate function, or a
directory entry in the administrative database utilized by the Software
that permits one user to interface with the Software.

Shrinkwrap License (SR). You may install and use the Software in
accordance with the terms and conditions of the applicable license
agreements, such as “shrinkwrap” or “clickthrough” license
accompanying or applicable to the Software (“Shrinkwrap License”).

Heritage Nortel Software

“Heritage Nortel Software” means the software that was acquired by
Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software is the
software contained within the list of Heritage Nortel Products located

https://support.avaya.com/LicenseInfo under the link “Heritage

at
Nortel Products” or such successor site as designated by Avaya. For
Heritage Nortel Software, Avaya grants Customer a license to use
Heritage Nortel Software provided hereunder solely to the extent of
the authorized activation or authorized usage level, solely for the
purpose specified in the Documentation, and solely as embedded in,
for execution on, or for communication with Avaya equipment.
Charges for Heritage Nortel Software may be based on extent of
activation or use authorized as specified in an order or invoice.

Copyright

Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express
written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.

Virtualization

The following applies if the product is deployed on a virtual machine.
Each product has its own ordering code and license types. Note,
unless otherwise stated, that each Instance of a product must be
separately licensed and ordered. For example, if the end user
customer or Avaya Channel Partner would like to install two
Instances of the same type of products, then two products of that
type must be ordered.

Third Party Components

“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may
contain software (including open source software) distributed under
third party agreements (“Third Party Components”), which contain
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the products, Documentation or on Avaya’s website at:

support.avaya.com/Copyright or such successor site as designated

by Avaya. The open source software license terms provided as Third
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these
Software License Terms, solely with respect to the applicable Third
Party Components to the extent that these Software License Terms
impose greater restrictions on You than the applicable Third Party
Terms.

The following applies only if the H.264 (AVC) codec is distributed with
the product. THIS PRODUCT IS LICENSED UNDER THE AVC
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE

https://

REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
L.L.C. SEE

Service Provider

THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS,
THE AVAYA CHANNEL PARTNER IS REQUIRED TO
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE,
DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE
AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES
THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729
CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE

WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS

LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
THE PERSONAL USE OF A CONSUMER OR OTHER USES IN
WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE
VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC
VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED
BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR
WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO
PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION
FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
OBTAINED FROM MPEG LA, L.L.C. SEE

WWW.MPEGLA.COM.

Compliance with Laws

You acknowledge and agree that it is Your responsibility for
complying with any applicable laws and regulations, including, but not
limited to laws and regulations related to call recording, data privacy,
intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.

Preventing Toll Fraud

“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.

Avaya Toll Fraud intervention

If You suspect that You are being victimized by Toll Fraud and You
need technical assistance or support, call Technical Service Center
Toll Fraud Intervention Hotline at [phone] for the United
States and Canada. For additional support telephone numbers, see
the Avaya Support website:
successor site as designated by Avaya.

Security Vulnerabilities

Information about Avaya’s security support policies can be found in
the Security Policies and Support section of

support.avaya.com/security.

Suspected Avaya product security vulnerabilities are handled per the
Avaya Product Security Support Flow (

support.avaya.com/css/P8/documents/100161515).

HTTP://WWW.MPEGLA.COM.

HTTP://

https://support.avaya.com or such

https://

https://

Downloading Documentation

For the most current versions of Documentation, see the Avaya
Support website: https://support.avaya.com, or such successor site
as designated by Avaya.

Contact Avaya Support

See the Avaya Support website: https://support.avaya.com for
product or Hosted Service notices and articles, or to report a problem
with your Avaya product or Hosted Service. For a list of support
telephone numbers and contact addresses, go to the Avaya Support
website:
designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users are
not permitted to use such Marks without prior written consent from
Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.

https://support.avaya.com (or such successor site as

Contents

Chapter 1: Introduction............................................................................................................ 9

Purpose.................................................................................................................................. 9

Change history........................................................................................................................ 9

Chapter 2: Networking Overview........................................................................................... 11

Network terminology.............................................................................................................. 11

Digital telephone calls............................................................................................................ 11

Network regions.................................................................................................................... 12

Features affected by the increase in locations and network regions..................................... 14

Interswitch trunk connections................................................................................................. 15

IP-connected networks.................................................................................................... 15

Branch office networks..................................................................................................... 15

Control networks............................................................................................................. 15

Spanning Tree Protocol................................................................................................... 16

Inter-Gateway Alternate Routing....................................................................................... 16

Dial Plan Transparency.................................................................................................... 17

Network quality management................................................................................................. 18

VoIP transmission hardware................................................................................................... 18

Processor Ethernet.......................................................................................................... 19

LAN security......................................................................................................................... 21

Connection Preservation........................................................................................................ 22

Session refresh handling.................................................................................................. 22

Connection Preserving Migration...................................................................................... 23

Support to tandem MIME for PIDF-LO..................................................................................... 24

Support for Channel Type identification over ASAI to CTI application......................................... 24

Chapter 3: Port network configurations............................................................................... 26

IP port network connectivity.................................................................................................... 26

Reliability.............................................................................................................................. 26

Simplex server................................................................................................................ 27

Duplex server.................................................................................................................. 27

Simplex IP-PNC for the single control network......................................................................... 28

Architecture of simplex server IP-PNC.............................................................................. 29

Duplicated TN2602AP circuit packs in IP-PNC port networks.............................................. 30

Circuit packs for duplicated bearer connections................................................................. 31

Duplex IP-PNC (single control network)................................................................................... 31

Architecture of duplex IP-PNC single control network......................................................... 33

Duplex server IP-PNC for a duplicated control network............................................................. 35

Architecture of duplex IP-PNC duplicated control network................................................... 35

Duplex server IP-PNC for a duplicated control and bearer network connection........................... 37

Architecture of duplex IP-PNC duplicated control and duplicated bearer network ................. 38

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 5

Comments on this document? [e-mail]

Contents

Example of IP-PNC port networks with different reliability levels................................................ 40

Chapter 4: Converged Networks........................................................................................... 43

Voice over IP converged networks.......................................................................................... 43

Network assessment....................................................................................................... 43

VoIP hardware...................................................................................................................... 44

Universal DS1 circuit packs and MM710 T1/E1Media Module............................................. 44

TN799DP Control LAN..................................................................................................... 47

TN2302AP IP Media Processor........................................................................................ 51

TN2602AP IP Media Resource 320.................................................................................. 52

TN2312BP IP Server Interface ........................................................................................ 55

MM760 VoIP Media Module............................................................................................. 59

Avaya gateways.................................................................................................................... 61

Avaya Aura® Media Server..................................................................................................... 61

IP trunks............................................................................................................................... 61

SIP trunks............................................................................................................................. 61

Creating a SIP trunk signaling group................................................................................. 62

H.323 trunks......................................................................................................................... 63

Preparing to administer H.323 trunks................................................................................ 64

Verifying customer options for H.323 trunking.................................................................... 64

Administering C-LAN and IP Media Processor circuit packs for simplex/duplex servers......... 65

QoS parameters.............................................................................................................. 65

IP node names and IP addresses..................................................................................... 66

Assigning IP node names................................................................................................. 66

Defining IP interfaces....................................................................................................... 67

Defining IP interfaces for duplicated TN2602AP................................................................. 67

Best Service Routing ...................................................................................................... 68

Administering an H.323 trunk........................................................................................... 68

H.323 trunk signaling group.............................................................................................. 69

Creating an H.323 trunk signaling group............................................................................ 69

Creating a trunk group for H.323 trunks............................................................................. 72

Modifying the H.323 trunk signaling group......................................................................... 73

Dynamic generation of private/public calling party numbers................................................ 73

Avaya IP phones................................................................................................................... 75

IP softphones.................................................................................................................. 75

Avaya IP telephones........................................................................................................ 78

Hairpinning, shuffling, and direct media............................................................................. 82

Examples of shuffling....................................................................................................... 85

Hairpinning and shuffling administration interdependencies................................................ 91

Network Address Translation............................................................................................ 93

Hairpinning and shuffling.................................................................................................. 96

Fax, modem, TTY, H.323 Clear Channel calls over H.323 IP trunks, and SIP 64K Data calls

over SIP trunks................................................................................................................... 102

Relay............................................................................................................................ 102

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 6

Comments on this document? [e-mail]

Contents

Pass-through................................................................................................................ 103

T.38.............................................................................................................................. 103

V.150.1 Modem Relay.................................................................................................... 104

SIP 64K Data................................................................................................................ 104

Administering fax, TTY, modem, and clear-channel calls over IP trunks............................. 104

Considerations for administering FAX, TTY, modem, and Clear-Channel transmission........ 105

FAX, TTY, modem, and clear channel transmission modes and speeds............................. 107

Bandwidth for FAX, modem, TTY, and clear channel calls over IP networks........................ 111

Media encryption for FAX, modem, TTY, and clear channel............................................... 112

SRTP media encryption....................................................................................................... 114

Platforms...................................................................................................................... 115

Administering SRTP....................................................................................................... 116

Administering SRTP for video signaling........................................................................... 117

Chapter 5: Voice, Video, and Network quality administration.......................................... 119

Factors causing voice degradation........................................................................................ 119

Packet delay and loss.................................................................................................... 120

Echo............................................................................................................................ 121

Transcoding.................................................................................................................. 125

Bandwidth..................................................................................................................... 125

Quality of Service and voice quality administration................................................................. 125

Layer 3 QoS................................................................................................................. 126

Layer 2 QoS................................................................................................................. 126

IP codec sets................................................................................................................ 128

IP network regions......................................................................................................... 131

Call Admission Control................................................................................................... 145

Administering DPT........................................................................................................ 150

Network Region Wizard................................................................................................. 151

Manually interconnecting the network regions.................................................................. 152

Setting network performance thresholds.......................................................................... 157

Enabling or disabling spanning tree................................................................................ 158

Jitter buffers.................................................................................................................. 160

UDP ports..................................................................................................................... 160

Media encryption................................................................................................................. 160

Limitations of media encryption...................................................................................... 161

Types of media encryption............................................................................................. 161

License file................................................................................................................... 161

Legal wiretapping.......................................................................................................... 165

Possible failure conditions.............................................................................................. 165

Interactions of media encryption with other features......................................................... 166

Network recovery and survivability........................................................................................ 166

Network management.................................................................................................... 167

H.248 link loss recovery................................................................................................. 168

Administrable IPSI Socket Sanity Timeout....................................................................... 175

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 7

Comments on this document? [e-mail]

Contents

Survivable core servers................................................................................................. 177

Improved port network recovery from control network outages.......................................... 178

Port Network Recovery Rules screen field descriptions.................................................... 179

Survivability.................................................................................................................. 180

Chapter 6: Resources........................................................................................................... 181

Documentation.................................................................................................................... 181

Finding documents on the Avaya Support website........................................................... 182

Training.............................................................................................................................. 183

Viewing Avaya Mentor videos............................................................................................... 184

Support.............................................................................................................................. 184

Appendix A: PCN and PSN notifications............................................................................ 185

PCN and PSN notifications................................................................................................... 185

Viewing PCNs and PSNs..................................................................................................... 185

Signing up for PCNs and PSNs............................................................................................ 186

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 8

Comments on this document? [e-mail]

Chapter 1: Introduction

Purpose

This book provides background information about the network components of Avaya Aura
Communication Manager.

You can refer to the book when you:

• Connect Avaya phones to various networks.

• Configure Avaya phones.

• Configure Port Networks (PN).

• Administer converged network components, such as Avaya Aura® Media Server, gateways,
trunks, fax, modem, TTY, and clear-channel calls.

This document is intended for anyone who wants to gain a high-level understanding of the product
features, functionality, capacities, and limitations within the context of solutions and verified
reference configurations.

• Technical support representatives

• Authorized Business Partner

Change history

®

Issue Date Summary of changes

4 February 2020 Updated the “Dial Plan Transparency” section.

Table continues…

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 9

Comments on this document? [e-mail]

Introduction

Issue Date Summary of changes

3 August 2019 Following sections are updated:

• Branch office networks

• Network assessment

• Installing the TN799DP C-LAN

• Voice, Video, and Network quality administration

• IP network regions

• Manually interconnecting the network regions

2 August 2017 • Added the “Support to tandem MIME for PIDF-LO” section.

• Added the “Support for Channel Type identification over ASAI to CTI
application” section.

1 May 2017 Initial release

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 10

Comments on this document? [e-mail]

Chapter 2: Networking Overview

Network terminology

The Communication Manager network can contain multiple servers and equipment, including
data-networking devices that servers control. Such equipment might be geographically dispersed
across many sites. Each site might segregate equipment into distinct logical groupings of
endpoints, including stations, trunks, and gateways, referred to as network regions. A single
server system has one or more network regions. If one server is inadequate for controlling the
equipment, multiple systems can be networked together. One or more network regions make a
site, and one or more sites make a system, which in turn is a component of a network.

Types of networks:

• Nondedicated network: Businesses have a corporate network, such as a LAN or a WAN.
Over this corporate network, businesses distribute emails and data files, run applications,
access the Internet, and exchange fax and modem calls.

This type of network and the traffic that it bears is a nondedicated network. The network is a
heterogeneous mix of data types.

• Converged network: A nondedicated network that carries digitized voice signals with other
data types is a converged network. The converged network is a confluence of voice and
nonvoice data.

• Dedicated network: Network segments that carry telephony traffic are dedicated networks
because the network segments carry only telephony-related information.

• IP network: A digital network carries telephony and nontelephony data in a packet-switched
environment, such as TCP/IP, instead of a circuit-switched environment, such as TDM. The
digital network is an IP network.

Digital telephone calls

A digital telephone call consists of voice data and call-signaling messages. Some transmission
protocols require transmission of signaling data over a separate network, virtual path, or channel
from the voice data. Data that is transmitted between switches during a telephone call includes:

• Voice data that contains digitized voice signals

• Call-signaling data with control messages

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 11

Comments on this document? [e-mail]

Networking Overview

• Distributed Communications System (DCS) signaling data

Use DCS to configure two or more communication switches as a single switch. DCS provides
attendant features and voice terminal features between these switch locations. DCS simplifies
dialing procedures and ensures transparent use of some Communication Manager features.
Feature transparency means that features are available to all users on DCS regardless of the
switch location.

Network regions

A network region is a group of IP endpoints that share common characteristics and common
resources. Every IP endpoint on the Communication Manager system belongs to a network
region. You can differentiate between the network regions either by the resources assigned or the
geographical location or both.

You can create different network regions when a group of endpoints:

• Require a different codec set based on bandwidth allocation or a different encryption
algorithm than another group.

• Gain access to specific C-LANs, MedPros, gateways, or other resources.

• Require a different UDP port range or QoS parameters than another group.

• Report to a different VoIP Monitoring Manager server than another group.

• Require a different codec set based on bandwidth requirement or encryption algorithm for
calls within the group than calls between separate endpoint groups.

The concept of locations is also similar to network regions. Use the location parameter to:

• Identify distinct geographic locations, primarily for call routing purposes.

• Ensure that calls pass through proper trunks based on the origin and destination of each call.

Communication Manager supports 2000 locations and network regions. This increase in the
number of network regions and locations applies to customers that use Communication Manager
installed on the following servers and VMware platforms: .

• HP ProLiant DL360 G7

• HP ProLiant DL360p G8

• HP ProLiant DL360 G9

• Dell™ PowerEdge™ R610

• Dell™ PowerEdge™ R620

• Dell™ PowerEdge™ R630

With the increase in the number of network regions and locations that Communication Manager
supports, organizations can expand businesses to various locations globally. Organizations can
also efficiently manage bandwidth by allocating the required bandwidth between a pair of network
regions

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 12

Comments on this document? [e-mail]

Network regions

To support the increase to 2000 network regions and locations, you can now configure network
regions as core network regions and stub network regions. You can configure network regions
from 1 to 250 as core network regions or stub network regions. Network regions 251 to 2000 are
stub network regions.

A core network region is the traditional network region and can have multiple direct links with other
network regions. For a diagrammatic representation of core network regions, see

Figure 1: Core
network regions on page 13. The solid lines in the diagram indicate a direct communication path

between two core network regions. The dotted lines indicate an indirect logical communication
path between two core network regions.

Figure 1: Core network regions

A stub network region must have a single defined pathway to only one core network region. For a
diagrammatic representation of core network regions and stub network regions, see

Figure 2:

Core and stub network regions on page 13.

Figure 2: Core and stub network regions

Stub network regions communicate with other network regions using the defined communication
pathways of the core network regions. For example, a scenario where stub network region 251
directly communicates with core network region 1. If stub network region 251 wants to send data
to core network region 3, then stub network region 251 first sends data to core network region 1.
From core network region 1, Communication Manager uses the predefined communication

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 13

Comments on this document? [e-mail]

Networking Overview

pathway of core network region 1 to reach core network region 3. For a diagrammatic
representation of the communication pathway, see .Figure 3: Communication Pathway from a stub

network region to a core network region on page 14

Figure 3: Communication Pathway from a stub network region to a core network region

The benefit of having a stub network region is that you do not have to configure multiple
communication pathways to different network regions. When you add a stub network region,
administer the communication path only to the core network region to which the stub network
region connects.

You must assign all Communication Manager hardware, such as branch gateways, media
processors, C-LANs, and G650 cabinets to network regions 1 to 250. This assignment must be
done regardless of whether the network region is a core network region or a stub network region.

Features affected by the increase in locations and network regions

The increase in the number of network regions and locations can affect the following features:

• Dial Plan Transparency (DPT): The DPT feature can work in a stub network region only with
endpoints. Stub network regions use the media processing resources of the core network
regions that the stub network regions connect to. Administer the DPT feature in a core
network region that is directly linked with other stub network regions. Only then can the
endpoints in the stub network regions connect to endpoints in other network regions.

• Inter-gateway Alternate Routing (IGAR): Any stub network region from 1 to 250 can use
IGAR if the stub network region contains a branch gateway or a port network. IGAR is
unavailable for stub network regions from 251 to 2000.

• Emergency Calling: When an endpoint in a stub network region dials an emergency number,
Communication Manager analyzes the dialed number. Communication Manager then uses

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 14

Comments on this document? [e-mail]

Interswitch trunk connections

the ARS location table to route the call to the destination. The call is routed using a
predefined route pattern.

Interswitch trunk connections

You can use the connected switches within an enterprise to communicate easily, regardless of the
location or the communication server that the switches use. Interswitch connections also provide
shared communications resources, such as messaging and call center services.

Switches communicate with each other over trunk connections. Different types of trunks 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 send 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 connect switches in a private network.

• SIP trunk equipped with SIP signaling

For more information about the trunk types, see Administering Avaya Aura® Communication
Manager, 03-300509.

IP-connected networks

For more information about IP-connected (IP-PNC) networks, see Chapter 3: Port network

configurations on page 26.

Branch office networks

In Communication Manager environments, MultiVOIP™ gateways provide distributed networking
capabilities to small branch offices of large corporations. MultiVOIP extends the call features of a
centralized Avaya server. MultiVOIP provides local office survivability to branch offices of up to 15
users who use analog or IP telephones.

Control networks

Control networks are networks over which Communication Manager exchanges signaling data
with port networks. Communication Manager exchanges signaling data through the IPSI circuit
packs.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 15

Comments on this document? [e-mail]

Networking Overview

Spanning Tree Protocol

Spanning Tree Protocol (STP) is a loop avoidance protocol. If your network does not have loops,
you do not need STP. However, you must always enable STP. If you do not enable STP, all traffic
stops on the network with a loop or with the wrong cable plugged into wrong ports.

However, STP is slow to converge after a network failure and provide a new port into the network.
By default, the speed is ~50 seconds.

A modified version of STP is the Rapid Spanning Tree protocol. Rapid Spanning Tree converges
faster than STP and enables new ports faster than the older protocol. As the Rapid Spanning Tree
protocol works with all Avaya equipment, use the Rapid Spanning Tree protocol.

Inter-Gateway Alternate Routing

With Inter-Gateway Alternate Routing (IGAR), Communication Manager can use the PSTN
instead of the IP-WAN for bearer connections. This feature is beneficial when the IP-WAN cannot
carry the bearer connection for the single-server systems that use the IP-WAN to connect bearer
traffic between port networks or gateways.

Note:

Communication Manager Release 6.3.5 and earlier supported IGAR for analog, DCP, and H.
323 endpoints. Communication Manager Release 6.3.6 extends this support to SIP endpoints.

IGAR requests PSTN to provide bearer connections in any of the following conditions:

• Reaching the number of calls or bandwidth allocated through Call Admission Control­Bandwidth Limits (CAC-BL).

• Facing VoIP RTP resource exhaustion in a port network or media gateway.

• Encountering the codec set between a pair of network regions set to pstn.

• Finding forced redirection configured between a pair of network regions.

IGAR provides enhanced Quality of Service (QoS) to large, distributed single-server
configurations. IGAR is intended for configurations where the IP network is not reliable enough to
carry bearer traffic. If you have more than one IP network available, you can use H.323 or SIP
trunks for IGAR instead of the PSTN.

When Communication Manager needs an intergateway connection and adequate IP bandwidth is
unavailable, Communication Manager attempts to substitute a trunk connection for the IP
connection. For example, Communication Manager can substitute a trunk connection in any of the
following situations:

• A user in one Network Region (NR) calls a user in another NR

• A station in one NR bridges on to a call appearance of a station in another NR

• An incoming trunk in one NR routes to a hunt group with agents in another NR

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 16

Comments on this document? [e-mail]

Interswitch trunk connections

• An announcement or music source from one NR must be played to a party in another NR

Communication Manager attempts to use a trunk for interregion voice bearer connection when the
following five conditions are met:

• An intergateway connection is needed.

• IGAR requests PSTN to provide bearer connections.

• IGAR is enabled for the NRs associated with each end of the call.

• The Enable Inter-Gateway Alternate Routing system parameter is set to y.

• The number of trunks, used by IGAR in each NR, has not reached the limit administered for
that NR.

The SRC PORT TO DEST PORT TALKPATH page of the status station screen shows the IGAR
trunk connectivity for an inter-NR call.

A Trunk Inter-Gateway Connection (IGC) is established using ARS to route a trunk call from one
NR to IGAR Listed Directory Number (LDN) extension administered for another NR. The Trunk
IGC is independent of the call. Therefore, Communication Manager can originate the IGC from the
NR of the calling party to the NR of the called party, or vice versa. Some users use Facility
Restriction Levels or Toll Restriction to determine who gets access to IGAR resources during a
WAN outage. For these users, the calling user is considered the originator of the Trunk IGC for
authorization and routing. For outgoing trunk groups administered to send the Calling Number, the
IGAR Extension in the originating NR is used to create this number using the appropriate
administration.

A few examples of failure scenarios and how Communication Manager handles the scenarios:

• On a direct call, the call continues to the first coverage point of the unreachable called
endpoint. If no coverage path is assigned, the calling party hears a busy tone.

• If the unreachable endpoint is accessed through a coverage path, the coverage point is
skipped.

• If the unreachable endpoint is the next available agent in a hunt group, that agent is
considered unavailable. The system tries to route the call to another agent using the
administered group type, such as Circular distribution and Percent Allocation Distribution.

Dial Plan Transparency

Dial Plan Transparency (DPT) preserves the dial plan when a gateway registers with a Survivable
Remote server or when a port network registers with a Survivable Core server. Port network
registers with a Survivable Core server 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.

You need not activate DPT in the license file. DPT is a standard feature in Communication
Manager Release 4.0 and later. DPT is similar to IGAR as both provide alternate call routing when
normal connections are unavailable. A major difference is that DPT routes calls between
endpoints that two independent servers control. IGAR routes calls between endpoints that a single

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 17

Comments on this document? [e-mail]

Networking Overview

server controls. The DPT and IGAR features are independent of each other, but you can activate
both simultaneously.

Limitations of DPT:

• DPT only handles IP network connectivity failures between network regions.

• DPT calls are trunk calls. Therefore, Communication Manager does not support many station
features.

• For Release 4.0, DPT applies only to endpoints that are dialed directly. DPT cannot route
redirected calls or calls to groups.

• DPT cannot reroute calls involving a SIP endpoint that has lost registration with the Session
Manager.

• DPT works only when failover strategies for gateways and port networks, and alternate
gatekeeper lists for IP stations are consistent.

For information about administering DPT, see

Administering DPT on page 150.

Network quality management

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

• Delay: Significant end-to-end delay can cause echo and talker overlap.

• Packet loss: During peak network loads and periods of congestion, voice data packets might
drop.

• Jitter (Delay variability): Data packets arrive at their destination at irregular intervals because
of variable transmission delay over the network.

For more information about these QoS factors and network quality management, see:

• Chapter 6: Voice and Network quality administration on page 119

• Avaya Aura® Solution Design Considerations and Guidelines, 03-603978.

VoIP transmission hardware

The following circuit packs are essential in an Avaya telecommunications network:

• 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)

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 18

Comments on this document? [e-mail]

VoIP transmission hardware

Transports control messages between servers and port networks.

• TN2302AP IP Media Processor and TN2602AP IP Media Resource 320

Provide high-capacity VoIP audio access to the switch for local stations and outside trunks.

• Branch 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 S8300D Server and
S8300E.

- Survivable Remote server backup for a remote server.

The branch gateways include the G700, G250 Branch Gateway, G350 Branch Gateway,
G430 Branch Gateway G450 Branch Gateway and IG550.

Note:

S8300E supports G430 Branch Gateway and G450 Branch Gateway.

• MM760 VoIP Media Module

Provides another 64 VoIP channel in the G700 motherboard VoIP engine. The MM760 VoIP
Media Module is a clone of the G700.

• Avaya Aura® Media Server

Avaya Aura® Media Server is used by Communication Manager to provide IP audio
capabilities similar to legacy H.248 media gateways or port networks with media processors.

For more information about 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 VoIP hardware on
page 44.

Processor Ethernet

Processor Ethernet (PE) 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. The NIC is the s-called native NIC. PE uses the PROCR IP-interface type. You
do not need additional hardware to implement PE.

During the configuration of a server, PE is assigned to a Computer Ethernet (CE). PE and CE
share the same IP address, but are different in nature. The CE interface is a native computer
interface while the PE interface is the logical appearance of the CE interface within the
Communication Manager software. The interface that is assigned to PE can be a control network
or a corporate LAN. The interface that is selected determines which physical port PE uses on the
server.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 19

Comments on this document? [e-mail]

Networking Overview

For more information about how to configure the server, see Administering Avaya Aura
Communication Manager, 03-300509.

A Survivable Remote server or a Survivable Core server enables the Processor Ethernet interface
automatically. Using the PE interface, you can register H.248 gateways and H.323 endpoints on
the Survivable Remote server. You must set the H.248 and the H.323 fields on the IP Interface
Procr screen to the default value yes.

In Communication Manager Release 5.2 and later, Branch Gateway and H.323 endpoint
registration on the Survivable Core server is possible. Administer the Enable PE for H.248
Gateways and Enable PE for H.323 Endpoints fields on the Survivable Processor screen of the
main server. The IP Interface Procr screen of the Survivable Core server displays the values that
you administered for the H.248 and H.323 fields.

Important:

Both the Survivable Core server and the Survivable Remote server require the PE interface to
register to the main server. Do not disable the PE interface on either server.

®

Support for Processor Ethernet and port networks on a Survivable Core server

In Communication Manager Release 5.2 and later, the capabilities of survivable core servers are
enhanced to support the connection of IP devices to the Processor Ethernet (PE) interface and to
C-LAN interfaces. C-LAN interfaces are located in G650 gateways. G650 are port networks.

A survivable core server can use the PE interface to support IP devices, such as Branch Gateway,
H.323 Gateways, IP Adjuncts, IP telephones, IP trunks, and SIP trunks. The survivable core
server can optionally control port networks through IPSI simultaneously. Without port networks in
the configuration, the survivable core server can provide the equivalent benefit of a survivable
remote server. The survivable core server can be duplicated, providing more redundancy to the
survivability of the system.

For PE on duplex servers to work, assign the PE interface to the PE Active server IP address 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 survivable remote server or the survivable core server registers to the C-LAN on the
main server, the C-LAN must have IP connectivity to the LAN. The LAN must be assigned to
the NIC used for PE on the survivable core server.

• If the survivable remote server or the survivable core server registers to PE on the main
server, PE must have IP connectivity to the LAN. The LAN must be assigned to the NIC used
for PE on the survivable core server.

Firmware for optimal performance

Processor Ethernet on duplex servers works effectively only when the branch gateways and IP
telephones are on the current release of the firmware.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 20

Comments on this document? [e-mail]

LAN security

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 later 96xx and
96x1 models that support Time to Service (TTS) work optimally.

• 4601+, 4602SW+, 4610SW, 4620SW, 4621SW, 4622SW, and 4625SW Broadcom
telephones with firmware R 2.9 SP1 or later. 46xx telephones are supported if the 46xx
telephones are not in the same subnetwork as the servers.

All other IP telephone models must reregister if a server interchange occurs. The 46xx telephones
reregister if the telephones are in the same subnetwork as the servers.

To ensure that you have the most current versions of firmware, go to the Avaya Support website at

http://support.avaya.com. Click Downloads and select the product.

LAN security

Customers do not want users to access the switch by using the INADS line. When users use the
INADS line, users continue to C-LAN and then gain access to a customer LAN. However, the
Avaya architecture prevents users from accessing the customer LAN.Figure 4: Security-related

system architecture on page 21 shows a high-level switch schematic with a TN799 (C-LAN)

circuit pack.

Figure 4: Security-related system architecture

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 21

Comments on this document? [e-mail]

Networking Overview

Logging in through the INADS line, customers can access software. Software communicates with
firmware over an internal bus through a limited message set. The two main reasons why a user
cannot go to the customer LAN through the INADS line are:

• A user logging into software cannot get direct access to the C-LAN firmware.

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

• Communication Manager disables the C-LAN application TFTP and cannot enable the
application.

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

Connection Preservation

Communication Manager supports Connection Preservation and Call Preservation for handling
SIP calls. Any SIP telephone connected to Communication Manager through a server that enables
SIP can use this feature. SIP Connection Preservation and Call Preservation are always active.

Call Preservation and Connection Preservation during LAN failure

When near-end failure is detected, the SIP signaling group state changes to the 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
the In-service/active state. When the active connection is dropped, SIP trunk changes to the Out­of-service state. When far-end failure is detected, the SIP signaling group state changes to the
Far-end-bypass state. Stable or active calls are not dropped, and the SIP trunk changes to the
pending-busyout state. When the active connection is dropped, the SIP trunk status changes to
the Out-Of-Serivce/FarEnd-idle state.

Call Preservation and Connection Preservation when LAN connectivity is revived

When the near-end failure ends, the SIP signaling group state changes to the In-service/active
state. Stable or active calls on the SIP-trunk are kept in the In-service/active state. When the far­end failure ends, the SIP signaling group state changes to the In-service/active state. The state of
Stable or active calls on the SIP trunk changes from pending-busyout to the In-service/active
state.

The Connection Preservation mechanism also works with DCP and H.323 telephones.

Session refresh handling

When SIP session refresh handling fails, the SIP call is set to Connection Preservation. A net
safety timer keeps the call active for 2 hours. After 2 hours, the call drops unless the user ends the
call before that time.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 22

Comments on this document? [e-mail]

Connection Preservation

Connection Preserving Migration

The Connection Preserving Migration (CPM) feature preserves bearer connections while Branch
Gateway migrates from one Communication Manager server to another because of network failure
or server failure. Users on connection preserved calls cannot use features such as Hold,
Conference, or Transfer.

CPM does the following:

• Preserves the audio voice paths.

• Extends the period for recovery operations.

• Continues to function during the complementary recovery strategies of Avaya.

H.248 and H.323 link recovery

The H.248 link connects a Communication Manager server and a gateway. The H.323 link
connects ties a gateway and an H.323-compliant IP endpoint. Link recovery is an automated
method that the gateway uses to reacquire a lost link. The link might be lost from either a primary
call controller or a Survivable Remote server. The H.248 link and the H.323 link provide the
signaling protocol for:

• Call setup

• Call control during the call

• Call tear-down

When the link is out of service, link recovery preserves calls and attempts to reestablish the
original link. If the gateway or the endpoint cannot reconnect to the original server or gateway,
then link recovery automatically attempts to connect with alternate TN799DP (C-LAN) circuit
packs. Link recovery only connects with circuit packs that are within the configuration of the
original server or the Survivable Remote server.

Auto fallback to the primary server

The auto fallback to primary controller feature returns a fragmented network to the primary server
automatically. Fragmented networks have a number of branch gateways that one or more
Survivable Remote servers service. This feature applies to all branch gateways. You can complete
the distributed telephony switch network by automatically migrating the gateways back to the
primary server.

Survivable Remote servers

Survivable remote servers can function as survivable call processing servers for remote or branch
customer locations. Survivable remote servers have a complete set of Communication Manager
features. With the license file, survivable remote servers function as survivable call processors.

If the link between the remote branch gateways and the primary controller breaks, the telephones
and the gateways register with the survivable remote server. Survivable remote servers provide a
backup service to the registered devices and control these devices in a license-error mode.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 23

Comments on this document? [e-mail]

Networking Overview

For more information about survivable remote servers, see Avaya Aura® Communication Manager
Hardware Description and Reference, 555-245-207.

Note:

The survivable remote server is also known as Enhanced Local Survivability (ELS).

Survivable core servers

Survivable core servers provide survivability to port networks by putting backup servers in various
locations in the customer network. The backup servers service port networks when:

• The Simplex server fails.

• The Duplex server pair fails.

• connectivity to the main Communication Manager server is lost.

Survivable core servers can be either Simplex or Duplex servers. The servers offer full
Communication Manager functionality in the survivable mode, provided enough connectivity exists
to other Avaya components. For example, endpoints, gateways, and messaging servers.

Standard Local Survivability

Standard Local Survivability (SLS) consists of a module built in to G430 Branch Gateway or G450
Branch Gateway to provide partial backup gateway controller functionality. The gateway provides
the backup function when the connection with the primary controller is lost. To provide
Communication Manager functionality when no link is available to an external controller, you can
use a G430 Branch Gateway or G450 Branch Gateway without a local S8300E.

Support to tandem MIME for PIDF-LO

Communication Manager Release 7.1.1 can tandem Multipurpose Internet Mail Extensions
(MIME) attachments for Presence Information Data Format Location Object (PIDF-LO) in a SIP
message. Communication Manager can also pass the PIDF-LO information in the SIP message.

Support for Channel Type identification over ASAI to CTI application

Communication Manager Release 7.1.1 supports channel type identification over ASAI to a CTI
application. For incoming SIP trunk calls, Communication Manager Release 7.1.1 identifies the
channel type as voice, video, or unknown when the call:

• Enters a monitored Vector Directory Number (VDN) or hunt group (skill/split).

• Is monitored and is alerting at a deskphone or Agent.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 24

Comments on this document? [e-mail]

Support for Channel Type identification over ASAI to CTI application

For this feature to work, the CTI link between Communication Manager and Application
Enablement Services must be greater than 7.

This feature might not work or might show an unknown channel type on the CTI application when:

• The Direct Media feature is enabled.

• Communication Manager is not able to identify the channel from the incoming SIP request.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 25

Comments on this document? [e-mail]

Chapter 3: Port network configurations

You can control call processing of port networks in various ways by using Communication Manager.
Using only Ethernet connections, you can establish control networks. Over LAN/WAN connections,
you can transmit voice, fax, and TTY. Types of reliability achieved with Duplex servers can include
single control and bearer networks, duplicated control networks, duplicated control and bearer
networks, or a combination of reliabilities.

Types of control networks and the corresponding types of reliability:

• Single control and bearer networks are standard reliability.

• Duplicated control networks are high reliability.

• Duplicated control and bearer networks are critical reliability.

IP port network connectivity

IP port network connectivity allows servers and port networks and Branch Gateways to be
connected over IP networks. Communication Manager uses a proprietary method to package
signaling messages over IP. This method allows deployment of communications systems
throughout a customer’s data network.

For bearer transmission and control signaling from the server, IP port network connectivity (IP­PNC) uses LAN or WAN connections between port networks. Each port network must have either
one or two control IPSI circuit packs for control signaling.

Reliability

Reliability is the capability of a Communication Manager configuration to maintain service when
components within the configuration fail. Components that fail might include Ethernet switches,
circuit packs, or gateways. The available reliability levels depend on whether the port networks
use IP-PNC and whether the server is simplex or duplex.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 26

Comments on this document? [e-mail]

Simplex server

A Simplex server provides several reliability options.

• Standard reliability:

For IP port network connectivity (IP-PNC), a Simplex server supports a single IPSI for
controlling the IP-PNC port network, TN2302BP, or TN2602AP circuit packs. The circuit
packs are used for the bearer network. However, TN2602AP circuit packs are implemented in
the load-balancing mode only.

• Duplicated bearer reliability:

For IP-PNC, a Simplex server does not support duplicated control. However, IP-PNC port
networks can have duplicated TN2602AP circuit packs to duplicate the bearer connections.
In a port network with duplicated TN2602AP circuit packs, control signaling always occurs
over a direct IPSI connection to the server. A duplicated bearer network that uses TN2602AP
circuit packs is implemented for each port network. Uniform implementation for all port
networks within the configuration is not required.

Reliability

Duplex server

A Duplex server has multiple levels of reliability.

IP port network connectivity

Reliability for Port Networks that use IP port network connectivity (IP-PNC) within a single
Communication Manager configuration is implemented for each Port Network. Uniform
implementation for other IP-PNC Port Networks within the configuration is not required. In
addition, duplicated bearer and duplicated control can be implemented independently of each
other.

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

• Standard duplicated servers:

A single IPSI provides control signaling between the Port Network and the server. The Port
Network contains only single or load balancing TN2302BP, or TN2602AP circuit pack pairs.
check data accuracy

• Duplicated control:

In addition to the standard duplicated servers, duplicated IPSIs for control reside in each Port
Network. The Port Network 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 Port Network to provide duplicated bearer.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 27

Comments on this document? [e-mail]

Port network configurations

Note:

For duplicated bearer for IP-PNC Port Networks, use duplicated IPSI control.

• Duplicated control and bearer:

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

Simplex IP-PNC for the single control network

In the IP-PNC configuration, the Simplex server uses IP connections to control call processing on
the port networks. The Simplex server uses an existing VoIP-ready IP infrastructure to send voice
between port networks over the IP network. With this solution, customers save the cost of building
a separate telephony network. In this type of configuration, all port networks are connected to the
server and to each other over the customer network. You can configure up to 64 port networks in
an IP-PNC configuration. Depending on the Ethernet switches to connect to the port networks and
the port network locations, the network can require multiple Ethernet switches to support the port
networks.

G650 Media Gateway: You can use G650 Media Gateway in an IP-PNC network. A G650 port
network can consist of one to five G650 gateways in a stack connected by a TDM or LAN bus
cable. One gateway that functions as a control gateway in position A at the bottom of the stack
contains the TN2312BP IPSI circuit pack. Only G650 Media Gateway is available for new
installations. However, different migrations from older systems are supported.

IP/TDM conversion resource: Each port network 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 for endpoint connections between port networks. You can
insert the circuit packs in any gateway in the port network. Each port network can optionally house
a TN799DP C-LAN circuit pack for control of the:

• G150 Branch Gateway

• G700, G450, G430, G350, and G250 Branch Gateways

• IP endpoints

• Adjunct systems, such as messaging and firmware downloads

Ethernet connections: In the IP-PNC configuration, the Simplex server connects to the gateways
through a single Ethernet switch. Each port network connects to the Simplex server through a
local Ethernet switch. As a result, remote port networks in an IP-PNC configuration over WAN can
require Ethernet switches in addition to the Ethernet switch that supports the Simplex server. You
can administer IP connections to the Simplex server as dedicated private LAN connections or
connections over the customer LAN.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 28

Comments on this document? [e-mail]

Architecture of simplex server IP-PNC

Simplex IP-PNC for the single control network

Number Description

1 Simplex server C or B.

Table continues…

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 29

Comments on this document? [e-mail]

Port network configurations

Number Description

2 Ethernet Switch.

For local LAN connections, the same Ethernet
switch can connect both the servers and the
gateways. For remote LAN/WAN connections, the
remote gateways must have an Ethernet switch at
the remote location.

3 Port networks (G650 Media Gateway or stack).

4 Port network control gateway in the A position in the

gateway stack which contains TN2312AP/BP IPSI
circuit pack for IP connection to server.

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

Note:

For the G650 Media Gateway, you require the
BP version of the TN2312 to provide
environmental maintenance.

5 IPSI-to-server control network connection via

Ethernet switch.

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, port networks, and
adjunct systems. These circuit packs can be
inserted into a port gateway (shown in figure)
or the port network control gateway.

7 Customer LAN/WAN.

8 LAN connections of servers for remote

administration.

Duplicated TN2602AP circuit packs in IP-PNC port networks

For a simplex server, any IP-PNC port network can contain load-balancing or duplicated
TN2602AP circuit packs. However, TN2602AP circuit packs do not need to be implemented
uniformly within the system. Port networks can either have a single TN2602AP circuit pack, load­balancing TN2602AP circuit packs, or duplicated TN2602AP circuit packs. A simplex server can
have duplicated bearer connections although the server does not support a duplicated control
network.

February 2020 Administering Network Connectivity on Avaya Aura® Communication Manager 30

Comments on this document? [e-mail]