Avaya Session Manager Part 2

Exercise 7: Verify or Configure SIP Phone
Open the SIP Phone Emulators on the XP Desktop Navigate to View >> Admin Options Use your down or up Arrow Key until SIP is highlighted and press Enter SIP Global Settings is highlighted, press Enter Enter or Verify: SIP Mode = Proxied SIP Domain = training.com Click Save, or Back if no changes made Select SIG = Sip
Use your down or up Arrow Key until SIP Proxy Settings is highlighted and press Enter Click New (or Select if already created) SIP Proxy Server = Enter or verify your assigned Session Manager Security Module IP Transport Type = TLS SIP Port = 5061 Click Save, Back, Back, Exit to save any changes, otherwise, Click Back (or Cancel), Back, Back, Exit
Avaya Proprietary & Confidential. Under NDA
2007 Avaya Inc. All rights reserved.
301
Exercise 8: Register SIP Phone x101
Extensions Student01 Student02 Student03 Student04 => => => =>
User / Password 1101 / 123456 2101 / 123456 3101 / 123456 4101 / 123456
302
Exercise 9: Register 2nd SIP Phone x102

Open SIP Phone Emulator 2 under the SIP Phone Emulator Folder
User / Password 1102 / 123456 2102 / 123456 3102 / 123456 4102 / 123456
303
Exercise 10: Place a Call

Observe the Features available on the SIP Phone Make sure your traceSM is running and clear the screen.
Access Session Manager as cust/cust01 and execute traceSM x (see next two slides for details)
Have x101 dial x102

What did you observe when you selected the line to dial? Did the call complete? What was the SIP Path in traceSM? Did new headers get added to the request? What are they?
304
Exercise 11: Place a Restricted Call

Make sure your traceSM is running and clear the screen. In System Manager >> Communication Manager >> Endpoints >> Manage Endpoints, access x102 and change the Class of Restriction to 2 on the General Tab. Run Incremental Sync From x102, dial x101
What was the SIP Path in traceSM? What was the reason the call did not complete?
305
Accessing the Session Manager Host

Enter your Session Manager Management IP Address 135.122.80.x
Login as cust/cust01
2011. All rights reserved.

SIP Tracing
traceSM
Type traceSM -h at the command line to get help with the
different arguments that the script supports.

Half Call Model Route Headers
Route: SecurityModule@135.122.81.xx Route:SessionManager@135.122.80.xx
Need to have CM process Origination logic. How to I override the requestURI?

Route: CM@135.122.80.142 Route: SecurityModule@135.122.81.xx Route:SessionManager@135.122.80.xx
Route:SessionManager@135.122.80.xx
Security Module
No More Route Headers Route: SecurityModule@135.122.81.xx Route: CM@135.122.80.142 Route: SecurityModule@135.122.81.xx Route:SessionManager@135.122.80.xx
RequestURI:callee@training.com

Sequenced Applications and Communication Manager

Communication Manager
CM different modes
CM-Evolution Server Access Point Acts as Access Point SIP Entity for H.323, DCP & Analog endpoints Supports SIP endpoints Supports all CM Trunk Types Limited Application Sequencing Full Call model
OR
CM-Feature Server IMS type feature server Half Call Model Application Sequencing Only SIP Endpoint Signaling Supported

CM-ES & CM-FS as feature server Difference?

CM-FS: Half Call Model
CM-ES: Full Call Model

CM as Feature Server (CM-FS)
CM is connected to the SM via a SIP-ISC interface. Half call model is required.

SIP-ISC
CM only supports SIP endpoints. Calls are always routed via the SM.
Avaya Aura
SIP
SIP
2011. All rights reserved. 31 2
CM as Evolution Server (CM-ES)
Avaya Aura
CM is connected to the SM via a SIP-ISC interface. Full call model is required.

SIP-A analog SIP-ISC SIP-B
H323
AES
ISDN trunk
SIP endpoints can communicate with all other endpoints. Calls from/to SIP endpoints are routed via the SM.
DCP
PSTN
Comparing CM-ES with Classic-CM, Classic-CM integrates with Session Manager using the traditional SIP trunk interface, CM-ES allows the traditional SIP trunk as well as the SIP-ISC interface. Classic-CM supports SIP endpoints using SES, while CM-ES supports SIP endpoints using SM.
31 3
Half Call Principle CM-FS

SIP- A User
Dialing Analysis Origination Processing Line Reservation 183 REINVITE (imsorig) INVITE (origdone) INVITE off-hook (imsorig) INVITE (termdone) Termination Processing
SIP- B User
Dialing Analysis Origination Processing
Termination Processing
INVITE (imsterm)
SIP-B SIP-A
CM-FS is processing half call using two call records All rights reserved. 2011.
Phase mode?
Ill tell him I might want to do different things depending on what phase we are in. How do I know?
Caller
Originating
Outgoing Calls
Terminating
Incoming Calls
Callee

Example of Phase Tags Options

Destination: user in the Request URI Originator: user in P-Asserted ID header Phase tags are added into the route header.

imsorig: added by Session Manager to request origination side processing origdone: added by URE to its own route header to indicate Origination side processing done imsterm: added by Session Manager to request termination side processing termdone: added by URE to its own route header to indicate Termination side processing done
INVITE sip:callee@avaya.com SIP/2.0 To: Bill<sip:bill@work.com> From: John<sip:john@home.com> Call-ID: 267343@135.122.8.2 P-Asserted ID: caller@callersdomain.com
Route: appuri;lr;phase=imsorig Route: asmuri;lr;phase=origdone

Full Call Principle CM-ES

Upon receiving a request that contains an IMS Origination phase tag on a non-IMS signaling trunk, CM-ES will suppress the half-call model processing. It will perform the originating and terminating side processing (the traditional call model) before forwarding the request back to Session Manager.

Full Call Principle CM-ES

SIP- A User
Dialing Analysis Origination Processing Line Reservation 183 ReINVITE (imsorig) INVITE (imsterm) shortcut Termination Processing
SIP- B User
Dialing Analysis Origination Processing Shortcut INVITE (termdone)
Termination Processing
INVITE (origdone) shortcut
INVITE off-hook (imsorig)
SIP-B SIP-A
2011. CM-ES is processing full call using one call record All rights reserved.
Shortcut flag

Configuring Communication Manager

Evolution Server
Configuring CM
135.122.80.62
We will be using Private Numbering in Class. Pre-Configured (same for CM-ES and CM-FS)
Node Names: display node-names ip IP Network Region: display ip-network-region 1 Dial Plan Analysis: display dialplan analysis Stations: list stations Uniform DialPlan: display uniform-dialplan 1 AAR Digit Analysis Table: display aar analysis 1 Private Numbering: display private-numbering 1
Needs Configured by Student

Signaling Group Trunk Group Route Pattern

Configuring CM Evolution Server in System Manager

Use the System Manger to view/create/modify Communication Manager
CM_ES2 135.122.80.62

Pre-Configured Node-Names
All Session Managers have been defined as a node name.

* same for CM-ES & CM-FS
Pre-Configured IP Network Region

Pre-Configured Dial Plan Analysis

Pre-Configured Stations
Three 9630SIP Stations defined for each student: Student 1: 1201, 1202, 1203 Student 2: 2201, 2202, 2203 Student 3: 3201, 3202, 3203 Student 4: 4201, 4202, 4203
Pre-Configured Stations
Setting SIP Trunk to aar automatically creates and offpbx station mapping for this SIP station.
Three 9630SIP Stations defined for each student: Student 1: 1201, 1202, 1203 Student 2: 2201, 2202, 2203 Student 3: 3201, 3202, 3203
Student 4: 4201, 4202, 4203
Pre-Configured Off-pbx-telephone

Pre-Configured Uniform Dial Plan

Pre-Configured AAR Analysis Table

Pre-Configured AAR Analysis Table
Use unku for the dialed string for SIP Stations. Student 1: 1 Student 2: 2 Student 3: 3 Student 4: 4

Pre-Configured Private Numbering

To view the Private Numbering, you have to access the Element Cut Through. There is not a page available under Communication Manager.

Pre-Configured Private Numbering

display private-numbering 1
Enter an extension number or pattern for extension numbers Empty Trk Grp field applies to all trunks
Student 1: 1201, 1202, 1203 Student 2: 2201, 2202, 2203 Student 3: 3201, 3202, 3203 Student 4: 4201, 4202, 4203

