Avaya Session Manager Part 1

Avaya Aura ® Session ManagerAdministrationAvaya Aura ® Session ManagerAdministration

5U00081VVersion 6.1

Before we begin

Courses strongly recommended to complete before this course:– System Manager Administration 5U00080V– SIP Essentials ATC01290WEN– Session Manager General Overview ATU00171OEN– Session Manager Technical Overview ATU00170OEN– Session Manager Installation & Initial Setup ATA02446OEN

Course Length = 24 Hours– vILT = 4 Days @ 6 hours

Breaks– Instructor’s discretion

©2011. All rights reserved.© 2007 Avaya Inc. All rights reserved.

Courses strongly recommended to complete before this course:– System Manager Administration 5U00080V– SIP Essentials ATC01290WEN– Session Manager General Overview ATU00171OEN– Session Manager Technical Overview ATU00170OEN– Session Manager Installation & Initial Setup ATA02446OEN

Course Length = 24 Hours– vILT = 4 Days @ 6 hours

Breaks– Instructor’s discretion

Agenda – Live Instructor & Virtual LedVirtual Training

Day 1 (6 Hours)– Module 1: Session Manager Instance Configuration - 3 Hours– Module 2: Session Manager Routing Policy - 3 Hours– End of Day

Day 2 (6 Hours)– Module 2: Session Manager Routing Policy - 3 Hours– Module 3: Session Manager Application Configuration - 3 Hours– End of Day

Day 3 (6 Hours)– Module 3: Session Manager Application Configuration - 3 Hours– Module 4: Session Manager User Profile Administration - 3 Hours

Day 4 (6 Hours)- Module 5: Troubleshooting System and Session Manager- 6 Hours


Day 1 (6 Hours)– Module 1: Session Manager Instance Configuration - 3 Hours– Module 2: Session Manager Routing Policy - 3 Hours– End of Day

Day 2 (6 Hours)– Module 2: Session Manager Routing Policy - 3 Hours– Module 3: Session Manager Application Configuration - 3 Hours– End of Day

Day 3 (6 Hours)– Module 3: Session Manager Application Configuration - 3 Hours– Module 4: Session Manager User Profile Administration - 3 Hours

Day 4 (6 Hours)- Module 5: Troubleshooting System and Session Manager- 6 Hours

Course Objectives – Module 1Configure a Session Manager Instance Accessing Servers Define SIP Domain Define a Location Define a SIP Entity Define Session Manager Instance in System Manager Enable Session Manager to Accept New Services Troubleshooting Discuss Core Redundancy


Configure a Session Manager Instance Accessing Servers Define SIP Domain Define a Location Define a SIP Entity Define Session Manager Instance in System Manager Enable Session Manager to Accept New Services Troubleshooting Discuss Core Redundancy

Course Objectives – Module 2

Session Manager Routing Policy Routing Policy Overview SIP Routing Policy

– SIP Domains– Review Locations– SIP Entities– Entity Links– Routing Policy– Dial Patterns– Regular Expressions– Adaptations

Make and Trace Calls Alternate Routing

– Alternate Policy– Time of Day

Local Host Name Resolution System Health Call Route Testing


Session Manager Routing Policy Routing Policy Overview SIP Routing Policy






Session Manager Application Configuration Overview of Application Sequencing

– Sequenced Vs. Named Applications Sequenced Applications with Communication Manager

– Communication Manager Overview• Communication Manager Configuration - CM Evolution Server & CM

Feature Server System Manager Application Configuration Applying Application Sequences to Users Sequenced Application with Non-CM Feature Server Implicit Users and Sequenced Applications Named Applications


Session Manager Application Configuration Overview of Application Sequencing

– Sequenced Vs. Named Applications Sequenced Applications with Communication Manager

– Communication Manager Overview• Communication Manager Configuration - CM Evolution Server & CM

Feature Server System Manager Application Configuration Applying Application Sequences to Users Sequenced Application with Non-CM Feature Server Implicit Users and Sequenced Applications Named Applications

Course Objectives – Module 4Session Manager User Profile Administration – Communication Profile Overview of Registration and Location Define System Manager SIP User

– Define Communication Profile• Communication Address• Session Manager Profile

Register SIP users View User Registrations Calling Registered Users Multiple User Identities

– Multiple Communication Addresses– Multiple Communication Profiles

Personal Profile Management – Communication Manager– Overview– Manage Communication Manager Endpoints

• Create System Manager SIP User Endpoint Profile– Adding a Communication Manager– Troubleshooting


Session Manager User Profile Administration – Communication Profile Overview of Registration and Location Define System Manager SIP User

– Define Communication Profile• Communication Address• Session Manager Profile

Register SIP users View User Registrations Calling Registered Users Multiple User Identities

– Multiple Communication Addresses– Multiple Communication Profiles

Personal Profile Management – Communication Manager– Overview– Manage Communication Manager Endpoints

• Create System Manager SIP User Endpoint Profile– Adding a Communication Manager– Troubleshooting


By the end of the course you should..UnderstandSession Manager and System Manager Architectural Components

and TopologyUnderstand common Session and System Manager issues

Be able to:Access troubleshooting tools

Access and interpret key log files

Apply troubleshooting techniques to identify and implement solutions


By the end of the course you should..UnderstandSession Manager and System Manager Architectural Components

and TopologyUnderstand common Session and System Manager issues

Be able to:Access troubleshooting tools

Access and interpret key log files

Apply troubleshooting techniques to identify and implement solutions

Toolwire Student InformationToolwire Student Information

135.122.80.71 135.122.80.55 eth0:135.122.80.58Security Module:135.122.81.58


135.122.80.142

Student01

Student02

Training lab


eth0:135.122.80.88Security Module:135.122.81.88



135.122.80.62Student03

Student04

Avaya Aura ® Session ManagerInstance ConfigurationAvaya Aura ® Session ManagerInstance Configuration

Objectives – Module 1Configure a Session Manager Instance Accessing Servers Define SIP Domain Define a Location Define a SIP Entity Define Session Manager Instance in System Manager Enable Session Manager to Accept New Services Troubleshooting Discuss Core Redundancy


Configure a Session Manager Instance Accessing Servers Define SIP Domain Define a Location Define a SIP Entity Define Session Manager Instance in System Manager Enable Session Manager to Accept New Services Troubleshooting Discuss Core Redundancy

Access System Manager

Avaya Aura ®Session Manager

Access System Manager

System Manager Administration

Access via browser

To access the System Manager administration page,navigate to https://<HOSTIP>/

The username and password are admin/Tr@1ning


Access via browser

To access the System Manager administration page,navigate to https://<HOSTIP>/


mailto:Tr@1ning

Exercise 1: Access servers

• System Manager Console (browser)– https://<ipaddress>– admin/Tr@1ning

15© 2007 Avaya Inc. All rights reserved.

• System Manager Console (browser)– https://<ipaddress>– admin/Tr@1ning

mailto:Tr@1ning

mailto:Tr@1ning15

SIP Domains

mailto:Tr@1ning

SIP Domains


Is this a SIPDomain I’msuppose toprocess?

SIP Domains


SIP Domains

Routing >> Domains


Only Domains of type SIP can be used for routing

Exercise 2: Define a Domain• Navigate in System Manager to Routing >> Domains• Define training.com as a domain

20© 2007 Avaya Inc. All rights reserved. 20© 2007 Avaya Inc. All rights reserved.

Locations

Enterprise a

Network Locations

IP Range: 135.*

IP Range: 148.* IP Range: 136.*

IP Range: 176.*

IP Range: 149.*


Enterprise b

IP Range: 172.*

IP Range: 133.*

IP Range: 10.10.*

Locations


Locations

Routing >> Locations


The Location associates an IP address pattern with a name to be used in the RoutingPolicy to determine the originating location of a call.

Locations


Examples of IP Address Patterns:135.*

135.12x.121.123135.12x.121.*

10.0.0.1-10.0.0.5135.9.0.0/16

Exercise: Create a Location

• Create a new Location called ‘classroom’• Add a pattern of 135.*


SIP Entities

SIP Entities

10.29.32.15

13.132.2.12


110.23.14.22

17.156.24.276

asm2135.122.80.2255060 TCP/UDP

5061 TLS

SIP Entities


SIP Entities

Routing >> SIP Entities


Sip Entity – Session Manager

IP

SIP Entities – General Settings


Use IP Address of SM-100Select Type: Session Manager

