Avaya Aura™
A New Era of Business Communications
Jim Su
Solutions Architect
Quagga
jim.su@quagga.com
916-673-5054
Session Initiation Protocol
SIP can be called a “rendezvous” protocol. That is, it allows endpoints on the
Internet to discover, locate, negotiate, and establish sessions. What kind of
sessions? Any kind of sessions. SIP is used to establish VoIP (of course),
video, gaming, text, call control.
SIP is an open protocol standard, with an active working group
on the Internet Engineering Task Force (IETF). Avaya and other
major companies are active in the IETF SIP working group and
in other industry groups, working to ensure that SIP-enabled
solutions work across businesses and enterprises with a variety of
legacy, new, and evolving networking and telecommunications
infrastructures and products to enhance and revolutionize the world of
real-time business communications.
SIP is used to identify, locate, and enjoin parties who want to communicate
using any peer-to-peer media type. However, SIP does not transport the
media itself: That is handled by codecs within the communications
programs or devices.
2
Gartner Hype Cycle – Where is SIP?
3
Important SIP Characteristics
 Born of the Internet
 Made for mobility
 Media agnostic (Separation of signaling and media)
 Ability to support multiple media within the same session
 Text-based and extensible (Heterogeneity is the norm)
 Standard APIs
“SIP is probably the third great protocol of the Internet, after TCP/IP and HTTP”
- Vinton Cerf, “Father” of the Internet
4
SIP Elements
 User Agents (UA): Endpoint devices that originate or terminate the
SIP signaling. They can be clients (UAC) that initiates a request, or a
server (UAS) that terminates a request (most endpoints do both)
 Proxies route SIP requests to their destination. They sit in the
signaling path between endpoints, and may add parameters to a
request or reject a request, but they do not initiate requests
 Registrars handle REGISTER requests from endpoints to bind a user
to the device. This information is then stored in a location service
database for the proxy’s domain.
 Back-to-Back User Agent(B2BUA): Similar to a proxy, except that it
terminates the SIP dialog on both sides. Commonly used to provide
services because it can manipulate the signaling between endpoints
5
SIP Addressing/Registration
SIP Connects People to People, not Device to Device
How do I reach Jim? Just use sip:jim.su@quagga.com
Cell Phone
I am ready to take calls
My ID: sip:jim.su@quagga.com
Location: 5054@212.55.34.2
Identity (AOR)
Location
sip: jim.su@quagga.com 5054@212.55.34.2
Desk Phone
212.55.34.2
Location Service
Registrar
IM Client
6
A Simplified SIP Call Flow
Location Service
Call initiation to Jim
INVITE: <jim@quagga.com>
Request
Call initiation to Jim
INVITE: <jim@quagga.com>
Request
Fred’s
Outgoing Proxy
Registrar
Jim’s
Incoming Proxy
Registrar
Call initiation to Jim
INVITE: <5054@212.55.34.2>
Request
OK Response
UAC
UAS
Media Paths (RTP)
Fred
Jim
7
SIP Separation of Signaling and Media
SIP routing core is media agnostic
IP Network
Signaling Path
Media Path - Voice
Media Path - Video
Media Path - Whiteboard
Rich Voice – Multiple media streams can be incorporated in a single session
8
SIP Rich Communications Not Limited to the Enterprise
A More Complete User Experience – Extended to Your Customers
Voice
CM
Voice Conference
Unified
Web Conference
Communications Whiteboard
MM
MX
3G SIP Smart Phones
Mobile Customer Care
Interactive Voice
Interactive Video
VP
3rd
Pty
1. Greg Allman - $50
2. Air Supply - $50
5. See More Events
Session
Manager
3G Mobile
Network
3G Gateway
Session Manager Rich Communications
•
• Media/session independence
• Add new media without impacting
existing services
•
• Loosely coupled feature servers
Self-service IVR with video
previews
Send information and images
along with audio
9
SIP Extensibility
Principle: Heterogeneity is the Norm
 SIP can be extended by adding new headers, methods,
parameters, or bodies – without a dramatic impact on
existing systems
 Proxies only need to understand 3 core SIP methods
(INVITE/CANCEL/ACK) – addition of new methods have
no impact
 New content types have no impact on proxy operation
 Built-in mechanisms enable forward compatibility between
clients and servers while minimizing possible
interoperability breaks
 Clients/servers are expected to NOT assume universal
support for new extensions
10
Technology Shift
Using SIP & SOA for Business Advantage
Pre 2000
2000 - Today
Tomorrow
IN/SS7
Overlay
CTI
Overlay
Peering and
Loose Coupling
SOA
Application
Application
Session Mgt
Session Mgt
Network
IP
ISDN and TDM
H.323
App
SIP
Presence
Session Mgt
SIP
Network
Flatten
Consolidate
Extend
App
Applications
Everywhere
Network
11
Communication Application Development Today
One Large Code Base is Difficult to Change or Add New Features
 Foundation elements written for each
