Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Deployment Best Practicesand ArchitectureDave Deutschman, Alan Percy, GeorgeNiculae, Joegen BaclorModerated by Martin Stei...
Introduction to the PresentersSession 1: Deployment Best Practices and ArchitectureJoegen Baclor                          ...
Best Practices for a Next Generation SolutionTransition to all software and an IT application imply profound changesIT / a...
IT Best Practices Demand a New Architecture    SIP Session Oriented Architecture - SSOAInternet Scale Communications•   Na...
New Session State Server (SSS)Modern and scalable presence solutionWhat is new in SSS ?    Load-sharing redundancy and sc...
Session State Server (SSS) ArchitectureFully redundant highly available deploymentFailure cases addressed: Ability to det...
New in 4.6: Redundant Media ServicesSeamless global resiliency and scaleopenUC 4.4: Configuration and voicemail server tig...
Redundant Media Services                           8
Redundant Media Services                           9
Redundant Media Services                           10
Redundant Media Services                           11
Redundant Media Services                           12
Redundant Media Services: How Does It Work?Seamless user experience with geo-redundancyRedundancy achieved at:   Proxy lev...
Redundant Media Services                           14
Redundant Media Services                           15
Redundant Media Services                           16
Redundant Media Services                           17
Deployment Best PracticesHow to build a system                            18
Health Provider with 10 LocationsDesign Considerations- Single data center- Reliable corporate network with QoS- Locations...
Single Multi-Server ClusterHealth Provider with 10 Locations                                    20
Deployment Model BenefitsSingle Multi-Server Cluster- Distributed services to support scalability and availability     - R...
Large Corporation with Many LocationsDesign Considerations- Multiple corporate data centers- Many locations with a large n...
Multi-Server, Distributed ClusterLarge Corporation with many Locations                                        23
Deployment Model BenefitsMulti-Server, Distributed Cluster- Scalability and availability- Geo-redundancy for call processi...
IT Best Practices: Multi-Vendor HardwareGiving you freedom and lower costDisintegration of the vertical model: Certified a...
AudioCodes Gateways and openUCConnecting TDM Networks to SIP ApplicationsKey Benefits:• Plug & play configuration with ope...
SmartTAP Recording for openUC•   Software based IP Centric all-in-one or distributed recording solution•   Support from 8 ...
openUC Appliance with OSN3 ModuleScalable/Modular Appliance for the SMB/SME Branch Office                                 ...
eZuce openUC Appliance with Mediant 800                  Up to 12 FXS                 ports for POTS               OSN    ...
Introduction to Stand Alone SurvivabilityAt Typical Branch Office                                                     Digi...
SAS - Registration Process                                                 Digital                                        ...
SAS - Normal Dialing Mode                                              Digital                                            ...
SAS - E911 Call                                                     Digital                 Phones user                   ...
SAS - Emergency Mode                                                         Digital                Phone user            ...
Simplicity mattersIt is measured in operating expense         openUC is an order of magnitude         simpler than previou...
Q&A• System architecture / SSOA• Deployment best practices• Geo-Redundancy• Gateways & phones• Network requirements and Qo...
CoLab session 1   deployment best practices and architecture
Prochain SlideShare
Chargement dans…5
×

CoLab session 1 deployment best practices and architecture

Livres associés

Gratuit avec un essai de 30 jours de Scribd

Tout voir

Livres audio associés

Gratuit avec un essai de 30 jours de Scribd

Tout voir
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

