Avaya Session Manager Part 1

Avaya Aura Session Manager Administration
5U00081V Version 6.1
Before we begin
Courses strongly recommended to complete before this course:
System Manager Administration SIP Essentials Session Manager General Overview Session Manager Technical Overview Session Manager Installation & Initial Setup
5U00080V ATC01290WEN ATU00171OEN ATU00170OEN ATA02446OEN
Course Length = 24 Hours
vILT = 4 Days @ 6 hours
Breaks
Instructors discretion
2011. All rights reserved.

2007 Avaya Inc. All rights reserved.
Agenda Live Instructor & Virtual Led Virtual 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

Course Objectives Module 1

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


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 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 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.. Understand
Session Manager and System Manager Architectural Components and Topology Understand 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 Information
Training lab
Student01
135.122.80.71
135.122.80.55
eth0:135.122.80.58 Security Module: 135.122.81.58
Student02
135.122.80.142
135.122.80.72
135.122.80.57
eth0:135.122.80.88 Security Module: 135.122.81.88 135.122.80.62
Student03
135.122.80.73
135.122.80.157
Student04
135.122.80.74
135.122.80.177
Avaya Aura Session Manager Instance Configuration
Objectives Module 1

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

Exercise 1: Access servers

System Manager Console (browser)
https://<ipaddress> admin/Tr@1ning
15
SIP Domains
SIP Domains
Is this a SIP Domain Im suppose to process?

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
Locations
Network Locations
Enterprise a
IP Range: 148.* IP Range: 136.* IP Range: 149.* IP Range: 176.*
IP Range: 135.*
IP Range: 172.*
IP Range: 133.*
Enterprise b
IP Range: 10.10.*

Locations

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

Locations
Examples of IP Address Patterns:

135.* 135.12x.121.123 135.12x.121.* 10.0.0.1-10.0.0.5 135.9.0.0/16

Exercise: Create a Location

Create a new Location called classroom Add a pattern of 135.*
26
SIP Entities
SIP Entities
10.29.32.15
13.132.2.12
asm2 135.122.80.225 5060 TCP/UDP 5061 TLS
110.23.14.22
17.156.24.276

SIP Entities

SIP Entities
Routing >> SIP Entities

Sip Entity Session Manager

SIP Entities General Settings
IP
Only Session Managers managed by this System Manager should be specified as type Session Manager
Use IP Address of SM-100 Select Type: Session Manager

SIP Entities
SIP Entities Ports
Defines the port(s) and protocol that this Session Manager listens for SIP traffic.
PORT You must add a listening port for the Session Manager SIP Entity. Add a port for TCP, TLS and UDP. You must specify a Default Domain.

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 5060 TCP 5060 UDP training.com training.com training.com
33
Session Manager Instance
Master DB
Jim
Replica DB
Only after a Session manager Instance is defined can we: Monitor health and status of the Session Manager Administer Routing Policies, Users Communication Profiles and Application Sequencing



Global Settings


Session Manager >> Session Manager Administration

Define Session Manager Instance - Continued
IP
IP Address of Session Managers eth0
Defaults based on IP Address defined in SIP Entity.


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 or inactive The number of times Session Manager tries to reach the SIP entity before marking it as down or unavailable This controls whether CDR is enabled at the system level for that Session Manager instance. If CDR is enabled, you can individually control call detail recording for specific SIP 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 SIP Entity 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
43
Post Configuration Checks
Post Configuration

Enable New Service

The default state of the Session Manager is Deny New Service. This must be 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
52
SIP Firewall Configuration
SIP Firewall Configuration

TraceViewer Blocked Call

SIP Firewall Configuration - Rules

Multiple Session Manager Instances

Core 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 makes them exact replicas each other able to support a redundant configuration.
Master DB
Jim
Replica DB
Only after a Session manager Instance is defined can we: Monitor health and status of the Session Manager Administer Routing Policies, Users 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 Session
Manager.
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 in Communication Manager. Once the Trunk Group is created, it can be added to the Primary Session Managers Route Pattern.
Primary Session Manager Secondary Session Manager

Assign Session Managers to Users

DEMO: Failover from Primary to Secondary Session Manager

Topics in this video are covered in: Session Manager User Profile Management Routing Policy
64
Troubleshooting
Accessing the Servers

Exercise 7: Access servers