Only Session Managers “managed” by thisSystem Manager should be specified as type“Session Manager”

SIP Entities

SIP Entities – Ports


PORT – You must add a listening port forthe Session Manager SIP Entity.

Add a port for TCP, TLS and UDP.

You must specify a Default Domain.

Defines the port(s) and protocol that this Session Manager listens for SIP traffic.

Exercise 4: Session Manager SIP Entity

• Define your Session Manager as a SIP Entity– Use the IP Address of your software Security Module (eth2)– Type is “Session Manager”– Location is ‘classroom’– Select Timezone Denver– Ports

• 5061 TLS training.com• 5060 TCP training.com• 5060 UDP training.com


• Define your Session Manager as a SIP Entity– Use the IP Address of your software Security Module (eth2)– Type is “Session Manager”– Location is ‘classroom’– Select Timezone Denver– Ports

• 5061 TLS training.com• 5060 TCP training.com• 5060 UDP training.com


Session Manager Instance



Master DB Replica DBJim

Only after a Session manager Instance is defined can we:

• Monitor health and status of the Session Manager

• Administer Routing Policies, User’s Communication Profiles and Application Sequencing




Global Settings



Session Manager >> Session Manager Administration


Define Session Manager Instance - Continued

Defaults based on IP Addressdefined in SIP Entity.

IP Address of Session Manager’seth0IP


Defaults based on IP Addressdefined in SIP Entity.




How often the entity is monitored when the link to the entity is up or active

How often the entity is monitored when a link to the entity is down orinactive

The number of times Session Manager tries to reach the SIP entity beforemarking it as down or unavailable

To enable or disable monitoring of the SIP entities by this Session Manage instance


How often the entity is monitored when the link to the entity is up or active

How often the entity is monitored when a link to the entity is down orinactive

The number of times Session Manager tries to reach the SIP entity beforemarking it as down or unavailable

This controls whether CDR is enabled at the system level for that SessionManager instance.

If CDR is enabled, you can individually control call detail recording for specificSIP entities using the Call Detail Recording drop-down menu.

Define Session Manager - Continued

Connection settings specify the global parameters that apply to all SM instances


Exercise 5: Define a Session Manager• Navigate in System Manager Session Manager >>

Session Manager Administration• Deselect Ignore SDP for Call Admission Control• Define the Session Manager Instance• Be Prepared to enter:

– Select the SIP Entity you previously defined in the SIPEntity Name dropdown list

– The management address for Session Manager (eth0:135.122.80.xx)

– The Security Module Netmask = 255.255.254.0– The Security Module Gateway = 135.122.80.1– Let all other fields default


• Navigate in System Manager Session Manager >>Session Manager Administration

• Deselect Ignore SDP for Call Admission Control• Define the Session Manager Instance• Be Prepared to enter:

– Select the SIP Entity you previously defined in the SIPEntity Name dropdown list

– The management address for Session Manager (eth0:135.122.80.xx)

– The Security Module Netmask = 255.255.254.0– The Security Module Gateway = 135.122.80.1– Let all other fields default


Post Configuration ChecksPost Configuration Checks

Post Configuration


Enable New Service

The default state of the Session Manager is Deny New Service. This mustbe enabled to start the SM-100 and take calls.


Monitor Session Manager Status


Maintenance Tests


Data Replication Status






Exercise 6: Post Configuration Checks

• Enable the Session Manager to Accept New Services• Verify Status of Session Manager• Verify Database Replication = Synchronized


SIP Firewall ConfigurationSIP Firewall Configuration

SIP Firewall Configuration


TraceViewer – Blocked Call


SIP Firewall Configuration - Rules


Multiple Session Manager InstancesMultiple Session Manager InstancesCore Redundancy

Scaling Session Manager


Enterprise


All SIP Entities defined as type ‘Session Manager’ may be defined as a Session Manager Instance.

The System Manager replicates the same data to all Session Manager Instances which makesthem exact replicas each other able to support a redundant configuration.


Master DB Replica DBJim

Only after a Session manager Instance is defined can we:

• Monitor health and status of the Session Manager

• Administer Routing Policies, User’s Communication Profiles and Application Sequencing

Adding more Session Manager Instances

1. Create a SIP Entity for your Session Manager as type‘Session Manager’

2. Create a Session Manager Instance for your SessionManager.

Same as before!


1. Create a SIP Entity for your Session Manager as type‘Session Manager’

2. Create a Session Manager Instance for your SessionManager.

Same as before!

Adding more Session Manager Instances

Create Entity Links between:– Primary and Secondary Session Manager– Any other SIP Entity, like CM, that is required if the Primary

Session Manager fails


CM and Redundant Session Manager

The secondary Session Manager must be configured inCommunication Manager. Once the Trunk Group is created, it can beadded to the Primary Session Manager’s Route Pattern.

Primary Session Manager

Secondary Session Manager


Primary Session Manager

Secondary Session Manager

Assign Session Managers to Users


DEMO:Failover from Primary to Secondary Session ManagerTopics in this video are covered in:

Session Manager User Profile ManagementRouting Policy


TroubleshootingTroubleshooting

Accessing the Servers


Exercise 7: Access servers

• Access Servers using putty application- Run putty.exe- Connect using ASM’s Eth 0 Ip Address

• Log into Session Manager Server with thefollowing login details:

Login: craft Password: craft01

• At command line switch your user to srootby typing the following:

• su - sroot• password: sroot01


• Access Servers using putty application- Run putty.exe- Connect using ASM’s Eth 0 Ip Address

• Log into Session Manager Server with thefollowing login details:

Login: craft Password: craft01

• At command line switch your user to srootby typing the following:

• su - sroot• password: sroot01

SMConsole

A command-line tool installed on Session Manager developed fordebugging purposes. It can be used to access runtime Call Processingor PPM data.

runsmconsole – starts the SMConsole application


SMConsole

Running help at the promptdisplays all the availablecommands

The GET command retrievesstored data and can verify thatthe replication client (SM) is insync with System Manager.

REINIT and RM impact run-time data and are destructive –don’t use!

exit – leave smconsolesession.


Running help at the promptdisplays all the availablecommands

The GET command retrievesstored data and can verify thatthe replication client (SM) is insync with System Manager.

REINIT and RM impact run-time data and are destructive –don’t use!

exit – leave smconsolesession.

Exercise 8: runsmconsole

• Execute the following GET commands:– GET AllAsmInstances– GET AllLocations– GET AllSIPDomains– GET AllSIPEntities– GET SIPEntity (Long entityId)– GET SystemManagerIP– Help (view list)– exit


• Execute the following GET commands:– GET AllAsmInstances– GET AllLocations– GET AllSIPDomains– GET AllSIPEntities– GET SIPEntity (Long entityId)– GET SystemManagerIP– Help (view list)– exit

You have completed the followingObjectives - Module 1

Configure a Session Manager InstanceAccessing ServersDefine SIP DomainDefine a LocationDefine a SIP EntityDefine Session Manager Instance in System ManagerEnable Session Manager to Accept New ServicesTroubleshootingDiscuss Core Redundancy


Configure a Session Manager InstanceAccessing ServersDefine SIP DomainDefine a LocationDefine a SIP EntityDefine Session Manager Instance in System ManagerEnable Session Manager to Accept New ServicesTroubleshootingDiscuss Core Redundancy

Avaya Aura ® Session ManagerRouting PolicyAvaya Aura ® Session ManagerRouting Policy

Objectives - Module 2 Routing Policy Overview SIP Routing Policy






Routing Policy Overview SIP Routing Policy





Routing PolicyRouting Policy

Determines how SIP calls are routed


SIP Routing

Who– Request SIP domain?– Source and destination…

…Is this a SIP Entity I trust?

Where– Where is this SIP Entity located?

• In my network or outside of my network?

– Does it have any rules for routing?

Special Headers– Do I need to modify the SIP request so it is understood by

the receiving network or endpoint?

SessionManager


Who– Request SIP domain?– Source and destination…

…Is this a SIP Entity I trust?

Where– Where is this SIP Entity located?

• In my network or outside of my network?

– Does it have any rules for routing?

Special Headers– Do I need to modify the SIP request so it is understood by

the receiving network or endpoint?

Creating Network Routing Policies

Lots to think about!

Collections– records in database

compiling from collections tocreate something more


Actions• Set budget• Employ workers• Organise

premises• Order tools• Order materials• Organise

insurance• First aid

