7120V - Core - Module 04 - Session Manager - v4 - 1 PDF

Module 4:
Avaya Aura® Session

Manager
© 2017 Avaya, Inc. All rights reserved. Page 1

Module Objectives
After completing this session, you will be able to:
 Identify the purpose and key functionality of Avaya Aura®
Session Manager
 Describe the deployment process for Avaya Aura ® Session
Manager
 Describe the post-installation check for Avaya Aura® Session
Manager
 Describe the process for the Session Manager Core
Integration
 Describe the troubleshooting tools used for Avaya Aura®
Session Manager

Module Lessons
The Lessons in the Session Manager module are:
 Lesson 1 – Session Manager Overview
 Lesson 2 – Evolution of the IMS Network
 Lesson 3 – Session Manager Deployment Process
 Lesson 4 – Building the SIP Network
 Lesson 5 – SIP Registration and Registry Routing
 Lesson 6 – Network Routing Policy Design Overview
 Lesson 7 – Configuring Network Routing Policy
 Lesson 8 – Configuring Communication Manager as a
Managed Element
 Lesson 9 – Configuring Communication Manager as a
Application and as an Application Sequence
 Lesson 10 – Maintenance and Troubleshooting

Session Manager Lab Exercises
 Here are the lab exercises for the Session Manager module:
1. Session Manager Post-Implementation check
2. Session Manager Core Integration
3. Configuring Network Routing Policies
4. Session Manager Alarms
5. Backup and Restore
 Refer to your Lab Exercises document for the step-by-step instructions on
performing these exercises.
 You also have a Lab Document that provides the information on the pod numbers
and IP addresses to use during the exercises.

Lesson 1:
Session Manager
Overview

Lesson Objectives – Session Manager Lesson 1
After completing this lesson, you will be able to:
 Describe the purpose and key functionality of Avaya Aura®
Session Manager.

Session Manager Overview
 Many companies have a variety of communication
servers and endpoints within their organization. Session
 As companies grow, add branch offices, or acquire Manager
other enterprises, they need a way to integrate these
different communication devices into a centralized
system.
 Session Manager provides a solution to this business
need.
 Session Manager uses Session Initiation Protocol
(SIP), which provides a standard signaling protocol for
communication across the enterprise.
 Avaya uses both SIP and H.323 signaling protocols in
its products

What is Session Initiation Protocol (SIP)?
 You will hear SIP mentioned throughout this module. But
what is SIP?
 Session Initial Protocol (SIP) defines a mechanism or set
of communication standards by which a Voice over IP
(VoIP) conversation or session can be started.
 Traditional telephony is based on circuit-based switching.
 SIP is based on internet protocols and uses packets for
media exchange.
 SIP does not carry any media such as voice, video, or
instant messaging – it is a signaling protocol only.

SIP Signaling and Media
 A SIP session consists of two parts:
– Signal – starts the communication session
– Media packet exchange – the content of the session
 This diagram represents the SIP message flow and shows the two parts:
– SIP Signal
– RTP Media stream

SIP Background /The SIP-Knowledge Check-In Quiz
 Prior to all Aura Solution-Based
Training Programs, students are
encouraged to take a Standard SIP
Basic Knowledge Check-In Quiz.
 The deeper the student’s SIP
knowledge is, the better the chances of
being successful in managing every
installation, configuration, and support
scenario across the Avaya Aura®
components and their integration.
 The intention of the SIP Quiz is to help students measure how proficient they
are in SIP matters in general.
 The score is only for the student to see and does not impact any Avaya
Learning training session or certification exam – it is for your own training.
 To access the SIP Quiz, proceed to the following link:
– http://sipsense.com/test/avayasiptech/sip-foundation-quiz

SIP Background /The SIP sense® 3rd-Party Training
 Avaya Learning does not provide Standard SIP Training directly.
 Instead, Avaya Learning encourages students who would like to leverage their SIP
knowledge, to proceed to SIP sense® (sipsense.com), a Learning Partner that
offers SIP training online.
 Use the following link: http://sipsense.com/catalog/Course/11/sip-foundation
 The SIP sense Essential SIP program covers all the main RFC 3261 topics, plus
content on implementation in service provider and enterprise networks.
 SIP sense offers a
discount voucher to all
those students who,
after taking the SIP
Quiz, are interested in
improving their
proficiency in SIP
matters.

Session Manager Routes and Integrates
 Session Manager is a centralized SIP routing and integration tool.
 It also provides service and access to features for SIP Endpoints.
Session
Manager
ooo
3rd Party PBXs
SIP Endpoints
ooo
Heritage
Avaya PBX

Session Manager Functionality
Centralized SIP Routing Integration and Adaptation SIP Firewall
Scalable High Availability and Redundancy Registration and Authentication

Documentation and Resources
https://support.avaya.com
support.avaya.com
 What’s New with Avaya Aura® Release 7.0

 What’s New with Avaya S8300E Server
 Deploying Avaya Aura® Applications
 Deploying Avaya Aura® Utility Services on Avaya Aura® Communication Manager on
VMware®
 Deploying Avaya Aura® System Manager on VMware®
 Upgrading System Manager to Release 7.0 on VMware in Virtualized Environment
 System Manager 7.0 SNMP White paper (including MIBS)
 Deploying Avaya Aura® Session Manager on VMware®
 Avaya Aura® Application Enablement Services using VMware® in the Virtualized Environment
Deployment Guide
 Deploying Avaya Aura® Application Enablement Services in a Software-Only Environment
 Avaya Aura® Presence Services Snap-in Reference
 Migrating from System Platform to Appliance Virtualization Platform
 Upgrading to Avaya Aura® 7.0
 Deploying and Updating Avaya Aura® Media Server Appliance © 2017 Avaya, Inc. All rights reserved. Page 14
Checkpoint
What is the function of Avaya Aura Session Manager? Choose two.
A. Register digital (DCP) and H.323 endpoints

B. Act as an H.323 routing engine
C. Act as a sophisticated SIP routing engine
D. Provide SIP service to SIP endpoints

Checkpoint
What is the function of Avaya Aura Session Manager? Choose two.
A. Register digital (DCP) and H.323 endpoints

B. Act as an H.323 routing engine
C. Act as a sophisticated SIP routing engine
D. Provide SIP service to SIP endpoints

Lesson Key Takeaways
You have successfully completed the following learning objectives:
 Describe the purpose and function of Session Manager

Lesson 2:
Evolution of the IMS

Enterprise Network and
Session Manager

Lesson Overview – Session Manager Lesson 2
 Describe the differences in the heritage enterprise telephony
networks and the IP Multimedia Subsystem, or IMS.
 Describe the basic components for building the Avaya SIP
network.

What is an IP Multimedia Subsystem?
 Session Manager is part of a network
called an IP Multimedia Subsystem, or
IMS.
 Simply defined, an IMS network builds
on a traditional voice-telephony
network to include SIP-based
telephony devices.
 In the next series of slides, we will
review this evolution from the
traditional voice network to the IMS
network.
 We will also present the main
components of Session Manager and
illustrate how they function in this IMS
network.

Enterprise Communications – A Look Back
 Let’s take a look at the evolution of Enterprise Communications and how Session
Manager dramatically changes how enterprises function.
Session Session
Manager Manager

The Legacy TDM PBX
PSTN Application
Connection Mgmt
Access
 Limited Scope  Primarily Designed for Voice

 Multi-Location  Multiple Systems  PBX owns entire user experience
 Lack of Geo-Redundancy  Devices are tightly bound to PBX
 Resources bound to PBX  Devices are unsophisticated
 Limited Scalability  New Services  Upgrade
 Very Limited Mobility  Single Vendor
 Large Footprint  Application Integration Limitations

The IP PBX
Application
PSTN
IP Connection Mgmt
IP H.323 /
Unistim
Access

 Scalability  New Services  Upgrade

Leveraging the New IMS Network
App App App

App App
Application
Application Platform
IP SIP
PSTN
Connection Mgmt
Session Session
Manager Manager
IP SIP
ooo
ooo Access

Improved
 Scalability  New Services  Upgrade Problem Fixed

Avaya Aura® IP Multimedia Subsystem (IMS) Architecture
Avaya
Avaya Aura® Communicator
Applications Applications Applications
System Manager Portfolio and Snap-Ins and Snap-Ins
Avaya Aura Presence Services
Avaya Scopia® Avaya Aura Messaging
Desktop and Avaya Aura Contact Center
Mobile Clients Avaya Aura Experience Portal Avaya
Engagement
Development
Platform
Avaya Session PSTN
Boarder
Avaya Aura® Session Manager Controller for
Enterprise
SIP
Trunks
TDM
Trunks
Avaya Aura
Conferencing
Avaya G
AES Series
Gateway
Avaya Avaya Aura® Avaya Aura®

SIP endpoints 3rd-Party PBXs Avaya Aura® Avaya CS 1000 Communication Media Server
for Survivable Manager
Remote