Signaling Group
The difference between the configuration of CM for CM Evolution server and CM Feature server is:
CM-ES uses Full Call Model CM-FS uses Half Call Model
SIP-ISC
SIP-ISC

Signaling Group Configuration Difference
IMS Enabled: n: uses Full Call Model (CM-ES) y: uses Half Call Model (CM-FS) Peer Detection Enabled: y: Automatic detection of peer server type (default) n: manual setting of peer server type Peer Server: SM: SIP signaling group is connected to a SIP server, that is a Session Manager others: SIP signaling group is connected to a SIP server, that is 2011. All rights reserved. not a Session Manager
Add Signaling Group

Add Signaling Group
Enable Layer 3 Test If no, the links will not be monitored by Communication Manager. This test is required for trunks connected to Session Manager. Maintenance will take the trunks out of service if this test is not enabled.
Add Trunk Group

Add Trunk Group page 1

Add Trunk Group page 2

Add Route Pattern

Add Route Pattern

Exercise 12 Add a Signaling Group between Session Manager and CMES

Access System Manager Communication Manager >> Network >> Signaling Group New
Select CM_ES2
Student 1 = 1 Student 2 = 2 Student 3 = 3 Student 4 = 4 Group Type = SIP IMS Enabled = n Transport Method = tls Peer Detection Enable = y
May change to n, enter SM in Peer Server, then change back to y.
Near-end Node Name = procr Near-end Listen Port = 5061 Far-end Listen Port = 5061 Far-end Node Name = sm<X> Far-end Network Region = 1 Far-end Domain = training.com Enable Layer 3 Test? = y Click Enter to Save
343
Exercise 13 Add a SIP Trunk Group

Access System Manager Communication Manager >> Group >> Trunk Group Delete previous Sip Trunk Group New
Select CM_ESx
Student 1 = 1 Student 2 = 2 Student 3 = 3 Student 4 = 4
Group Type = SIP Group Name = <your name> TAC = *0<X> Service Type = tie Signaling Group = <X> Number of Members = 50 Go to Page 3 Numbering Format = private Click Enter to save
344
Exercise 14 Add a Route Pattern

Access System Manager Communication Manager >> Network >> Route Pattern Delete previous route pattern New
Select CMx
Student 1 = 1 Student 2 = 2 Student 3 = 3 Student 4 = 4
Pattern Name = SIP Group Name = sm<X> GRP No = <X> FRL = 0 Click Enter to save
345
Exercise 15: Test CM Config by Placing a Call

Make sure your traceSM is running and clear the screen.
Access Session Manager as cust/cust01 and execute traceSM x (see next two slides for details)
Have x201 dial x202

Did the call complete? What was the SIP Path in traceSM? Did new headers get added to the request? What are they? Can you see PPM Data?
346
System Manager Application Configuration
Review System Manager Configuration Steps

Now that the CM is configured, lets create the Application Sequence and assign it to our x201, x202 and x203 Users as the Origination and Termination Application Sequence.
Before going to the next slide, discuss the steps required to complete this exercise.
1. 2. 3. 4. 5.
Create a SIP Entity for CM2 Create an Entity Link between MySessionManager and CM2 Create an Application using the SIP Entity CM2 and the Managed Element CM_ES2 Create an Application Sequence that includes the CM2 Application Assign the Application Sequence to the users

SIP Entity
Tell Session Manager about the Feature Server box
Its address, type, location, etc
SIP Entity
Entity Link
SIP Entity

Defining Applications

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

Define the Application Sequence For CM
Sequence 1

System Manager Users
Edit System Manager User to apply Application Sequence to Users Communication Profile
Bulk Communication Profile Editor
Use the Bulk Communication Profile Editor to edit multiple Users Communication Profiles at one time!
Exercise: SIP Entity Definition

Add a new SIP Entity for CM
CM2 135.122.80.62 Type is CM Location is classroom
Add a new Entity Link between the MySessionManager and the new SIP Entity for CM2
Listening port for both Session Manager and CM are TLS 5061

Exercise: Create Application and a Application Sequence

Create a new Application using the CM you just added as a SIP Entity
Create a new Application called CM2: SIP Entity = CM2 CM System for SIP Entity = CM_ES2
Create new Application Sequence using the new Application Create new Application Sequence using the new Application CM2

Exercise: Update User Profiles to apply Application Sequence
Update your System Manager Users to use the new Application Sequence that includes CM2
Users to Modify: Student 1: 1201, 1202, 1203 Student 2: 2201, 2202, 2203 Student 3: 3201, 3202, 3203 Student 4: 4201, 4202, 4203

Exercise: Register SIP Phone

View >>Options >>Logout your other user if you are still registered
User / Password 1201 / 123456 2201 / 123456 3201 / 123456 4201 / 123456

2007 Avaya Inc. All rights reserved. 2007 Avaya Inc. All rights reserved. Avaya Proprietary & Confidential. Under NDA 359
Exercise: Register 2nd SIP Phone

View >>Options >>Logout your other user if you are still registered
User / Password 1202 / 123456 2202 / 123456 3202 / 123456 4202 / 123456

Exercise: Register 3rd SIP Phone

Open SIP Phone Emulator 3 under the SIP Phone Emulator Folder
User / Password 1203 / 123456 2203 / 123456 3203 / 123456 4203 / 123456

Exercise: Place a Call

Make sure your traceSM is running and clear the screen. Have x201 dial x202
What did you observe when you selected the line to dial? Did the call complete? What was the SIP Path in traceSM? Did new headers
get added to the request? What are they?

Exercise: Call Forwarding

Based on what you know complete the following activity.
When station x202 receives a call, it should use the CM call forwarding feature to forward the calls to x203.
You will need to run three emulators to test
On the desktop, open the folder Additional SIP Phone Emulators

Exercise: Bridged Call Appearance
Place a call between x201 and x202 and observe x203 You will need to run three emulators to test

Bridged Call Appearance
Ext: x203
Ext: x201

Bridged Call Appearance
Ext: x203
Ext: x201

Non-CM Feature Server

Application Sequencing
Feature v. Feature Server
App A App B Features / Applications App C App D
Feature Server

Define the Application for Non CM Feature Server
Route: sip:AppD@featureserver

Session Manager and Applications
Q.
How many applications will need to be configured on Session Manager?

Session Manager and Applications

CM-Features
Aura Apps
CM-as-FeatureSer
AuraAppA AuraAppServer
Aura Apps
AuraAppB AuraAppServer AppA CM-Features CM-as-FeatureSer AuraAppA AuraAppServer2 AppB AuraAppB AuraAppServer2 AppC
Aura Apps
Aura Apps
AuraAppC
Aura Apps
AuraAppServer
Aura Apps
AuraAppD AuraAppServer
AppD AppD AppD
A. 8
One for each CM. CM is the app Six for other Feature Servers 4 for 1, 2 for the other
Additional Application Parameters
I need more information
user=phone
Before
After

Running SAMPLE Sequenced Application
Runs on Windows on port 6053

Origination Vs. Termination ?
Application Handle - CSECallBlocker

Need to add handle as Communication Address for user being spoofed.
Application Handle - CSECallSpoofer

Application Handle - CSEsCallForwarder

Configuring the new Feature Server

Create a SIP Entity for the new Feature Server
Runs on each students XP Desktop Type = Other
Disable SIP Link Monitoring
Create an Entity Link between MySessionManager and the new Feature Server
The TCP listening port for the SampleApp is 6053 on each students desktop

Defining the Application

Define an Application for each feature

Create an Application Sequence for Call Blocker

Run the Application Call Blocker
Block x902 from calling x901

Assign the new Application Sequence
Is Call Blocker an Origination or Termination Application?

Exercise 16: Implement Sample Application CSECallBlocker Have x901 block calls from x902 using the SampleApp feature called CSECallBlocker
Define the SIP Entity (use desktop ip) Define the Entity Link (port 6053/TCP) Define the Application Define the Application Sequence Assign the Application Sequence to the User x901 as Termination
382
Viewing Results
383
Multiple Applications in a Sequence
Application Sequences