Access Servers using putty application - Run putty.exe - Connect using ASMs Eth 0 Ip Address
Log into Session Manager Server with the following login details: Login: craft Password: craft01 At command line switch your user to sroot by typing the following:
su - sroot password: sroot01
67
SMConsole
A command-line tool installed on Session Manager developed for debugging purposes. It can be used to access runtime Call Processing or PPM data. runsmconsole starts the SMConsole application

SMConsole
Running help at the prompt displays all the available commands The GET command retrieves stored data and can verify that the replication client (SM) is in sync with System Manager. REINIT and RM impact runtime data and are destructive dont use!
exit leave smconsole session.

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
70
You have completed the following Objectives - Module 1


Avaya Aura Session Manager Routing Policy
Objectives - Module 2
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

Routing Policy
Determines how SIP calls are routed

SIP Routing
Who
Request SIP domain? Source and destination
Session Manager
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 to create something more

Actions
Set budget Employ workers Organise premises Build and assemble shed Order tools Order materialsBuy paint and paint the house Organise insurance Cut grass Sweep patio First aid Plant seeds Prune trees
Tasks

1. Destination SIP Entity
2. Time Ranges
Time Range 1
3. Dial Patterns
4. Expressions
Time Range 1 Monday to Thursday 9.00am to 4.00pm Time Range 2 Saturday and Sunday 12.00am to 11.59pm
Time Ranges

PSTN Gateway
2. Time Ranges
Time Range 1
3. Dial Patterns
4. Expressions
Communication Manager PSTN Gateway
10.24.35.112 22.117.32.12
SIP Entities

Location 1
Denver
Location 2
Cardiff
Locations
Adaptation 1
+44 to 0144
Adaptation 2
02920 to +44292 0
Communication Manager
10.24.35.112 Location
Denver
SIP Entities
Adaptation
+44 to 0144
Adaptations
Locations
Adaptations
SIP Entity
Entity Links
Time Ranges
SIP Domains avaya.com avaya.co.uk avaya.co.sng elsewhere.com
Dial Patterns +44 to 00144 001 to +1 02920 to +442920 02920 to 001442920
2. Time Ranges
3. Dial Patterns
4. Expressions

Defining the SIP Routing Policy
Session Manager & Communication Manager
SM SIP Entity
SM SIP Entity
H.323
H.323
Routing Scenario 1:
CM H.323 Phone Call Routing through Session Manager
SIP SIP
H.323
135.122.80.142 TLS 5061 training.com
H.323
135.122.80.62 TLS 5061 training.com
Extensions User/Password User/Password Student01 => 81001/123456 dials...... 92001/123456 Student02 => 81002/123456 dials...... 92002/123456 Student03 => 81003/123456 dials...... 92003/123456 Student04 => 81004/123456 dials...... 92004/123456

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?
135.122.80.142
135.122.80.62
2007 Avaya Inc. All rights reserved. 86
Access the 1st H.323 Phone

Call Server = 135.122.80.142 Station 81001 => Student01 Station 81002 => Student02 Station 81003 => Student03 Station 81004 => Student04 Password: 123456
Full detail on accessing the IP Phones is documented in the Toolwire Setup File
https://dcm.toolwire.com
Pod 1 Student 1 Student 2 Student 3 Student 4 IP Phone ip010170/welcome ip010171/welcome ip010172/welcome ip010173/welcome Pod 2 Student 1 Student 2 Student 3 Student 4 IP Phone ip010174/welcome ip010175/welcome ip010176/welcome ip010177/welcome Pod 3 Student 1 Student 2 Student 3 Student 4 IP Phone ip010178/welcome ip010179/welcome ip010180/welcome ip010181/welcome
87
Access the 2nd H.323 Phone

Call Server = 135.122.80.62 Station 92001 => Student01 Station 92002 => Student02 Station 92003 => Student03 Station 92004 => Student04 Password: 123456
Full detail on accessing the IP Phones is documented in the Toolwire Setup File
https://dcm.toolwire.com
Pod 1 Student 1 Student 2 Student 3 Student 4 IP Phone ip020170/welcome ip020171/welcome ip020172/welcome ip020173/welcome Pod 2 Student 1 Student 2 Student 3 Student 4 IP Phone ip020174/welcome ip020175/welcome ip020176/welcome ip020177/welcome Pod 3 Student 1 Student 2 Student 3 Student 4 IP Phone ip020178/welcome ip020179/welcome ip020180/welcome ip020181/welcome
88
Lets look at our first scenario

Who? How do I Route extension 92001? Where?
INVITE
Session Manager
192.168.0.210:3002
SIP Entity: MySessionManager