Tasks• Build and

assemble shed• Buy paint and

paint the house• Cut grass• Sweep patio• Plant seeds• Prune trees


1. Destination SIP Entity

2. Time Ranges

3. Dial Patterns

4. Expressions

Time Range 1


Time RangesTime Range 1• Monday to

Thursday• 9.00am to

4.00pm

Time Range 2• Saturday and

Sunday• 12.00am to

11.59pm


2. Time Ranges

3. Dial Patterns

4. Expressions

Time Range 1

PSTN Gateway


SIP EntitiesCommunicationManager

• 10.24.35.112PSTN Gateway

• 22.117.32.12

Locations

Location 1

• DenverLocation 2

• Cardiff


SIP Entities

Adaptations

CommunicationManager

• 10.24.35.112

Adaptation 1

• +44 to0144

Adaptation 2

• 02920to+442920

•Adaptation•+44 to0144

•Location•Denver

Locations Adaptations SIP Entity Entity Links Time Ranges SIP Domains

avaya.comavaya.co.uk

avaya.co.sngelsewhere.com

Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

Defining the SIP Routing PolicyDefining the SIP Routing Policy

Session Manager & Communication Manager

SM SIP Entity


H.323

SM SIP Entity H.323

Routing Scenario 1:CM H.323 Phone Call Routing through Session Manager

135.122.80.142TLS 5061training.com


SIP SIP

H.323


Extensions User/Password User/PasswordStudent01 => 81001/123456 ……………dials…....…….. 92001/123456Student02 => 81002/123456 ……………dials…....…….. 92002/123456Student03 => 81003/123456 ……………dials…....…….. 92003/123456Student04 => 81004/123456 ……………dials…....…….. 92004/123456



H.323H.323

Exercise 1: Log into IP Phone

• Log into both H.323 phones and place a call– Login information on next slide

• Does the call complete?


• Log into both H.323 phones and place a call– Login information on next slide

• Does the call complete?



135.122.80.142 135.122.80.62

Access the 1st H.323 PhoneCall Server = 135.122.80.142Station 81001 => Student01Station 81002 => Student02Station 81003 => Student03Station 81004 => Student04

Password: 123456


Full detail on accessing the IP Phones is documented in the Toolwire Setup Filehttps://dcm.toolwire.com

Pod 1 IP PhoneStudent 1 ip010170/welcomeStudent 2 ip010171/welcomeStudent 3 ip010172/welcomeStudent 4 ip010173/welcome



Access the 2nd H.323 PhoneCall Server = 135.122.80.62Station 92001 => Student01Station 92002 => Student02Station 92003 => Student03Station 92004 => Student04

Password: 123456


Full detail on accessing the IP Phones is documented in the Toolwire Setup Filehttps://dcm.toolwire.com




Let’s look at our first scenario

SessionManager

Who?How do I Route extension 92001?

Where? INVITE

192.168.0.210:3002


SIP Entity:MySessionManager

CM station: 81001 CM Station 92001

INVITE

192.168.0.210:3002

200 OK

192.168.0.210:3002

135.122.80.142 135.122.80.62

Scenario 1

Sip Entity: SM172.25.1.60:5060

Entity Link1

Entity Link2

SIP Domain: training.com

SessionManager

©2011. All rights reserved.

H323 station - 8100X

SIP Domain: training.com


H323 station - 9200X


Session Manager Configuration –Common Console

To access the System Manager administration page,navigate to http://<HOSTIP>/



SIP DomainsReviewSIP DomainsReview

mailto:Tr@1ning

Locations Adaptations SIP Entities Entity Links Time Ranges SIP Domains



Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

SIP Domains


SIP Domains


Is this a SIPDomain I’msuppose toprocess?

SIP Domains – No Authoritative Domain


No Authoritative Domainfor jojo.com

Sending it to DNS to resolve jojo.com

SIP Domains

Routing >> Domains


Only Domains of type SIP can be used for routing

Exercise 2: Add abc.com Domain1. Navigate in System Manager to Routing >> Domains

- Define abc.com as a domain


1. Navigate in System Manager to Routing >> Domains- Define abc.com as a domain


Exercise 2 cont: Add 5062 Port to ASM

2. Select SIP Entities Menu:

Edit your Session Manager SIP Entity andadd:– Port 5062– Protocol: TLS– Domain: abc.com


2. Select SIP Entities Menu:

Edit your Session Manager SIP Entity andadd:– Port 5062– Protocol: TLS– Domain: abc.com

LocationsReviewLocationsReview




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

Enterprise a

Network Locations

IP Range: 135.*

IP Range: 148.* IP Range: 136.*

IP Range: 176.*

IP Range: 149.*


Enterprise b

IP Range: 172.*

IP Range: 133.*

IP Range: 10.10.*

Locations

Routing >> Locations


The Location associates an IP address pattern with a name to be used in the RoutingPolicy to determine the originating location of a call. Locations also set the CAC

parameters.

Locations – 6.0 Behavior

CAC – Call Admission ControlParameters

Prevents oversubscription of VOIP networks,applies to media traffic, not signaling traffic.


Each Location has an"bandwidth per call" and a"total managed bandwidth"



Locations – 6.1


Locations




Each Location has an "bandwidth per call" and a "total managed bandwidth"



Managed Bandwidth Usage

Displays system-wide bandwidth usage information for locations where usage ismanaged. The details expansion shows the breakdown of usage among SessionManager Instances.


Locations


Examples of IP Address Patterns:135.*135.12x.121.123135.12x.121.*10.0.0.1-10.0.0.5135.9.0.0/16

Exercise 3: Review existing Location

• Routing >> Locations• Edit ‘classroom’ location• Review

classroom


AdaptationsReviewAdaptationsReview




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

Not Required for thisscenario. More on these

later!

SIP EntitiesSIP Entities




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

SIP Entities

10.29.32.15

13.132.2.12


13.132.2.12 is atrusted source…Will process thisrequest

110.23.14.22

17.156.24.276

SIP Entities for our Scenario

SIP Entity: SM135.122.81.xx:5061

TLS

SessionManager



TLS



SIP Entities


SIP Entities

Routing >> SIP Entities


SIP Entities

Choose the Type.This cannot bechanged once saved.


SIP Entities


How often the Entity is monitored when the link to the Entity is upor active

How often the Entity is monitored when a link to the Entity isdown or inactive

The number of times Session Manager tries to reach the SIPEntity before marking it as down or unavailable

Question: How does Session Manager monitor Entities?

Answer: Session Manager sends SIP OPTIONs messages.

Exercise 4: Define CM’s as SIP Entities

To support our first scenario, we need to define a SIP Entity for each ofthe Communication Managers.

• Define a SIP Entity for each CM calling them CM1 and CM2• Enter the IP Address below for each CM.• Use the ‘classroom’ location• Use ‘Session Manager Configuration’ for SIP Link Monitoring


To support our first scenario, we need to define a SIP Entity for each ofthe Communication Managers.

• Define a SIP Entity for each CM calling them CM1 and CM2• Enter the IP Address below for each CM.• Use the ‘classroom’ location• Use ‘Session Manager Configuration’ for SIP Link Monitoring


CM1: 135.122.80.142 CM2: 135.122.80.62

Entity LinksEntity Links




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

Entity Links


TLS

SessionManager

Entity Link 1 Entity Link 2



TLS



Entity Links


To be able to communicate with other SIP entities, Session Manager must know the portand the transport protocol.

Exercise 5: Define Entity Links

• Define an Entity Link between the Session Manager andeach of the Communication Managers

• Your Session Manager is always SIP Entity 1

SessionManager

Entity Link


• Define an Entity Link between the Session Manager andeach of the Communication Managers

• Your Session Manager is always SIP Entity 1


Sip Entity: SessionManagerPort: 5061

Protocol: TLS

SessionManager

CM1Port: 5061Protocol: TLS

CM2Port: 5061Protocol: TLS

Entity Link

Time RangesTime Ranges




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

SessionManager

Routing Policy – Time of day and Sip Entity


INVITE

192.168.0.210:3002

Time Ranges


You must specify as many time ranges as necessary to cover all hours and days in a week for eachadministered routing policy.

Exercise 6: Define a Time Range

• Define a Time Range thataccepts calls Mondaythrough Friday, 9 am to 5pm.

Special Note: There is a 24/7Time Range by default so itdoes not need to be created.


• Define a Time Range thataccepts calls Mondaythrough Friday, 9 am to 5pm.