A Sequence is a template
4201
1001
1002
1003
Group of users
Great flexibility!
Administering an Application Sequence
Sequence 1
Sequence/Template 1
1st
2nd
Click Click

Originating Application Sequence Originating Application Sequence
Is the order of applications important
YES!
Callee
Other applications may modify the request, re-route it or even reject it
Caller
Originating
What combinations provide required outcome?

This one first?
Then this one?
And this one last?

Originating Application Sequence
Where should CM sit in the sequence Depends on what type of CM

- CM-ES (Evolution Server) - CM-FS (Feature Server)
Caller
Callee
Originating
Rules for Application Sequence Placement for CM
CM-ES must be last in the origination sequence, first in the termination sequence.
The CM-FS must be first in the in the origination sequence, and the termination sequence.

Exercise Multiple Applications in a Terminating Sequence

1. When x203 is called by 1901, it should block it using CSECallBlocker Make a new Application Sequence that includes CM2 and CSECallBlocker.
What order should the Applications be placed?
Apply the new Application Sequence to the User x203.
Blocked

Exercise Multiple Applications in an Origination Sequence

2. When x201 calls anyone, it should be spoofed using your name (first
initial, last name. i.e.: llind) Make a new Application called SampleAppSpoofer for CSECallSpooffer
Make a new Application Sequence that includes CM2 and SampleAppSpoofer
- What order should the Applications be placed?
Modify the User x201

- Add a Communication Address = assistant@training.com - Apply the new Application Sequence.

Implicit Users
1st problem?
SM expects SIP
1st solution?
Gateway SIP Entity

2nd problem?
SM checks User Profile for Sequences. Non-SIP endpoints dont have a User Profile
Administrator
SIP Entity
Caller 2 Non - SIP Caller 1 - SIP
1st problem?
SM expects SIP
1st solution?
Gateway SIP Entity

2nd problem?
SM checks User Profile for Sequences. Non-SIP endpoints dont have a User Profile
2st solution?
Implicit Users
SIP Entity
Caller 2 Non - SIP

42 4 4
Any 4 digit number beginning with 42
Sequence 1 Sequence 3
Originating
Outgoing Calls
Terminating
Incoming Calls

Access the Non-SIP 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

Exercise 17: Implicit User
Have x901 dial the H323 phone 8100x. Once the call completes, add a rule using Implicit Users to block x901 from calling 8100x.
399
Named Applications
Named Apps & Sequenced Apps
The difference?
Callee I will do something to trigger the feature
Something in this request tells me to route it to a named app feature server
Dial a special access number Caller Issue a request with special details in URI,
Named Applications
Named Application
Think of a really clever phone Must dial a specific number to get to phone Caller has no control over what user at phone does with call User can push buttons on phone to effect handling of call
Reject Forward to Voice Mail or to
App
another phone
Conference in another party
These are characteristics of a named app!
Named Applications
Named Application Routing

Named Applications are NOT sequenced Two possible ways to route to Named Application:
Routing Policy
NRP
Register Application as System Manager User
SIP Location

Creating Network Routing Policies
An administrator

SIP Location
No different for an Application. Registration for a User associated to an Application!
OR
NRP
App App
I want to call 4201
App
Application Registers as 4201
Session Manager checks for User Profile If profile exists, checks registry for registration If registered get destination location from registry and proxy on
Ext 1001
LOCATION
You have completed the following 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
System Manager Application Configuration Applying Application Sequences to Users
Sequenced Application with Non-CM Feature Server Implicit Users and Sequenced Applications Named Applications
Avaya Aura Session Manager User Administration
Objectives - Module 4
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

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
Dial Plan
135.122.80.58
Student01
135.122.81.58
Ext: 1xxx
135.122.80.178
135.122.80.88
Student04
135.122.81.178
Session Manager
135.122.81.88
Student02
Ext: 2xxx
Ext: 4xxx
135.122.80.158
Student03
135.122.81.158
Ext: 3xxx
Ext: 1xxx
135.122.80.58
Since number dialled starts with a 4, route to SM 4
400x
135.122.81.58
Dial Plan
NRP Preconfigured SIP Entity SIP Location SIP Domain Entity Links
135.122.80.178
Route locally
135.122.81.178
Ext: 4xxx
Dial Plan
Registration & Location

Session Manager and SIP Registration & Location
REGISTRATION
Q. What determines if SM will use NRP or SIP Location?
Session Manager checks for User Profile If profile exists, checks registry for registration If registered get destination location from registry and proxy on
LOCATION reject the call, or other call processing if defined Else
https
dsheppard 4021 ****
User Name: dsheppard Handle (ext): 4201 Password: ****
Administrator
User Profile
System Manager User Profile Communication Profile
Create New User for SIP Registration

Create new user (not an admin user!) SIP Handle tells Session Manager the registration details Username: 5001 Password: *****
???
REGISTER

Creating User Profiles - Review



User Profile The Communication Profile

Creating User Profiles

System Manager Users and Redundancy

Creating User Profiles
Once happy, select Commit

Exercise 1: Create New System Manager User add User Identity and Communication Profile
Access System Manager User Profile: x902
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 Use the following as the User Name:
Student01 = 1902@training.com Student02 = 2902@training.com Student03 = 3902@training.com Student04 = 4902@training.com Assign the user to the a Primary Session Manager of
MySessionManager and the Home Location classroom under Session Manager Profile
2007 Avaya Inc. All rights reserved. Avaya Proprietary & Confidential. Under NDA 425
Commit
Exercise 2: Create New System Manager User add User Identity and Communication Profile
Access System Manager User Profile: x903
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 Use the following as the User Name:
Student01 = 1903@training.com Student02 = 2903@training.com Student03 = 3903@training.com Student04 = 4903@training.com Assign the user to the a Primary Session Manager of
MySessionManager and the Home Location classroom under Session Manager Profile
Commit
426
Register System Manager SIP User
Configure SPARC Emulator

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

Configure SIP Phone Emulator
135.122.80.xx
Provide the Security Module IP Address
135.122.81.xx

Exercise 3: Prepare SIP Phone

Open the SIP Emulator Folder on the Desktop Double Click SIP Phone Emulator 1 Navigate to View >> Admin Options 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 = training.com Click Save Arrow up to SIG and select SIP Use your down or up Arrow Key until SIP Proxy Settings is highlighted and press Enter Click New SIP Proxy Server = Enter your assigned Session Manager Security Module IP Transport Type = TLS SIP Port = 5061 Click Save, Back, Back, Exit
2007 Avaya Inc. All rights reserved. Avaya Proprietary & Confidential. Under NDA 430
Exercise 4: Register SIP Phone
User / Password 1902 / 123456 2902 / 123456 3902 / 123456 4902 / 123456
431
Exercise 5: Register 2nd SIP Phone - Open the SIP Emulator Folder on the Desktop
- Double Click SIP Phone Emulator 2
User / Password 1903 / 123456 2903 / 123456 3903 / 123456 4903 / 123456
432
Analysing the Registration
Username: 5001 Password: *****
REGISTER

SIP Tracer Configuration
Enabled by Default to Trace All Messages
Select your Session Manager Instance, and click Read to see the current configuration. Make changes and click Commit to save.

Exercise 6 Enable SIP Trace Viewer

Navigate from the System Manager Home Page to Session Manager >> System Tools >> SIP Tracer Configuration
At the bottom, select MySessionManager then click the Read Button
Commit
435
Viewing the SIP Trace

Viewing the SIP Trace - Filter
Enter the time range and select your time zone. This is relative to the system date and time which will vary in the training environment.

Viewing the SIP Trace

Lots and Lots of Messages enable filter of results

View a SIP Message
Request URI: Addressed to SIP Proxy To: Public Address of the User
Contact: IP Address of the User

Sample Registration Trace
REGISTER
401 Unauthorized
REGISTER
200 OK

Exercise 7 View SIP Trace Viewer

Navigate from the System Manager Home Page to Session Manager >> System Tools >> SIP Tracer Viewer View Trace Viewer
Enable the Filter in Results to display Register Select Register in Actions column
441
User Registrations

Alternate Sip Tracing - Analysing the Registration traceSM shows the SIP call flow for the SM Gives insight into SM decisions

Alternate - Accessing the Session Manager Host

Enter your Session Manager Management IP Address 135.122.80.xx
Login as cust/cust01

