Avaya Aura™ a new Era of Business Communications Gartner Hype Cycle Where is sip?

Avaya Aura™ A New Era of Business Communications

Gartner Hype Cycle – Where is SIP?

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 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

SIP Addressing/Registration SIP Connects People to People, not Device to Device

A Simplified SIP Call Flow

SIP Separation of Signaling and Media SIP routing core is media agnostic

SIP Rich Communications Not Limited to the Enterprise A More Complete User Experience – Extended to Your Customers

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

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”

• Months-long development cycles

• Significant testing effort

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)

Software as a Service

One Service – Multiple Applications

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

A New Unified Communications Architecture Avaya Architecture Today

A New Unified Communications Architecture Aura is Enterprise IMS (Internet Multimedia Subsystem)

Avaya Aura™ Architecture (IMS Architecture) One Unifying Protocol for All Services

A Rather Special SIP Routing and Integration Engine

Multi-Vendor Integration with Centralized Dial Plan

SIP Adaptation Modules (Dialed Number and SIP Header) Normalizes SIP, Normalizes Dial Plans

What if Some of My Systems Do Not Support SIP?

A Rather Special Global Routing Policy Engine Super Flexible, Super Scalable, Super Resilient

• Session Manager

• 250K+ BHCC

• 25K SIP Entities

• 50K Users/SM (Nov)

• Active/Active

• Geo-Redundant

• Up to 3 (May), 10 (Nov)

Tail-End Hop Off and Least Cost Routing

SIP Call Admission Control Routing Policies

Centralized SIP Trunking Reduce PSTN Interface Costs and Improve Bandwidth Utilization

SIP Trunks and System Interfaces Lower Cost, More Efficient, and Greater Flexibility

Security at Scale

Session Manager/System Manager Profile Maps Each User to Their Communication Applications

Centralized Applications SIP-ready Avaya applications

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

Extend existing functionality with application sequencing

Aura Integration with Business Process Management Processes now have a “Voice”

Migrate at Your Own Path, Your Own Pace

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

thank you

• A New Era of Business Communications