Special Note: There is a 24/7Time Range by default so itdoes not need to be created.


Routing PoliciesRouting Policies




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

Routing Policies


Routing Policies

Each Routing Policy defines the "Routing Destination“. Select a defined SIP Entity.


24/7 Time of Day is the default.

Routing Policies

Save the new Routing Policy then define a new Dial Pattern or Regular Expression. The Routing Policycan 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.

Exercise 7: Define Routing Policies

Define a Routing Policy to route calls to theCommunication Managers

• Create two new Routing Policies. One for CM1and the other for CM2.

• Notice the 24/7 Time Range defaults• There are no Dial Pattern or Regular Expression

to select so leave it empty• Commit


Define a Routing Policy to route calls to theCommunication Managers

• Create two new Routing Policies. One for CM1and the other for CM2.


to select so leave it empty• Commit


CM1: 135.122.80.142 CM2: 135.122.80.62

Dial PatternsDial Patterns




Dial Patterns

+44 to 00144001 to +1

02920 to +44292002920 to 001442920

12 43 5 6 7



2. Time Ranges

3. Dial Patterns

4. Expressions

SessionManager

Who?How do I Route extension 92001?Where?

Dial Pattern


SIP Entity:MySessionManager

CM station: 81001 CM Station 92001

INVITE

192.168.0.210:3002

135.122.80.142 135.122.80.62

Dial Patterns


A dial pattern specifies which routing policy is used to route a call based matching the digits dialed by a user

Dial Pattern

…and has a minimum of 5digits and a maximum of

5 digits….

Extension starts with81..…


…and has a minimum of 5digits and a maximum of

5 digits….

For matches of equal length, exact matches have a higher priority over wildcard matches.For example, +1601555 has a higher priority as compared to +1xxx555.

Longer matches get a higher priority over shorter matches.For example, +1601555 has a higher priority as compared to +1601.

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

Dial Pattern

Route To this endpoint……Defined in Routing Policy……


….and uses this RoutingPolicy

…and the source has anIP defined in this

Location

Dial Patterns


Exercise 8: Define Dial Pattern

• Define Dial Patterns to route calls between CM1 andCM2– Click Add and Select –All- Originating Locations– Select Corresponding Routing Policy– Commit Your Changes– Once the Dial Pattern is saved, go back and review the

Routing Policy. What do you notice?– When you dial 9200x from 8100x, it should route through

Session Manager to CM2.– When you dial 8100x from 9200x, it should route through

Session Manager to CM1.


• Define Dial Patterns to route calls between CM1 andCM2– Click Add and Select –All- Originating Locations– Select Corresponding Routing Policy– Commit Your Changes– Once the Dial Pattern is saved, go back and review the

Routing Policy. What do you notice?– When you dial 9200x from 8100x, it should route through

Session Manager to CM2.– When you dial 8100x from 9200x, it should route through

Session Manager to CM1.


Make a CallMake a Call

Exercise 9: Place a call• This exercise will demonstrate routing by ASM from an

h.323 endpoint to another h.323 endpoint registered toCM

• From IP Softphone 8100x, dial 9200x• From IP Softphone 9200x, dial 8100x


H323 station - 8100X H323 station - 9200X


135.122.80.142 135.122.80.62

Outcome of call

Satisfied?– Did the call connect?– If it did, how do we know the path?


Tracing CallsTracing Calls

Call Flow ReviewSessionManager

Dialed number is9200x.

Session Manageruses Routing Policyfor CM2 to route call

SIP SIP


H.323 station - 8100X H.323 station - 9200X

H.323 H.323

SIP Tracing

traceSM– Custom tool that allows us to trace SIP Requests &

Responses in and out of the Session Manager. This toolenables us to more easily diagnose problems.


Accessing the Session Manager Host

Enter your Session ManagerManagement IP Address

135.122.80.xx


Login as cust/cust01

SIP Tracing

traceSM– Type traceSM -h at the command line to get help with the

different arguments that the script supports.


Exercise 10: Run traceSM

• ssh into the Session Manager host as cust/cust01 and then execute:– traceSM –x– ‘s’ to start the capture

• Place the previous call again

• TIPS– Use your up/down arrow keys to select a line in the trace– Press ‘Enter’ to view the details of a selected line– Press ‘Enter’ to close details of selected line– ‘c’ will clear the capture screen– ‘s’ to stop the capture once finished.– ‘q’ to exit the tool– ‘f’ to apply a filter– traceSM –h for help commands