Alternate - Sip Tracing

traceSM
Run traceSM -h to get the help with the different arguments
that the script supports.

Making a Call
Session Manager & SIP Location
Exercise 8: Making a Call

Run two SIP Emulators: x901 dials x902 Before you place the call, remove any FILTERS for the User on the SIP Tracer Configuration page.
Location or Routing Policy?
447
Sample Successful INVITE Trace
INVITE
INVITE
100 Trying
100 Trying 180 Ringing
180 Ringing
200 OK 200 OK ACK BYE BYE 200 OK 200 OK
ACK

Sample INVITE
Request URI Destination of Call
PAI = P-Asserted Identity. Added my Session Manager and defines the source
Media Offer Session Description Protocol (SDP)

Exercise 9: View Call Trace Use the SIP Trace Viewer to review the INVITE from x901 to X902 Apply a new time filter on the SIP Trace Viewer Page Make sure you removed the User Filter added in the Registration
exercise on the SIP Tracer Configuration Page.
Commit View the results Enable a filter on the results for INVITE
450
Exercise 10: Making a Call

Have x901 dial x904
Did the call complete? Why not? Use the trace tool to help answer.
451
So weve got a call being routed entirely using SIP Registration & Location!
Really?
Multiple Session Managers & SIP Routing

OR OR
NRP NRP
I want to call 4201

Exercise 11 : Team Up and Make a Call Team up with another course participant - Take turns calling each other on your x901 extensions
Location or Routing Policy?
454
Location What does this mean for the user?

Users can use any device Not tied to a specific phone or location Session Manager can orchestrate routing for non-CM, SIP end points

Multiple Addresses for a Single User

Communication Profile
Multiple Communication Addresses
Can log in as either 4001 or 4999 and receive calls for both!

Multiple Communication Profiles
Completely unrelated to Communication Addresses in another Communication Profile
Each Communication Profile has its own Session Manger Profile!

PPM
Personal Profile Manager (PPM)
Different users Different settings

Personal Profile Manager
JBOSS Running on SM
HTTP(S)/SOAP


PPM Requests

Example: getAllEndpointConfiguration Request

Example: getAllEndpointConfiguration Response

Ownership of Station
PPM Owner PPM Broker

Configuration
Must tell Session Manager how to get PPM data from CM

Network
administrator
Range of stations etc

2011. All rights reserved. Operations Support System Interface
Viewing Communication Manager Data
Communication Manager

View Communication Manager Data

View Communication Manager Endpoints

Ext: x101
EC500 Call-fwd Send-Calls
EC500
Ext: x102
Brdg-Appr
Ext: x103
Exercise 12: View CM Stations
Once the endpoint list is displayed, select your one of your endpoints.
Student01 = 1xxx Student02 = 2xxx Student03 = 3xxx Student04 = 4xxx *Review the station details. Take note of Button Assignments.
Close the endpoint without saving changes.
473
Associating Communication Manager Stations to System Manager Users
User Profiles and existing CM Stations

Walk Through 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 CMx for both Origination and Termination Application Sequences 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
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
Ext: x101
Assign the user to the Primary Session Manager of
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. Avaya Proprietary & Confidential. Under NDA 2007 Avaya Inc. All rights reserved. Save the new user

479
Exercise 13: Create User Profile for x102

EC500
Ext: x102

Student01 = 1102@training.com Student02 = 2102@training.com Student03 = 3102@training.com Student04 = 4102@training.com Assign the user to the Primary Session Manager of
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
480
Exercise 14: Create User Profile for x103

Brdg-Appr
Ext: x103

Student01 = 1103@training.com Student02 = 2103@training.com Student03 = 3103@training.com Student04 = 4103@training.com Assign the user to the Primary Session Manager of
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
481
Exercise 15: Log in using new User Profile View Differences
Access the SIP Phone Emulator folder and run three phones Student01 => 1101/1102 / 1103 Password: 123456
SIP Phone 1
Student02 => 2101/2102 / 2103 Password: 123456 Student03 => 3101/3102/3103 Password: 123456 Student04 => 4101/4102/4103 Password: 123456
log in as x101 Take time to review the SIP Trace Use the right arrow key to view features
Ext: x101
SIP Phone 2
Log on as x102 Use the right arrow key to view features
EC500
Ext: x102
SIP Phone 3
Log on as x103 Use the right arrow key to view features
Brgd-Appr
Ext: x103
2007 Avaya Inc. All rights reserved. 482
Exercise 16: Add Send-Calls Button Assignment

Log Off of station x102. Access the Communication Manager Endpoint profile via System Manager. Edit station x102. Under Button Assignment, select Send-Calls in drop down 6. Leave the extension blank. Save the Station. Log on to station x102 on the SIP Phone. View the phone features.
483
Events & Notifications
???

Troubleshooting
PPM Personal Profile Manager

When a SIP phone registers to Session Manager, it is sent CM data such as button assignments, Dial Plan information, etc.
Activate/Deactivate PPM Logging

enable PPM logging:
sm ppmlogon
To disable PPM logging:

sm ppmlogoff

Verify User Login

To verify a users login and to view the data sent to the phone, log out a registered SIP phone then re-login the same phone.
On the Session Manager that the phone registers to:
vi /var/log/Avaya/jboss/SessionManager/ppm.log
go to bottom and search up for DialPlanData

Exercise 17 Enable PPM.log
Execute: sm ppmlogon Logoff x102 Logon x102 vi /var/log/Avaya/jboss/SessionManager/ppm.log Type /DialPlanData To quit, type :q!
488
You have completed the following Objectives - Module 4

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 Overview Manage Communication Manager Endpoints
Create System Manager SIP User Endpoint Profile
Personal Profile Management Communication Manager
Adding a Communication Manager Troubleshooting


Avaya Aura Session Manager and System Manager Troubleshooting
Lesson Objectives Module 5

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

Section 1: Session Manager Architecture
Section 1- Session Manager Components

Effective troubleshooting of Avaya Aura Session and System Manager really begins with a good understanding of Session Manager :
1. architectural elements 2. clear picture of how the SIP domain functions.

Session Manager
SIP Application Server
SM100 Software
Major Session Manager Components
ServiceDirector ServiceHost0 Management Service
Service Director (SIPasSD) Service Host (SIPas-SH) Management Server (SIPas-MS)

SIP A/S
Session Manager is an application running on a SIP Application Server SIP/AS which consists of the Service Director, the Service Host and the Management Server. The functionality of these three components is essential to the performance of Session Manager.
Lets take a closer look at how SIP messages arrive at Session Manager

SIP messages enter the Session Manager box, through eth2 and are processed directly by the SM100. If all of the security checks pass, then the request continues on to the next Session Manager component, the Service Director.
SM100
Port 3 = Eth2

Service Director (SIPas-sd)

SIP Application Server
SM100 Software
Perform check on SIP header
ServiceDirector ServiceHost0 Management Service
In the Session Manager setup, the Service Director checks the contents of the SIP message headers then forwards the SIP message onto the Service Host which is where most of the call processing takes place.
Verifying Status: SIPas-SD

When troubleshooting Service Director issues first do the following: Verify the SM100 Status is up on the Dashboard Go to Elements > Session Manager > System Tools > Maintenance Tests Select Session Manager from Select Target list. Select the following tests and Execute: Test Service Director status test

If test fails, establish an SSH connection to Session Manager using putty Run statapp to verify status of SIPas-SD

SIPas-SD Down
If the status of SIPas-SD is Down run restart SIPas-SD and give the Service Director time to restart. Reinitiate the statapp command to verify the status of SIPas-SD Re-run the Test Service Director status test If the Service Director remains down after performing the above steps, contact Avaya Technical Support.

Service Host (SIPas-sh)

The Service Host functions as a SIP Server and the Service Host Container is where all of the SIP rules and standards are applied.
Service Host
Container
Timer B
UA
Location Proxy
Auth
Timer F Proxy Location

Service Host
The Service Host is also designed to host the SIP Servlet Archive files which contain the logic defined in the servlet code.
Contains program code

Servlet Archive (SAR)
Servlet executes tasks Passes control back to Service Host container
SIP
Servlet
SIP
Servlet

Service Host
These SARs complete all of the necessary functions such as Call Processing, Network Routing Policy, Registration and many more other services mentioned earlier in the course
Network Routing Individual Routing

