Core - Module 05 - Core Integration Basics

71200V | Integrating Avaya Aura® Core Components
Page 1
© 2018 Avaya Inc. All Rights Reserved.
By the end of this module, you should be able to:

• Understand the Platform basics of the Team Engagement Core Components, to
have a good visibility of the Post Installation and Readiness Conditions.
• Have a good understanding of the Licensing Mechanism used for the Avaya
Team Engagement® Solution.
• Install the Security Certificates necessary to establish TLS Encrypted
connections in the Core.
• Perform a Check-List for readiness conditions of the Core Components prior to
building the Core.
• Understand the Links and Relatoinships that must be established to build the
Core.
• Understand the Session Manager Integration Basics.
• Build a CM High Availability Cluster.
Page 2
By the end of this module, you should be able to:

• Understand the Platform basics of the Team Engagement Core Components, to
have a good visibility of the Post Installation and Readiness Conditions.
• Have a good understanding of the Licensing Mechanism used for the Avaya
Team Engagement® Solution.
• Install the Security Certificates necessary to establish TLS Encrypted
connections in the Core.
• Perform a Check-List for readiness conditions of the Core Components prior to
building the Core.
• Understand the Links and Relatoinships that must be established to build the
Core.
• Understand the Session Manager Integration Basics.
• Build a CM High Availability Cluster.
Page 3
Page 4
Before starting with the Team Engagement Core Integration, a check for readiness
has to be done on each of the three basic components, through a wide number of
parameters and conditions.
Click to find out about each Core Product high level checklist for readiness.
Page 5
Page 6
The Team Engagement Core consists of 3 main elements: System Manager,

Session Manager and Communication Manager.
System Manager is a multi functional server, which, as far as the basic core is
concerned, and among other things, works as the management front end for
Session Manager, and alternate administration interface for Communication
manager, a centralized licensing server, a specialized directory server for
administrators and SIP accounts, and a Certificate Authority for Session Manager,
Communication Manager and the various SIP Endpoints.
Session Manager works as a SIP Proxy, which connects Endpoints and SIP
Switches and SIP Application Servers together in a flexible and secure way. It plays
the role of a local Registry as well as an edge Proxy, routing the calls to other
switches and Application Servers though SIP Trunks.
Communication Manager has a double purpose from the Core Standpoint. It
provides the Avaya SIP Endpoints with features and Call Processing as a Feature
Server, and also connects the SIP cloud to Legacy H.323, Analogue and Digital
Endpoints, as well as Analogue and Digital Trunks beneath the CM Umbrella.
Page 7
Page 8
CM has a unique mechanism to add high availability to its functions, compared to

other Aura Components.
CM Duplex Cluster works on a active-standby structure, although each CM is
connected to the Corporate Network and has its own IP Address, they also share a
common IP address called Alias.
Endpoints and Trunks shall use the Alias IP Address, to register and exchange any
Signalling Information, but only Active CM will respond to those messages.
Whichever CM Duplex Server, playing the active one at a given time, will update
the Memory content to the Standby one, through a separate back-to-back network
called Duplication Link. Similarly, when the memory content gets saved to the Hard
Disk, it automatically gets saved on both servers.
Page 9
Page 10
Configure both CM Duplex Servers to build a Cluster-Unit.

From SMGR, add CM as a Managed Element, so CM can be configured from
SMGR.
From CM SMI Web, import the SMGR Certificate and make it trusted.
Page 11
From CM, build the SIP Trunk to ASM.

From CM SAT Console, add the Dial Plan, Call Routing entries, and modify the
necessary route patterns to reach the ASM SIP User Agents.
Page 12
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23
Page 24
Page 25
Page 26
Page 27
Page 28
Page 29
Page 30
Page 31
TLS, Transport Layer Security, is an industry-standard security protocol for

