Embed Size (px)
Citation preview
2
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 groupon the Internet Engineering Task Force (IETF). Avaya and othermajor companies are active in the IETF SIP working group andin other industry groups, working to ensure that SIP-enabledsolutions work across businesses and enterprises with a variety of legacy, new, and evolving networking and telecommunicationsinfrastructures 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.
Session Initiation Protocol
3
Gartner Hype Cycle – Where is SIP?
4
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
5
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
6
SIP Addressing/RegistrationSIP Connects People to People, not Device to Device
212.55.34.2
Identity (AOR) Locationsip: [email protected] [email protected]
Desk Phone
How do I reach Jim? Just use sip:[email protected]
IM Client
Cell Phone
I am ready to take callsMy ID: sip:[email protected]: [email protected]
RegistrarLocation Service
7
A Simplified SIP Call Flow
Jim’sIncoming Proxy
Registrar
UAS
Fred’sOutgoing Proxy
Registrar
UAC
JimFred
Call initiation to JimINVITE: <[email protected]> 50
54@
212.
55.3
4.2
Location Service
sip:jim
.su@
quag
ga.co
mCall initiation to JimINVITE: <[email protected]>
Call initiation to JimINVITE: <[email protected]>
OK Response
Media Paths (RTP)
Request
Request
Request
8
SIP Separation of Signaling and MediaSIP routing core is media agnostic
IP NetworkSignaling Path
Media Path - Voice
Media Path - Video
Media Path - Whiteboard
Rich Voice – Multiple media streams can be incorporated in a single session
9
SIP Rich Communications Not Limited to the EnterpriseA More Complete User Experience – Extended to Your Customers
SessionManager
Session Manager Rich Communications• Media/session independence• Add new media without impacting
existing services• Loosely coupled feature servers
MXMM VPCM1. Greg Allman - $50 2. Air Supply - $50
5. See More Events
1. Greg Allman - $50 2. Air Supply - $50
5. See More Events
3rd
Pty
3G SIP Smart PhonesMobile Customer Care
3G Gateway• Self-service IVR with video
previews
• Send information and images along with audio
3G MobileNetwork
VoiceUnified
Communications
Voice ConferenceWeb Conference
Whiteboard
Interactive VoiceInteractive Video
10
SIP ExtensibilityPrinciple: 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
11
Technology ShiftUsing SIP & SOA for Business Advantage
Application
Session Mgt
Network
ISDN and TDM
IN/SS7Overlay
Pre 2000
Application
Session Mgt
Network
H.323
CTIOverlay
2000 - Today
IPSession Mgt
Network
Tomorrow
Peering andLoose Coupling
SIP
App App
SIP Presence
SOA
ApplicationsEverywhere
FlattenConsolidate
Extend
12
Communication Application Development Today One Large Code Base is Difficult to Change or Add New Features
Networking SecurityMgt FaultToleranceScalability
UASB2BUA Redirect UAC
A1
A3.a
A4
A2
A3.b
Foundation Services
Protocol Services
“Features”
Foundation elements written for each application – no reuse
Features become “intertwined”
Months-long development cycles
Significant testing effort
13
SOA/SIP Application Server DevelopmentLeverages Enterprise Application Server Technology
Networking Security Mgt FaultTolerance Scalability
Proxy Registrar B2BUA Redirect LocationService
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)
FeatureA1
FeatureA2
FeatureA3
FeatureA4
ApplicationCall Blocker
Concept to Trial ~1.5 days!
Web Service
Avaya SIP FoundationServer
14
Software as a Service
Hi, I’m Quagga Outcall Service. Use me!
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!
Voice Portal
SavvionBPM
EmailWeb service
OutboundVoice Call
Web Service
15
One Service – Multiple Applications
Customer CareAutomate outbound calling campaigns and customer
status notifications
OperationsIT systems trigger calls
with real-time information on critical alertsFinance
Automate purchase approvals from mgt
Workforce MgtWorkforce mgt identifies absent employees, calls
back-ups, and sends email to mgr
16
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
17
Introducing Avaya Aura™ A new unified communications architecture
Intelligent Access and Enterprise Application Integration
Intelligent Access and Enterprise Application Integration
Collaboration and Interaction Solutions
Collaboration and Interaction Solutions
Core Communication Services
Core Communication Services
Communication InfrastructureCommunication Infrastructure
Perfo
rman
ce An
alyticsP
erform
ance A
nalytics
En
d to
En
d M
anag
emen
t S
ecurity an
d S
erviceability
En
d to
En
d M
anag
emen
t S
ecurity an
d S
erviceability
Mu
ltivend
or In
tegratio
nM
ultiven
do
r Integ
ration
Communication Manager
Communication Manager System
ManagerSystem Manager
ApplicationEnablementApplicationEnablement PresencePresence
Session ManagerSession Manager
NEW Avaya Aura™
18
A New Unified Communications ArchitectureAvaya Architecture Today
o o o
SessionControl
Features
SessionControl
SessionControl
Communication Manager 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
SES
MXMMVP
CM
SIP
SIP
Still adjuncts offof CM
AppsUser Policy
19
SIP Foundation Server
A New Unified Communications ArchitectureAura is Enterprise IMS (Internet Multimedia Subsystem)
o o o
SessionControl
SessionControl
SessionControl
Communication Manager MXMM
VPCM
SIP
SES
SIP
Still adjuncts offof CM
SessionManager
SessionManager
SessionManager
Features Apps
Dedicated Session Control Layer
SIP
ApplicationServer LayerCM
Feature Server
Access Layer
User Policy
User Policy
System Manager
20
MX
Application Platform
Avaya Aura™ Architecture (IMS Architecture)One Unifying Protocol for All Services
App
3rd PartyendpointsAvaya
CM Branch
o o o
AvayaCM Standalone
o o o
Application Platform
G860
3rd Party PBXs
SBC
App
ServiceProviders
SystemManager
App MMVP
CM
SessionManager
Avaya Aura Core
SIPTrunks
MediaServers
TDMTrunks
Access
Session Control
Application Layer (SOA)
SIPPresence
SessionManager
SessionManager
Avaya one-X®
endpoints
21
Introducing the SIP Session Manager
Global Global Routing PolicyRouting Policy
22
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
23
Data Center2
Branch Edition
i120
Contact Center
Data Center1
CommunicationManager(Active)
CommunicationManager(Active)
CommunicationManager
(Standby - ESS)
CommunicationManager
(Standby - ESS)
Multi-Vendor Integration with Centralized Dial Plan
O O OO O OO O OO O O O O OO O O
PSTN
SIP Trunks
SIP Trunks
Sales Office
i120
Regional Office
45-XXX445-XX 630-XXXX 22-XXXXX
SMSM
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!)
24
SM
SIP Adaptation Modules (Dialed Number and SIP Header)Normalizes SIP, Normalizes Dial Plans
Adaptation
Module
Adaptation Properties: Adaptation Module Egress URI Parameters Digit Conversion for Incoming Calls Digit Conversion for Outgoing Calls
Incoming Digit
ConversionSIP
Entity
Outgoing Digit
Conversion
Routing
Engine
Examples Avaya: No adaption required Cisco: CallMgr 5.X, 6.X, 7.X Nortel: CS1000 Verizon: Move History-info AT&T: Remove History-info
25
What if Some of My Systems Do Not Support SIP?
SessionManager
Avaya Aura Core
SessionManager
SessionManager nectar esm
AvayaCM 3.x
AvayaCM 2.x
GenericH.323
SIP
DigitalPBX
AudioCodesGateway
KeySystem
AudioCodesGateway
GenericH.323
AudioCodesGateway
H.323
H.323
H.323
QSIG/T1/PRI
SIP
SIP SIP
QSIG/T1/PRIT1/PRI
26
A Rather Special Global Routing Policy EngineSuper Flexible, Super Scalable, Super Resilient
SessionManager
SessionManager
SessionManager
Routing Policies
Routing Execution
SystemManager
SystemManager
Network Routing Policies
Session Manager Community
DatabaseSynchronization
N+1 Active
Active
JGroups/JMSSynchronization
Session Manager 250K+ BHCC 25K SIP Entities 50K Users/SM (Nov) Active/Active Geo-Redundant Up to 3 (May), 10 (Nov)
System Manager
Global Routing Policies
Security Profile
User Profiles (Nov)
Replicated Databases
Management/Monitoring
S8510 Server
Security Module SM-100• TLS acceleration (50K links)• 50K TLS set-up in 2 minutes• SIP Firewall and DoS protection
27
Tail-End Hop Off and Least Cost Routing
AvayaCM Branch
o o o
AvayaCM Standalone
o o o
3rd Party PBX
SBC
SessionManager
Avaya Aura Core
SessionManager
SessionManager
PRI
PRI
G860
SBC
SIPTrunks
TDMTrunks
PSTN
The “Outside World”Public networks
ITSP 1
ITSP N
28
SIP Call Admission Control Routing Policies “Star” configurations supported RTP assumed to travel over WAN with
signaling Location based Administrator specifies for each location
– Average call usage– Total bandwidth to manage
Multiple SIP entities per location Intra-location calls are not counted in
CAC (WAN)
o o o
CORE SM
SMSM
CM
WAN Pipe
Entity Links
CMo o o
3rd Party PBX
SingleLocation
29
Centralized SIP TrunkingReduce PSTN Interface Costs and Improve Bandwidth Utilization
AvayaCM Branch
o o o
AvayaCM Standalone
o o o
3rd Party PBX
SBC
SessionManager
Avaya Aura Core
SessionManager
SessionManager
PRI
PRI
G860
SBC
SIPTrunks
TDMTrunks
PSTN
The “Outside World”Public networks
ITSP 1
ITSP N
MPLS/Internet
30
SIP Trunks and System InterfacesLower Cost, More Efficient, and Greater Flexibility
Lower Hardware Costs• Eliminate TDM hardware • Share trunk resources• Share voice/data bandwidth
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
More Efficient• On Demand – add capacity when needed• Online provisioning –add new lines in
minutes• Map to average usage vs peak usage
31
SIP Centralized Call DeliveryVirtual Telephone Numbers Eliminate Geographic Boundaries
Establish Virtual Locations Where You Do BusinessEstablish Virtual Locations Where You Do Business
SacramentoDID
San FranciscoDID
Los AngelesDID
Hong KongDID
Toll Free 800
San JoseDID
PSTN
ITSPSessionManager
Avaya Aura Core
SessionManager
SessionManager
916-XXX-XXXX
916-XXX-XXXX
Remote Sacramento AgentCentral Contact Center“Sacramento” Specialist
Virt
ual O
ffic
e Lo
catio
ns
32
A Rather Special SIP Security Agent
33
Data Center2
Data Center1
SIP Applications(Active)
SIP Applications(Active)
SIP Applications(Active)
SIP Applications(Active)
CommunicationManager(Active)
CommunicationManager(Active)
(Active)(Active)(Active)(Active)
CommunicationManager
(Standby - ESS)
CommunicationManager
(Standby - ESS)
Security at Scale
O O OO O O
TLSTLSTLSTLS
Branchesi120
TLSTLS
TLSTLSTLSTLS
O O OO O O
Rate LimitSIP FirewallRate Limit
SIP Firewall
A1 A2A1 A2
SessionManager
SessionManager
All SIP TLS encrypted 3rd party certificate support Standards-based AAA Radius compliance Rate Limiting for “hyperactive” endpoints / branches Denial of service protection, SIP packet inspection
34
A Rather Special Personal Routing Assistant
UserApplication
Policies
UserRoutingPolicies
Application Policies
I get access to:
Feature A
Feature C
Feature D
Things get very interesting when we add users to Aura…..
35
Enterprise Wide Registrar/Location Service
36
Individual Policies
37
Session Manager/System ManagerProfile Maps Each User to Their Communication Applications
ManagerEmployee Partner Kiosk Customers
Quickly add different capabilities for different people and workgroups
Access is based on worker profile, not their location.
Application Policies
I get:Feature AFeature CFeature D
Feature B Feature C Feature D Feature E
VP 3rd PartyMX
Feature F
MMCM
Feature A
CM “Essentials”
Application Policies
I get:Feature EFeature F
Application Policies
I get:Feature E
Application PoliciesI get:Feature BFeature CFeature DFeature EFeature F
Application Policies
I get:Feature CFeature D
38
Centralized ApplicationsSIP-ready Avaya applications
SIP
SIP
BranchCM
Thirdparty
Meeting Exchange
SMSMSM
Voice PortalVoice Portal
ModularMessaging
Communication ManagerSIP Feature Server
Avaya Aura Core
39
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
40
Extend existing functionality with application sequencing
SessionManager
SIP Foundation ServerCommunication
Manager
Call Analyzer
ANS
Hospitality
Healthcare
Application Policies
If not on VIP list, thenForward to voicemail
If on X list, then begin…..
Rapid SOA Feature Development Platform
Request
Media Path - Voice
41
Aura Integration with Business Process ManagementProcesses now have a “Voice”
SIP Foundation Server
ANS
Request
SMSEmailTTS
VoiceIP Phone
“Push” Display
Business Process with Integrated Aura Services
Patient’s Family Housekeeping
Find doctor to approve patient
dischargeRequest
Approve!
SessionManager
Notify nurse and
pharmacy
Request
Request
Sanitize room 201
Room 201 ready for next patient
42
Migrate at Your Own Path, Your Own Pace
o o o
SIP Foundation Server
App App
MXMM
VP
CMSES
(S8510)
Avaya one-X®
endpoints
Security Module SM100
SBCG860
SBC
TDMTrunks
The “Outside World”Public networks
ITSP 1
ITSP N
PSTN
SessionManager
PRI
43
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
44© 2009 Avaya Inc. All rights reserved.
thank youA New Era of Business Communications