INVITE 200 OK
192.168.0.210:3002 192.168.0.210:3002
135.122.80.142
135.122.80.62
CM station: 81001
CM Station 92001
Scenario 1
Session Manager
Entity Link 1 Entity Link 2
Sip Entity: SM 172.25.1.60:5060

SIP Domain: training.com
135.122.80.142 TLS 5061 training.com
H323 station - 8100X

Session Manager Configuration Common Console To access the System Manager administration page, navigate to http://<HOSTIP>/ The username and password are admin/Tr@1ning
SIP Domains
Review
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

SIP Domains

SIP Domains
Is this a SIP Domain Im suppose to process?

SIP Domains No Authoritative Domain
No Authoritative Domain for 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 Domain

1. Navigate in System Manager to Routing >> Domains - Define abc.com as a domain
98
Exercise 2 cont: Add 5062 Port to ASM

2. Select SIP Entities Menu: Edit your Session Manager SIP Entity and add: Port 5062 Protocol: TLS Domain: abc.com
99
Locations
Review
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

Network Locations
Enterprise a
IP Range: 148.* IP Range: 136.* IP Range: 149.* IP Range: 176.*
IP Range: 135.*
IP Range: 172.*
IP Range: 133.*
Enterprise b
IP Range: 10.10.*

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

Locations 6.0 Behavior
CAC Call Admission Control Parameters

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
CAC Call Admission Control Parameters

Prevents oversubscription of VOIP networks, applies to media traffic, not signaling traffic.
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 is managed. The details expansion shows the breakdown of usage among Session Manager Instances.

Locations
Examples of IP Address Patterns:

135.* 135.12x.121.123 135.12x.121.* 10.0.0.1-10.0.0.5 135.9.0.0/16

Exercise 3: Review existing Location

Routing >> Locations Edit classroom location Review
classroom
109
Adaptations
Review
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
Not Required for this scenario. More on these later!
2. Time Ranges
3. Dial Patterns
4. Expressions

SIP Entities
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

SIP Entities
10.29.32.15
13.132.2.12
110.23.14.22
13.132.2.12 is a trusted source Will process this request

17.156.24.276

SIP Entities for our Scenario

Session Manager
SIP Entity: SM 135.122.81.xx:5061 TLS 135.122.80.142 TLS 5061 training.com 135.122.80.62 TLS 5061 training.com

SIP Entities

SIP Entities
Routing >> SIP Entities

SIP Entities
Choose the Type. This cannot be changed once saved.

SIP Entities
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 or inactive The number of times Session Manager tries to reach the SIP Entity before marking it as down or unavailable
Question: How does Session Manager monitor Entities? Answer: Session Manager sends SIP OPTIONs messages.
Exercise 4: Define CMs as SIP Entities

To support our first scenario, we need to define a SIP Entity for each of the 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
120
Entity Links
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

Entity Links
Session Manager
Entity Link 1 SIP Entity: SM 135.122.81.xx:5061 TLS 135.122.80.142 TLS 5061 training.com
Entity Link 2

Entity Links
To be able to communicate with other SIP entities, Session Manager must know the port and the transport protocol.

Exercise 5: Define Entity Links
Define an Entity Link between the Session Manager and each of the Communication Managers Your Session Manager is always SIP Entity 1
Session Manager
Entity Link
CM1 Port: 5061 Protocol: TLS
Entity Link
Sip Entity: SessionManager Port: 5061 Protocol: TLS
CM2 Port: 5061 Protocol: TLS
125
Time Ranges
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

Routing Policy Time of day and Sip Entity

Session Manager
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 each administered routing policy.

Exercise 6: Define a Time Range
Define a Time Range that accepts calls Monday through Friday, 9 am to 5 pm.
Special Note: There is a 24/7 Time Range by default so it does not need to be created.
130
Routing Policies
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
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 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.
Exercise 7: Define Routing Policies

Define a Routing Policy to route calls to the Communication Managers Create two new Routing Policies. One for CM1 and 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
CM1: 135.122.80.142
CM2: 135.122.80.62
136
Dial Patterns
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
2. Time Ranges
3. Dial Patterns
4. Expressions

Dial Pattern
Who? How do I Route extension 92001? Where?
Session Manager
SIP Entity: MySessionManager

INVITE
192.168.0.210:3002
135.122.80.142
135.122.80.62
CM station: 81001
CM Station 92001
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
Extension starts with 81..
and has a minimum of 5 digits and a maximum of 5 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 as compared to +1xxx555.
Dial Pattern
Route To this endpoint Defined in Routing Policy
and the source has an IP defined in this Location
.and uses this Routing Policy