Network Routing Individual Routing Registration Event Handling Database Access Data Distribution Name Resolution
Registration Authentication Event Handling Database Access Data Distribution Name Resolution
Authentication
Verify Status: SIPas-SH

If the Service Host is malfunctioning all critical call processing components will be down. How do you verify the status of the Service Host? Go to the System Manager Dashboard and verify the Session Manager Service State is Accept New Services.

Verify Status: SIPas-SH

Verify the SM100 Status is Up on the Dashboard Go to Elements > Session Manager > System Tools > Maintenance Tests
Select Session Manager from Select Target list. Select the following tests and Execute: Test Call Processing status & Test Service Host Status
If both tests fail, establish an SSH connection to Session Manager using putty Run statapp to verify status of SIPas-SH

SIPas-SH Down
If the status of SIPas-SH is Down run restart SIPas-SH and give the Service Host time to restart.
Reinitiate the statapp command to verify the status of SIPas-SH Re-run the Test Call Processing Status and Test Service Host Status tests.
2011. All rights If problem persists a possible re-install of ASM may be required. reserved.
Management Server (SIPas-ms):

The Management Server also provides several very important functions of the SIP Application Server: The SIPas-ms is responsible for configuring the Service Host and Service Director. Pushing the configuration when the SIPAS processes start (SH and SD) At runtime, it also monitors the status of the SD and SH processes.

Session Manager Management (sm-mgmt):

This JBoss service runs when configuration changes are being made to both the ASM parameters and the SM100 security module Facilitates communication to System Manager Same service used to set ASM to Accept New Services or Deny New Services

Verify Status sm-mgmt:

Go to Elements > Session Manager > System Tools > Maintenance Tests Select Session Manager from Select Target list. Select the following tests and Execute: Test Data Distribution and Redundancy Link If test fail, establish an SSH connection to Session Manager using putty Run statapp to verify status of sm-mgmt

Checkpoint
System Manager and Session Manager servers do not need to be started in any specific order for initTM to execute successfully? True or False?

Other Critical Services
Successful Installation
initTM
- initial trust management between both servers - Security certificates exchanged - SMGR can manage ASM
initDRS
- initial load of the ASM database from SMGR - Can configure SM100 - Monitor Health of ASM

Initial Trust Management

During installation InitTM (/opt/Avaya/bin/initTM) is the primary script that runs to establish trust management between System and the SIP A/S. The script automatically runs at the end of the Session Manager or Branch Session Manager installation and does not need to be run again once the trust management is established. It will also automatically run if the ASM ip/fqdn is changed. System Manager must be running during this process as initTM sends a ping request to determine if it is available. If initTM is successful then it will automatically fire up the initDRS script.

Initial Trust Management Issues

initTM is the foundation for: - Establishing communication between SMGR and ASM
- Database replication which enables the SM100 config to
get registered in ASM

- SMGR management of ASM
If initTM fails, ASM will be OUT OF SERVICE!

Database Replication Service

During installation the initDRS (/opt/Avaya/bin/initDRS) is activated once initTM has been established. The master database which is located in System Manager begins to replicate itself to the replica nodes.
Master Database
Replica Database

Replication Updates from the Master DB

The master queries its database for updates every 5 seconds. Changes in the master database is cause a DB trigger to mark the record and store it in the replication_updates table ready to be sent.
Master Database
Updates Query
1. Do I have any new updates? 2. Checks updates table If yes, then sends an update to the replica node.
replication_updates table
SIP user 1901, 1902 Nrp 1 Nrp 2
Yes! Every 5 seconds

Replication Updates
The record is then packetized into JSON format (JavaScript Object Notation) and sent to the replica node using JMS for message transport. The replica node then updates its tables with the new record.
replication_updates table
SIP user 1901, 1902 Nrp 1 Nrp 2
updates
Replica Node

Replica Database Synchronization

Replication audits, which are controlled by the replica nodes, keep the master and replica nodes synchronized. These audits run every 15 minutes. The replica sends a delete and update request to the master. Checks its database against the master every 15 minutes
Every 15 minutes Master Database Replica Database
Replication Audit

SMGR sends info to the replica that it can use to compare its database Once the ASM replica node receives the housekeeping information from the master, it compares its version to the master.
Master Database
Update/Delete Request
Replica Database


If it finds missing records in its copy of the master database, it will request an update from the master and records that dont belong will subsequently get deleted from the replica node.
Master Database
Master 220 SIP users 10 nrp 50 SIP entities
Replica 200 SIP users 8 nrp 45 SIP entities
Replica Database
Database Synchronization
Replica Database
Master Database
Master 220 SIP users 10 nrp 50 SIP entities
Replica 220 SIP users 10 nrp 50 SIP entities

Queuing an Update- Did You Know?

During a network outage System Manager will queue the updates for up to 24 hours. If network connectivity is restored within that time frame then the database will not need repairing but if the outage lasts longer than 24 hours a database repair will be required on the replica.
24 hours!
updates

Exercise: Verify the Database is Running

To ensure the database process is running on Session Manager: Establish an SSH connection to Session Manager Swich user to root Execute the following command: ps ef | grep postgres There should be the following two processes running:
root 8859 20589 0 11:31 pts/3 00:00:00 grep postgres root 19056 18972 0 01:32 ? 00:00:07 /usr/java/jdk1.6.0_11/bin/java -server -XX:NewSize=32m ...

Exercise: Verify the Status of the Database:

Execute the following command: service postgresql status There should be output that matches the following:
postmaster (pid 32617 32570 32569 32568) is running...

Database Repair- Start Database
If there is a connection to the database but the database is down, execute the following command:
start s postgres-db
Replica Database

Non-Intrusive Repair of a Replica Node

A non-intrusive repair to the replica nodes database can be done using the System Manager web console: Replication > Select Replica Group > Select Repair button. All of the Session Manager components (SD, SH and MS) will continue to function while the DRS client wipes out its copy of the database.
Not Service Affecting

Intrusive Database Repair

Running initDRS will reinitialize the DRS replication on the Session Manager side. It will re-register ASM to SMGR and complete an initial load of the master database. This script will cause the Session manager components (SD, SH, MS) to restart and is therefore service-affecting.
Service Affecting!

Facilitated Discussion
Look at synchronised databases on SMGR and SM. What happens if they are not synchronised? What are the symptoms? What could cause the databases to be out of synch? How could one verify that the databases are out-of-synch? What are the steps to correcting the synchronisation issue?

Checkpoint
Database Synchronization is triggered by the:
A. Master Database B. Replica Node C. Postgres script D. Spirit Agent

Checkpoint
The __________ manages call processing for Session Manager.
A. Service Director B. Replica Node C. Servlet D. Service Host

Checkpoint
The __________ performs a non-intrusive Database Repair in Session Manager.
A. postgres_sql.sh B. Repair from SMGR console C. initDRS D. Service Host

Summary
Session Manager consists of a SIP Application Server which hosts the Service Director, Service Host and Management Server and the Session Manager Management. All of these services allow for Session Manager to operate. Critical Services such as Trust Management, Database Replication are also essential to the performance of Session Manager. Understanding how to validate the status of these services is important in validating the status of the system Understanding how the SIP domain is designed is also essential in effectively maintaining and troubleshooting any issue.

Maintenance and Troubleshooting Tools

Status/Real-Time Monitoring, Trace and Maintenance Tools
Maintenance & Troubleshooting Tools

System Manager provides a wide variety of tools for providing visibility, real-time status, trace and monitoring of SIP components essential for troubleshooting Session Manager some of which weve gone over and some that are new. Well take a look at all of the tools and how they can be used to troubleshoot specific issues.

Maintenance and Troubleshooting Tools Overview

Avaya Aura System Manager provides a suite of diagnostic tools for monitoring the Session Manager operation and status System Manager maintenance and troubleshooting tools include:
Real-Time Status and Monitoring tools
Session Manager Dashboard SIP Entity Monitoring SM100 Status Managed Bandwidth Status SIP Application Server Status Statapp

Real-Time Status and Monitoring Tools
Session Manager Dashboard

The Session Manager Dashboard displays:
- The overall status and health summary of each administered Session
Manager
Major, Minor, Warning
SIP Entities down/total #
Managed Session Managers
SM100 Status
Registered SIP endpoints


