Session Manager is Avaya's SIP routing and integration tool that centrally manages SIP signaling across an entire enterprise. It integrates different telephony systems, routes calls to achieve the cheapest routing, and provides high availability and scalability. Session Manager promotes a software-centric approach and provides policy-based routing, centralized management of dial plans and networks, and support for third-party SIP endpoints and applications.

1. © 2011 Avaya Inc. All rights reserved.
Session Manager Overview
1

2. © 2011 Avaya Inc. All rights reserved.
So… What is Session Manager?
A rather Special
SIP Routing Server
Integration Engine
2

3. © 2011 Avaya Inc. All rights reserved.
What is Avaya Session Manager?
Avaya Session Manager acts as a SIP routing and
integration tool. It integrates all the SIP entities across
the entire enterprise network within a company. Session
Manager offers a new perspective to enterprise
communication where individual locations are no longer
managed as separate units within the enterprise
– Integrates different telephony systems
– Routes call signaling packets to achieve Cheapest calls.
– Is highly available with geo redundancy.
– Is highly scalable & very secure.
3

4. © 2011 Avaya Inc. All rights reserved.
Why Avaya Session Manager?
ASM promotes Avaya’s move to a software centric
company by evolving the Avaya SES [SIP Enablement
Services] from a server based product to an service
based solution.
ASM exceeds the demands of our customers in
scalability and reliability.
ASM provides a solution that normalizes disparate
networks, centralizes a customer’s routing and dial plan,
and provides robust policy-based routing.
4

5. © 2011 Avaya Inc. All rights reserved.
Avaya Aura™ Session Manager
5

6. © 2011 Avaya Inc. All rights reserved.
Revolution in Communications Architecture
Flexibly connect users, applications and systems enterprise-wide
Enterprise
Network
Collaboration
Apps Video
Apps
Business
Apps
Avaya
New York
Avaya
London
Nortel
Hong Kong
Siemens
Frankfurt
Contact Center
Mumbai
Cisco
Rome
Contact Center
Chicago
Users
anywhere
Avaya
London
Nortel
Hong Kong
Siemens
Frankfurt
Contact Center
Mumbai
Cisco
Rome
Contact Center
Chicago
Data Centers
SIP
Trunking
Avaya Aura™
Communication
Manager
New York
Apps
Integrated
Avaya Aura™
Session
Manager
6

7. © 2011 Avaya Inc. All rights reserved.
Avaya Aura Session Manager
Avaya One-X &
3rd Party
SIP Endpoints
Avaya CM, IP
Office
3rd Party PBX
SIP
Session
Manager
Avaya CS1K,
BCM
Named & Sequenced Applications
• N Interconnects
• 1 Routing Database
• SIP Trunking
• On-Net Dialing
• Centralized SIP Applications
• Named Apps
• Sequenced Apps
• 3rd Party SIP Endpoints
7

8. © 2011 Avaya Inc. All rights reserved.
Named vs. Sequenced Applications
“Named” applications
–Named Applications are “Selected” by the Request Address
–Examples: Modular Messaging, Voice Portal, Meeting Exchange
“Sequenced” applications
–A new concept in the Enterprise Communications world
–A series of applications automatically engaged depending on the
user
• Comes from the Service Provider world – but simplified to fit
the enterprise
• Each application in a Sequence “Sees” all requests
• Each application can deny, modify, or forward initial SIP
requests
8

9. © 2011 Avaya Inc. All rights reserved.
Tests for “Named Applications”
Does the User Indicate What the Application Is to Do?
Does the User Dial A Number to Get this Application?
Does the User Expect A Certain Response?
–Answer of “Yes” Indicates Strongly a Named Application
–SM is NOT Needed To Sequence These
9

10. © 2011 Avaya Inc. All rights reserved.
Tests for “Sequenced Applications”
Does the User Have No Idea the App Is Invoked?
Can You “Gang” Together with Other Apps?
Can the Administrator Enable or Disable the Applications without
User Knowing?
–Answer of “Yes” Indicates Strongly a Sequenced Application
–SM IS Needed To Sequence These
10

11. © 2011 Avaya Inc. All rights reserved.
Avaya AuraTM Sequenced Applications
Session
Manager
Direct MediaUser #1 User #2
Billing
Service
Voice
Monitor
Call
Blocker
Enhanced
Caller ID
Caller ID
Converter
Personal
Assistant
Meeting
Coordinator
CM
11