Dial Patterns

Exercise 8: Define Dial Pattern

Define Dial Patterns to route calls between CM1 and CM2
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.
144
Make 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 to CM From IP Softphone 8100x, dial 9200x From IP Softphone 9200x, dial 8100x

135.122.80.142

135.122.80.62
146
Outcome of call
Satisfied?
Did the call connect? If it did, how do we know the path?

Tracing Calls
Call Flow Review

Session Manager
Dialed number is 9200x. Session Manager uses Routing Policy for CM2 to route call
SIP
SIP
H.323
H.323
H.323 station - 8100X

H.323 station - 9200X

SIP Tracing
traceSM
Custom tool that allows us to trace SIP Requests &
Responses in and out of the Session Manager. This tool enables us to more easily diagnose problems.

Accessing the Session Manager Host

Enter your Session Manager Management 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 traceSM Kill -9 (2nd #)
TraceSM is delivered under /opt/Avaya/contrib/bin

153
Sip Tracing
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
-u 1901 no ns nr > The above will show only messages to/from 1901 and hide OPTIONS, SUBSCRIBES and
You can apply multple filters:
REGISTERS

Dont Forget Another Option: Trace Viewer

Call Flow Review for Next Routing Scenario
135.122.80.58
Student01
1135.122.81.58 SM100
Ext: 1xxx
135.122.80.88 135.122.80.178
Student02
135.122.81.88/SM100 135.122.81.178/SM100
Ext: 2xxx
Student04
135.122.80.158
Ext: 4xxx
Student03
135.122.81.158
Ext: 3xxx
Prep for Next Call Routing Scenario: Sip-toSip Calling between different ASMs
Once all of the elements have been configured each Session Manager within a lab will be able to route sip calls to each other. What elements need to be configured in order for calls to get Routed successfully? 1. ? 2. ? 3. ? 4. ?

Exercise 11 : Define Other ASMs as Sip Entities

To support our second scenario, we need to define a SIP Entity for each of the Session Managers.
Define a SIP Entity for your partners Session Manager naming them ASM1, 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
158
Exercise 12: Define Other ASM Entity Links

Entity Link
Define an Entity Link between your Session Manager and each of your partners Session Managers. This will allow the Session Managers to be able to route calls to each other using NRP.
159
Exercise 13: Define Routing Policies to ASMs

Define a Routing Policy to route calls to each the other Session Managers Create four new Routing Policies. Select your partners Sip Entity. Notice the 24/7 Time Range defaults There are no Dial Pattern or Regular Expression yet, so leave it empty Commit
CM1: 135.122.106.x
135.122.81.xx
160
Exercise 14 : Define Dial Pattern to ASMs

Define Dial Patterns to route calls between ASM1 and ASM2, ASM3 and ASM4 etc.
ASM1 Dial Pattern: 19 Min: 4 Max: 4 Domain: -ALLASM2 Dial Pattern: 29 Min: 4 Max: 4 Domain: -ALLASM3 Dial Pattern: 39 Min: 4 Max: 4 Domain: -ALLASM4 Dial Pattern: 49 Min: 4 Max: 4 Domain: -ALLClick 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?
161
Lets create our users for testing!
Create New User for SIP Registration

Create new user SIP Handle tells Session Manager the registration details Username: 5001 Password: *****
???
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: x901 User Management >> Manage Users >> New
On the Identity Tab: Add First/Last Name: Anything Login Name: email address format i.e. jennifer@avaya.com 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 = 1901@training.com Student02 = 2901@training.com Student03 = 3901@training.com Student04 = 4901@training.com Assign the user to: Primary Session Manager of MySessionManager
Assign classroom Location under Session Manager Profile Commit

2007 Avaya Inc. All rights reserved. Avaya Proprietary & Confidential. Under NDA 171
The next exercise will show you how to configure 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
172
Exercise 16 cont: Configure SIP Emulator

Open the SIP Emulators Folder on the Desktop 1. Navigate to View >> Admin Options
2. Select SIG Menu

3. Select the SIP Protocol: hit right arrow until SIP is selected and Save
173
Exercise 16 cont: Configure SIP Emulator

4. Arrow down to SIP Menu
5. Go to SIP Global Settings:

SIP Mode: Proxied Domain: training.com 6. Arrow down to SIP Proxy Settings: SIP Proxy Server: 135.122.81.xx Transport Type: TLS SIP Port: 5061
Exercise 17: Register SIP Phone

Register x901 using the SIP Phone Emulator
Extensions Student01 Student02 Student03 Student04 => => => => User / Password 1901 / 123456 2901 / 123456 3901 / 123456 4901 / 123456
Disregard PPM download error for now and Enter OK.
Avaya Proprietary & Confidential. Under NDA
175
Make a Call
Scenario 2 Sip-to-Sip Routing

Session Manager
1. Routing applied for dial pattern 29
Session Manager
1. Routing pattern matched for registered user 2901
sm2
sm1
Digits Dialed: 2901
Ext/Password Student 1 => 1901/123456 Student 2 => 2901/123456 Student 3 => 3901/123456 Student 4=> 4901/123456
Registered SIP User 1901


Exercise 18: Place calls

This exercise will demonstrate sip-to-sip routing by Session Manager using Routing Policies From Sip Ext. 1901, dial Ext. 2901 and vise versa. From Sip Ext. 3901, dial Ext. 4901 and vise versa.
135.122.81.x
135.122.81.x
Sip station x901
User/Password User/Password Student01 => 1901/123456 Student02 => 2901/123456 Student03 => 3901/123456 Student04 => 4901 /123456
Sip station x901
178
Regular Expressions
Regular Expressions
Regular Express enables use of: 1. Alpha-numeric characters 2. 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 (for example, name@company.de) to a Frankfurt Gateway.
Regular Expressions
Used in place of a Dial Pattern
sip:12[5-9]{2}@sales\.net
Associates this Regular Expression to an existing Routing Policy

Session Manager to Session Manager Calls SIP to SIP with Adaptations

Call Routing Scenario 3
Sip-to-Sip Calling between ASMs and Adaptation
Signalling path
Branch Office
Branch Office
Branch Office

Scenario 3 Sip-to-Sip Routing

Session Manager
1. Routing applied for pattern *9 2. Adaptation applied to remove *9 sm1
Session Manager
No Adaptation needed 1. Routing pattern matched for registered user 2901
sm2
Dials: *92901
Ext/Password Student 1 => 1901/123456 Student 2 => 2901/123456 Student 3 => 3901/123456 Student 4=> 4901/123456


Create an Adaptation
Adaptability
What can be modified?

Dialled Number Format SIP Message Format

Number Adaptation
Must go to
02920817500
I expect format +442920817500
I expect format 011442920817500
02920817500

Number Adaptation
Must go to
+442920817500
I expect format +442920817500
Needs adapting
+442920817500 02920817500

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

Adaptations

Application of Adaptations
Adaptation is created and applied to a SIP Entity.
When a call is sent to that SIP Entity from Session Manager: When an incoming call from that SIP Entity is 1. Digit Conversions for received:
Incoming Calls to SM applied 2. Routing Policy applied 1. 2. Routing Policy applied Digit Conversion for Outgoing Calls from SM

Adaptations
Could be: DigitConversionAdapter VerizonAdapter AttAdapter CiscoAdapter CS1000Adapter OrangeAdapter

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.
193
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.
Session Manager
1. Routing applied for pattern *9 2. Adaptation applied to remove *9 sm1
Session Manager
No Adaptation needed 1. Routing pattern matched for registered user 2901
sm2
Dials: *92901
Applying Adaptations
Once the Adaptation is created, it can be applied to far end SIP Entities. Adaptations CANNOT be applied to SIP Entities defined as type Session Manager.

Exercise 20: Place a Call That routes through two Session Managers 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 prior to 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 partners Session Manager? Know how to communicate with your partners Session Manager? Have a way to route the request to your partners Session Manager? Know what dial plan to match to route to your partners Session Manager?
Test using the SIP Phone Emulator (see following slides 106- 109) to configure and log in if you havent done so already)
Register as your x901 User
Use traceSM to trace the call.
196
Exercise 20 cont.: Summary of Configuration Required