CoLab session 1 deployment best practices and architecture

  1. 1. Deployment Best Practicesand ArchitectureDave Deutschman, Alan Percy, GeorgeNiculae, Joegen BaclorModerated by Martin Steinmann
  2. 2. Introduction to the PresentersSession 1: Deployment Best Practices and ArchitectureJoegen Baclor Dave Deutschman George Niculae Alan Percy
  3. 3. Best Practices for a Next Generation SolutionTransition to all software and an IT application imply profound changesIT / all software solution managed as part of the IT stackNot vertically integrated: Standards based and interoperableDatacenter or cloud deployments, centrally managedTolerant to hardware failures – resiliency in the SWarchitectureFocus on communications enablement of applications (singlesign-on, user profiles, social graphs, presence, activitystreams) 3
  4. 4. IT Best Practices Demand a New Architecture SIP Session Oriented Architecture - SSOAInternet 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 > Scalable• Pushing communication and collaboration into the cloud > Resilient > Cost efficient
  5. 5. New Session State Server (SSS)Modern and scalable presence solutionWhat 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
  6. 6. Session State Server (SSS) ArchitectureFully redundant highly available deploymentFailure 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 6
  7. 7. New in 4.6: Redundant Media ServicesSeamless global resiliency and scaleopenUC 4.4: Configuration and voicemail server tightly coupled – both reading data from local file systemopenUC 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
  8. 8. Redundant Media Services 8
  9. 9. Redundant Media Services 9
  10. 10. Redundant Media Services 10
  11. 11. Redundant Media Services 11
  12. 12. Redundant Media Services 12
  13. 13. Redundant Media Services: How Does It Work?Seamless user experience with geo-redundancyRedundancy achieved at: Proxy level (DNS) Media Services level (DNS) Voicemail level via FreeSWITCH dial plan Distributed voicemail storage 13
  14. 14. Redundant Media Services 14
  15. 15. Redundant Media Services 15
  16. 16. Redundant Media Services 16
  17. 17. Redundant Media Services 17
  18. 18. Deployment Best PracticesHow to build a system 18
  19. 19. Health Provider with 10 LocationsDesign Considerations- 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
  20. 20. Single Multi-Server ClusterHealth Provider with 10 Locations 20
  21. 21. Deployment Model BenefitsSingle Multi-Server Cluster- 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
  22. 22. Large Corporation with Many LocationsDesign Considerations- 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
  23. 23. Multi-Server, Distributed ClusterLarge Corporation with many Locations 23
  24. 24. Deployment Model BenefitsMulti-Server, Distributed Cluster- 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
  25. 25. IT Best Practices: Multi-Vendor HardwareGiving you freedom and lower costDisintegration of the vertical model: Certified andinteroperable with a large set of devicesOffering plug n’ play management and end-to-end supportfor a select set of vendor’s productsAudiocodes gateways as the preferred choice for PSTNtermination 25
  26. 26. AudioCodes Gateways and openUCConnecting TDM Networks to SIP ApplicationsKey Benefits:• Plug & play configuration with openUC• Modularity, Scalability & Flexibility Mediant ™ 1000• Interoperability Mediant ™ 800 mix-and-match Gateway/E-SBC for Business Cost effective• Survivability (SAS) MediaPack™ 124 Branch office Gateway/E-SBC With 24 FXS• Wide Availability MediaPack™ 11X with FXS/FXO interfaces via Distribution interfaces 26
  27. 27. SmartTAP Recording for openUC• 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 27
  28. 28. openUC Appliance with OSN3 ModuleScalable/Modular Appliance for the SMB/SME Branch Office Create an appliance: openUC software on OSN3PSTN module T1/E1 OSN3 or FXO Module AudioCodes Mediant 1000B SIP SIP Phones LAN Switch 28
  29. 29. eZuce openUC Appliance with Mediant 800 Up to 12 FXS ports for POTS OSN Module FXSWAN AudioCodes PoE LAN Mediant 800 SIP Phones 29
  30. 30. Introduction to Stand Alone SurvivabilityAt Typical Branch Office Digital SIP Phones AudioCodes E911 and Media Gateway or Survivability MSBG with SAS FXO Connection PSTN WAN 30
  31. 31. SAS - Registration Process Digital SIP Phones Phones register with MediaPack AudioCodes E911 and Media Gateway or Survivability MSBG with SAS FXO Connection PSTN Gateway forwards registrations to openUC WAN 31
  32. 32. SAS - Normal Dialing Mode Digital SIP Phones Phone user makes telephone call AudioCodes E911 and Media Gateway or Survivability MSBG with SAS FXO Connection PSTN Normal Mode: MediaPack forwards INVITES to openUC WAN 32
  33. 33. SAS - E911 Call Digital Phones user SIP Phones dials “911”MediaPack detects AudioCodes E911 and“911” and redirects Survivability Media Gateway or MSBG with SAS call to FXO port FXO Connection toward PSTN PSTN WAN 33
  34. 34. SAS - Emergency Mode Digital Phone user SIP Phones makes telephone call Gateway detects connection to network is down (keep Emergency Mode: MediaPack MP-112/FXO E911 and alive messages fail) and Media Gateway With SAS Gateway redirects Survivability activatesall calls to FXO port FXO Connection Emergency Mode toward PSTN PSTN WAN 34
  35. 35. 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. 36. Q&A• System architecture / SSOA• Deployment best practices• Geo-Redundancy• Gateways & phones• Network requirements and QoS• Setting up and managing a cluster 36

×