encrypted communications, and is the most widely used protocol for secure
connections over internet.
TLS is implemented based on client-server structure. In TLS connection
establishment, the initiator or client, of a secure communication, will provide a list of
supported cryptographic suites to the receiver or server, while initiating the session.
The receiver will select the strongest encryption algorithm combination, from the
list, based on its own capability.
The two parties will start the communication by using the selected algorithm
combination.
Page 32
Nowadays, for privacy and security purposes, Cryptography has adopted a Key-
Role in Communications.
TLS is an Encrypted alternative to TCP connection oriented but with cryptography
added.
TLS 1.0, 1.1 and 1.2 supported in Avaya Aura 7.1 and a minimum TLS version can
be set.
TLS requires a mechanism through which a proven identity certificate is shared
between two peers.
The Certificate Authority, issues certificates that are later exported to other servers,
clients, endpoints, etcetera.
These certificates must be made trusted by each peer so that the TLS
communication goes on.
When two peers trust the same certificate, issued by the Certificate Authority, they
will trust each other automatically.
Page 33
Page 34
Page 35
Page 36
Page 37
Page 38
Page 39
Page 40
The Minimum TLS Version feature provides the ability to administrators to define
the minimum TLS version, to be deployed for negotiating TLS encrypted
connections.
The feature was built for customers, who desire to specify a higher operational
version of TLS, to operate in a higher security environment
Product Release Requirements:
• ASM Release 7.1
• CM Release 7.1
• G430/G450 Release 7.1 – load 38.14 (or newer)
Page 41
A Session Manager Administrator can choose to specify minimum TLS version

usage for the following connection types:
• SIP Entities (SIP Clients and SIP Trunks)
• Endpoints (HTTPS push of PPM profile information)
Configured in SMGR-Element-Session Manager-Session Manager Administration-
Global Settings
Pull-down window offers choices of TLS versions (1.0, 1.1, 1.2)
Page 42
A Communication Manager Administrator can choose to specify minimum TLS

version usage for the following connection types:
• System Management (SMI) pages
• CM Duplication link
• FileSync connection
• CM Signaling Connections (SIP trunks, H.248 gateways, H.323 phones, AES)
Configured in System Management Interface-Security-Server Access
Pull-down window offers choices of TLS versions (1.0, 1.1, 1.2)
Page 43
Using the System Manager web interface, navigate to Elements-Session Manager-

System Status-Security Module Status.
Select the appropriate Session Manager
Click Connection Status
The TLS version displays in the Transport field
Page 44
Page 45
After completing this lesson, you will be able to describe the process for configuring
Communication Manager as a Managed Element.
Page 46
Page 47
Page 48
Page 49
Page 50
Page 51
Page 52
Lesson 8: Configuring Communication Manager as a Managed Element.
Page 53
One benefit of configuring CM as a managed element is that System Manager can

replace Avaya Site Administration (ASA) or System Administration Terminal (SAT)
in managing Communication Manager. Important - CM must become a Managed
Element before it can provide features to SIP phones.
Begin at the System Manager (SMGR) web console main screen. Click the
Elements menu and then select Inventory.
Hostname/IP address – points to the CM Duplex Server 1’s IP address (not the
Alias)
Alternate IP address – points to the CM Duplex Server 2’s IP address (not the
Alias)
Enable Notifications – required for changes made directly in Communication
Manager to be replicated in System Manager
Login – the CM login that you wish System Manager to use when accessing
Communication Manager
Password – the password for the above CM login.
Page 54
SNMP Attributes
SNMP enables CM for polling and monitoring, and enables SMGR to receive
any alerts from CM. Each customer network is different but in our lab we’ll use
“public” for the read and write community settings. The rest of the fields can
stay at default.
Note that System Manager and CM support both SNMP v1 and SNMP v3.
Page 54
Page 55
Using the Initialize data for selected devices option we are asking Communication
Manager for it’s entire database, this may take a few minutes!
Page 56
From the Synchronization/Communication System page we can see the status of

the last synchronisation, order a Full system synchronisation (Initialize data for
selected devices) or a synchronisation of just the changes made since the last
sync (Incremental Sync data for selected devices).
Page 57
Changes made in Communication Manager, using Avaya Site Administration (ASA)

or similar tools, are reflected in System Manager almost immediately.
Page 58
Now that the data has been synchronized between System Manager and
Communication Manager, let’s look at the data that has been brought over from
Communication Manager.
To do that, go from the System Manager Common Console and click the
Communication Manager link. This launches the web pages associated with
Communication Manager.
The Communication Manager menu is located under the Elements menu on the
System Manager Common Console. Click the Communication Manager link to
launch the web pages for managing the Communication Manager endpoints.
Page 59
Now, let’s select the Endpoints menu options.
Page 60
Page 61
Page 62
Page 63
Page 64
Page 65
Page 66
Page 67
Page 68
Page 69
Page 70
Off-PBX Telephony Integration Mapping (OPTIM)