1. Sip Entity for Partners Session Manager (type- Other) 2. Sip Entity Link for Partners Session Manager 3. Apply adaptation to Sip Entity 4. Create Routing Policy to Partners Session Manager 5. Create Dial Pattern 6. Assign Routing Policy to Dial Pattern
197
traceSM What to look for
Request URI is changed, no *9.
To: remains unchanged.
Matches Dial Pattern *9 and finds Routing Policy.
198
Call 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 Test

Use the Call Routing Test Tool and place the same call as Scenario 2
204
Session Manager Calls H323 to SIP

Call RoutingScenario 4
Session Manager & Communication Manager
SM SIP Entity
SIP
H.323
Scenario 4 Place a call from an IP Phone to SIP User

SIP SIP
135.122.80.142 training.com
SIP H.323
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 Calls SIP to H323

Call Scenario 5
Scenario 4a Place a call from a SIP Phone to IP Phone

SIP SIP
SIP sip:x901@training.com
H.323
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 23: Placing a call between SIP User to IP Phone
SM SIP Entity
Student01 => 1901@training.com Student02 => 2901@training.com Student03 => 3901@training.com Student04 => 4901@training.com
211
Scenario 5b Place a call from a SIP Phone to IP Phone

SIP SIP
SM SIP Entity
SIP sip:x999@abc.com
H.323
What additional configuration do we need to make to place this call? -Assume the SIP Domain (abc.com) 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? Yes, it has been created for you.
Exercise 24: Create System Manager User add Communication Profile