• To delete traceSM process: Ps –ef | grep traceSMKill -9 (2nd #)

• TraceSM is delivered under /opt/Avaya/contrib/bin153© 2007 Avaya Inc. All rights reserved.

• ssh into the Session Manager host as cust/cust01 and then execute:– traceSM –x– ‘s’ to start the capture

• Place the previous call again

• TIPS– Use your up/down arrow keys to select a line in the trace– Press ‘Enter’ to view the details of a selected line– Press ‘Enter’ to close details of selected line– ‘c’ will clear the capture screen– ‘s’ to stop the capture once finished.– ‘q’ to exit the tool– ‘f’ to apply a filter– traceSM –h for help commands

• To delete traceSM process: Ps –ef | grep traceSMKill -9 (2nd #)

• TraceSM is delivered under /opt/Avaya/contrib/bin153© 2007 Avaya Inc. All rights reserved.

Sip TracingtraceSM

– Once traceSM is running, type ‘F’ to apply a filter.– Examples

• -no = no OPTIONS• -nr = no REGISTERS• -ns = no SUBSCRIBES• -u 1901 will filter calls that contain that URI in the from or to headers• You can apply multple filters:

– -u 1901 –no –ns –nr> The above will show only messages to/from 1901 and hide OPTIONS, SUBSCRIBES and

REGISTERS


traceSM– Once traceSM is running, type ‘F’ to apply a filter.– Examples

• -no = no OPTIONS• -nr = no REGISTERS• -ns = no SUBSCRIBES• -u 1901 will filter calls that contain that URI in the from or to headers• You can apply multple filters:

– -u 1901 –no –ns –nr> The above will show only messages to/from 1901 and hide OPTIONS, SUBSCRIBES and

REGISTERS

Don’t Forget Another Option: Trace Viewer


Call Flow Review for NextRouting Scenario

135.122.80.178

Ext: 1xxx

Student01

Student02

135.122.80.58

1135.122.81.58 SM100

135.122.80.88


Ext: 4xxx

Student04135.122.81.178/SM100

Ext: 2xxx

Ext: 3xxx

Student03

135.122.81.88/SM100

135.122.80.158

135.122.81.158

Prep for Next Call Routing Scenario: Sip-to-Sip Calling between different ASM’s

Once all of the elements have been configured each Session Managerwithin a lab will be able to route sip calls to each other.

What elements need to be configured in order for calls to getRouted successfully?

1. ?2. ?3. ?4. ?


Once all of the elements have been configured each Session Managerwithin a lab will be able to route sip calls to each other.

What elements need to be configured in order for calls to getRouted successfully?

1. ?2. ?3. ?4. ?

Exercise 11 : Define Other ASM’s as Sip Entities

To support our second scenario, we need to define a SIP Entity for each of theSession Managers.

• Define a SIP Entity for your partner’s Session Manager naming themASM1, ASM2 or ASM3 and ASM4 etc.

• Use type “Other”

• Enter the SM100 IP Address for each ASM.

• Use the ‘classroom’ location

• Use ‘Session Manager Configuration’ for SIP Link Monitoring


To support our second scenario, we need to define a SIP Entity for each of theSession Managers.

• Define a SIP Entity for your partner’s Session Manager naming themASM1, ASM2 or ASM3 and ASM4 etc.

• Use type “Other”

• Enter the SM100 IP Address for each ASM.

• Use the ‘classroom’ location

• Use ‘Session Manager Configuration’ for SIP Link Monitoring

135.122.81.x

Exercise 12: Define “Other” ASM Entity Links

Entity Link

Define an Entity Link between your Session Managerand each of your partner’s Session Managers.

This will allow the Session Managers to be able toroute calls to each other using NRP.


Define an Entity Link between your Session Managerand each of your partner’s Session Managers.

This will allow the Session Managers to be able toroute calls to each other using NRP.

Exercise 13: Define Routing Policies to ASM’s

Define a Routing Policy to route calls to each theother Session Managers

• Create four new Routing Policies. Select yourpartner’s Sip Entity.


yet, so leave it empty• Commit


Define a Routing Policy to route calls to each theother Session Managers

• Create four new Routing Policies. Select yourpartner’s Sip Entity.


yet, so leave it empty• Commit


CM1: 135.122.106.x 135.122.81.xx

Exercise 14 : Define Dial Pattern to ASM’s

• Define Dial Patterns to route calls between ASM1and ASM2, ASM3 and ASM4 etc.

– ASM1 Dial Pattern: 19 Min: 4 Max: 4 Domain: -ALL-– ASM2 Dial Pattern: 29 Min: 4 Max: 4 Domain: -ALL-– ASM3 Dial Pattern: 39 Min: 4 Max: 4 Domain: -ALL-– ASM4 Dial Pattern: 49 Min: 4 Max: 4 Domain: -ALL-– Click Add and select –All- Originating Locations– Select Corresponding Routing Policy– Commit– Once the Dial Pattern is saved, go back and review the

Routing Policy. What do you notice?


• Define Dial Patterns to route calls between ASM1and ASM2, ASM3 and ASM4 etc.

– ASM1 Dial Pattern: 19 Min: 4 Max: 4 Domain: -ALL-– ASM2 Dial Pattern: 29 Min: 4 Max: 4 Domain: -ALL-– ASM3 Dial Pattern: 39 Min: 4 Max: 4 Domain: -ALL-– ASM4 Dial Pattern: 49 Min: 4 Max: 4 Domain: -ALL-– Click Add and select –All- Originating Locations– Select Corresponding Routing Policy– Commit– Once the Dial Pattern is saved, go back and review the

Routing Policy. What do you notice?


Let’s create our users fortesting!


Let’s create our users fortesting!

Create New User for SIP Registration

Create new user

SIP Handle tells Session Manager theregistration details

???Username: 5001Password: *****


Create new user

SIP Handle tells Session Manager theregistration details

REGISTER

Creating User Profiles







User Profile – The Communication Profile




System Manager Users and Redundancy




Once happy, select ‘Commit’

Exercise 15: Create Sip User Communication Profile

Create New User Profile: x901User Management >> Manage Users >> New

On the Identity Tab:•Add First/Last Name: Anything•Login Name: email address format i.e. [email protected]•Password: alpha-numeric format. 7 digit minimum i.e. abc1234

On the Communication Profile Tab:

• Edit the Communication Profile Password and enter 123456

• Create a new Communication Address using the domain training.com• Select Add

Use the following as the User Name:Student01 = [email protected] = [email protected] = [email protected] = [email protected]

• Assign the user to: Primary Session Manager of MySessionManager• Assign classroom Location under Session Manager Profile•Commit

171© 2007 Avaya Inc. All rights reserved. 171© 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 171© 2007 Avaya Inc. All rights reserved.

Create New User Profile: x901User Management >> Manage Users >> New

On the Identity Tab:•Add First/Last Name: Anything•Login Name: email address format i.e. [email protected]•Password: alpha-numeric format. 7 digit minimum i.e. abc1234



• Create a new Communication Address using the domain training.com• Select Add



mailto:[email protected]










The next exercise will show you how toconfigure the SIP Phone Emulator• Before you can register your new user, you must configure the SIP

Phone Emulator• Launch the SIP Phone found in the SIP Emulators folder

on your desktop.• The information needed to configure your SIP phone is located in

the Classroom Info.txt file


Exercise 16 cont: Configure SIP Emulator

2. Select SIG Menu3. Select the SIP Protocol:

hit right arrow untilSIP is selected and Save

•Open the SIP Emulators Folder on theDesktop

1. Navigate to View >> Admin Options


3. Select the SIP Protocol:hit right arrow until

SIP is selected and Save

Exercise 16 cont: Configure SIP Emulator4. Arrow down to SIP Menu


5. Go to SIP Global Settings:SIP Mode: ProxiedDomain: training.com

6. Arrow down to SIP Proxy Settings:SIP Proxy Server: 135.122.81.xxTransport Type: TLSSIP Port: 5061

Exercise 17: Register SIP Phone

Register x901 using the SIP Phone EmulatorExtensions User / Password

Student01 => 1901 / 123456

Student02 => 2901 / 123456

Student03 => 3901 / 123456

Student04 => 4901 / 123456


Extensions User / Password

Student01 => 1901 / 123456

Student02 => 2901 / 123456

Student03 => 3901 / 123456

Student04 => 4901 / 123456

Disregard PPM download error for now andEnter OK.

Make a CallMake a Call

Scenario 2 Sip-to-Sip Routing

sm1

SessionManager

SessionManager

sm2

1. Routing applied fordial pattern 29 1. Routing pattern matched

for registered user 2901


Registered SIP User 1901 Registered SIP User 2901

Digits Dialed:2901

Ext/PasswordStudent 1 => 1901/123456Student 2 => 2901/123456Student 3 => 3901/123456Student 4=> 4901/123456

Exercise 18: Place calls

• This exercise will demonstrate sip-to-sip routing bySession Manager using Routing Policies

• From Sip Ext. 1901, dial Ext. 2901 and vise versa.• From Sip Ext. 3901, dial Ext. 4901 and vise versa.


Sip station – x901 Sip station – x901User/Password User/Password

Student01 => 1901/123456Student02 => 2901/123456Student03 => 3901/123456Student04 => 4901 /123456

135.122.81.x 135.122.81.x

Regular ExpressionsRegular Expressions

Regular Expressions


Regular Express enables use of:1. Alpha-numeric characters2. Wildcards"*" matches any character string."." matches one character."\ " makes a character lose its special meaning

Some examples are:- For “www.sipentity.domain.com”, use the string “www\.sipentity\.domain\.com”

- For “192.14.11.22”, use string “192\.14\.11\.22”.

- The routing policy with a regular expression .*@.*\.de routes all calls requesting a domain in Germany (forexample, [email protected]) to a Frankfurt Gateway.

www.sipentity.domain.com

Regular Expressions

Used in place of a Dial Pattern sip:12[5-9]{2}@sales\.net


Associates this RegularExpression to an existing

Routing Policy


mailto:@sales

Session Manager to Session Manager CallsSIP to SIP with AdaptationsSession Manager to Session Manager CallsSIP to SIP with Adaptations

Call Routing Scenario 3

Branch Office

Signalling path

Sip-to-Sip Calling between ASM’s and Adaptation


Branch Office

Branch Office

Scenario 3 Sip-to-Sip Routing

sm1

SessionManager

SessionManager

sm2

1. Routing applied forpattern *9

2. Adaptation appliedto remove *9

No Adaptation needed

1. Routing pattern matchedfor registered user 2901


Registered SIP User 1901 Registered SIP User 2901

Dials: *92901Ext/Password

Student 1 => 1901/123456Student 2 => 2901/123456Student 3 => 3901/123456Student 4=> 4901/123456

Create an AdaptationCreate an Adaptation

Adaptability

What can be modified?– Dialled Number Format– SIP Message Format


What can be modified?– Dialled Number Format– SIP Message Format

Number Adaptation

I expect format+442920817500

Must go to… 02920817500 ?


I expect format011442920817500


02920817500

Number Adaptation

I expect format+442920817500

Must go to…

Needs adapting

+442920817500




02920817500

+442920817500

Adaptability

DigitConversionAdapter• Adaptation direction• Matching digit pattern and corresponding digits to remove/insert• Domain name change for source components and destination components

Additional extensions are delivered to support additional service providers:• VerizonAdapter• AttAdapter• CiscoAdapter• OrangeAdapter• CS1000Adapter


DigitConversionAdapter• Adaptation direction• Matching digit pattern and corresponding digits to remove/insert• Domain name change for source components and destination components

Additional extensions are delivered to support additional service providers:• VerizonAdapter• AttAdapter• CiscoAdapter• OrangeAdapter• CS1000Adapter

Adaptations


Application of Adaptations

Adaptation is created and applied to a SIP Entity.

When a call is sent to thatSIP Entity from Session

Manager:


1. Digit Conversions forIncoming Calls to SM applied

2. Routing Policy applied

When an incoming callfrom that SIP Entity isreceived:

When a call is sent to thatSIP Entity from Session

Manager:

1. Routing Policy applied

2. Digit Conversion forOutgoing Calls from SM

Adaptations

Could be:DigitConversionAdapterVerizonAdapterAttAdapterCiscoAdapterCS1000AdapterOrangeAdapter


Exercise 19: Create Adaptation

• Create a new Adaptation called: RemoveDialCode• Module Name: DigitConversionAdapter• Add a Digit Conversion for Outgoing Calls from SM to remove a ‘ *9 ‘ from a 6

digit destination address.


Scenario 3 –Configure your Session Manager so that when your partner at *9x901, your Session Manager will route the call

based on the *9 dial pattern then remove the *9 before sending it.

sm1

SessionManager

SessionManager

sm2

1. Routing applied forpattern *9

2. Adaptation appliedto remove *9

No Adaptation needed

1. Routing pattern matchedfor registered user 2901

©2011. All rights reserved.© 2007 Avaya Inc. All rights reserved.Registered SIP User 1901

sm1 sm2

Registered SIP User 2901

Dials: *92901

Applying Adaptations

Once the Adaptation is created, it can be applied to ‘far end’ SIPEntities. Adaptations CANNOT be applied to SIP Entities defined astype ‘Session Manager’.


Exercise 20: Place a Call That routes through two SessionManagers using an Adaptation

• Discuss and implement what is required to have:– Student 1 call Student 2 (1901 to *92901)– Student 3 call Student 4 (3901 to *94901)

• The *9 will be used to determine the routing but should be removed priorto the request being sent to your partners Session Manager.

• What configuration still needs to be done??– Assume the same SIP Domain and Location are used. Consider the following:– Does your Session Manager:

• Have a trusted SIP Entity for your partner’s Session Manager?• Know how to communicate with your partner’s Session Manager?• Have a way to route the request to your partner’s Session Manager?• Know what dial plan to match to route to your partner’s Session Manager?

• Test using the SIP Phone Emulator (see following slides 106- 109) toconfigure and log in if you haven’t done so already)

– Register as your x901 User

• Use traceSM to trace the call.


• Discuss and implement what is required to have:– Student 1 call Student 2 (1901 to *92901)– Student 3 call Student 4 (3901 to *94901)

• The *9 will be used to determine the routing but should be removed priorto the request being sent to your partners Session Manager.

• What configuration still needs to be done??– Assume the same SIP Domain and Location are used. Consider the following:– Does your Session Manager:

• Have a trusted SIP Entity for your partner’s Session Manager?• Know how to communicate with your partner’s Session Manager?• Have a way to route the request to your partner’s Session Manager?• Know what dial plan to match to route to your partner’s Session Manager?

• Test using the SIP Phone Emulator (see following slides 106- 109) toconfigure and log in if you haven’t done so already)