Login to System Manager web console Navigate to Elements > Session Manager


Access the Session Manager System Status and System Tools

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

SIP Entity Link Monitoring is a real-time maintenance tool that provides automatic background detection for monitored SIP entities Improves alternate routing and minimizes call setup times due to SIP link failures


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


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


Entities are considered DOWN if the response to the OPTIONS request is:
408 Request Timeout 503 Service Unavailable 503 Service Unavailable (LSP is inactive) 503 Service Unavailable - System Busy 504 Server Timeout
Down

SIP Entity Monitoring Status Summary

At the Session Manager Dashboard, navigate to System Status > SIP Entity Monitoring You can click on Run Monitor for on demand monitor testing

You can also click on each SIP Entity to see its current link status and its last response to Session Managers OPTIONS message

SIP Entity Monitoring Things to know

SIP Entity Monitoring can only report problems if the Security Module is functional. SIP Entity Monitoring setup is configured through ASM instance and SIP Entities Screen

SM100 Status
The SM100 Security Module can be checked through the Session Manager Dashboard At the Session Manager Dashboard, navigate to System Status Security Module Status

SM100 Status
Administrators can check the connection status, reset, synchronize, and get details regarding the SM100. Synchronizing the SM100 triggers an update from the replica node and can be used when the replica node is not synchronized to the master node

SM100 Connection Status

Click on the SM100 Connection Status to view basic information for all active connections Clicking the show button will display: link direction, last message received, last message sent, messages/bytes dropped,

SM100 Reset
If DRS is running and the replica node is synchronized but the SM100 is not up, it can be reset from this screen.

Managed Bandwidth Usage

Managed Bandwidth Usage provides bandwidth usage information for SM Locations. Navigate to Session Manager System Status Managed Bandwidth Usage

Managed Bandwidth Usage

SIP/AS Console
The SIP Application Server real-time system status can be monitored using the SIP A/S console

SIP/AS Console
At-a-glance view of Configuration Issues

SIP/AS Console
Select Monitoring > System Status > Statistics Statistics for each SIPas component includes: Ip address, Administrator port, version and current status

SIP/AS Console
To access the SIP/AS console from the SMGR console Select the SIP AS 8.1 Menu

SIP/AS Console
Login using the management ip address (eth0) of your ASM Select the default primary port: 5759 and click Connect
Use ASM Eth0 IP Address NOT SM100

Statapp
This script provides status of the SIP A/S components

Statapp
Watchdog- service does all the work. parent and child. The child monitors the services and does essentially provides all of the functionality. The parent watchd simply monitors the child and restarts it if it halts. Logevent- service logging system events Postgres-db- ASM replica node Sm-mgmt- Service that manages ASM configuration of parameters SIPas-MS- Service that configures SD and SH SIPas-SD- Service that routes messages from SM100 to the SH SIPas-SH- SIP Server and Call Processing SIPas-LH- Service supports retrieval, archival/analysis of SAL-enabled hosts or elements SIPas-CDR- Service recording information on tandem calls Secmod- SM100 Security Asset
Trace Tools
SIP Tracer
SIP Tracer allows for the configuration of SIP message traces:
Incoming through
the security module

Outgoing from the
security module
Messages dropped
by ASSET Proxy or SIP firewall.

SIP Tracer
SIP Tracer Viewer provides the output of the configured traces.

TraceSM
Assists in the isolation, identification, and resolution of SIP-based problems. Collects the logs generated by the SIP A/S components. Both the calls.log and asm.log are merged into this log which is located in the Service Host. TraceSM is located in /opt/Avaya/contrib/bin

TraceSM100
Message tracing at the SM100 level Captures messages that may never get to traceSM Used to trace all SIP messages received by the SM100 from the tracer_asset.log Located: /var/Avaya/asset/activeversion/var/log/

TraceSM vs. TraceSM100

traceSM traces SIP messages that travel to the Service Host traceSM100 traces SIP messages that terminate at the SM100

TraceSM100
To analyze a previously captured tracesm.log: # traceSM /tmp/my_capture.txt
To filter SIP messages from/to: #traceSM100 -i 135.122.1.|2.2.2.2
Can help determine if issues are SM100-related or Service Host-related

Call Routing Test

Call Routing Test allows for the testing of SIP routing configuration against the configured SM database. Testing requires the following parameters:
Called Party URI Calling Party URI Calling Party Address

Call Routing Test Tool

Troubleshooting routing issues even if the called party is not available Validate routing configurations Pre-deployment testing of a SIP entities, links, routing and Session Manager instance configuration Validating the use of adaptations

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
To verify the ASM replica node is synchronized with System Manager at ASM CLI type: GET AllUsers - view user ids, login names etc. GET AllRegistrationsLocal shows all registered users GET usersub 1901 training.com shows subscriptions for user

Tshark and jconsole

Tshark- Avaya proprietary packet sniffer jConsole- Avaya proprietary Java JDK includes the Java Monitoring and Management Console (JConsole) tool. It uses the extensive instrumentation of the Java virtual machine to provide information on performance and resource consumption of applications running on the Java platform using Java Management Extension (JMX) technology.

Logs
Logs are instrumental in troubleshooting issues They capture errors and alarms that were logged by internal system components or services and are instrumental in isolating system issues

Depends on Entity
dig @localhost <LHNR> dig @localhost _SIP._tcp.<LHNR> dig @localhost _SIP._tls.<LHNR> dig @localhost _SIP._udp.<LHNR> nslookup <LHNR>
SIP logs/tools
SM100 Software
/var/log/asset.log traceSM100 /var/log/tracer_asset.log tshark asset-report > ashreport.txt
Depends on Entity
SIP Entity A
SIP Entity B
ServiceDirector
/var/log/Avaya/sm/ServiceDirector/ /var/log/Avaya/sm/ServiceDirector.sh.log /var/log/Avaya/sm/ServiceHost/ /var/log/Avaya/sm/ServiceHost/traceSM.log* /var/log/Avaya/sm/ServiceHost.sh.log traceSM
ServiceHost0 Management Service

SMGR/ASM logs/tools
/opt/Avaya/JBoss/4.2.3/jboss-4.2.3.GA/jboss-as/server/avmgmt/log
/var/log/Avaya/mgmt/drs psql U postgres asm /var/log/Avaya/jboss Runsmconsole smconfig
SMGR Web Browser to SMGR JBOSS

/var/log/Avaya/mgmt
postgres
SH
ASM
IPTCM CM FS/ES
Database
Alice
/var/log/Avaya/jboss/SessionManager/ppm.log sm ppmlogon sm ppmlogw sm ppmlogv sm ppmlogoff
/var/log/Avaya/mgmt/drs SMGR web Replication psql U postgres avmgmt

Log Files
The following logs may be useful for troubleshooting:
Session Manager Installation Issues - Install Log: /var/log/Avaya/asm-install.log - initTM failure details: /var/log/Avaya/jboss/SessionManager/server.log - initDRS failure details: /var/log/Avaya/mgmt/drs/symmetric.log

Log Files
Service Director /var/log/Avaya/sm/ServiceDirector/ /var/log/Avaya/sm/ServiceDirector.sh.log
Service Host /var/log/Avaya/sm/ServiceHost/ /var/log/Avaya/sm/ServiceHost/traceSM.log* /var/log/Avaya/sm/ServiceHost.sh.log traceSM

Log Files
SM100 /var/log/asset.log /var/log/tracer_asset.log asset-report > ashreport.txt

Log Files
Database Replication /var/log/Avaya/mgmt/drs psql U postgres asm /var/log/Avaya/jboss

Log Files
PPM var/log/Avaya/jboss/SessionManager/ppm.log sm ppmlogon sm ppmlogw sm ppmlogv sm ppmlogoff

Group exercise: View Install Log

Work through sample log file that contains clues to a problem. Discuss how to navigate/interpret the log. Identify the log entries that relate to an issue.

Group Exercise: View Install log

Navigate to install log cd /var/log/Avaya Type ls l to determine name of log file (i.e avaya_aura_installlog_2011-03-12_01.02.49.txt) To open log file type cat insertfilenamehere.txt

/var/log/Avaya/asm-install.log

Maintenance Tools
Shutdown/Rebooting Session Manager