application – no reuse
 Features become “intertwined”
A3.b
 Months-long development cycles
A2
 Significant testing effort
A3.a
A1
B2BUA
“Features”
A4
Redirect
UAS
UAC
Protocol Services
Networking
Mgt
Security
Scalability
Fault
Tolerance
Foundation Services
12
SOA/SIP Application Server Development
Leverages Enterprise Application Server Technology
 All foundation elements provided by the platform
 All features/services modular and independent
 Rapid development – software as a service
 Loosely couple features/services to create new applications
 Off-the-Shelf development tools and methodology familiar to huge developer community
(Eclipse, J2EE, web services, etc)
Application
Call Blocker
Concept to Trial ~1.5 days!
Feature
A1
Proxy
Avaya SIP Foundation
Server
Networking
Web Service
Feature
A3
Feature
A2
Feature
A4
Registrar
B2BUA
Redirect
Location
Service
Security
Mgt
Fault
Tolerance
Scalability
13
Software as a Service
Hi, I’m Quagga Outcall
Service. Use me!
Voice Portal
Outbound
Voice Call
Web Service
Email
Web service
Savvion
BPM
Give Me:
• Subject
• Message
• Response Option
• Recipient contact info
• Your contact info
I’ll call them and use TTS
to provide your message
and get their response.
I’ll put the response in an
email and send it back to
you!
14
One Service – Multiple Applications
Customer Care
Automate outbound calling
campaigns and customer
status notifications
Workforce Mgt
Workforce mgt identifies
absent employees, calls
back-ups, and sends email
to mgr
Operations
Finance
IT systems trigger calls
with real-time information
on critical alerts
Automate purchase
approvals from mgt
15
Why SIP
 Open Standard => Industry Momentum
 SIP trunking => Cost savings, new capabilties
 Hardware Architecture => Software Architecture
 Many protocols => One unified protocol
 Telephony network => Real-time communications network
 Presence
 SIP Extensibility
 Development Community and SOA
 It is becoming ubiquitous
16
Introducing Avaya Aura™
A new unified communications architecture
Collaboration and Interaction
Solutions
Core Communication
Services
Multivendor Integration
Performance Analytics
End to End Management
Security and Serviceability
Intelligent Access and Enterprise
Application Integration
Communication Infrastructure
Communication
Manager
Application
Enablement
Presence
System
Manager
Session Manager
NEW
Avaya Aura™
17
A New Unified Communications Architecture
Avaya Architecture Today
Still adjuncts off
of CM
Communication Manager
Features
User
Policy
MM MX
VP
CM
Apps
SIP
Session
Control
Session
Control
Session
Control
SES
SIP
 Monolithic – CM does all
 Centralized – CM controls all
 Everyone has same features
 Other apps are CM adjuncts
 New features require CM upgrade
 Single point of application control
 Scale limited by max system size
 Core is voice-centric
ooo
18
A New Unified Communications Architecture
Aura is Enterprise IMS (Internet Multimedia Subsystem)
Still adjuncts off
of CM
Communication Manager
Features
User
Policy
Apps
Application
Server Layer
MM MX
VP
CM
CM
Feature
Server
SIP Foundation
Server
SIP
Session
Control
Session
Control
System Manager
ooo
Session
Control
SIP
SES
SIP
Session
Manager
Session
Manager
Session
Manager
Dedicated
Session Control Layer
User Policy
Access Layer
19
Avaya Aura™ Architecture (IMS Architecture)
One Unifying Protocol for All Services
Application Layer (SOA)
System
Manager
MM MX
VP
CM
App
App
Application Platform
Avaya Aura Core
Media
Servers
Session
Manager
Session
Manager
Session Control
Session
Manager
App
Application Platform
SIP
Presence
Service
Providers
SIP
Trunks
TDM
Trunks
SBC
Avaya one-X®
endpoints
ooo
ooo
Access
3rd
Party PBXs
Avaya
CM Branch
3rd
Avaya
G860
Party
endpoints CM Standalone
20
Introducing the SIP Session Manager
Global
Routing Policy
21
A Rather Special SIP Routing and Integration Engine
 Establishes an Open, Interoperable SIP Network
– Integrates disparate PBX/Key systems into a single communication
network
– Normalizes SIP into a common, open implementation
– Pools and shares global trunking resources
– Fully leverages SIP trunk services from ITSPs
 Manages a Global Network Dial Plan