12. © 2011 Avaya Inc. All rights reserved.
Examples of Other Sequenced Applications
Do-not call and selective call lists
–White or Black-lists, could depend on time or agent skill
Caller-ID manipulation: Outsourcers or partners calling “on behalf of”
their customer
Conference bridge selector: Use built in 6-party conferencing first,
then automatically switch to conference bridge (internal or hosted) if
greater capacity needed
Call screener: Could be activated if user is in a meeting or depending
on their presence status
facebook (or other social network) pop up
Selective call recording
12

13. © 2011 Avaya Inc. All rights reserved.
Benefits of Sequenced Applications
 Business benefits
– Increased agility and flexibility
– Improved customer service
 Proof points (most provide multiple benefits)
– Requires no upgrades to the call processing system (Communication
Manager / Session Manager) – major differentiator from our current model
and what our competitors offer
– Applications can be added / licensed per user or group of users
– New versions of applications can be added on the fly; migrating part of the
users in a pilot
– Customers / Partners / OEM’s can quickly develop new applications;
Application development in weeks vs. months
– Once applications exist customer can deploy them in days vs. weeks or
months
13

14. © 2011 Avaya Inc. All rights reserved.
1. An Enterprise User Makes an
Outbound Call
2. Session Manager Invokes the
Originating Applications Associated
with the Caller
3. The DND App (Do Not Call) verifies
that the called party is not listed in
“Do Not Call” registry.
4. After Verification, it forwards the
call to Session Manager.
5. Session Manager Sequences to
the Next Application in the
Sequence
Session Manager
DND App
Example: Origination Side Sequencing
INVITE
SM
14

15. © 2011 Avaya Inc. All rights reserved.
1. SM Gets INVITE from Trunk
2. Session Manager Invokes the
Term Apps For the Called Party
3. The Call Blocker App Does Not
Block Call
4. SM invokes the next application
5. The Call Screening App Checks
Called Party’s Status
6. Called Party is Busy, Call
Screening app Forwards Request
to Media Server
7. The Media Server Plays Custom
Message
Session Manager
Call Blocker
Media Server
Call Screening
App
Example: Termination Applications
SM
15

16. © 2011 Avaya Inc. All rights reserved.
Applications Can Be Identified as “Mandatory” or Not
– An Unresponsive Mandatory Application Will Fail the Call
– A Timeout will Fail the Call
– Timer is Settable - Timer “B”
– Error Codes of 500,503,408 will Fail the Call
– If SIP Monitoring has Found the Application Unresponsive,
All Calls will Fail
– CM Should Be a Mandatory Application
– Other Applications May or May Not Be Mandatory
– Call Blocker Is Probably Not Mandatory
– Call Recording May be Mandatory for Finance
Transactions
Mandatory Applications
16

17. © 2011 Avaya Inc. All rights reserved.
1. A User Makes an Outbound Call
2. SM Invokes Orig Applications
3. The DND App (Do Not Call) is
Sequenced
4. Session Manager Sequences
Recording application
5. Enterprise Application recording
is down.
6. As recording is NOT Marked
Mandatory, so recording is
“skipped”
7. CM is Sequenced
8. Outgoing Call is Sent
Session Manager
CM
DND App
record App
Example: Non-Mandatory Application Is Down
Timeout
SM
INVITE
17

18. © 2011 Avaya Inc. All rights reserved.
Geographic Redundancy
ASM instances in an enterprise can be geographically
distributed – separated by WANs, etc.
All the ASM instances in an enterprise function as an
organic whole – to continue providing service – to all
users – should any one ASM instance fail.
Each ASM in an enterprise operates in “active” mode –
can and does handle INVITE, REGISTER, SUBSCRIBE
and other SIP messages
Each user in the enterprise is assigned two ASM
instances to support that user (proxy, registrar,
application sequencer, event-handler for that user!)
18

19. © 2011 Avaya Inc. All rights reserved.
Session Manager Location
Large Enterprises can have Geo Specific Session Managers
These can all be controlled through a Common or Duplicated
Active/ Active OR Active/ Standby System Managers
19

20. © 2011 Avaya Inc. All rights reserved.
ACTIVE-ACTIVE Geo Redundancy
 Primary Session Manager keeps the alternate SMs updated of the call setup parameters.