– Register as your x901 User

• Use traceSM to trace the call.


Exercise 20 cont.: Summary of Configuration Required

1. Sip Entity for Partner’s Session Manager (type- Other)

2. Sip Entity Link for Partner’s Session Manager

3. Apply adaptation to Sip Entity

4. Create Routing Policy to Partner’s Session Manager

5. Create Dial Pattern

6. Assign Routing Policy to Dial Pattern


Exercise 20 cont.: Summary of Configuration Required

1. Sip Entity for Partner’s Session Manager (type- Other)

2. Sip Entity Link for Partner’s Session Manager

3. Apply adaptation to Sip Entity

4. Create Routing Policy to Partner’s Session Manager

5. Create Dial Pattern

6. Assign Routing Policy to Dial Pattern

traceSM – What to look for

198© 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA

Matches Dial Pattern *9and finds Routing Policy.

Request URI is changed, no *9.

To: remains unchanged.

Call Routing TestCall Routing Test

Call Routing Test


Call Route Testing – Scenario 2


Call Route Testing - Results

After Execute Test is clicked, the Routing Decision results are displayed.


Call Route Testing - Results

Page 2 of the Routing Decision Results


Exercise 21: Call Routing TestUse the Call Routing Test Tool and place the same call as Scenario 2


Session Manager CallsH323 to SIP

Call RoutingScenario 4

Session Manager CallsH323 to SIP

Call RoutingScenario 4

Session Manager & Communication Manager


H.323

SM SIP EntitySIP

Scenario 4 –Place a call from an IP Phone to SIP User

135.122.80.142training.com

SIPSIP


H.323SIP


What additional configuration do we need to make to place this call?

-Assume the SIP Domain and Location are configured.

-Does your Session Manager:

-Recognize the CM as a SIP Entity?

-Know how to communicate with CM?

-Recognize the registered SIP User?

Exercise 22: Place a call via CM to SIP User

• Log into your 8100x IP Station• Log into your x901 SIP Phone• Place the call



Session Manager CallsSIP to H323Call Scenario 5

Session Manager CallsSIP to H323Call Scenario 5

Scenario 4a –Place a call from a SIP Phone to IP Phone


SIP SIP


H.323SIP

sip:[email protected]



-Assume the SIP Domain and Location are configured.




-Recognize the registered SIP User?

mailto:sip:[email protected]

Exercise 23: Placing a call between SIP User to IPPhone

SM SIP Entity

Student01 => [email protected] => [email protected] => [email protected] => [email protected]



Student01 => [email protected] => [email protected] => [email protected] => [email protected]








Scenario 5b –Place a call from a SIP Phone to IP Phone

SM SIP Entity


SIP SIP


H.323

SIPsip:[email protected]



-Assume the SIP Domain (abc.com) and Location are configured.




-Recognize the registered SIP User? – Yes, it has been created for you.


mailto:sip:[email protected]

Exercise 24: Create System Manager User – addCommunication ProfileCreate New User Profile: x999User Management >> Manage Users >> NewOn the Identity Tab:•Add First/Last Name: Anything•Login Name: email address format i.e. [email protected]•Password: alpha-numeric format. 7 digit minimum i.e. abc1234



• Create a new Communication Address using the domain abc.com• Select Add




Create New User Profile: x999User Management >> Manage Users >> NewOn the Identity Tab:•Add First/Last Name: Anything•Login Name: email address format i.e. [email protected]•Password: alpha-numeric format. 7 digit minimum i.e. abc1234



• Create a new Communication Address using the domain abc.com• Select Add













Exercise 25 : Prepare 2nd SIP Phone• Open a 2nd instance of the SIP Emulator• Navigate to View >> Admin Options• Select SIG Menu and enter SIP• Use your down or up Arrow Key until SIP ishighlighted and press Enter

• SIP Global Settings is highlighted, press Enter•SIP Mode = Proxied•SIP Domain = abc.com

• Click Save

• Use your down or up Arrow Key until SIP Proxy Settings ishighlighted and press Enter

• Click existing SIP ProxyChange SIP Port = 5062

• Click Save, Back, Back, Exit


• Open a 2nd instance of the SIP Emulator• Navigate to View >> Admin Options• Select SIG Menu and enter SIP• Use your down or up Arrow Key until SIP ishighlighted and press Enter

• SIP Global Settings is highlighted, press Enter•SIP Mode = Proxied•SIP Domain = abc.com

• Click Save

• Use your down or up Arrow Key until SIP Proxy Settings ishighlighted and press Enter

• Click existing SIP ProxyChange SIP Port = 5062

• Click Save, Back, Back, Exit

Exercise 26: Place a call via SIP User to CM IP Station

• Log into your 8100x IP Station• Log into your x999 2nd SIP Phone• TestWas it successful?


User/Password User/PasswordStudent01 => 1999/123456 …………dials…....…….81001/123456Student02 => 2999/123456…………dials…....……..81002/123456Student03 => 3999/123456 ………..dials…....……..81003/123456Student04 => 4999/123456……… ..dials…....……..81004/123456

403 Forbidden: Invalid Domain in From Header


Adaptability

Adaptations can be used to change the SIP Domain in the RequestURI(destination) and the P-Asserted Identity (PAI) (source).

DigitConversionAdapter: Domain Name Change– Outbound call Domain Modification Parameter

> overrideDestinationDomain (odstd)replaces the domain in Request-URI

> overrideSourceDomain (osrcd):replaces the domain in the P-Asserted-Identity header

– Inbound call Domain Modification Parameters> ingressOverrideDestinationDomain (iodstd)

replaces the domain in Request-URI> ingressoverrideSourceDomain (iosrcd)

replaces the domain in the P-Asserted-Identity header


Adaptations can be used to change the SIP Domain in the RequestURI(destination) and the P-Asserted Identity (PAI) (source).

DigitConversionAdapter: Domain Name Change– Outbound call Domain Modification Parameter

> overrideDestinationDomain (odstd)replaces the domain in Request-URI