– Local PBX dial plans don’t change
– Adapts to existing dial plans that overlap or have different digit
patterns
– One point of administration to handle dialplan changes between
systems
22
Multi-Vendor Integration with Centralized Dial Plan
PSTN
Data Center
1
SIP
Trunks
SIP
Trunks
SM
SM
Data Center
2
Communication
Manager
(Active)
Communication
Manager
(Standby - ESS)
45-XXX
445-XX
Contact Center
Regional Office
OOO
22-XXXXX
630-XXXX
Branch Edition
Sales Office
i120
i120
OOO
OOO
 Multivendor with “SIP adaption” – Nortel, Cisco, Service Providers, …
 One global dial plan in Session Manager (don’t need to change local
PBX dial plans – administration moves to the core!)
23
SIP Adaptation Modules (Dialed Number and SIP Header)
Normalizes SIP, Normalizes Dial Plans
Incoming Digit
Routing
SM
Conversion
Adaptation
Engine
Module
SIP
Entity
Outgoing Digit
Conversion
Examples
Adaptation Properties:
 Avaya: No adaption required
 Adaptation Module
 Cisco: CallMgr 5.X, 6.X, 7.X
 Egress URI Parameters
 Digit Conversion for Incoming Calls
 Digit Conversion for Outgoing Calls
 Nortel: CS1000
 Verizon: Move History-info
 AT&T: Remove History-info
24
What if Some of My Systems Do Not Support SIP?
Digital
PBX
Key
System
T1/PRI
QSIG/T1/PRI
AudioCodes
Gateway
AudioCodes
Gateway
Avaya
CM 3.x
SIP
SIP
H.323
Avaya Aura Core
Session
Manager
Session
Manager
SIP
nectar esm
Session
Manager
H.323
Avaya
CM 2.x
H.323
SIP
Generic
H.323
AudioCodes
Gateway
QSIG/T1/PRI
Generic
H.323
25
A Rather Special Global Routing Policy Engine
Super Flexible, Super Scalable, Super Resilient
System Manager
 Global Routing Policies
Database
Synchronization
 Security Profile
 User Profiles (Nov)
System
Manager
System
Manager
 Replicated Databases
 Management/Monitoring
Routing Policies
Routing Execution
Network Routing Policies
Session Manager
 250K+ BHCC
S8510 Server
 25K SIP Entities
Session
Manager
N+1
Security Module SM-100
• TLS acceleration (50K links)
• 50K TLS set-up in 2 minutes
• SIP Firewall and DoS protection
JGroups/JMS
Synchronization
Session
Manager
Session
Manager
Active
Active
 50K Users/SM (Nov)
 Active/Active
 Geo-Redundant
 Up to 3 (May), 10 (Nov)
Session Manager Community
26
Tail-End Hop Off and Least Cost Routing
Avaya
Avaya
3rd Party PBX
CM Branch
CM Standalone
ooo
ooo
PRI
PRI
PSTN
ITSP 1
Avaya Aura Core
Session
Manager
Session
Manager
Session
Manager
SIP
Trunks
ITSP
N
SBC
SBC
TDM
Trunks
G860
The “Outside World”
Public networks
27
SIP Call Admission Control Routing Policies
 “Star” configurations supported
 RTP assumed to travel over WAN with
CORE
signaling
SM
SM
 Location based
SM
 Administrator specifies for each location
– Average call usage
– Total bandwidth to manage
WAN Pipe
 Multiple SIP entities per location
Entity Links
 Intra-location calls are not counted in
CAC (WAN)
Single
Location
ooo
CM
ooo
3rd Party PBX
CM
28
Centralized SIP Trunking
Reduce PSTN Interface Costs and Improve Bandwidth Utilization
Avaya
Avaya
3rd Party PBX
CM Branch
CM Standalone
ooo
ooo
PRI
PRI
PSTN
ITSP 1
Avaya Aura Core
Session
Manager
Session
Manager
Session
Manager
SIP
Trunks
ITSP
N
SBC
SBC
TDM
Trunks
G860
The “Outside World”
Public networks
29
SIP Trunks and System Interfaces
Lower Cost, More Efficient, and Greater Flexibility
Lower Hardware Costs
• Eliminate TDM hardware
• Share trunk resources
• Share voice/data bandwidth
More Efficient
• On Demand – add capacity when needed
• Online provisioning –add new lines in
minutes
• Map to average usage vs peak usage
Greater Flexibility
• Bandwidth, not channels, determines call
capacity
• ~40 channels per T1 vs. 23
• Linear cost model - add SIP lines in
increments of 1
• Local, long-distance, 800 access over same
circuit
30
SIP Centralized Call Delivery
Virtual Telephone Numbers Eliminate Geographic Boundaries
916-XXX-XXXX
Virtual Office Locations
Sacramento
DID
San Francisco
DID
Los Angeles
DID
San Jose
DID
Avaya Aura Core
PSTN
ITSP
Session
Manager
Session
Manager
Session
Manager
Hong Kong
DID
Toll Free 800
916-XXX-XXXX
Remote Sacramento Agent
Central Contact Center
“Sacramento” Specialist
Establish Virtual Locations Where You Do Business
31
A Rather Special SIP Security Agent
32
Security at Scale
SIP Applications
(Active)
A1
SIP Applications
(Active)
A2
Data Center
1
A1
(Active)
(Active)
Session
Manager
Communication
Manager
(Standby - ESS)
Session
Manager
A2
Data Center
2
Communication
Manager
(Active)
Rate Limit
SIP Firewall
TLS
TLS
TLS
OOO
i120
 All SIP TLS encrypted
