CoLab session 1 deployment best practices and architecture

Deployment Best Practices and ArchitectureDave Deutschman, Alan Percy, George Niculae, Joegen Baclor

Moderated by Martin Steinmann

Introduction to the PresentersSession 1: Deployment Best Practices and Architecture

Joegen Baclor

George Niculae

Dave Deutschman

Alan Percy

3

IT / all software solution managed as part of the IT stack

Not vertically integrated: Standards based and interoperable

Datacenter or cloud deployments, centrally managed

Tolerant to hardware failures – resiliency in the SW architecture

Focus on communications enablement of applications (single sign-on, user profiles, social graphs, presence, activity streams)

Best Practices for a Next Generation SolutionTransition to all software and an IT application imply profound changes

IT Best Practices Demand a New ArchitectureSIP Session Oriented Architecture - SSOA

Internet Scale Communications• Native Session Initiation Protocol (SIP)

architecture for a modern, highly scalable and resilient communications infrastructure

• Based on a distributed and load-sharing network of SIP proxy servers

• Geo-redundant redundancy reduces complexity and number of servers required

• Peer-to-peer media for industry leading voice and video quality

• Introducing presence based communications that facilitates social business integration and multi-media interactions

• Pushing communication and collaboration into the cloud

> Scalable

> Resilient

> Cost efficient

5

Modern and scalable presence solution

What is new in SSS ?

Load-sharing redundancy and scale for line state presence and session state

New technology from the ground up:• Fast and modern SIP Stack using reSIProcate

• Multiple Watchers and State Agents

• Load-balanced subscriptions via DNS/SRV

• Shared Subscription State – no single point of failure

• Centralized Event Queue

5

New Session State Server (SSS)

6

Fully redundant highly available deployment

6

Session State Server (SSS) Architecture

Failure cases addressed: Ability to detect failure of a node via real-time notification Standard SIP fail-over for transaction failures Load sharing using standard SIP DNS/SRV transaction spreading Bottle neck free fairly-queued task distribution

openUC 4.4: Configuration and voicemail server tightly coupled – both reading data from local file system

openUC 4.6: Improved voicemail REST API, configuration server retrieves data

using voicemail REST API New voicemail architecture – abstract connector layer to allow

pluggable storage types Decoupled voicemail + ability to read / write from external storages =

foundation for redundant voicemail Efficient memory & disk usage, built in replication - GridFS storage

connector Moving forward to cloud - Amazon S3 storage connector

7

New in 4.6: Redundant Media ServicesSeamless global resiliency and scale

8

Redundant Media Services

9


10


11


12


Redundancy achieved at:

Proxy level (DNS)

Media Services level (DNS)

Voicemail level via FreeSWITCH dial plan

Distributed voicemail storage

13

Redundant Media Services: How Does It Work?Seamless user experience with geo-redundancy

14


15


16


17


Deployment Best PracticesHow to build a system

18

- Single data center

- Reliable corporate network with QoS

- Locations have different telco providers

- Need for groups in the same location to use different caller IDs

- 24 emergency hot lines

- Limited remote worker support (IT)

- Instant Messaging (IM)

19

Health Provider with 10 LocationsDesign Considerations

20

Single Multi-Server ClusterHealth Provider with 10 Locations

- Distributed services to support scalability and availability

- Registration and call processing balanced across master and distributed proxy

- ACD deployed on separate server

- Centralized management of all locations

- Local services- Network applications (DHCP and DNS)

- PSTN access

- Remote support through VPNs

21

Deployment Model BenefitsSingle Multi-Server Cluster

- Multiple corporate data centers

- Many locations with a large number of users

- Reliable corporate network with QoS

- Need for location survivability

- Customer uses basic telephony services and voicemail

- Large scale remote worker support

22

Large Corporation with Many LocationsDesign Considerations

23

Multi-Server, Distributed ClusterLarge Corporation with many Locations

- Scalability and availability

- Geo-redundancy for call processing service

- Centralized management

- Flexible PSTN options- Media Gateways

- SIP Trunking

- Scalable Remote Worker support through use of Session Border Controller

24

Deployment Model BenefitsMulti-Server, Distributed Cluster

Disintegration of the vertical model: Certified and interoperable with a large set of devices

Offering plug n’ play management and end-to-end support for a select set of vendor’s products

Audiocodes gateways as the preferred choice for PSTN termination

25

IT Best Practices: Multi-Vendor HardwareGiving you freedom and lower cost

MediaPack™ 11X

with FXS/FXO

interfaces

Key Benefits:

• Plug & play configuration with openUC

• Modularity, Scalability & Flexibility

• Interoperability

• Survivability (SAS)

• Wide Availabilityvia Distribution

26

AudioCodes Gateways and openUCConnecting TDM Networks to SIP Applications

MediaPack™ 124

With 24 FXS

interfaces

Mediant ™ 800

Cost effective

Branch office

Gateway/E-SBC

Mediant ™ 1000

mix-and-match

Gateway/E-SBC

for Business

• Software based IP Centric all-in-one or distributed recording solution

• Support from 8 - 300 concurrent sessions per server with expandability to grow with your organization by adding additional servers.

• Scalable to 1000s of concurrent IP/TDM Channels

• Designed for easy deployment, ease of use, easy maintenance

SmartTAP Recording for openUC

27

openUC Appliance with OSN3 Module

Scalable/Modular Appliance for the SMB/SME Branch Office

LAN SwitchSIP Phones

SIP

PSTNPSTN

T1/E1 or FXO

OSN3 Module

AudioCodesMediant 1000B

Create an appliance: openUC

software on OSN3 module

28

http://acportal/MarcomNew/Image%20Library/Forms/DispForm.aspx?ID=221




eZuce openUC Appliance with Mediant 800

SIP Phones

PoE LANAudioCodesMediant 800

OSN Module

Up to 12 FXS ports for POTS

WANWAN

FXS

Ideal for

Branch

Offices

29



Introduction to Stand Alone SurvivabilityAt Typical Branch Office

WANWAN

PSTNPSTN

AudioCodes Media Gateway or

MSBG with SAS

E911 andSurvivability

FXO Connection

Digital SIP Phones

30

SAS - Registration Process

WANWAN

PSTNPSTN


FXO Connection

Digital SIP Phones

Phones register with MediaPack

Gateway forwards registrations to

openUC


MSBG with SAS

31

SAS - Normal Dialing Mode

WANWAN

PSTNPSTN


FXO Connection

Digital SIP Phones

Phone user makes

telephone call

Normal Mode:MediaPack

forwards INVITES to openUC


MSBG with SAS

32

SAS - E911 Call

WANWAN

PSTNPSTN


FXO Connection

Digital SIP PhonesPhones user

dials“911”

MediaPack detects “911” and

redirects call to FXO port toward

PSTN


MSBG with SAS

33

SAS - Emergency Mode

WANWAN

PSTNPSTN

MediaPack MP-112/FXOMedia Gateway With SASE911 and

SurvivabilityFXO Connection

Digital SIP Phones

Emergency Mode:

Gateway redirects all calls

to FXO port toward PSTN

Phone user makes

telephone call

Gateway detects connection to network is

down (keep alive messages fail) and

activates Emergency Mode

34

Simplicity mattersIt is measured in operating expense

openUC is an order of

magnitude simpler than

previous generation solutions

and therefore cheaper to

operate and develop

35

36

• System architecture / SSOA

• Deployment best practices

• Geo-Redundancy

• Gateways & phones

• Network requirements and QoS

• Setting up and managing a cluster

Q&A

Technology

CoLab session 1 deployment best practices and architecture