• Used by Advance SIP Telephones (AST) to enable advanced CM features
Good practice to separate :-
• Advanced SIP Telephony (AST) phone traffic from other traffic such as calls
routing to/from Internet Telephony Service Providers (ITSP) via SBCE
• Enables sizing of trunks according to need and prevents OPTIM traffic starving
non-OPTIM traffic, or vice versa
• Separation can be achieved using different transport ports or SIP domains on the
SIP Entity/Entity Links/Signaling Groups/Trunk Groups
Page 71
Page 72
Page 73
Page 74
Page 75
Page 76
Lesson 9: Configuring Communication Manager Application and Application

Sequence.
Page 77
Session Manager watches over registered SIP Users and all of their calls, both
incoming and outgoing, ready to take any special action when the occasion
requires.
Session Manager uses a pre-defined Application Sequence to apply special rules
or features to individual users. For example, one feature server in the sequence
might block certain types of calls, another feature server might forward certain
other calls to an announcement, and Communication Manager might apply its
features to the remaining calls. Application Sequencing enables us to apply
services and features that go way beyond simply routing a call from Point A to Point
B. And all these choices are made by the System Administrator who builds and
assigns the Application Sequences to SIP users.
Page 78
Because it is a private branch exchange, Communication Manager is different from

most other application servers employed in an Application Sequence. Over the
years, we have programmed CM with numerous features and have coordinated
those features so they don’t conflict with each other. So, instead of having to create
a sequence that requests each one of perhaps a thousand individual features, it is
enough to hand the call to CM. We can trust that it will know which features to
engage. So, in an Application Sequence when Session Manager routes the call to
Communication Manager, Session Manager needs to identify only the relevant
extension numbers.
Obviously, this assumes an administrator has already programmed the extensions
in Communication Manager and assigned to them appropriate features. If
Communication Manager doesn’t recognise a caller’s extension, it simply can’t
process the request.
In short, all Session Manager needs to be programmed to do is to the route the call
request, along with the extension numbers, to Communication Manager. We can
trust that Communication Manager will know what features to invoke.
Page 79
An application sequence is a list of applications that should applied, in a particular

order, to a call. Typically, an administrator would have programmed several
different sequences, each of which produces a different effect.
These Application Sequences are applied to calls using the half-call model. That
means the call is broken into two parts. The first half of the call is determined by the
caller who originates the call. The second half of the call is determined by the callee
who receives the call. Another way to describe the two halves of the call is to use
the terms the origination side and the termination side.
When administering SIP User Agents, such as SIP Phones, the critical information
is contained in their User Profiles. It is there where we identify which Application
Sequence to apply when the device is the origination source of the call, and which
application sequence to apply when the device is the termination destination of the
call.
This model where we distinguish between the origination and termination of calls is
fundamental to the IMS Architecture – IP Multimedia Subsystem (IMS).
Page 80
In the first half of the call, Session Manager acts in the Origination mode, applying
features assigned in the caller’s Origination Application Sequence. When all the
originating features have been applied to the outgoing call, Session Manager then
switches over to Termination mode. It then applies all the features found in the
callee’s Termination Application sequence to the incoming call.
Page 81
Now that we have covered the concepts, it’s time to discuss how you create an
Application Sequence that calls upon CM to provide features. There are some
programming steps that must be completed first, and must be done in this order:
Define CM as a SIP Entity and include it in a Network Routing Policy. This ensures
that Session Manager knows how to route SIP messages to Communication
Manager for processing.
Define CM as a Managed Element, which means that System Manager has been
programmed to administer Communication Manger and therefore knows about all
the extension numbers within CM. System Manager will share that information with
Session Manager.
Define CM as an Application Server. We need to ensure that System Manager
knows what information to provide to CM so that CM can process the appropriate
features.
Only then can you add the CM Application Server to Application Sequence. Note
that CM might be just one of several feature servers to provide calls. In that
sequence, we will determine the order in which the feature servers will be invoked.
Page 82
Here is the screen where we define Communication Manager as an application. We