> overrideSourceDomain (osrcd):replaces the domain in the P-Asserted-Identity header

– Inbound call Domain Modification Parameters> ingressOverrideDestinationDomain (iodstd)

replaces the domain in Request-URI> ingressoverrideSourceDomain (iosrcd)

replaces the domain in the P-Asserted-Identity header

Example:ModuleName: DigitConversionAdapter

Module Parameter: odstd=training.com osrcd=training.com

Change Domain of Source

DigitConversionAdapter overrideDestinationDomain = training.com overrideSourceDomain=training.com(can also use: odstd=training.com osrcd=training.com)


Result of Domain Changeodstd=training.com


osrcd=training.com

Exercise 27: Define an Adaptation to change the Source andDestination SIP Domain from abc.com to training.com

• Create a new Adaptation called ‘ChangeDomain’ using theDigitConversionAdapter Module.– Add Outbound Module Parameters to change the:

• Destination SIP Domain to training.com

• (odstd= training.com)

• Source SIP Domain to training.com• (osrcd=training.com)

• Test– Place the actual call and view traceSM– Use the Call Routing Test tool to see the Adaptation


• Create a new Adaptation called ‘ChangeDomain’ using theDigitConversionAdapter Module.– Add Outbound Module Parameters to change the:

• Destination SIP Domain to training.com

• (odstd= training.com)

• Source SIP Domain to training.com• (osrcd=training.com)

• Test– Place the actual call and view traceSM– Use the Call Routing Test tool to see the Adaptation


Alternate Routing PolicyAlternate Routing Policy

Alternate Routing – Failover


Where is Routing Ranking Set ?

…in the Routing Policy


Exercise 28: Alternate Routing – Failover

Let’s setup a new SIP Entity. For the purpose of this exercise, it is a“dummy” SIP Entity that is not monitored by Session Manager. Let’smodify the Dial Pattern 8 so that it attempts to route to our “fake” entity first,then to CM1 if the “fake” entity isn’t available.

• Begin by creating a SIP EntityName: FakeEntity

IP:135.122.80.99

Type: Other

Location: Classroom

Time Zone: America/Denver

SIP Link Monitoring: LinkMonitoring Disabled


Name: FakeEntity

IP:135.122.80.99

Type: Other

Location: Classroom

Time Zone: America/Denver

SIP Link Monitoring: LinkMonitoring Disabled

Exercise 28 cont.: Alternate Routing – Failover• Define the SIP Entity Link

• Create a Routing Policy for ‘FakeEntity’. Leave the Ranking a ‘0’ for 24/7.


Exercise 28 cont.: Alternate Routing – Failover• Modify the Routing Policy for CM1. Change the Ranking to 10 for 24/7.


Exercise 28 cont. : Alternate Routing –Failover

• Modify the Dial Pattern for 8. Add another ‘Originating Locations and RoutingPolicies’ for the classroom Location that uses the Routing Policy for theFakeEntity.


• Modify the Dial Pattern for 8. Add another ‘Originating Locations and RoutingPolicies’ for the classroom Location that uses the Routing Policy for theFakeEntity.

Exercise 28 cont. : Alternate Routing –Failover

Place the call from your x901 SIP User to your 81x H.323 phone and view traceSM.


TimerB – 4 Seconds

After FakeEntity isunresponsive, nextPolicy according to

Ranking is attempted.

Alternate Routing – Time of Day


How does Session Manager know what time or dayit is for a specific destination…….?


Exercise 29: Alternate Routing – Time of DayUse the Call Routing Test Tool to see which Policy is selected.• Create a New Time Range for Saturday and Sunday, all day

• Modify the “FakeEntity” Routing Policy by removing 24/7 and adding 9-5.


Use the Call Routing Test Tool to see which Policy is selected.• Create a New Time Range for Saturday and Sunday, all day

• Modify the “FakeEntity” Routing Policy by removing 24/7 and adding 9-5.

Exercise 29 cont. : Alternate Routing – Time of Day• Modify the “CM2” Routing Policy by removing 24/7 and adding Weekend.


• Modify the Dial Pattern for 9. Add another ‘Originating Locations and RoutingPolicies’ for the classroom Location that uses the Routing Policy for theFakeEntity.•removing 24/7 and adding Weekend

Exercise 29 cont. : Alternate Routing – Time of Day• Modify the Dial Pattern for 9. Add another ‘Originating Locations and RoutingPolicies’ for the classroom Location that uses the Routing Policy for theFakeEntity.


Exercise 29 cont. : Alternate Routing – Time ofDay

Use the Call Routing Test Tool to see which Policy is selected.


Local Host Name ResolutionLocal Host Name Resolution

Local Host Name Resolution

A host table internal for Session Manager that resolves a host name toa specific IP address.


If unchecked, Session Manager usesa local table to resolve. If checked,Session Manager will use DNS toresolve the FQDN.





Exercise 30: Modify SIP Entity for Local HostName Resolution

• Modify the SIP Entity for your Partners Session Manager to aFQDN (train2.com)

• Add an entry in the Local Host Name Resolution to resolve theFQDN to an IP Address

• Place a call to that destination


Entity Link MonitoringEntity Link Monitoring

System Health

Monitoring health

Regular health checks

Modifying circumstances forimproved health

Rapid intervention on failure




Health of SIP Entities

Monitor the state of each defined SIP Entity


OPTIONS Request


Enable SIP Monitoring in Session Manager Instance


How often the Entity is sent an OPTIONS when the link to the Entity is up or active

How often the Entity is sent an OPTIONS when a link to the Entity is down orinactive

The number of times Session Manager tries to reach the SIP Entity before marking itas down or unavailable

To enable or disable monitoring of the SIP Entities by this Session Manage instance

Monitoring Health of SIP Entities

Controlling monitoring of individual SIP Entities.

Link Monitoring Enabledoverrides Session Manager

Instance properties, as long asmonitoring is enabled on theSession Manager Instance.


Link Monitoring Enabledoverrides Session Manager

Instance properties, as long asmonitoring is enabled on theSession Manager Instance.

Take a BreakTake a BreakOptional Workshop

You have completed the followingObjectives - Module 2 Routing Policy Overview SIP Routing Policy






Routing Policy Overview SIP Routing Policy





Avaya Aura ® Session ManagerCM and other Feature Server AdministrationAvaya Aura ® Session ManagerCM and other Feature Server Administration

Overview of ApplicationsSession Manager and Sequenced & Named ApplicationsSession Manager and Sequenced & Named Applications

Objectives - Module 3Overview of Application Sequencing

– Sequenced Vs. Named Applications

Sequenced Applications with Communication Manager– Communication Manager Overview

• Communication Manager Configuration - CM Evolution Server & CMFeature Server

Adding CM as a Managed ElementSystem Manager Application ConfigurationApplying Application Sequences to UsersSequenced Application with Non-CM Feature ServerImplicit Users and Sequenced ApplicationsNamed Applications


Overview of Application Sequencing– Sequenced Vs. Named Applications

Sequenced Applications with Communication Manager– Communication Manager Overview

• Communication Manager Configuration - CM Evolution Server & CMFeature Server

Adding CM as a Managed ElementSystem Manager Application ConfigurationApplying Application Sequences to UsersSequenced Application with Non-CM Feature ServerImplicit Users and Sequenced ApplicationsNamed Applications

Sequenced and Named Applications




Sequenced Applications

Feature Servers

Benefit of Application Sequencing

Session Manager watches over Registered SIP Users and all of theircalls, both incoming and outgoing, ready to take any special action

when the occasion requires.


CM as a Feature Server

CM has thousands of “features”. Since the CM has knowledge of the user, theSession Manager does not have to address each feature.

It simply sends the request to CM and CM will apply the appropriate features basedon the user and whether they are the caller or the callee.


CM has thousands of “features”. Since the CM has knowledge of the user, theSession Manager does not have to address each feature.

It simply sends the request to CM and CM will apply the appropriate features basedon the user and whether they are the caller or the callee.

OriginatingApplicationSequence

Session Manager retrievescaller’s User Profile

Retrieves callers OriginatingApplication Sequence

– An ordered list of applications tobe applied to outbound callsmade by the caller

How CM Features are Applied


CalleeCaller

Who is the caller?Do I know him?

IMS: Half-Call Model

Session Manager retrievescaller’s UserProfile

Retrieves callers OriginatingApplication Sequence