Note: Graceful Shutdown
It is strongly suggested that the Session Manager be placed in the Deny New Service state, and that you wait for all active calls to end before shutting down/rebooting the server. Active calls through the affected Session Manager will drop if it remains down too long. New calls will immediately use an alternate Session Manager (if available) once the affected Session Manager is placed in the Deny New Service state.

Shutdown/Rebooting Session Manager

After logging in to Session Manager CLI type: shutdownSM or rebootSM

You will receive a confirm request after selecting shutdown from the Shutdown/Rebooting Session Manager SMGR console Shutdowns done remotely will require onsite staff to power up Session Manager

Stopping and Starting System Manager

Browse to the cdom web console that hosts the System Manager template. Select Virtual Machine Management Select the SMGR Virtual Machine Select Stop


To restart SMGR select the Start button SMGR Jboss server resumes functionality approximately 15 20 minutes A Reboot will automatically Stop and Start System Manager


System Manager server has completely stopped.

Alarming
The alarming service provides access to alarms generated by the Session Manager components. Alarms can be viewed, exported and have their status changed. Alarms are generated by System Manager to notify administrators of system events. They can be configured to forward alarms to Avaya Services or send SNMP traps and Session Manager Element failure events to a Network Management System.

Alarming
Can be accessed through the dashboard

Alarm List displays all severity levels Can select alarm and Change Status to: Acknowledged or Cleared

Alarm Event Id
The event id can be traced using the Avaya Maintaining & Troubleshooting Avaya Aura Session Manager doc

Troubleshooting Methodology
Sample Troubleshooting Methodology

Step 1 Baseline
Determine what components/services are working. Is Data Replication functioning? Are calls being routed? Are phones registering?
Action
Confirm Issue with Customer Always verify with customer that issue reported is the same issue being experienced. Have any changes been made recently? How long has this issue existed? Was this working before?
Data Collection Document Symptoms Are phones able to register? Are calls dropping? Is SM100 responding to ping requests? Is database replication completing successfully? Are there alarms or error messages?

Sample Troubleshooting Methodology

4 Determine Scope of Issue
Is it affecting an individual or is it widespread? Are SIP or h.323 users affected? Is issue isolated to a location or is enterprise-wide? How frequently does the issue appear?
Service Restoration
Can service be quickly restored using a work-around until issue is resolved?
Implement Resolution
Implement solution to permanently restore service.
Testing
Run tests to verify resolution was effective. If possible, duplicate issue.

Checkpoint
Which tool would be most effective in troubleshooting the SM100 status?
A. smconsole B. traceSM C. SM100 status from SMGR console D. SIP tracer tool

Summary
Troubleshooting tools are essential: baselining system performance monitoring system status detecting errors and deciphering messages tracing and isolating issues speedy resolutions

Common Issues
Troubleshooting Common Issues

Before completing the Troubleshooting Exercises lets get familiar with some issues common to Session and System Manager and their resolutions.
What do you think the majority of Session Manager issues received by Avaya Support are?

Session Manager Issues- Discussion

80% of the issues are related to installation or provisioning problems.
20% of the issues are related to interoperability directly impacting routing.

Common Issues
Interopera 0% Interoperability bility 20% 0%
Installation/Provisioning

Session Manager Installation-Related Issue Issue: InitDRS Fails

Common Causes:
Incorrect Cabling Session Manager eth0 interface was connected but the SM100 eth2 was not connected
Hosts File Incorrect- Hosts file was not configured or the fqdns were configured incorrectly therefore SMGR and ASM could not resolve to each other
Date/Time Incorrect- The date must be identical on both SMGR and ASM. There must not be a time difference greater than 2 minutes.

Did you Know?

Security certificates between ASM and SMGR get invalidated if their time is not synchronized!
Resolution:
After installation verify hardware is cabled correctly At ASM & SMGR CLI type date to verify correct date At ASM & SMGR CLI type cd /etc/hosts to verify host names are correct Then run initTM

Session Manager Installation-Related Issue
OR
You can run the validate.sh
tool!

Validate.sh tool
- Developed by Avaya ETSS support engineers -
Addresses the large volume of installation issues upload tool to your system
- Open a case with Avaya technical support and they will - 6.2 will offer tool as standard utility - Works on ASM 5.2, 6.0, 6.1 and 6.2.

Validation Tool - Functionality

Validation tool can detect a problem and it will suggest how to solve it by adding directions in a log file Tests the tool checks for: - Verifies entry for local host in both SMGR and SM
- Sends fqdn ping request - Checks master database exists - Checks replica node exists - Verifies fqdn is configured correctl - Verifies date/time correct in both - Verifies DRS triggers are configured properly - Verifies replica records match records in master node tables

Validate Tool
After validate tool is saved in the temp/validation directory it can be executed Validate tool begins running through tests

Sample Validation Report

Session Manager Installation-Related Issue Issue: SM100 Down (eth2)

Common Causes:
Database replication will not initialize (initDRS) The SM100 down status is a symptom of DRS not functioning. SMGR/SM clocks out of sync DNS/name resolution problems, etc
Resolution:
Run validate.sh tool At ASM & SMGR CLI type date to verify correct date At ASM & SMGR CLI type cd /etc/hosts to verify host names are correct Avaya recommends using SMNetsetup script to modify hostnames then run ./install.sh

Session Manager Installation-Related Issue Issue: InitTM will not complete successfully
Common Causes:
If System Manager is not completely up before the Session Manager completes its installation the initTM will fail. During installation,Session Manager requested the enrollment password from SMGR in order to authenticate it and exchange the security certificates but SMGR was not able to respond.
Resolution:
Ensure SMGR is completely running before installing ASM by making sure you can connect to SMGR and access the web console.

Session Manager Interoperability Issue Issue: PPM not working correctly on Avaya endpoints
registered to Session Manager
Common Causes:
SUBSCRIBES to features not completing Due to private/public incorrect configuration on CM the
Resolution:
In CM change SIP trunk parameter back to private

Session Manager Interoperability Issue Issue: SM apparently dropping ACKs or other in-dialog SIP requests
Common Causes:
Usually the request URI is not constructed properly by the UA (SIP Gateways/SBC) which causes routing issues with the Session Manager Security Module. SM100 cant route call successfully Can use traceSM100 to see that there is mismatch between Request URI and Contact Header in the SM100 200 OK Resolution:
Ensure interoperability testing done and device is supported on DevConnect Code change will most likely be required to SIP Entity Usually occurs on non-Avaya SIP Entity

Session Manager Routing Issue Issue: Calls stuck in a loop

Common Causes:
Routing Loops due to incorrectly configured routing in Session Manager or end-device UA have a max forwards setting of 70 which ASM will keep track of and when the message reaches the limit ASM will send an error indicating maximum hops Usually happens with non-Avaya systems as CM can detect the loops
Resolution:
Run traceSM to verify that the SIP message goes and comes back to it Verify routing configuration on end-device is correct Verify ASM routing configuration is correct

Session Manager Common Issues Issue: ASM alarms do not make it to the Avaya Data Center
Common Causes:
SAL not configured properly Usually product ID's not properly configured on SM or SMGR alarm admin problem
Resolution:
Verify product ID is correct Verify alarm configuration is correct

System Manager Issues
System Manager Issues

>10% of the issues are related to installation or provisioning problems.
90% of the issues are related to configuration.

Interopera bility 0% Interoperability 20% 0%
Installation/Provisioning

System Manager Software Issue Issue: CM will not synchronize with SMGR
Common Causes:
IPTCM synchronization problems Known issue in 6.1 SP1
Resolution:
Upgrade to 6.1SP2
Also ensure the login created on the CM has the appropriate permissions.

System Manager Software Issue Issue: Users can not be deleted in SMGR
Common Causes:
Software bug that requires making manual modifications to the database
Resolution:
Escalate to Avaya Support

System Manager Issues Issue: Web UI is inaccessible

Common Causes:
due to JBOSS failure, filesystem problems, memory leaks
Resolution:
JBOSS restart and/or SMGR VM reboot

System Manager Issues Issue: SMGR alarms do not make it to the Avaya Data Center
Common Causes:
SMGR product ID's not properly administered, HTTP connection info (proxy, etc) not configured in System Manager -> Spirit Agent Data Transport screens.
Resolution:
Verify configuration of SAL Agent