will begin by assigning a name to this application server so that we can recognize it
later. In the example, we have chosen to call it CM App.
Because Session Manager communicates with CM, using SIP, we need to have
previously defined CM as a SIP Entity, and configured the Entity Links between it
and Session Manager. Here, we tell Session Manager which SIP Entity we will be
using. In this case, the SIP Entity is called CM1.
Back when we configured CM as a SIP Entity, we identified it to be of Type
Communication Manager. In this screen, as soon as you pick the SIP Entity that is
the source of features, it will be treated by System Manager as a special type of
SIP Entity—as a Communication Manager. In order for System and Session
Manager to deliver the appropriate CM features to a SIP endpoint, that CM must be
configured as a Managed Element. In other words, System Manager must have a
recently synchronized copy of CM’s translations database. So, here on this screen,
we need to identify which Managed Element CM, of the possibly 500 CMs that a
single System Manager can administer, is the same CM as the SIP Entity CM. In
this example, the Managed Element CM is called CM1.
Finally, at the bottom of the screen is the Application Attributes section. For most
application servers, we would need to specify more information in this section. But,
Page 83
because Communication Manager is a special type of application server, we

do not need to identify any more parameters. We leave it blank.
When we are satisfied with our work, we click Commit to save it.
Page 83
Now that we have defined Communication Manager as an Application, we go to the

Application Sequences menu link to launch the Application Sequence Editor
window.
Once again, we need to give this application sequence an easy-to-recognize name.
In this case, we chose the name CM App Seq.
When you first open this window, all applications that have been defined appear at
the very bottom of the screen under the Available Applications menu. In this
example, the only application we have defined so far is the CM App. But, in a real-
world scenario, there might be a dozen or more applications appearing here.
By clicking the plus sign next to an application, it is added into the sequence. In this
case, our sequence consists of this one application. But, if we had more
applications in the sequence, there are ways to re-arrange the order in which they
would be invoked by using the little arrows.
When satisfied with our work, we click Commit to save it.
Page 84
Page 85
Page 86
New for Avaya Aura 7.0 – Avaya Aura Media Server can provide another option for
older gateways for IP audio. Previously, Communications Manager relied on
hardware based DSPs that can now be replaced by software-based DSPs, on a
Virtual Machine. AAMS Provides a software based media application platform.
It connects to Communication Manager by SIP and is software only, with no
proprietary hardware. This means gateways are no longer required for media
resources. They might still be required for other reasons such as digital or analog
trunking. Media Gateways are required for analog and digital or TDM scenarios.
Avaya Aura Media Server (AAMS) 7.8 – Media source for Avaya Aura®
Communication Manager 7.1.
Software-based media server – AAMS provides soft DSP/media channel resources
on general-purpose hardware, with multiple deployment options.
Benefits:
Add to existing G650 and G450 DSP resources utilizing smaller footprint.
Possible to replace existing G650/G450 DSP resources, resulting in potentially
massive reduction in hardware footprint.
Page 87
Same voice announcements can be deployed to AAMS that are already