– An ordered list of applications tobe applied to outbound callsmade by the caller

Session Manager retrievescallee’s UserProfile

Retrieves callees TerminatingApplication Sequence

– An ordered list of applications tobe applied to inbound calls madeby the callee

OriginatingApplicationSequence

TerminatingApplicationSequence


Originating Terminating

Caller Callee

IMS: Half-Call Model

Who is the callee?Do I know him?

CM Relationships to ASM

1. Sip Entity2. Managed Element3. Application4. Added to Application Sequence

1. Sip Entity2. Managed Element3. Application4. Added to Application Sequence

Adding a Communication Manageras a Managed ElementAdding a Communication Manageras a Managed Element

Communication System Manager

The Communication System Manager interface can be used tosynchronize CM station data to the System Manager database.



The Communication System Manager interface can be used tosynchronize CM station data to the System Manager database.



Each CM must be administered as an Entity using Manage Elements.



Specify the name and IP address of the Communication Manager.



The login used must have ssh/sat access to Communication Manager.


Do not use any of the following logins when administering aCM entity for Communication System Manager:

craft, craft2, admin, inads, init, rasaccess, sroot, and tsc

Exercise 1: Add CM as a Managed Element

• Navigate to Inventory >> Manage Elements– Select New– Name: CM2_ES– Node: 135.122.80.62– Login/Password:

• Student 1 = smgr1, Tr*1ning• Student 2 = smgr2, Tr*1ning• Student 3 = smgr3, Tr*1ning• Student 4 = smgr4, Tr*1ning


• Navigate to Inventory >> Manage Elements– Select New– Name: CM2_ES– Node: 135.122.80.62– Login/Password:

• Student 1 = smgr1, Tr*1ning• Student 2 = smgr2, Tr*1ning• Student 3 = smgr3, Tr*1ning• Student 4 = smgr4, Tr*1ning

Scheduling CM Data Synchronization


Element Manager – Data Synchronization

Automatic CM Data Synchronization– After a CM has been added as a Managed Element, it will be automatically

scheduled for an initial and subsequent incremental data synchronization.• Subsequent changes made in System Manager will immediately update underlying CM when

committed.• If subsequent changes are made in CM SAT or ASA, they will NOT be reflected in

System Manager until a synchronization is performed.

Monitor Process – Inventory >> Synchronization >> Communication System


Automatic CM Data Synchronization– After a CM has been added as a Managed Element, it will be automatically

scheduled for an initial and subsequent incremental data synchronization.• Subsequent changes made in System Manager will immediately update underlying CM when

committed.• If subsequent changes are made in CM SAT or ASA, they will NOT be reflected in

System Manager until a synchronization is performed.

Monitor Process – Inventory >> Synchronization >> Communication System

Making Changes to Data


Scheduling CM Data Synchronization


Manual CM Data Synchronization

When you modify CM data in System Manager, it isautomatically replicated to CM when you commit.

If you make changes to CM data outside of SystemManager, the data is not replicated to System Manageruntil a scheduled incremental synchronization.


Exercise: View Synchronization Status Navigate to Inventory >> Synchronization >> Communication System


Configuring and ApplyingApplication SequencesConfiguring and ApplyingApplication Sequences

Defining Applications


Define the Application for CM

SIP Entity ManagedElement

(CM)


SIP Entity ManagedElement

(CM)

SIP Entity

Tell Session Manager about the FeatureServer box (CM) (was previously done)

– It’s address, type, location, etc


SIP Entity

Create Entity Link


SIP Entity

Managed Element - CM


Sequence/Template 1Sequence 1

Define the Application Sequence For CM


Click

Exercise 2: Create Application and a ApplicationSequence

Create a new Application called CM1:• SIP Entity = CM1

• CM System for SIP Entity = CM_ES1


Create new ApplicationSequence using the new

Application CM1

Applying Application Sequences to Users

System Manager

Adding User ProfilesAdding User Profiles

Walk Through Exercise – User Profile


Walk Though Continued - Communication Profile


Communication Address = Avaya SIPUsername= [email protected]

Walk Though Continued - Communication Profile

Select Primary Session Manager

Select a Home Location


Check the box for EndpointProfile.

System = CM1

Check ‘Use Existing Enpoints’

Select your x101 station

Let everything else defaultexpect enter a Security Code =123456


Walk Through – Create User Profile for x101• User Administration >> Manager Users• Click New• Identity Tab:

• Create a new user with a first and last name

• Create a Login Name <lastname>@training.com

• Enter abc1234 as the SMGR Login Password

• Communication Profile Tab:• Enter 123456 as the Communication Profile Password

• Create a new Communication Address using the domaintraining.com

Use the following as the Communication Address:Student01 = [email protected] = [email protected] = [email protected] = [email protected]

• Assign the user to the Primary Session Manager ofMySessionManager and the Home Location classroom under SessionManager Profile.

• Assign the user to an Endpoint Profile. Select the CM andcheck “use existing endpoint”. Select your station from thelist, or type it. Let everything else default – except theSecurity Code. Enter ‘123456’.

• Save the new user

Ext: x101

EC500Call-fwdSend-Calls

©2011. All rights reserved.© 2007 Avaya Inc. All rights reserved. 287© 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA 287© 2007 Avaya Inc. All rights reserved.

• User Administration >> Manager Users• Click New• Identity Tab:










mailto:@training.com










Exercise 4: Create User Profile for x102

Ext: x102

EC500










• Save the new user ©2011. All rights reserved.© 2007 Avaya Inc. All rights reserved.





















Exercise 5: Create User Profile for x103

Ext: x103

Brdg-Appr• User Administration >> Manager Users• Click New• Identity Tab:









• Save the new user©2011. All rights reserved.

© 2007 Avaya Inc. All rights reserved.





















System Manager Users


Edit System Manager User to apply Application Sequence to User’s CommunicationProfile


Exercise 3: Assign Application Sequence to a User

• Access System Manager and navigation to UserManagement >> Manager User and edit user x101

• On the Communication Profile Tab,scroll down and expandSession Manager Profile.

• Select the CM1 Application Sequenceyou created for both Origination ApplicationSequence and Termination ApplicationSequence for this user and Commit.


• Access System Manager and navigation to UserManagement >> Manager User and edit user x101

• On the Communication Profile Tab,scroll down and expandSession Manager Profile.

• Select the CM1 Application Sequenceyou created for both Origination ApplicationSequence and Termination ApplicationSequence for this user and Commit.

System Manager Users linked to CM EndpointSystem Manager Users linked to CM Endpoint

System Manager

Ownership of Station

SM100


PPM BrokerPPM Owner

User Profiles and existing CM Stations


Bulk Communication Profile Editor


Use the Bulk Communication Profile Editor to edit multiple Users’Communication Profiles at one time!

Exercise 6: Using the Bulk Communication ProfileEditor to apply Application Sequence Update User x102and x103

• Navigate in System Manager to Session Manager >> Communication ProfileEditor

• Select the two following users:

• Scroll down and select CM1/CM2/CM3/CM4 as the Origination and TerminationApplication Sequence under New Communication Profile Values and clickCommit.

Student 1: 1102, 1103

Student 2: 2102, 2103

Student 3: 3102, 3103

Student 4: 4102, 4103




• Scroll down and select CM1/CM2/CM3/CM4 as the Origination and TerminationApplication Sequence under New Communication Profile Values and clickCommit.

• When the confirmation page is displayed,verify you selected the correct users andclick Commit.

Exercise: Update User x102 and x103 using the BulkCommunication Profile Editor to apply ApplicationSequence to x102 and x103 Users



• Scroll down and select CM1 as the Origination and Termination ApplicationSequence under New Communication Profile Values and click Commit.

Student 1: 1102, 1103

Student 2: 2102, 2103

Student 3: 3102, 3103

Student 4: 4102, 4103




• Scroll down and select CM1 as the Origination and Termination ApplicationSequence under New Communication Profile Values and click Commit.

• When the confirmation page is displayed,verify you selected the correct users andclick Commit.

Configure SIP Phone Emulator

Before you can register your new user, you must configure the SIPPhone Emulator

This may already be configured if you used it in a previous course.


Verify or Configure SIP Phone Emulator


135.122.80.x

135.122.81.x

Provide theSecurity Module IPAddress

Date post:	27-Oct-2014
Category:	Documents
Upload:	sonbarse
View:	199 times
Download:	11 times

Avaya Session Manager Part 1

Documents