Troubleshooting Exercises
Troubleshooting Exercise #1
A System and Session Manager pair were installed in the Warner Enterprises Puerto Rico location by another business partner. Your team was called in because the systems went live on Day 1but the customer says nothing is working. Your teams responsibility is to get the site up as soon as possible. Objective: Use knowledge of ASM Components, Troubleshooting Tools and Methodology to resolve the issue and answer the following:
Step 1. 2. 3. 4. 5. Action
What tests were run to isolate the problem?
What logs were useful in isolating the problem? Did you find an error or status message that helped isolate problem? What was the cause of the problem? How was the problem resolved?

Exercise 1: Discussion
Was a resolution found? What was the issue? What other variables could contribute to this issue? What tools were used? Did any error messages/alarms register?

Troubleshooting Exercise #2
Session Manager and System Manager were both installed by the implementation team at Ceilex Company in their Dubai location. Before the systems are in production your team was responsible for configuring the routing, SIP entities and users . Your task is as follows: add one SIP user extension 1904@training.com and test
Step 1. 2. 3. 4. 5. Action
What tests were run to isolate the problem?
What logs were useful in isolating the problem? Did you find an error or status message that helped isolate problem? What was the cause of the problem? How was the problem resolved?


Troubleshooting Scenario #3: Issue: SIP users are complaining

they cant make calls
Objective:
Troubleshoot issue by using the tools, isolating issue, find errors/alarms and resolve. Answer the following:
Step 1. 2. 3. 4. 5.
Action What tests were run to isolate the problem? What logs were useful in isolating the problem? Did you find an error or status message that helped isolate problem? What was the cause of the problem? How was the problem resolved?

Troubleshooting Scenario #4 Issue: SIP users are complaining

they dont see any feature buttons
Objective:
Step 1. 2. 3. 4. 5.
Action What tests were run to isolate the problem? What logs were useful in isolating the problem? Did you find an error or status message that helped isolate problem? What was the cause of the problem? How was the problem resolved? All rights reserved. 2011.

Troubleshooting Scenario #5: Issue: SIP Users can not register Objective:
Step 1. 2. 3. 4. 5.
Action What tests were run to isolate the problem? What logs were useful in isolating the problem? Did you find an error or status message that helped isolate problem? What was the cause of the problem? How was the problem resolved?

Checkpoint
User can not connect to SMGR web console. What could be the problem? A. jboss failure B. initDRS failure C. initTM failure D. Service Host downn

You have completed the following Objectives Troubleshooting Module 5

You should now be able to.. 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 resolve issues

To Learn More
Support and Documentation
https://support.avaya.com - Avaya Aura Session Manager Avaya Aura Session Manager Overview Installing and Configuring Avaya Aura Session Manager Administering Avaya Aura Session Manager Maintaining and Troubleshooting Avaya Aura Session Manager Comparison of Avaya Aura SIP Enablement Services and Avaya Aura
Session Manager 6.x

Administering Avaya Aura Communication Manager as a Feature Server

Thank you!
Appendix A- Helpful Troubleshooting Commands

These commands reboot ASM applications without rebooting the box:
Service watchdsvc restart or start or stop or status To restart, start, stop or status Session Manager services (from any directory)
Or from init.d directory ./watchdsvc restart/ or stop or start or status -c
These commands can be initiated from /opt/Avaya/Contrib/bin:
restartcause: Shows date/time and type of restart for modules
smstat: Displays status of Session Manager elements
traceSM: Displays SIP traffic to/from Session Manager Service Host
traceSM100: Displays SIP traffic to/from SM100/eth2

Appendix A cont.
SIP- AS Management Server
restart SIP-as MS
service jboss restart: Restarts the SIP/AS Management Server
service jboss start: Starts the SIP/AS Management Server
smrestart: Restarts Session Manager elements
smstart: Starts Session Manager elements
smstop: Stops Session Manager elements

Appendix A- cont.
General Linux Commands
Cd = to change directory Cd - = puts in previous directory Ctrl c = to exit -c (at the end of command line) = allows command to update continuously ls l = to list contents of directory vi = to edit :wq = write quit x = deletes a character cat = to view or modify a file shutdown f = force a shutdown without asking to verify chmod = change permissions of a file cp = copy files dir = list directory contents in columns

Appendix A- cont.
find = find files ( example: find /opt/IBM name trace.log) ftp = transfer file to and from remote network site hostname = sets or displays the name of the current host system ifconfig = sets up network interfaces mkdir = create a directory mount = mount a file structure passwd <username > = change a password for designated user ps = list processes (ps ef | grep java ) su = switch user scp = secure copy (alternative to ftp)

Appendix B- Additional Log Files
LOG FILES /opt/Avaya/SIPAS/current/*/var/log4j.properties
DESCRIPTION file which controls what level gets logged (* = ServiceHost0, ServiceDirector, ManagementServer)
/opt/Avaya/SIPAS/current/ManagementServer/log4jMast whenever MS restarts, this file gets copied to all components' er/log4j.properties log4j.properties. /var/log/Avaya/sm/SIPas.log /var/log/Avaya/sm/event.log ERROR..DEBUG log entries from all SIPAS components. exceptions and other debugs
/var/log/Avaya/sm/calls.log
SIP message logging into/out-of ServiceHost. Command "sm clogon" turns call logging on (until the next SH restart). "sm clogoff" turns it off.
/var/log/Avaya/sm/ServiceHost.sh.log /var/log/Avaya/sm/spirit.log
for SH starting shell script; java console output goes here logs using Avaya spirit logging API (generally turn into alarms)


Avaya Session Manager Part 2

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 2

Uploaded by

Copyright:

Available Formats

Exercise 7: Verify or Configure SIP Phone

2007 Avaya Inc. All rights reserved.

Exercise 8: Register SIP Phone x101

Extensions Student01 Student02 Student03 Student04 => => => =>

2007 Avaya Inc. All rights reserved.

Avaya Proprietary & Confidential. Under NDA

Exercise 9: Register 2nd SIP Phone x102

Extensions Student01 Student02 Student03 Student04 => => => =>

2007 Avaya Inc. All rights reserved.

Avaya Proprietary & Confidential. Under NDA

Exercise 10: Place a Call

Have x101 dial x102

2007 Avaya Inc. All rights reserved.

Exercise 11: Place a Restricted Call

2007 Avaya Inc. All rights reserved.

Accessing the Session Manager Host

2011. All rights reserved.

different arguments that the script supports.

2011. All rights reserved.

Half Call Model Route Headers

Route: SecurityModule@135.122.81.xx Route:SessionManager@135.122.80.xx

Need to have CM process Origination logic. How to I override the requestURI?

2011. All rights reserved.

Sequenced Applications and Communication Manager

2011. All rights reserved.

CM-ES & CM-FS as feature server Difference?

CM-ES: Full Call Model

2011. All rights reserved.

CM as Feature Server (CM-FS)

CM is connected to the SM via a SIP-ISC interface. Half call model is required.

2007 Avaya Inc. All rights reserved.

CM as Evolution Server (CM-ES)

CM is connected to the SM via a SIP-ISC interface. Full call model is required.

Half Call Principle CM-FS

2011. All rights reserved.

Example of Phase Tags Options

Route: appuri;lr;phase=imsorig Route: asmuri;lr;phase=origdone

Full Call Principle CM-ES

2011. All rights reserved.

Full Call Principle CM-ES

INVITE (origdone) shortcut

INVITE off-hook (imsorig)

2011. All rights reserved.

Configuring Communication Manager

Needs Configured by Student

2011. All rights reserved.

Configuring CM Evolution Server in System Manager

2011. All rights reserved.

All Session Managers have been defined as a node name.

Pre-Configured IP Network Region

* same for CM-ES & CM-FS

Pre-Configured Dial Plan Analysis

* same for CM-ES & CM-FS

2007 Avaya Inc. All rights reserved.

Student 4: 4201, 4202, 4203

* same for CM-ES & CM-FS

Pre-Configured Uniform Dial Plan

* same for CM-ES & CM-FS

2011. All rights reserved.

Pre-Configured AAR Analysis Table

* same for CM-ES & CM-FS

Pre-Configured AAR Analysis Table

* same for CM-ES & CM-FS

2011. All rights reserved.