20

21. © 2011 Avaya Inc. All rights reserved.
Branch SIP Trunking (Reference Configuration))
BSM-1
SM-1
GW
CM-1
Non-SIP
Endpoints
LSP
GW
SIP
Endpoints
Non-SIP
Endpoints
SIP
Endpoints
Data Center-1
Branch - 1
BSM-2 GW
LSP Non-SIP
Endpoints
SIP
Endpoints
Branch - 2
SM-2
CM-2
Non-SIP
Endpoints
GW
SIP
Endpoints
Data Center-2
Connect branch directly with SIP Service Provider
BSM supports incoming and outgoing SIP trunk traffic in sunny day and rainy day modes
SIP
Service
Provider
21

22. © 2011 Avaya Inc. All rights reserved.
Branch SIP Trunk(Sunny Day Scenario)
SIP phones in the branch locations are
simultaneously registered with core SM(s)
and BSM
SIP phones have marked one of the core
SMs as the active controller
Gateways are registered with CM (in the
core)
BSM has direct connectivity with SIP
Service Provider
BSM and SM have direct connectivity
(with healthy OPTION pinging in place)
BSM routes all incoming calls to core
SM for routing.
SM routes outgoing calls thru BSM
BSM
SM
GW
CM
Non-SIP
Endpoints
LSP
GW
SIP
Endpoints
Non-SIP
Endpoints
SIP
Endpoints
SIP
Service
Provider
Core Network
Branch
22

23. © 2011 Avaya Inc. All rights reserved.
Branch SIP Trunk(Rainy Day Scenario )
Branch SIP phones, after losing
connectivity with core SM(S), mark
BSM as the active controller
Gateways in the branch detect
outage and connect with LSP as the
controller
LSP activates the link with BSM
Incoming calls from SIP SP are
routed locally in the branch
Outgoing calls from the branch
users are routed out to SIP SP
BSM
SM-1
GW
CM
LSP Non-SIP
Endpoints
SIP
Endpoints
SIP
Service
Provider
Core Network
Branch
23

24. © 2011 Avaya Inc. All rights reserved.
Quick view of Session Manager Capacities
Avaya Aura® Quick Reference
Item (CM/SM) R6.0.1/R6.1 R6.2/R6.2
Total Enterprise Users 100,000 250,000
Total Enterprise SIP Users 100,000 100,000
SIP Users/CM 18,000 36,000
SIP Users/SM 12,000 12,000
Total Enterprise Presence Users 81,000 81,000
Presence Users/SM 9,000 9,000
TLS Connections 100,000 100,000
SM Instances 10 10
BHCC per SM 300,000 350,000*
Simultaneous Sessions 80,000 90,000*
Registrations/Second per SM Unspecified 800
Advanced SIP Terminal Initializations/Second per SM Unspecified 10**
Survivable Remotes 250 250
Communication Managers/SMGR 500 500
Locations/Adaptations/SIP Entities 25,000 25,000
SIP Domains 1000 1000
Dial Patterns/Routing Policies 300,000 300,000
24

25. © 2011 Avaya Inc. All rights reserved.
Avaya Aura Session Manager Hardware
Offered on a fixed hardware platform (appliance model)
Choice of 2 hardware platforms:
– HP DL360G8
– Dell R620
Avaya Aura Session Manager is NOT offered on
customer provided hardware
List Price of $11,500 (USD) for each
6.2 offered on VMware as well
25

26. © 2011 Avaya Inc. All rights reserved.
SMSM
SM
SM
3rd Party
Application
CM
Enterprise
Edition
Avaya
Application
(AAM, AAC,
AAEP, MM, VP,
etc.)
CS 1000
Premium
CM
Standard
Edition
Avaya Aura SBC,
Avaya SBCE or
Avaya SBCAE
264148
$20
264148
$20
264231
$0
264231 $0
264231
$0
264231
$0 Avaya
BCM
Avaya
B5800
264231 $0
Avaya
Gateway
264231 $0
264231 $0
3rd Party
Gateway
264148
$20
CS 1000
Enhanced
264148
$20
3rd Party
SBC
$20/
Session
 Session Manager licensed based on:
– The number of simultaneous sessions required
– The type of device/system connecting to Session Manager
26

27. © 2011 Avaya Inc. All rights reserved.
Session Manager Licensing Matrix
27