Tail-End Hop Off
 Session Manager can be configured to route off-network calls through the WAN
and then hop off to local PSTN trunks.
Enterprise a
Jim
Bob
Enterprise b
PSTN
If a dialed number has the international dial code for Australia and the
city code of Sydney, then route to our gateway in Sydney office
Short hop – cheaper than long hop

Least Cost Routing
 Telco service providers have different costs for their lines so prices may change,
depending on time of day.
 Least-cost routing is finding the cheapest connection.

Scale and Redundancy

Remote Survivability
 A Survivable Remote instance of Session Manager can be configured as a branch
solution and is also known as a Branch Session Manager.
 Branch Session Manager is offered as a standalone OVA.
 Performs local site SIP message routing, including SIP Registry routing.
 Can provide connectivity to a local feature or application server.
CORE
SM Enterprise WAN
SM
SM
Branch LAN

Call Admission Control
CORE
SM
SM
SM

Session Manager Security
 Session Manager handles security primarily through the SM100 Module.
 SM100 is the front door of Session Manager, acting as a SIP Firewall and denying
or granting access to all SIP traffic.
 The SM100 offloads most of the heavy security processing and provides a
framework for Session Manager security.
SM100
No se puede mostrar la imagen.

Secure SIP Routing
 The following are additional security capabilities of Session Manager:
 The SM100 is the security module that manages SIP connections between
Session Manager and all other SIP elements.
 All SIP Endpoints must be configured with a SIP Communication Profile to be
considered trusted on the SIP Network.
 Session Manager requires authentication of SIP Endpoints.
 All SIP Entities must be configured with SIP Entity Links and integrated in order
for SIP sessions to be routed to and from them.
 All SIP elements connect to Session Manager through the SM100 software
module.

Quick Reference
Session Manager Network Architecture Terms
 Here are some key Session Manager network
terms that will be used throughout this module.

Session Manager Network Terminology
Term Definition
Avaya Aura® Session The Core of the Avaya Aura enterprise providing centralized routing,
Manager (ASM) SIP registration, security, and multi-vendor integration
Avaya Aura® System Avaya’s Centralized Administration/Management Platform – the

Manager (SMGR) primary way to configure Session Manager
IP Multimedia Subsystem is a type of enterprise or SIP domain, which

IMS Enterprise was designed for delivering IP multimedia services allowing for the
Network application of features from many different feature servers, regardless
of vendor.
IMS defines an ISC (IMS Service Control) Interface, a process

ISC Interface through which a server like Session Manager can invoke external
applications.
SIP Domain IMS level SIP enterprise network that Session Manager supports
SIP Entities Trusted servers in a SIP domain
Logical link that connects trusted SIP entities to Session Manager
Entity Link
defined by a port and transport protocol
SIP Communication Users created for all SIP endpoints in Session Manager in order for
Profile registration and routing to take place
Session Manager Network Terminology (continued)
Term Definition
Grouping of devices in a SIP domain based on their IP address scheme
Location
and/or geographic location
Dial Pattern Matching Method used to match a user’s dialed digits to a routing policy
Network Routing
NRP defines the destination to which a call will get routed.
Policy (NRP)
SIP sessions routed based on the location of a registered endpoint or

Location Routing
SIP Entity
A user's SIP phone number, using the following format

SIP URI
<username>@<SIP Domain>, for example, 1011911@avaya.com
The request a SIP endpoint sends when it wants to register to Session

Registration Request
Manager during the login process
A SIP message request from a SIP endpoint to a Session Manager

Subscribe Request
identifying it as its Primary Registrar
SIP message request sent from a SIP endpoint or entity wanting to

Invite Request
establish communication

Session Manager Network Terminology (continued)
Term Definition
TLS Secure transport layer protocol used by Avaya Session Manager (ASM)
Transmission Control Protocol provides reliability and error checking. Used
TCP
by Avaya Session Manager (ASM)
The process in which a trusted SIP endpoint authenticates with a SIP
Registrar such as Session Manager within a SIP domain and exchanges its
SIP Registration
extension and current IP address location in order to be able to receive
calls
Process in which System Manager sends a copy of its database to any
Replication
Session Manager instance configured in the SIP domain
Process in which CM’s or ASM’s database is synchronized with System
Synchronization
Manager
Initial Trust Management is the process in which a trust relationship is
established between Session Manager and System Manager for the
InitTM
purpose exchanging security certificates and allowing replication of the
System Manager database to Session Manager(s).
Enrollment The password Session Manager requires to exchange security certificates
Password with System Manager during the installation process

Checkpoint 1
Which of the following best describes the IP Multimedia Subsystem?
A. A multi-vendor, open, and flexible network architecture

B. Restricted, where the PBX provides most of the resources
C. Highly scalable network with little mobility
D. Interoperability is limited with proprietary forms of signaling
protocols

Checkpoint 1
Which of the following best describes the IP Multimedia Subsystem?
A. A multi-vendor, open, and flexible network architecture

B. Restricted, where the PBX provides most of the resources
C. Highly scalable network with little mobility
D. Interoperability is limited with proprietary forms of signaling
protocols

Checkpoint 2
What component of Session Manager provides security to the SIP domain?
A. SM100 Security Module

B. System Manager security policies
C. PPM Module
D. SIP Firewall Appliance

Checkpoint 2
What component of Session Manager provides security to the SIP domain?
A. SM100 Security Module

B. System Manager security policies
C. PPM Module
D. SIP Firewall Appliance

 Session Manager is part of an IP Multimedia Subsystem (IMS
network).
 Session Manager’s SIP-based routing provides centralized
control capabilities and significant improvements in scale and
redundancy, enabling more cost-effective and larger
distributed enterprise deployments.
 Avaya Aura® Session Manager leverages the existing PBX
infrastructure, helping ensure an evolutionary path forward that
protects investment in today’s Avaya systems and software.

Lesson 3:
Session Manager
Deployment Process

Lesson Objectives – Session Manager Lesson 3
 Describe the deployment process for Session Manager
 Identify the basic configuration steps necessary to complete
the Session Manager deployment process
 Perform the steps for the post-deployment verification

Avaya Aura® Session Manager Deployment Checklist
Here is a high-level overview of the OVA deployment activities
Pre-Deployment Deployment Post-Deployment
 Assess and verify the  Verify that System Manager  Configure the elements to
resource requirements with is configured connect Session Manager to
the customer  Deploy the Session Manager System Manager
 Enter the required OVA  Verify the enrollment
information in the Customer – Using AVP password
Configuration Data  Install the license file using
– Using customer’s
worksheet the System Manager
virtualized environment
 Verify that the customer has WebLM
 Configure the Session
all the required hardware at  Enable Enhanced Access
Manager virtual machine to
the site Security Gateway (EASG) if
start automatically after a
 Obtain license file from power failure. required
PLDS  Apply any Service Packs
 Start the Session Manager
 Obtain OVA and latest virtual machine.  Run maintenance tests
Service Packs from PLDS or
 Synchronize the database
the Avaya Support site

OVA Deployment Review
 The Session Manager OVA can be deployed by two methods:
– The Virtualized Platform option , using Avaya Virtualized Platform (AVP), which provides
the server, the customized ESXi environment, and the OVA
– The Virtualized Environment option , where the customer provides the servers and the
ESXi environment and Avaya provides the OVA
– Note: The OVA is the same for either deployment option.
 Refer to the Back-Up slides for the detailed steps to deploy the Session Manager
OVA.
– The OVA install process is similar for all applications , although there are some
differences in some of the individual screens that you fill out.
Note:
Refer to the following courses for more information on installing the OVAs:
2012V – Migrating and Upgrading to Avaya Aura® Platform.
2011V or W – What is New in Avaya Aura® System Manager and Session
Manager 7.0.

Connect Session Manager with System Manager
 After both Session and System Manager have been installed, Session Manager
needs to make a connection with System Manager.
 Once Session Manager has established a trusted connection with System
Manager, and the initial database replication occurs, Session Manager is ready to
be configured.
System Manager
Session Manager
Master Data
Database
Replica Data
Repository
Database

Connect Session Manager to System Manager
 Here are the high-level steps to connect Session Manager to System Manager.
 These steps must be completed before you can configure the Session Manager
routing.
1 Create the SIP Domain
2 Create the Location
3 Configure Session Manager as a SIP Entity
4 Configure the Session Manager Instance
5 Manually activate SIP Services by accepting New Service
6 Validate the Session Manager status

Create the Domain
 On the home page of the System Manager Web Console, locate the Elements
menu.
 Click Routing > Domain.
 Click New.
 Enter the following values on the Domain Management screen:
– Name: avaya.com
– Type: sip
 Click Commit.

Create the Location
 Stay on the Routing menu and click Locations.
 Click New.
 Enter the following information on the Location Details screen:
– Name: Denver
 Scroll down the page to the Location Pattern section and click Add.
 In the IP Address Pattern field, enter the IP address of your network location.
 Click Commit.