Create New User Profile: x999 User Management >> Manage Users >> New
On the Identity Tab: Add First/Last Name: Anything Login Name: email address format i.e. jennifer@training.com 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 abc.com Select Add Use the following as the User Name: Student01 = 1999@abc.com Student02 = 2999@abc.com Student03 = 3999@abc.com Student04 = 4999@abc.com
Assign the user to: Primary Session Manager of MySessionManager
Assign classroom Location under Session Manager Profile Commit

2007 Avaya Inc. All rights reserved. Avaya Proprietary & Confidential. Under NDA 213
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 is highlighted 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 is highlighted and press Enter Click existing SIP Proxy Change SIP Port = 5062 Click Save, Back, Back, Exit
214
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 Test Was it successful?
User/Password User/Password Student01 => 1999/123456 dials.....81001/123456 Student02 => 2999/123456dials......81002/123456 Student03 => 3999/123456 ..dials......81003/123456 Student04 => 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 Example: ModuleName: DigitConversionAdapter Module Parameter: odstd=training.com osrcd=training.com 2011. All rights reserved.
Change Domain of Source
DigitConversionAdapter overrideDestinationDomain = training.com overrideSourceDomain=training.com (can also use: odstd=training.com osrcd=training.com)

Result of Domain Change

odstd=training.com
osrcd=training.com

Exercise 27: Define an Adaptation to change the Source and Destination SIP Domain from abc.com to training.com Create a new Adaptation called ChangeDomain using the DigitConversionAdapter 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
220
Alternate Routing Policy
Alternate Routing Failover

Where is Routing Ranking Set ?

in the Routing Policy

Exercise 28: Alternate Routing Failover

Lets setup a new SIP Entity. For the purpose of this exercise, it is a dummy SIP Entity that is not monitored by Session Manager. Lets modify the Dial Pattern 8 so that it attempts to route to our fake entity first, then to CM1 if the fake entity isnt available. Begin by creating a SIP Entity
Name: FakeEntity IP:135.122.80.99 Type: Other Location: Classroom Time Zone: America/Denver SIP Link Monitoring: Link Monitoring Disabled
224
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.
225
Exercise 28 cont.: Alternate Routing Failover

Modify the Routing Policy for CM1. Change the Ranking to 10 for 24/7.
226
Modify the Dial Pattern for 8. Add another Originating Locations and Routing Policies for the classroom Location that uses the Routing Policy for the FakeEntity.
Exercise 28 cont. : Alternate Routing Failover
227
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 is unresponsive, next Policy according to Ranking Inc. All rights reserved. is attempted. 2007 Avaya
228
Alternate Routing Time of Day

How does Session Manager know what time or day it is for a specific destination.?

Exercise 29: Alternate Routing Time of Day

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.
231
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 Routing
Policies for the classroom Location that uses the Routing Policy for the FakeEntity.
removing 24/7 and adding Weekend
232

Modify the Dial Pattern for 9. Add another Originating Locations and Routing
Policies for the classroom Location that uses the Routing Policy for the FakeEntity.
233

Use the Call Routing Test Tool to see which Policy is selected.
234
Local Host Name Resolution

A host table internal for Session Manager that resolves a host name to a specific IP address.
If unchecked, Session Manager uses a local table to resolve. If checked, Session Manager will use DNS to resolve the FQDN.



Exercise 30: Modify SIP Entity for Local Host Name Resolution
Modify the SIP Entity for your Partners Session Manager to a FQDN (train2.com) Add an entry in the Local Host Name Resolution to resolve the FQDN to an IP Address Place a call to that destination
239
Entity Link Monitoring
System Health
Monitoring health Regular health checks Modifying circumstances for improved 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
To enable or disable monitoring of the SIP Entities by this Session Manage 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 or inactive The number of times Session Manager tries to reach the SIP Entity before marking it as down or unavailable