centrally deployed to CM-VAL boards, using the SMGR hosted VAL
Management functionality.
Reduced costs for call recording by reducing gateway footprint.
AAMS provides features not offered by Media Gateways and Port Networks:
Virtualization
High channel density
No playback announcement limits
Additional codecs
Page 87
The Avaya Media Server can reduce the hardware footprint. One Avaya Media
Server can replace 13 G450 Media Gateways, 4,160 channels, and 39U rack
space.
Page 88
The following Use Cases show the best scenarios for adopting the Avaya Media
Server with Communication Manager.
Best fit for AAMS with CM
• Call center requiring lots of DSP resources for call recording, announcements, or
IVR applications (digit collection)
• Customers with MCC or G650 cabinets looking to reduce their footprint as they
upgrade and transition to IP
• All IP construct (H.323 or SIP endpoints) with high DSP/media channel
requirements
Best fit for Gateways with CM
• Not ready for all IP. Still require TDM (analog and digital) and T.38 fax
• Customers with existing G450s who want to keep their investment
• These customers might add AAMS if doing a major addition
Page 89
CODEC stands for Encoder Decoder. It’s a mechanism for crafting Media Packets
in a format that can be easily transportable over a Data Network.
Audio gets digitized by some circuitry, which delivers a chain of bits. This stream is
broken in small chunks of information and some headers are added for
transportation over the data network, by a combination of software and Digital
Signal Processors or DSPs.
When the Codec has compression, DSPs also do their job.
DSPs also convert digital audio from one Codec to another, when necessary.
Once the packets have been crafted properly, they are handed off to the network.
Page 90
On an IP network, there are two types of Layer Four and Five Services, one called
TCP which controls and guarantees the reliable delivery of the information through
an acknowledgement of reception mechanism.
The other is called UDP, which is faster but not as reliable as TCP. It manages the
delivery of information without confirming so.
RTP generates eight thousand packets per second, switching the handset from the
left to the right ear makes about two thousand packets being spoken into the air,
and the conversation still goes on without having to repeat anything. The human
brain has the ability to reconstruct the phrase even though a few sounds get lost on
their way.
This makes perfectly possible and practical to send Audio through UDP a not so
reliable service, which, being faster than TCP, guarantees a better throughput and
quality, for a time sensitive application like RTP.
H.225 RAS also uses UDP transport services, although it can’t afford loosing a
single bit along the way. The reason why H.225 RAS has it’s own mechanism is for
reliable delivery implicit in the protocol.
Page 91
Why was H.225 RAS implemented over UDP services? Mainly because upon
a CM restart, all phones will try to register at the same time, which, for a CM
with thousands of stations, would have been overwhelming for the data
network, if TCP was used instead.
H.225 Call Signalling and H.248 don’t represent much work load for the
network while they rely mainly on TCP error correction mechanism, hence their
dependency on TCP.
SIP can be conveyed by either UDP, TCP or TLS which is a connection
oriented service like TCP, but encrypted. TLS, as opposed to UDP or TCP,
requires a trust based relationship between peers, where security certificates
must be exchanged for the relationship to be established.
Audio is directly encoded by the Digital Signal Processors into RTP as you can
see.
Page 91
Page 92
Page 93
Page 94
Page 95
Page 96
Page 97
Page 98
Page 99
Page 100
Page 101
The Correct answer is A. True.
Page 102
Page 103
The Correct answer is D
Page 104
Page 105
The Correct answer is A & C
Page 106
Page 107
The Core of Avaya Team Engagement® is built upon three main elements:
• System manager (SMGR)
• Session Manager (ASM)
• Communication Manager (CM)
Each Component of this Core can be deployed with different levels of complexity,
based on the number of users and fault tolerance options.
The Team Engagement Solution components obtain their licensing services from
the SMGR‘s WebLM service as a central point of contact.
The lab exercises presented in this course, are intended to deliver good
understanding of how to build the Core scopes with the minimum necessary
components to keep the tasks as simple as possible, yet reliable enough.
Prior to a Green-Field installation, or an integration of existing components, it‘s
always necessary to carry out a Simple Pre-Check for readiness to guarantee a
successful Integration.
Page 108
Page 109

Core - Module 05 - Core Integration Basics

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Core - Module 05 - Core Integration Basics

Uploaded by

Copyright:

Available Formats

71200V | Integrating Avaya Aura® Core Components

By the end of this module, you should be able to:

By the end of this module, you should be able to:

The Team Engagement Core consists of 3 main elements: System Manager,

CM has a unique mechanism to add high availability to its functions, compared to

Configure both CM Duplex Servers to build a Cluster-Unit.

From CM, build the SIP Trunk to ASM.

TLS, Transport Layer Security, is an industry-standard security protocol for

A Session Manager Administrator can choose to specify minimum TLS version

A Communication Manager Administrator can choose to specify minimum TLS

Using the System Manager web interface, navigate to Elements-Session Manager-

Lesson 8: Configuring Communication Manager as a Managed Element.

One benefit of configuring CM as a managed element is that System Manager can

From the Synchronization/Communication System page we can see the status of

Changes made in Communication Manager, using Avaya Site Administration (ASA)

Now, let’s select the Endpoints menu options.

Off-PBX Telephony Integration Mapping (OPTIM)

Lesson 9: Configuring Communication Manager Application and Application

Because it is a private branch exchange, Communication Manager is different from

An application sequence is a list of applications that should applied, in a particular

Here is the screen where we define Communication Manager as an application. We

because Communication Manager is a special type of application server, we

Now that we have defined Communication Manager as an Application, we go to the

Same voice announcements can be deployed to AAMS that are already

The Correct answer is A. True.

The Correct answer is D

The Correct answer is A & C

You might also like