Configure Session Manager as a SIP Entity
 Stay on the Routing menu and click SIP Entities.
 Click New.
 The SIP Entity Details page opens.

Configure Session Manager as a SIP Entity – Details Page
 On the SIP Entity Details page, enter the following information:
– Name: the name of your Session Manager
– FQDN or IP Address: IP address of your SM100
– Type: Select Session Manager from the drop-down list
– Location: Denver
– Time Zone: American/Denver
– SIP Link Monitoring: Use Session Manager Configuration
Use IP Address of SM-100
Only Session Managers “managed” by

this System Manager should be
specified as type “Session Manager”. Choose the Type. This cannot
be changed once saved.
Different fields will appear when
adding a SIP entity other than Session
Manager. They will be covered later
when adding CM.

Configure Session Manager as a SIP Entity – Listen Ports
 Listen Ports define the ports,
transport protocols, and default PORT – You must add one or more
domains on which this Session listening ports for the Session Manager
SIP Entity.
Manager listens for SIP traffic. A port can be added for TCP, TLS, or UDP.
 Scroll down to the Listen Ports You must specify a Default Domain for
section. each listening port.
 Click Add twice to open two Listen

Ports fields and enter the following
information:
– First Port:
• Port: 5060
• Protocol: TCP
• Default Domain: avaya.com
– Second Port:
• Port: 5061
• Protocol: TLS
• Default Domain: avaya.com
 Click Commit.

Confirm the SIP Entity for Session Manager
 Confirm that the Session Manager you added appears in the list of SIP Entities.

Create the Session Manager Instance
 Return to the Elements menu and click Session Manager > Session Manager
Administration.
 In the Global Settings section, leave the default settings.

Create the Session Manager Instance – New Instance
 Stay on the Session Manager Administration page and scroll down to the
Session Manager Instances section.
 Click New.
 In the General section, enter the following values in the fields below.
– SIP Entity Name: the name of the SIP Entity for your pod
– Management Access Point Host Name/IP: enter the IP address for the Session
Manager assigned to your pod
– Direct Routing to Endpoints: Enable (default selection)

Create the Session Manager Instance – Security Module
 In the Security Module section, enter the following values in the fields below:
– SIP Entity IP Address: IP address of the SM100 for your pod (pre-populates)
– Network Mask: 255.255.255.128 (Subnet mask for your lab)
– Default Gateway: 135.60.135.254 (default gateway assigned to your lab
– Call Control PHB: 46
– SIP Firewall Configuration: use SM 7.0 when available
 Leave the values in the remaining fields as default entries and click Commit.

Accept New Service – Session Manager Dashboard
 Under the Session Manager menu, click Dashboard.
 Click Refresh several times until values appear in the following fields:
– License mode
– Software version
– Security Module
– Data Replication
– Service State – leave the default Deny New Service for now.

Select Accept New Service
 In the Service State pull-down list, select Accept New Service.
 Click Confirm in the Confirm Accept New Service for Session Manager dialog
box.
 The Service State should show green text that reads Accept New Service:

Validate the Session Manager Status
 Confirm that the fields on the Session Manager Dashboard show the successful
values.
 At this point, Session Manager is connected to System Manager and all the values
are up.
 You can continue to configure Session Manager.

Session Manager License File Installation – 1
Installing the license file is a two-step process:
 Step 1: Create the license file from Product Licensing and Delivery System
(PLDS) https://plds.avaya.com
 Step 2: Install the license file from the System Manager WebLM
– Licensing for Avaya Aura® applications is provided through the System Manager
WebLM.
– Under the Services menu, click Licenses.
– The WebLM page is launched.

 Verify the Primary Host ID. This ID must match the Primary Host ID in the license.
 On the WebLM menu, click Server Properties.
 The Server Host ID page opens.
 Note the Primary Host ID.

 Next, on the WebLM menu, click Install License.
 The Install License page opens.
 Enter license path: click Choose File to select the location of the license file that
you are uploading.

 Select the license file that you are uploading.
 The license file that you are uploading displays in the field.
 Click Accept the License Terms & Conditions
 Click Install.

 After the license file is uploaded, you will see the following message:
– License file installed successfully

 The next step is to compare the Primary Host ID number that you checked earlier
with the Primary Host ID number included in the license.
 Click Licensed Products. Click the Product and verify the License File Host IDs.
 You can also check the licensed feature capacities for the product.

Enhanced Access Security Gateway Overview
 What is Enhanced Access Security Gateway (EASG)?
– EASG is a challenge-response authentication and authorization
solution
– Avaya Service personnel use EASG to securely access
customer systems for troubleshooting purposes
– EASG was introduced in Avaya Aura® Release 7.1
 Previous versions of Session Manager (7.0 and earlier)
used Access Security Gateway (ASG) instead
– ASG required an authentication file to be generated and
installed in Session Manager
– With EASG, an authentication file is no longer required
 EASG should be enabled if Avaya Service personnel need
to access the system. By default, EASG is disabled.

Enabling Enhanced Access Security Gateway
 At the Session Manager command-line prompt, log in with the cust credentials
 To enable EASG, type EASGManage --enableEASG
 The system displays the message Do you want to continue [yes/no] ?. Type yes
and press Enter

Apply Service Packs – 1
 As part of the Session Manager installation process, you may need to apply a
Service Pack to bring your system up to the latest software level.
 When to install Service Packs:
– During the implementation process
– As part of ongoing system administration and maintenance
 How to locate a Service Pack:
– Service Packs can be found on the https://support.avaya.com website.
– Check the Downloads for the product and current release.
– Service Packs for earlier releases can be found on the Product Licensing and Delivery
website (PLDS).
 Example of Service Packs available for Avaya Aura Session Manager 6.3.x:

 Click the link to the Service Pack –
– To read more information about what it contains
– To download it

 When you click the link to the Service Pack, you will be
directed to the Product Licensing and Delivery (PLDS)
website to download it:
– Download the Service Pack file from PLDS
(https://plds.avaya.com).
– Service Packs for earlier releases can be found on the
Product Licensing and Delivery website (PLDS).
 Additionally, download the Release Notes for the

Service Pack from the Avaya Support website for
further information on the Service Packs.

 Once you have downloaded the Service Pack that you need, you want to copy the
file from your computer to the /home directory of the Session Manager that you
are updating.
 Important Note: Applying a Service Pack or Update to a live Session Manager is
a potentially service-affecting operation.
– Refer to the Release Notes or the documentation for specific information about the
procedure for applying the Service Pack.
Procedure to Install the Service Pack:
 Log in to FileZilla or an FTP program of your choice.
 Copy the file from your computer to the /home directory of Session Manager.
 Log in to Session Manager, using PuTTy.
 Use the command upgradeSM Service Pack file name
 If presented with End User License Agreement (EULA), click Agree and
continue.

Procedure to Install the Service Pack (continued):
 Enrollment Password – if you are asked to enter the Enrollment Password, use
the Enrollment Password that you entered during the OVA installation.
 You can also create an Enrollment Password if you do not have one.
 Be patient and allow time – a Service Pack might take up to an hour to install.
 Once the file has successfully loaded, use the command swversion to verify the
new software level.

Run the Maintenance Tests – 1
 You can run the on-demand maintenance tests against System Manager or
Session Manager to verify any installation errors.
 Navigate to the System Manager web console and click Elements > Session
Manager > System Tools > Maintenance Tests.
 In the field for Select System Manager or a Session Manager to test, enter the
name of the application that you want to test. In this example, we are testing
Session Manager:

 You will see a list of the tests available for the Session Manager instance.
 You can select an individual test to run.
 Optionally, you can choose Execute All Tests.

 Here is the page showing the results of the Execute All Tests command.
Note that all the test results show Success.
 You can also run a test against an individual component that might be showing an
error such as the Security Module status.

Verify Data Replication
 On the home page of the System Manager Web Console, locate the Services
menu.
 Click Replication.
 Select the appropriate Replica Group and click View Replica Nodes.
 Confirm that the selected Replica Group host name is Synchronized (green).
“Synchronized” status refers to the Session

Manager replica node matching the master node.

 Session Manager is installed as an OVA.
 After the OVA is installed, the following basic configuration
steps complete the implementation process:
– Create the SIP Domain
– Set the SIP location
– Configure the SIP Entity
– Configure the Session Manager SIP Instances
– Manually activate SIP Services by accepting New Service
 Next, you install the license file and any service packs.
 Finally, you test the data synchronization.
 This basic configuration needs to be completed before any
network administration can be performed.

Lab Exercises 4-1 & 4-2
Perfom the Lab Exercises
SM Post-Installation Check & Session
Manager Core Integration
from the following document:
7120-CORE_Lab-Exercises-4-
ASM_xxxx.docx
Debrief your instructor and come back to
this point afterwards.

Lab Object Overview – Session Manager Exercises 1 and 2
Complete the post-implementation check and perform the
Session Manager Core Integration
Exercise Goals:
 Complete the post-implementation check
 Perform the Session Manager Core Integration
After completing this exercise, you will be able to:
 Install Enhanced Validation Certificates for Session Manager
 Launch a PuTTY session to Session Manager and verify the
FQDN of System Manager
 Create a SIP Domain
 Create a SIP Location
 Create a SIP Entity for SMa and SMb.
 Create a SIP Entity Link for SMa and SMb
 Create a Session Manager Instance for Sma and SMb
 Create an Enrollment Password for Session Managers a and b
 Accept New Service for Session Managers a and b
 Synchronize and perform a Test Pass for SMa and SMb

Debrief about Lab
 What worked in the lab?
 What were the challenges?
 Do you have any questions about the lab?

Lab Object Summary
Now that you have completed this exercise, you should be able to:
 Complete the post-implementation check
 Perform the Session Manager Core Integration

Lesson 4:
Building the SIP

Network

Lesson Objective – Session Manager Lesson 4
 Identify the key components of the SIP network
 Describe the purpose of the key components the SIP network

Avaya Aura® Session Manager Network Elements
 Before you begin to administer Session Manager centralized routing, it is important
to understand the components of the Session Manager or SIP Network.
 The Avaya Aura® Session Manager network components consist of:
System Manager:
Centralized administration
Session Manager:
Centralized routing and Integration
SIP and non-SIP Endpoints:

Avaya one-X® Communicator, 9600 series Handsets
SIP Entities:
Communication Manager Feature/Evolution Servers, CS1K, Presence

Building Trusted Relationships
SIP Domain
SMGR
Trusted Session Manager

SIP Entities Instance
ASM
PBX
Gateways
PSTN Service
Providers Adjuncts

Creating the SIP Domain
 Before we can configure routing, we must first create the SIP Domain.
 Every SIP domain must be configured in order for Session Manager to route to it.
Request URI
Is this a SIP
Domain I’m sip:1011111@avaya.com
supposed to sip:1011111@avaya.com
sip:1011111@avaya.com
process?
<sip:1011111@172.16.255.254:5061;transport=tls>

Network Locations
Location A Location E
IP Range: 135.* IP Range: 149.*
Location D
Location C IP Range: 136.*
IP Range: 172.*
Location F
IP Range: 10.10.*
Location B
IP Range: 148.*

Building the SIP Network – Key Takeaways
 Several key components of the SIP network must be in place
before you can administer routing for Session Manager.
 These key components are:
– SIP Domain
– SIP Location
– SIP Entity
– Session Manager as an Instance
 If any of these components are missing, then you will
experience errors in your network.

Lesson 5:
SIP Registration
and Registry Routing

After you complete this lesson, you will be able to:
 Describe the relationship between SIP Registration and
Registry Routing

Centralized Routing
Centralized Routing through Session Manager consists of:
SIP Registry Routing Network Routing Policies

 Routing to SIP endpoints that have a SIP  SIP and non-SIP routing
user communication profile  Routing between SIP endpoints
 The SIP User communication profiles are registered to separate Session
registered to the same Session Manager Manager networks
network
Session
Session Manager
Manager
CM
SIP Communication SIP Communication SIP Communication

Profile Profile Profile
H.323

SIP Endpoint Registration and Registry Routing
 Ideally, all SIP traffic in an enterprise is routed to Session Manager.
 Session Manager must authenticate all SIP endpoints before it will route its SIP
session.
 All SIP endpoints require a SIP Communication Profile, which contains the SIP
URI (1234@avaya.com) and password.
 Once the SIP Endpoint is authenticated, Session Manager stores its location info
(IP address, SIP URI) for future use.
 If the called party is a SIP endpoint, Session Manager will authenticate that user
and set up the call.
 The two SIP endpoints negotiate the preferred media type (audio or video) and
protocol (G729 or H.264) used between each other.
 Finally, the Real-Time Transport Protocol (RTP) packets are exchanged.

SIP Registration
 Session Manager (SM) checks for
a SIP User Profile.
 If a profile exists, SM (the registrar)
checks the registry for registration
details (extension/IP address).
 If the profile is registered, then the
call is processed.
Two bits of info included in a SIP Register request to ASM:

REGISTRATION 1. SIP URI = ext@avaya.com or +17869886544@avaya.com
2. Location = IP Address
SIP Registry Routing
SIP Registry Routing: SIP to SIP Call Flow
Session
Manager
Origination (user #1) Termination (user #2)
User #1 Direct Media User #2

Half Call Model

Create New User for SIP Registration
 The first step in SIP Registration and Registry Routing is to create a
Communication Profile for a new SIP user.
Username: 1011911
Password: *****
SIP User ???

REGISTER
REGISTRAR

User Profile
Administrators are responsible for creating SIP User Profiles in System Manager.
https Administrator
dsheppard
User Name: dsheppard
1011911 Handle (ext): 1011911
Password: ****
User Profile
Create a SIP Communication Profile
 Creating a SIP Communication Profile makes the endpoint assigned to a user
routable – it can register, authenticate, and be routed by Session Manager.
 Follow these steps to create the SIP Communication Profile:
– On the System Manager Common Console, or home page, locate the Users menu.
– Click User Management > Manage Users.
– Click New.
 The Identity tab is launched.

SIP Communication Profile – Identity Tab
 On the Identity tab, enter values in the mandatory fields that are indicated by a red
asterisk (*).
 These values are examples of the information that you should enter:
– Last Name: Parker
– First Name: Charles
– Login Name: cparker@avaya.com

SIP Communication Profile – Communication Profile Tab
 Select the Communication Profile tab.
 Enter the Communication Profile Password: 123456
 Confirm the Communication Profile Password: 123456
– Note: Remember that the Communication Profile password is the password for the
station authentication.

SIP Communication Profile – Communication Address
 Scroll down to the Communication Address section.
 Click New.
 Enter the following information in the fields shown on the screen:
– Type: Avaya SIP
– Fully Qualified Address: 10x1911 (extension you are assigning the user. X = your pod
number)
– Domain: avaya.com (select from pull-down list)
 Click Add.

SIP Communication Profile – Session Manager Profile
 Scroll down to the Session Manager Profile section.
 Click the arrow to expand the window.
 Use the pull-down menus to select the following information:
– Primary Session Manager: Use the Session Manager of your pod. In this example, it is
uk-c3-sm1a
– Secondary Session Manager: None
– Home Location: Denver
– Click Commit.

Register the SIP User
 In the previous step, you created the SIP Communication Profile for the user.
 The next step is to register the user.
 However, before you can register the new user, you must configure the phone to
register to Session Manager.
 Once the phone is registered to Session Manager, it can route to its SIP sessions.
 You can also analyze the registration by using SIP Tracing tools.

Analyzing the Registration
Once the SIP phone has registered, there are a couple of ways we can trace a SIP
call:
 We can use System Manager SIP Trace Viewer tool – a graphical interface that
captures historical trace information.
 We can establish an SSH connection to Session Manager, using the traceSM tool.
 traceSM captures real-time trace information.
Username: 1011911
Password: *****
REGISTER

SIP Tracer Configuration
 Before starting or viewing a call trace, you need to configure the SIP Tracer in
order to specify the information to capture.
 Access the SIP Tracer Configuration from System Manager under the Elements
menu.
 Navigate to Session Manager > System Tools > SIP Tracer Configuration.
 Confirm that the following boxes are selected:
– Tracer Enabled – shows that the tool is ready to capture calls.
– Trace All Messages – tells the tools what to trace.

Configure SIP Trace Viewer
 Access SIP Trace Viewer from the Session Manager System Tools menu on
System Manager.
 In the filter section, select the time frame for the trace.
 Also select the Session Manager for the trace.
 Click View and you should see some packets in the Trace Viewer.

Viewing the Registration SIP Trace with Trace Viewer
 Locate the Filter box in the upper-right corner of the Trace Viewer window and
click Enable.
 In the Action box, type REGISTER.
 You will see a list of REGISTER messages sent when the SIP endpoint was
logging in.
 Click Apply.

Set up traceSM
 Now that the SIP Tracer is configured, you want to set up traceSM.
 traceSM is a tool for tracing the SIP call flow in real time.
 Use a SSH connection such as PuTTy to set up traceSM.
For the Host Name or IP

address field, use the
Session Manager eth0 IP
address.

Start the Capture
 Execute traceSM from the command line.
 Once logged in, press S to start the trace.
 On the capture screen, select what to capture – in this example, we have selected
SIP messages.
 Click OK to start the capture.
 You will see a screen indicating that the capture is in progress.
You will use traceSM when

you complete the exercises
for performing the core test.

Sample SIP Trace: Registration
 Here is trace executed, using the traceSM tool.
 In this trace, User Agent sent a REGISTER request to Session Manager
represented by the SM100 Security Module.
Session
Manager
User #1

Viewing the REGISTRATION SIP Trace with traceSM
 A second way to view the REGISTRATION SIP Trace is with traceSM.
 Previously, you launched a SIP trace and left the window open on your desktop.
 Now, you can open the window and observe the real-time call flow capture.
 This capture shows the SIP endpoint sending its REGISTER message to the
primary Session Manager. The Primary Session Manager authenticates the SIP
users.

INVITE SIP Call Flow
INVITE
INVITE
100 Trying
100 Trying
180 Ringing
180 Ringing
200 OK
200 OK
ACK
ACK
Media Stream
BYE
BYE
200 OK
200 OK

Viewing Users Registrations
 You can also view a list of SIP users registered to the primary Session Manager.
 From the System Manager home page, navigate to Elements > Session Manager
> System Status > User Registrations.
 Confirm that all SIP phones are registered.
 You can also manipulate the data shown in this list by hiding the fields or
customizing the format of the table.

SIP Registry Routing Summary
You may wonder what criteria Session Manager uses to determine whether it will use
either NRP or SIP Registry Routing.
SIP REGISTRY ROUTING

Checkpoint
What check does Session Manager make to determine the type of routing to be used?
A. It checks for a communication profile

B. It references a routing table first
C. It checks for a match on the MAC address
D. It looks at the signaling protocol the endpoint supports

Checkpoint
What check does Session Manager make to determine the type of routing to be used?
A. It checks for a communication profile

B. It references a routing table first
C. It checks for a match on the MAC address
D. It looks at the signaling protocol the endpoint supports

Lab Exercise 4-3
Perform the Lab Exercise
Build a Basic SIP Phone (without CM
Features) from the following document:
ASM_xxxxx..docx

In this lesson, you learned to:
 Describe the relationship between SIP Registration and
Registry Routing

Lesson 6:
Network Routing Policy

Design Overview

 Describe the key concepts used in a SIP Routing Design

Purpose of Session Manager Routing Policies
 Determines how Session Manager

routes the calls when SIP Registry
Routing was not successful
 Routes a SIP Invite to a SIP Entity,

using either dial pattern matching
or regular expression
Global Policies
Network Routing Policies
If called number
contains 45** then
route through SIP
Entity at
10.23.142.22

SIP Routing Design
 A lot of planning and customer
collaboration is required at this
stage.
 Network Inventory
 Phased Approach
 Ask questions during the design
process: What? Where? When?
How?
Session
Manager

Routing Design – What?
 What are the SIP domains?
 What SIP Entities exist?
 How many digits to expect?
 What are the extension ranges and DNIS digits expected by CM?
 What types of endpoints: H.323, SIP, Digital, Analog?
SIP Entities Extensions (4-digit)

Cisco UCM 11xx to 69xx
Nortel CS1000
Communication
Manager

Routing Design – When?
 What are the hours of operation?
 “Thank you for calling Bloom

Inc. Our hours of operation are
Monday through Friday, 7am
to 7pm.”
Routing can be based on specific times of day and days of the week.

Routing Design – Where?
 Where is this SIP Entity located?
 How many Locations are there?
 Can I use the network to route international calls and hop off to local trunks?
Location B Location D
IP Range: 148.* IP Range: 136.* Location E
IP Range: 149.*
Location A IP
Range: 135.*
Location C
IP Range: 172.*
Location F
IP Range: 10.10.*
Tail-end Hop-off
Routing Design – How?
 Do I need to adapt the 3rd-Party vendor's SIP request so it is understood by the
receiving network or endpoint?
 What digits do I insert/delete to normalize my dial patterns in e164 format to
Session Manager?
 Do I have to adapt the numbers CM receives from, or sends to, Session Manager?
 Are there any 3rd-Party SIP Entities that require special handling?
CS1000 DigitConversion
Adapter SM Adapter
SIP header On SM egress:Converts. from

modification E164 to 4-digit ext
On SM ingress: Converts from
CS1000 4-digt ext to E164

Creating Network Routing Policies
Lots to think about!
 These questions have to be answered and the appropriate records have to be
added to the database in order to create routing policies.
 We’ll discuss those components in detail next.
Global Policies
If called number
contains 45** then
route through SIP
Entity at
10.23.142.22

Checkpoint
Routing design requires the following:
A. Customer collaboration
B. Understanding interoperability requirements
C. Location inventory of network components
D. License keys

Checkpoint
Routing design requires the following:
A. Customer collaboration
B. Understanding interoperability requirements
C. Location inventory of network components
D. License keys

Lesson 7:
Configuring Network
Routing Policy

 Describe the function of the key components required for
building Network Routing Policies (NRP):
– SIP Domain
– Locations
– SIP Entity
– SIP Entity Links
– Routing Policies
– Time Ranges
– Dial Patterns

Network Routing Policy Configuration
 Previously, we discussed SIP Registration and
Registry Routing.
 A second method of Centralized SIP Routing is
Network Routing Policy (NRP).
 To configure NRP, from the System Manager
Home Page, navigate to Elements > Routing.
 The Routing menu displays the elements that need
to be configured for the SIP Network.
 We have already configured:
– Domains, Locations, SIP Entities, and Entity Links
 Now, we are going to configure Time Ranges,
Routing Policies, and Dial Patterns.
 When all these elements are configured, we have
the information needed to create a Network
Routing Policy.

SIP Domain and Location
Location A
IP Range: 135.* Location B Location D Location E
IP Range: 148.* IP Range: 136.* IP Range: 149.*
Location C
IP Range: 172.*
INVITE SIP:1234@ SIP/2.0 Location F

IP Range: 10.10.*

Time Ranges
 Time Ranges are used to define the hours of
operation for a company.
 Time Ranges indicate how calls should be routed,
based on when the call comes in.
 You can create a Time Range for calls routed during
the weekday and during the weekend as well.
Time Range 1
Time Range 1
Global Policies
Network Routing Policies  Monday to Time Range 2
Thursday
1. Destination SIP Entity  9.00am to  Saturday Time Ranges
4.00pm and Sunday
2. Time Ranges
 12.00am to
3. Dial Patterns 11.59pm
4. Expressions

Time Ranges
 There is a default 24/7 Time Range which can be used when a company applies
the same routing policies in or out of business hours.
 The example below shows two Time Ranges: Standard and Week-end.
 Each Time Range will be created along with the routing polices.
 Specify as many time ranges as necessary to cover all hours and days in a week
for each administered routing policy.

Routing Policies
Global Policies
Session If called number
Manager INVITE:1011711@avaya.com Dial Pattern contains 10117**
10117 then route to SIP
Entity = CM1
1. SM looks at Request URI for destination

2. Checks Dial Pattern/Regular Expressions for a match
3. Once it finds a match, it uses the associated Routing Policy
to route the call
Routing Policies (continued)
Each Routing Policy defines the Routing Destination (which is a SIP Entity) as well as
the Time of Day and its associated Ranking.
Each Routing Policy defines the "Routing Destination“.

Select a defined SIP Entity.
24/7 Time of Day is the default.

Routing Policies (continued)
1. Save the new Routing Policy and then define a new Dial Pattern or Regular
Expression.
2. The Routing Policy can be assigned from within the Dial Pattern or Regular
Expression page.
If a Dial Pattern or Expression does not already exist, it CANNOT be created in the Routing
Policy page. Dial Patterns are created in the next step.
Dial Patterns
A dial pattern specifies which routing policy is used to route a call, based on matching
the digits dialed by a user.

Dial Patterns (continued)
Extension starts with 10117..…
…and has a minimum of 7 digits

and a maximum of 7 digits….
Pattern:
 Valid digits are 0-9
 Valid characters for the leading position are,+, * and #
 x (lowercase only) is a wildcard character
 White spaces are not allowed.
 * and # are not wildcards as they can be part of the Dial Pattern
Longer matches get a higher priority over shorter matches.
For example, 1601555 has a higher priority as compared to 1601.
For matches of equal length, exact matches have a higher priority over wildcard matches.
For example, +1601555 has a higher priority than +1xxx555.
Route to this SIP

Entity……
Defined in Routing
Policy……
…and the source has an IP defined

in this Location
….and uses this Routing Policy

You can block processing of calls from some or ALL locations.

Pulling It All Together
SIP Domains Locations SIP Entity Entity Links Time Ranges Routing Policies Dial Patterns
avaya.com +44 to 00144
avaya.co.uk 001 to +1
avaya.co.sng 02920 to +442920
elsewhere.com 02920 to
001442920
Global Policies
1. Destination SIP Entity
2. Time Ranges
3. Dial Patterns
4. Expressions

Checkpoint 1
Describe the statements that best describe routing policies:
A. Are used to match dialed digits on the SIP domain

B. Require dial patterns
C. Are selected based on the dial pattern applied
D. Are used when Session Manager cannot find a configured SIP
Communication Profile matching the dialed digits

Checkpoint 1
Describe the statements that best describe routing policies:
A. Are used to match dialed digits on the SIP domain

B. Require dial patterns
C. Are selected based on the dial pattern applied
D. Are used when Session Manager cannot find a configured SIP
Communication Profile matching the dialed digits

Checkpoint 2
Select the statements that best describe dial patterns:
A. Are used to match digits dialed to an endpoint that

does not have a communication profile within that
Session Manager’s registry
B. Are always associated with at least one
corresponding routing policy
C. Can be used for alpha and numeric digits
D. Can be applied to some, or all, locations

Checkpoint 2
Select the statements that best describe dial patterns:
A. Are used to match digits dialed to an endpoint that

does not have a communication profile within that
Session Manager’s registry
B. Are always associated with at least one
corresponding routing policy
C. Can be used for alpha and numeric digits
D. Can be applied to some, or all, locations

You should now be able to:
 Describe the key routing components for building routing
policies such as:
– SIP domain
– Locations
– SIP Entity
– SIP Entity Links
– Routing Policies
– Time Ranges
– Dial Patterns

Lab Exercise 4-4, 4-5
Perform the Lab Exercise
Configuring Network Routing Policies
ASM_xxxxx..docx

Lab Object Overview – SM Exercise 4-4 & 4-5
Routing Policies and Dial Patterns
Exercise Goal:
 Create a network routing policy for calls, building the SIP
Trunk from Session Manager to Communication Manager
 Create a Time Range for Standard Business Hours
 Create a Time Range for Weekend Hours
 Create a Routing Policy to Communication Manager
 Create a Dial Pattern to Communication Manager

Debrief about Lab

Lab Object Summary
 Create a network routing policy for calls

Lesson 8:
Configuring
Communication
Manager as a
Managed Element

 Describe the process for configuring Communication Manager
as a Managed Element.

Defining Communication Manager as a Managed Element
Note:
Before CM can be added as a Managed
Element, CM must be configured as a
SIP Entity.
From the System Manager (SMGR) dashboard

select: Inventory

Defining Communication Manager as a Managed Element
To create CM as a Managed Element:
 Click Manage Elements.
 Select New.

Communication System Manager
 Select the Communication Manager Type from the drop-down list.

Communication System Manager (continued)
 Specify the name and IP address of Communication Manager.
 Also, define the login and password SMGR uses to access CM.
Click Enable Notifications to be

sure that changes made in
Communication Manager
synchronize immediately with
Session Manager.

SNMP Settings
 Once you configure the General Attributes, the SNMP Attributes tab opens.
 SNMP enables CM for polling and monitoring and enables SMGR to receive any
alerts from CM.
 System Manager and CM support both SNMP v1 and SNMP v3.

CM Data Synchronization
As soon as the element is saved, the initial sync is performed.
After the initial copy, a synchronization is performed every few minutes.
To view status, navigate to

Synchronization > Communication System.

Making Changes to Data
 Changes made in CM are reflected in System Manager almost immediately!

Manual CM Data Synchronization
 You can force an immediate sync.
 On the Inventory menu, click Synchronization > Communication System.
 Select your CM, then select the Incremental sync option, and then click Now.

Communication Manager Menu
Here is the System Manager menu that you use to administer the data that has been
brought over from Communication Manager during the sync process.

View Communication Manager Data
 Select Endpoints to view the stations configured in CM.

View Communication Manager Endpoints
 Select the system and click Show List.
 This displays the stations defined in that CM.
 Shortly, we will create SIP User Communication Profiles and associate them to
these CM stations.

Checkpoint
What administrative tool can be used to manage Communication Manager once it has
been added as a Managed Element?
A. PuTTY
B. System Platform
C. Linux
D. System Manager

Checkpoint
What administrative tool can be used to manage Communication Manager once it has
been added as a Managed Element?
A. PuTTY
B. System Platform
C. Linux
D. System Manager

 Communication Manager can be added as a Managed
Element in System Manager
 Once Communication Manager is added as a Managed
Element, System Manager can be used as the administrative
management tool for Communication Manager.

Lesson 9:
Configuring
Communication
Manager
Application and
Application Sequence

After you complete this lesson, you should be able to:
 Describe the benefits of Application Sequencing
 Define Communication Manager as an application and as an
Application Sequence

Benefit of Application Sequencing
 With Application Sequencing, Session Manager can watch over registered SIP
Users and all of their calls.
 Avaya recommends using a separate CM SIP Entity + Entity Link called OPTIM
trunk (Off-PBX Telephony Integration Mapping).
 Application Sequencing assigns special rules, or features, to individual users.
 Examples of these features are blocked calls and call forwarding.
 The System Administrator builds these Application Sequences.

CM Feature Server as a Sequenced Application
 Communication Manager has thousands of “features.” Since Communication

Manager has knowledge of the user, Session Manager does not have to address
each feature.
– Session Manager sends the request to Communication Manager.
– Communication Manager applies the appropriate features based on the user and whether
they are the caller or the callee.

How Communication Manager Features are Applied
 Session Manager retrieves a caller’s User Profile – the Origination Application
Sequence.
 The Origination Application Sequence is an ordered list of applications to be
applied to outbound calls made by the caller.
Originating
Application
Sequence
Callee
Data Repository
Database
Caller Callee
Who is the caller?

Do I know him?
IMS: Half-Call Model

Half-Call Model
 Session Manager retrieves a caller’s  Session Manager retrieves a callee’s
User Profile User Profile
 Retrieves a caller's Originating  Retrieves callee's Terminating
Application Sequence Application Sequence
– An ordered list of applications to be – An ordered list of applications to be
applied to outbound calls made by applied to inbound calls made by
the caller the callee
Terminating
Originating
Application
Application
Sequence
Sequence
Data Repository
Database
Caller Callee
Who is the callee?
Do I know him?
Originating Terminating
IMS: Half-Call Model

OPTIM Trunks
 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 prevent 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

OPTIM Schematic
Port Based
Domain Based

Order of Implementation
Before CM can be added to a Sequenced Application, the following administrative
steps must be completed and in this order:
1. Define CM as a OPTIM SIP Entity
2. Create an OPTIM Entity Link
3. Define CM as a Managed Element
4. Define CM as an Application Server
 Only then can the CM Application Server be added to Application Sequence.

Defining Applications
 Use the Session Manager menu under the Elements column for Application
Configuration.
 Click Session Manager to launch the Session Manager Administration menu.
 Then, click Application Configuration.

Defining Applications (continued)
 We define Communication Manager as an application so that it can provide
features to the telephone.
 There can be up to ten applications that provide features.
 After CM is defined as an application, it can be bundled into a sequence of
applications.
 From the Applications Menu, select New.

Define the Application for CM
1. Define the name of
the CM Application.
2. Select the OPTIM
CM SIP Entity.
3. Select the CM OPTIM CM
SIP Entity
System for SIP
Entity. Managed
Element
4. Commit. (CM)
When creating an Application for CM, DO NOT enter an

application handle. Leave it blank.
Note:
CM must first be configured as an OPTIM SIP entity with
entity links.

Define the Application Sequence for CM
 Select the + next to your CM Application to add to Sequence.
Sequence 1

Checkpoint
What is the benefit of a Sequenced Application?
A. Application Sequencing assigns special rules, or

features, to individual users
B. Enables administrator to apply services and features
C. Allows Session Manager to watch over registered
SIP users and all of their calls
D. None of the above.

Checkpoint
What is the benefit of a Sequenced Application?
A. Application Sequencing assigns special rules, or

features, to individual users
B. Enables administrator to apply services and features
C. Allows Session Manager to watch over registered
SIP users and all of their calls
D. None of the above.

Lab Exercises 4-6
Perform the Lab Exercises
Building OPTIM SIP Trunk from SM to
CM (for App. Sequencing)
ASM_xxxx

 Communication Manager can be defined as an Application.
 We define Communication Manager as a application so that it
can provide features to the telephone.

Lesson 10:
Session Manager
Maintenance and
Troubleshooting

 Identify Session Manager Troubleshooting Tools and Daily
Operational Maintenance tasks

Maintenance and Troubleshooting
System Manager and Session Manager have a variety of tools to effectively maintain
and troubleshoot Session Manager, such as:
 Real-time Status and Monitoring Tools
 Trace Tools
 Maintenance Tools

Real-Time Status and Monitoring Tools
 Session Manager Dashboard
 Security Module Status
 SIP Entity Link Monitoring

Session Manager Dashboard
The Session Manager Dashboard displays:
 The overall status and health summary of each administered Session Manager.
Major, Minor, Warning SIP Entities down/total #
Registered SIP endpoints

Managed Session Managers SM100 Status

Session Manager Dashboard – How to Access
 How do you locate the Session Manager Dashboard?
 Navigate to the System Manager Web Console
 Navigate to Elements > Session Manager

Session Manager Dashboard (continued)
Access the Session Manager System Status and System Tools

Maintenance Mode Service State – New with Aura 7
 Flexible Pre-Staging – Deploy a large number of
SM/BSMs without impacting online services.
 Maintenance – Take a Session Manager or
Branch Session Manager out of service.
 Support 500 BSMs (FP1) – Categorized into four
primary areas:
– SM Management GUI Support
– Data Replication Service
– Session Manager Maintenance Mode
– SM Management Web Service
 Available in both Core and Branch Session Managers.
SM
Maintenance Mode
Service State

Maintenance Mode Service State (continued)
 Deny New Service – Sets SM/BSM into Deny New Service state.
 Alarming – No alarm triggered when SM/BSM is put into MMSS.
 SAL Agent – Disabled while in MMSS.
 Logs – Files are rolled over to prevent false alarm.
– Also applicable to SM/BSM upgrade.
Administration and Maintenance:
 Status – No polling status information.
 Administration – No GUI-based administration is supported while in MMSS.
– Exception: Dashboard polling for limited information and changing SM/BSM out of MMSS
 Supports DRS and User Data Storage maintenance.
 System Manager Geo-Redundancy – MMSS supports all status and
administration screens.

Maintenance Mode Service State: Administration
 Enabling/Disable Maintenance Mode Service State – Added to the General
section of the SM Instance admin pages.
 Default setting when adding a new instance is enabled (selected).
 Maintenance Mode Service State setting can also be changed on the Session
Manager Instance Edit page.

Maintenance Mode Service State – Administration
 Session Manager Dashboard – Indicates a SM/BSM is in Maintenance Mode
Service State (MMSS).
 Prevents GUI System Status and System Tools operations.
 Administrators are able to:

– Execute on-demand maintenance tests against MMSS SM/BSM
– Repair DRS
– Configure and repair User Data Storage

Dashboard Fields
Fields in blue are hyperlinks.
Field (urls) Description
Name of the administered Session Manager. Click the name to go to the Session Manager
Administration page.
Session Manager
Link takes you the Session Manager Administration page (Session Manager >Session Manager
Administration)
Type Core or BSM (Branch Session Manager)
Raised alarm counts (Major & Critical, Minor, Warning with the format X/Y/Z). Click the value to go to the
Alarms Alarms List page.
Link takes you to the Alarms page
Maintenance test result. A green check mark indicates the tests passed, a red X indicates the tests failed.
Tests Pass
Click the check mark or X to go to the Maintenance Tests page.
Status of the Security Module of the Session Manager (UP or DOWN). Click the status to go to the
Security Module Security Module Status page.
Link takes you to the SM100 Status page
Service State Shows the Service State of the Session Manager.
Number of down links and total links in the format down links/total links. Click the value to review the
Entity Monitoring
down links on the Session Manager Entity Link connection Status page.
Active Call Count Number of calls that are active on this Session Manager.
Registrations Current registration summary. Click the value to go to the Registration Summary page.
Versions Current software version that is running on the Session Manager.
Refer to the Maintenance and Troubleshooting Avaya Aura Session Manager, 03-603325, Release 6.1 Issue for field
descriptions located on the Avaya support website.
SIP Entity Monitoring
 SIP Entity Link Monitoring is a real-time
maintenance tool that provides automatic
background detection for monitored
SIP entities.
 Improves alternate routing and minimizes
call setup times due to SIP link failures.

SIP Entity Monitoring – OPTIONS Request
Originating SIP Proxy sends SIP OPTIONS
request to entities to detect whether the status is:
 UP
 PARTIALLY UP
 DOWN
Destination SIP Entity sends a SIP RESPONSE
message with its capabilities.
SIP
200 OK
OPTIONS

OPTIONS Request Example

SIP Entity Monitoring – Addresses
Entities are considered UP if all the addresses associated with the SIP Proxy server
are responsive.
Addresses for a SIP Entity may include:
 IP address UP
 FQDN
 DNS
 Hostname
SIP Entity Addresses

SIP Entity Monitoring – Entities DOWN Examples
Entities are considered DOWN if the response to the OPTIONS request is:
 408 Request Timeout
 503 Service Unavailable
 503 Service Unavailable (LSP is inactive) Down
 503 Service Unavailable – System Busy
 504 Server Timeout

SIP Entity Monitoring Status Summary
 Shows the status of the Entity links
At the Session Manager

Dashboard, navigate to
System Status > SIP
Entity Monitoring.
You can click

Run Monitor for on-demand
monitor testing.

SIP Entity Monitoring – Link Connection Status
You can also click each SIP Entity to see its current link status and its last response to
Session Manager’s OPTIONS message.

SIP Entity Monitoring Summary
Some of the key points about SIP Entity Monitoring are:
 The SIP Entity Monitoring tool is a real-time monitoring tool that provides automatic
background detection for monitored SIP Entities.
 The SIP Entity Monitoring tool is accessed from the Session Manager Dashboard.
 The SIP Entity Monitoring tool displays a SIP Entity Link Monitoring Status
Summary page.
 From the Status Summary page, you can click Run Monitor for on-demand
monitor testing.

Trace Tools
 Trace tools capture the SIP call flow in real time from SIP endpoints and SIP
Entities to Session Manager and can uncover issues in routing, database
replication, and improper SIP message format.

SIP Tracer
Use SIP Tracer for the configuration of SIP message traces:
 Incoming through the security module
 Outgoing from the security module
 Messages dropped by SM100/SIP firewall

SIP Trace Viewer
 SIP Trace Viewer provides the output of the configured traces.
 Best used for historical traces. Use traceSM for real-time traces.

traceSM
 traceSM assists in the isolation, identification, and resolution of SIP-based
problems.
 Starting on SM 6.3, traceSM is a combination of the old traceSM and traceSM100.
 The following log files are generated when running traceSM:
– SIP messages: /var/log/Avaya/trace/tracer_asset.log*
– Call Processing: /var/log/Avaya/trace/call_proc.log*
– PPM: /var/log/Avaya/trace/trace_ppm.log*
 traceSM is located in /opt/Avaya/contrib/bin

Sample SIP Trace: Registration
 Trace executed using the traceSM tool.
 In this trace, the User Agent sent a REGISTER request to Session Manager
represented by the SM100 Security Module.
Session
Manager
User #1

Replication Groups
 Replica Groups – shows status of database synchronization between System
Manager and Session Manager.
 Can also repair Replica Groups from this page.

Maintenance Tools
 Alarms are essential for proactively managing Session Manager potential issues.

Automatic Alarm Clearing
 Automatically clears alarms when possible.
 Session Manager clears alarms when:
– Alarm condition has been resolved
– Alarm condition is not seen for a certain amount of time
Example: Security Module periodic test fails. SM automatically clears the alarm when the
test passes.
 Session Manager does not clear the alarm if:
– Alarm requires Avaya Technical Services to correct the alarm
– Alarm is generated for information purposes only
– Session Manager cannot determine if the alarm condition has been resolved
Example: Firewall rule alarm indicates an IP address is blocked.
 Alarms not automatically cleared by Session Manager must be manually cleared
by the customer or Avaya Technical Services.
SM
Alarm! Cleared!

Automatic Alarm Clearing – Alarm Generation
 SM Log-based Alarming Scheme – SMGR provided Serviceability Agent
functionality, which is the method for getting alarms from Session Manager to
System Manager.
 Cleared Events – Sent as SNMP traps similar to alarm events and is sent to the
same destinations that are configured for alarming.
 Alarm Triggers – Session Manager flow to generate an alarm:
– SM generates a log message in the EVENT.log.
– Severity of the message is equivalent to:
• ERROR
• WARNING
• INFO
SM
Alarm! Cleared!

Automatic Alarm Clearing – Administration
 System Manager Home – Services – Inventory – Manage - Serviceability Agents:
– SNMPv3 User Profiles – User profiles for SNMPv3 traps/informs.
– SNMP Target Profiles – Create and modify profiles for SMGR (provided by default with
SMGR install), customer NMS, SAL gateway, test trap receivers, etc.
– Serviceability Agents – Activate Managed Elements' agents, managing target profiles
for each agent, assigning/removing SNMPv3 profiles for sending V3 traps/informs.
SM
Alarm! Cleared!

Automatic Alarm Clearing – Administration (continued)
 System Manager Alarms and Log Events: Home – Services – Events – Alarms.
– Filtering for specific information for alarm state, host, Event ID, NotificationOID, etc.
 System Manager Log Viewer: Services – Events – Logs – Log Viewer.
– Filter for specific information for host, Severity, Product Type, Event ID, etc.
SM
Alarm! Cleared!

Checkpoint
What is the function of the traceSM tool?
A. Is a tool that provides real-time trace information for a call.

B. Is a tool used to backup and restore data.
C. Is a tool that used to install OVAs in a customer network.
D. Is a tool used to view historical data for a call.

Checkpoint
What is the function of the traceSM tool?
A. Is a tool that provides real-time trace information for a call.

B. Is a tool used to backup and restore data.
C. Is a tool that used to install OVAs in a customer network.
D. Is a tool used to view historical data for a call.

Lab Exercises 5 and 6
Perform the Lab Exercises
Session Manager Alarms
& Backup and Restore
ASM_xxxx

Lab Object Overview – Session Manager Exercises 5 and 6
Exercise Goal:
 View, Acknowledge and look up the Resolution to a Session Manager Alarm
 Back up and Restore the Session Manager database in System Manager

Exercise #5– Session Manager Alarms
 View the Session Manager Dashboard
 Open the Alarm List
 Acknowledge an Alarm
 Look up the resolution of the Alarm
 Clear a Session Manager Alarm
Exercise #6– Backup and Restore
 Back up the Session Manager database in System Manager
Restore the Session Manager database in System Manager

Debrief about Lab

Lab Object Summary
 View, Acknowledge, and look up the Resolution to a Session Manager Alarm
 Back up and Restore the Session Manager database in System Manager

 Session Manager and System Manager have a variety of tools
used for maintenance and troubleshooting functions.
 Real-time status and monitoring tools include:
– Session Manager Dashboard
– Security Module Status
– SIP Entity Link Monitoring
 Trace tools include:
– SIP Tracer
– SIP Trace Viewer
– traceSM
 Maintenance tools
– Alarms and Log Events
– Log Viewer

Questions and Answers

Backup Slides
Deploying the Session Manager OVA in a Virtualized

Environment

Lesson Overview – Session Manager– Backup Slides
 Describe the process for deploying the Session Manager OVA

Deploying the Session Manager OVA – 1
 System Manager must be up and
functional before you install
Session Manager.
 Before you begin deploying the
OVA on vCenter, verify the
following:
– the vSphere client is installed
– the vCenter server is installed
– the VMware host is added to the
vCenter
 Step 1: Launch the vSphere
Client.
 Step 2: Enter the IP address and
user credentials for the ESXi
host and then click Login. Ignore
any security warnings that the
system displays.

 Step 3: From the vSphere Menu bar, select File > Deploy OVF Template.
 Step 4: Locate the Deploy from a file or URL section. Click Browse and select
the location of the OVF/OVA file. In this example, the OVA/OVF file has been
uploaded to a PC.

 Step 5: Highlight the OVA file and click Open. Click Next to continue.

 Step 6: On the OVF Template Details screen, verify that the information is correct
for the template that you selected.
 Step 7: If the template details are correct, click Next.
 Highlight the OVA file and click Open.

 Step 8: Review the End User License Agreement (EULA). Click Accept and
then click Next to continue.

 Step 9: In the Name field, enter the name that you have assigned to your virtual
machine (VM). In this example, we have identified the VM by region (UK-c3) and
application (sm5a).
 Step 10: Select a location for this virtual machine if you have not already done so.
 Step 11: Click Next to continue.

 Step 12: On the Deployment Configuration page, use the drop-down menu to
select the required Configuration Profile for your installation. The screenshot
example shows Profile 1, which is the Profile that we use in our labs.

 Step 14: On the Host/Cluster page, select the host on which your new virtual
machine will be deployed. Click Next to continue.

 Step 15: In the Storage window, select the Data Store for your new virtual
machine (VM). Be sure that you have enough free storage space for the VM. Click
Next to continue.

 Step 16: On the Disk Format page, select the required disk format. In this
example, we are using Thick Provision Lazy Zeroed. Click Next to continue.
 Note that the system shows the Datastore that you selected on the previous page,
and the available space.

 Step 17: On the Network Mapping page, select the Destination Network. If you
have multiple virtual machines (VMs) in your environment, you need to choose the
appropriate network. If you do not have multiple networks, you will not see this
prompt.
– Select a Destination Network for both Public and Out of Band Management.

 Step 19: Next, the Network Settings page is displayed. Enter the IP addresses,
host names, and other relevant information on this page.

 Step 19, continued (note that this information is different from the System
Manager Network Mapping page)
– Enter the System Time Settings and IP address for the NTP Server
– Enter the Customer Login Name and Customer Account Password
– Enter the Primary Session Manager IP address and the Enrollment Password

 Step 21: Review the information on the Ready to Complete screen. If the
information is correct, click Finish to begin building the virtual machine (VM).

 Step 22: The status bar shows the progress of the installation.
 Step 23: The Completed Successfully message is displayed when the

deployment is complete. Click Close to complete the virtual machine installation.

 Note: It is possible to further refine the virtual machines once the deployment
process is complete. For additional information on how to edit the virtual machine,
download the documentation below from the Avaya Support website
(https://support.avaya.com)
Deploying Avaya Aura® Session Manager on VMware in a Virtualized Environment
 Step 24: Turn on the power to the Virtual Machine. The new virtual machine will be
in a powered-off state after it is built. There are two ways to turn the power on:
– Click Power on the virtual machine in the main window.
– Right-click the virtual machine name and choose Power > Power On.

 Step 25: Next, open a console to allow initial administration of the new Session
Manager. Right-click the virtual machine and select Open Console.
 From here, you can watch the newly built virtual machine starting up.
 You can now begin configuring your Session Manager.

In this session, we have described the process for deploying the
Session Manager OVA in a Virtualized Environment.

Questions and Answers

7120V - Core - Module 04 - Session Manager - v4 - 1 PDF

Uploaded by

Copyright:

Available Formats

You might also like

7120V - Core - Module 04 - Session Manager - v4 - 1 PDF

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

7120V - Core - Module 04 - Session Manager - v4 - 1 PDF

Uploaded by

Copyright:

Available Formats

Module 4:

Avaya Aura® Session

© 2017 Avaya, Inc. All rights reserved. Page 1

© 2017 Avaya, Inc. All rights reserved. Page 2

© 2017 Avaya, Inc. All rights reserved. Page 3

© 2017 Avaya, Inc. All rights reserved. Page 4

© 2017 Avaya, Inc. All rights reserved. Page 5

© 2017 Avaya, Inc. All rights reserved. Page 6

© 2017 Avaya, Inc. All rights reserved. Page 7

© 2017 Avaya, Inc. All rights reserved. Page 8

© 2017 Avaya, Inc. All rights reserved. Page 9

© 2017 Avaya, Inc. All rights reserved. Page 10

© 2017 Avaya, Inc. All rights reserved. Page 11

3rd Party PBXs

© 2017 Avaya, Inc. All rights reserved. Page 12

Centralized SIP Routing Integration and Adaptation SIP Firewall

Scalable High Availability and Redundancy Registration and Authentication

© 2017 Avaya, Inc. All rights reserved. Page 13

 What’s New with Avaya Aura® Release 7.0

A. Register digital (DCP) and H.323 endpoints

© 2017 Avaya, Inc. All rights reserved. Page 15

A. Register digital (DCP) and H.323 endpoints

© 2017 Avaya, Inc. All rights reserved. Page 16

© 2017 Avaya, Inc. All rights reserved. Page 17

Evolution of the IMS

© 2017 Avaya, Inc. All rights reserved. Page 18

© 2017 Avaya, Inc. All rights reserved. Page 19

© 2017 Avaya, Inc. All rights reserved. Page 20

© 2017 Avaya, Inc. All rights reserved. Page 21

 Limited Scope  Primarily Designed for Voice

© 2017 Avaya, Inc. All rights reserved. Page 22

 Limited Scope  Primarily Designed for Voice

© 2017 Avaya, Inc. All rights reserved. Page 23

App App App

 Limited Scope  Primarily Designed for Voice

© 2017 Avaya, Inc. All rights reserved. Page 24

Avaya Avaya Aura® Avaya Aura®

© 2017 Avaya, Inc. All rights reserved. Page 25

© 2017 Avaya, Inc. All rights reserved. Page 26

© 2017 Avaya, Inc. All rights reserved. Page 27

© 2017 Avaya, Inc. All rights reserved. Page 28

© 2017 Avaya, Inc. All rights reserved. Page 29

© 2017 Avaya, Inc. All rights reserved. Page 30

No se puede mostrar la imagen.

© 2017 Avaya, Inc. All rights reserved. Page 31

© 2017 Avaya, Inc. All rights reserved. Page 32

© 2017 Avaya, Inc. All rights reserved. Page 33

Avaya Aura® System Avaya’s Centralized Administration/Management Platform – the

IP Multimedia Subsystem is a type of enterprise or SIP domain, which

IMS defines an ISC (IMS Service Control) Interface, a process

SIP sessions routed based on the location of a registered endpoint or

A user's SIP phone number, using the following format

The request a SIP endpoint sends when it wants to register to Session

A SIP message request from a SIP endpoint to a Session Manager

SIP message request sent from a SIP endpoint or entity wanting to

© 2017 Avaya, Inc. All rights reserved. Page 35

© 2017 Avaya, Inc. All rights reserved. Page 36

A. A multi-vendor, open, and flexible network architecture