TLS
 3rd party certificate support
Branches
TLS
OOO
 Standards-based AAA Radius compliance
 Rate Limiting for “hyperactive” endpoints / branches
 Denial of service protection, SIP packet inspection
33
A Rather Special Personal Routing Assistant
Application Policies
I get access to:
Feature A
Feature C
Feature D
User
Routing
Policies
User
Application
Policies
Things get very interesting when we add users to Aura…..
34
Enterprise Wide Registrar/Location Service
35
Individual Policies
36
Session Manager/System Manager
Profile Maps Each User to Their Communication Applications
Access is based on worker profile, not their location.
CM “Essentials”
Feature A
CM
Feature B
Application
Policies
Application
Policies
I get:
Feature A
Feature C
Feature D
I get:
Feature C
Feature D
Employee
Partner
MM
MX
VP
Feature C
Feature D
Feature E
Application
Policies
I get:
Feature B
Feature C
Feature D
Feature E
Feature F
Manager
3rd Party
Feature F
Application
Policies
Application
Policies
I get:
Feature E
I get:
Feature E
Feature F
Kiosk
Customers
Quickly add different capabilities for different people and workgroups
37
Centralized Applications
SIP-ready Avaya applications
Communication Manager
SIP Feature Server
Meeting
Exchange
Modular
Messaging
SIP
Voice Portal
Voice Portal
Avaya Aura Core
SM
SM
SM
SIP
CM
Branch
Third
party
38
SIP Load Balancing
 SIP load balancing is necessary to support
– Voice Portal MPPs
– Modular Messaging MASs
– Other SIP Entities deployed for redundancy
 Entities to load balance may be identified
– Local Host administration on System Manager
– DNS SRV records
 Advanced load balancing techniques
– Automatic Entity enable/disable via OPTIONS check
– Random distribution
– Priority and weighting
Servers with
different
performance
39
Extend existing functionality with application sequencing
Application
Policies
Rapid SOA Feature Development Platform
If not on VIP list,
then
Forward to
voicemail
ANS
If on X list, then
begin…..
Communication
Manager
Call
Analyzer
Healthcare
Hospitality
SIP Foundation Server
Session
Manager
Request
Media Path - Voice
40
Aura Integration with Business Process Management
Processes now have a “Voice”
Business Process with Integrated Aura Services
Room 201 ready
for next patient
Request
IP Phone
TTS
“Push” Display Voice
Email
SMS
Request
Find doctor to
approve patient
discharge
Request
Notify nurse
and
pharmacy
ANS
Request
SIP Foundation Server
Sanitize
room 201
Session
Manager
Approve!
Patient’s
Family
Housekeeping
41
Migrate at Your Own Path, Your Own Pace
App
App
one-X®
Avaya
endpoints
SIP Foundation Server
MM MX
VP
ooo
PSTN
ITSP 1
ITSP
N
PRI
CM
Session
SES
Manager
(S8510)
SBC
Security Module
SM100
SBC
TDM
Trunks
G860
The “Outside World”
Public networks
42
A Fundamental Shift in Avaya Architecture
 Multiple Protocols => One protocol (SIP)
–
–
–
One protocol for all communication services
Multi-vendor interoperability
Session Manager provides adaptation modules
 Session Manager => New Routing Core of the Communications Network
–
–
–
Carrier class scalability
Geographic Redundancy
SIP as core unifying protocol
 Telephony Network => Real-Time Multimedia Communications Network
–
–
–
Seamlessly blend voice, video, whiteboarding, IM, and file sharing into a single integrated session
Load share SIP feature servers for scalability and redundancy
Loose coupling to quickly add/upgrade features
 Centralized/Monolithic Apps => Distributed/Component Services (SOA)
–
–
Features designed/deployed as modular services
Flexible licensing capabilities
 Session Manager Provides Platform for Future
–
–
–
Extend existing applications via application sequencing
Business Process Integration via Web Services
Rapid feature development, flexible licensing to extend the right features to the right people
43
thank you
A New Era of Business Communications
© 2009 Avaya Inc. All rights reserved.
44