Monitoring Health of SIP Entities

Controlling monitoring of individual SIP Entities.
Link Monitoring Enabled overrides Session Manager Instance properties, as long as monitoring is enabled on the Session Manager Instance.

Take a Break
Optional Workshop
You have completed the following Objectives - Module 2

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
Avaya Aura Session Manager CM and other Feature Server Administration
Overview of Applications
Session Manager and Sequenced & Named Applications
Objectives - Module 3
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
Adding CM as a Managed Element System Manager Application Configuration Applying Application Sequences to Users
Sequenced Application with Non-CM Feature Server Implicit Users and Sequenced Applications Named Applications
Sequenced and Named Applications



Sequenced Applications
Feature Servers
Benefit of Application Sequencing

Session Manager watches over Registered SIP Users and all of their calls, both incoming and outgoing, ready to take any special action when the occasion requires.

CM as a Feature Server
CM has thousands of features. Since the CM has knowledge of the user, the Session Manager does not have to address each feature. It simply sends the request to CM and CM will apply the appropriate features based on the user and whether they are the caller or the callee.

How CM Features are Applied

Session Manager retrieves callers User Profile Retrieves callers Originating Application Sequence
Originating Application Sequence
An ordered list of applications to be applied to outbound calls made by the caller
Caller Who is the caller? Do I know him?
Callee
IMS: Half-Call Model

Session Manager retrieves callers UserProfile Retrieves callers Originating Application Sequence
Session Manager retrieves callees UserProfile Retrieves callees Terminating Application Sequence
An ordered list of applications to be applied to outbound calls made by the caller
An ordered list of applications to be applied to inbound calls made by the callee

Terminating Application Sequence
Originating Application Sequence
Caller
Who is the callee? Do I know him?
Callee
Originating Terminating IMS: Half-Call Model

CM Relationships to ASM
1. Sip Entity 2. Managed Element 3. Application 4. Added to Application Sequence
Adding a Communication Manager as a Managed Element
Communication System Manager

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


The Communication System Manager interface can be used to synchronize 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 a CM 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
267
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

Making Changes to Data

Scheduling CM Data Synchronization

Manual CM Data Synchronization

When you modify CM data in System Manager, it is automatically replicated to CM when you commit. If you make changes to CM data outside of System Manager, the data is not replicated to System Manager until a scheduled incremental synchronization.

Exercise: View Synchronization Status

Navigate to Inventory >> Synchronization >> Communication System

Configuring and Applying Application Sequences
Defining Applications

Define the Application for CM
SIP Entity
Managed Element (CM)

SIP Entity
Tell Session Manager about the Feature Server box (CM) (was previously done)
Its address, type, location, etc
SIP Entity
Create Entity Link
SIP Entity

Managed Element - CM

Define the Application Sequence For CM
Sequence 1
Sequence/Template 1
Click

Exercise 2: Create Application and a Application Sequence
Create a new Application called CM1: SIP Entity = CM1 CM System for SIP Entity = CM_ES1
Create new Application Sequence using the new Application CM1
281
Applying Application Sequences to Users

System Manager
Adding User Profiles
Walk Through Exercise User Profile

Walk Though Continued - Communication Profile
Communication Address = Avaya SIP Username= x101@training.com

Walk Though Continued - Communication Profile
Select Primary Session Manager Select a Home Location
Check the box for Endpoint Profile. System = CM1 Check Use Existing Enpoints Select your x101 station Let everything else default expect 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
EC500 Call-fwd Send-Calls
Communication Profile Tab:
Enter 123456 as the Communication Profile Password Create a new Communication Address using the domain training.com Use the following as the Communication Address:
Student01 = 1101@training.com Student02 = 2101@training.com Student03 = 3101@training.com Student04 = 4101@training.com Assign the user to the Primary Session Manager of
Ext: x101
MySessionManager and the Home Location classroom under Session Manager Profile. Assign the user to an Endpoint Profile. Select the CM and check use existing endpoint. Select your station from the list, or type it. Let everything else default except the Security Code. Enter 123456.
2007 Avaya Inc. All rights reserved. 2007 Avaya Inc. All rights reserved.
Save the new user

Avaya Proprietary & Confidential. Under NDA 287
Exercise 4: Create User Profile for x102

EC500
Ext: x102
MySessionManager and the Home Location classroom under Session Manager Profile. Assign the user to an Endpoint Profile. Select the CM and check use existing endpoint. Select your station from the list, or type it. Let everything else default except the Security Code. Enter 123456. Save the new user
Exercise 5: Create User Profile for x103

Brdg-Appr
Ext: x103
MySessionManager and the Home Location classroom under Session Manager Profile. Assign the user to an Endpoint Profile. Select the CM and check use existing endpoint. Select your station from the list, or type it. Let everything else default except the Security Code. Enter 123456. Save the new user
System Manager Users
Edit System Manager User to apply Application Sequence to Users Communication Profile

Exercise 3: Assign Application Sequence to a User

Access System Manager and navigation to User Management >> Manager User and edit user x101 On the Communication Profile Tab, scroll down and expand Session Manager Profile. Select the CM1 Application Sequence you created for both Origination Application Sequence and Termination Application Sequence for this user and Commit.
292
System Manager Users linked to CM Endpoint

System Manager
Ownership of Station
SM100
PPM Owner PPM Broker

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 Profile Editor to apply Application Sequence Update User x102 and x103
Navigate in System Manager to Session Manager >> Communication Profile Editor Select the two following users: 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 Termination Application Sequence under New Communication Profile Values and click Commit. When the confirmation page is displayed, verify you selected the correct users and click Commit.
297
Exercise: Update User x102 and x103 using the Bulk Communication Profile Editor to apply Application Sequence to x102 and x103 Users
Navigate in System Manager to Session Manager >> Communication Profile Editor Select the two following users: 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 Application Sequence under New Communication Profile Values and click Commit.
When the confirmation page is displayed, verify you selected the correct users and click Commit.
298
Configure SIP Phone Emulator

Before you can register your new user, you must configure the SIP Phone Emulator This may already be configured if you used it in a previous course.

Verify or Configure SIP Phone Emulator
135.122.80.x
Provide the Security Module IP Address
135.122.81.x


Avaya Session Manager Part 1

Uploaded by

Document Information

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

Avaya Session Manager Part 1

Uploaded by

Copyright:

Available Formats

Avaya Aura Session Manager Administration

5U00081V Version 6.1

5U00080V ATC01290WEN ATU00171OEN ATU00170OEN ATA02446OEN

Course Length = 24 Hours

vILT = 4 Days @ 6 hours

2011. All rights reserved.

Agenda Live Instructor & Virtual Led Virtual Training

Module 5: Troubleshooting System and Session Manager- 6 Hours

2011. All rights reserved.

Course Objectives Module 1

2011. All rights reserved.

Course Objectives Module 2

Make and Trace Calls Alternate Routing

Alternate Policy Time of Day

Local Host Name Resolution System Health Call Route Testing

Course Objectives Module 3

2011. All rights reserved.

Course Objectives Module 4

Adding a Communication Manager Troubleshooting

2011. All rights reserved.

Course Objectives Module 5

2011. All rights reserved.

Toolwire Student Information

eth0:135.122.80.58 Security Module: 135.122.81.58

eth0:135.122.80.88 Security Module: 135.122.81.88 135.122.80.62

eth0:135.122.80.158 Security Module: 135.122.81.158

eth0:135.122.80.178 Security Module: 135.122.81.178

2011. All rights reserved.

2007 Avaya Inc. All rights reserved.

Avaya Aura Session Manager Instance Configuration

2011. All rights reserved.

Access System Manager

System Manager Administration

2011. All rights reserved.

Exercise 1: Access servers

2007 Avaya Inc. All rights reserved.

Is this a SIP Domain Im suppose to process?

2011. All rights reserved.

2011. All rights reserved.

Only Domains of type SIP can be used for routing

2011. All rights reserved.

Exercise 2: Define a Domain

2007 Avaya Inc. All rights reserved.

2011. All rights reserved.

2011. All rights reserved.

2011. All rights reserved.

Examples of IP Address Patterns:

2011. All rights reserved.

Exercise: Create a Location

2007 Avaya Inc. All rights reserved.

asm2 135.122.80.225 5060 TCP/UDP 5061 TLS

2011. All rights reserved.

2011. All rights reserved.

2011. All rights reserved.

Sip Entity Session Manager

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

2011. All rights reserved.

2011. All rights reserved.

Exercise 4: Session Manager SIP Entity

Define your Session Manager as a SIP Entity

2007 Avaya Inc. All rights reserved.

Session Manager Instance

Session Manager Instance

2011. All rights reserved.