Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Microsoft Lync & Acme Packet Session Management Solutions


Published on

Geraint Evans, a guest speaker from Acme Packet, presents on how Acme Packet achieves SIP session management within the SME up to carrier-grade environments.

Published in: Technology
  • Login to see the comments

Microsoft Lync & Acme Packet Session Management Solutions

  1. 1. Microsoft Lync &Acme PacketSessionManagementSolutionsApril 2012 Geraint Evans, Technical Channel Director, EMEA
  2. 2. Introduction & agenda This material is designed for Acme Packet & Microsoft Lync solution architects that need to:  Implement Lync SIP trunking with enterprise SBC (E- SBCs)  Leverage Enterprise Session Management (ESM) to successfully deploy Lync enterprise voice in a multi- vendor IP-PBX environment Agenda:  Deployment challenges  Applications of E-SBCs and Session Managers  Use cases  Acme Packet solutions for Lync SIP trunking & Session Management
  3. 3. Deployment challenges SIP Trunking deployment challenges  Potential interop problems with SIP trunk provider (i.e. support of all of the SIP protocols, methods, and variants used by provider)  Security concerns Routing challenges (i.e. routing of incoming calls to the right place) Session Management deployment challenges  Making calls between Lync and legacy IP-PBX element  Implementing dial plans in every Lync & legacy IP-PBX elements Lync enterprise voice deployment challenges  Legacy IP-PBX vendors fight it as a means of retaining customer control
  4. 4. Functions of Acme Packet E-SBCs SIP Trunk Services UC Vendor Agnostic B2B SIP Trunk Services Provider Enterprise Remote Workers Easy Strong Security Assured reliability Compliance Interoperability• Protect IP • SIP interworking • Quality user • Session network • Protocol experience replication for boundaries interworking • Enables recording• Privacy business continuity
  5. 5. E-SBCs – Why should you care? E-SBCs solve real problems for the customer, VAR and Service Provider  Faster, easier deployment and time to service Most medium / large enterprises are embracing the solution They are rapidly becoming included in most IP telephony & UC vendor reference architectures  Avaya, A-LU, SEN & Cisco include SBCs in their enterprise IP telephony & UC reference architecture  Acme Packet SBCs are qualified for use in MSFT OCS/Lync architectures   Many Service Providers are including SBCs to terminate their SIP Trunks  Vendor agnostic solution to accelerate time to service revenue
  6. 6. SBCs & 3 flavours of Lync Enterprise Voice Service ProviderLocal Lync Lync Clients Mediation SIP Trunk Server SP Core & Access to PSTN Enterprise Premises Lync Lync FE Lync Remote Lync Clients & Edge Internet Federations Server Servers PSTN Office 365 Cloud Voice Service Provider Lync Mediation SIP Trunk Office 365 SP Core & Server Access to PSTN Lync Lync FE Lync (MS Hosted - Internet Lync Clients Enterprise Server Edge Servers Part of BPOS) PSTN Hosted Lync Operator Voice Service Provider Lync Mediation SIP Trunk SP Core & “SP Hoster Pack” Lync Server Access to PSTN (Lync hosted by Lync FE Lync Lync Clients Enterprise third-party SP) Edge Internet Server Servers
  7. 7. Migrating from TDM – PBX Vendor View  Legacy vendors try to fight Lync deployments with their own session management strategy or agendas“Before” view “After” view• PBX(i.e. Avaya or Cisco) is the “session • All Lync calls routed through IP-PBX or Session manager” Manager elements• Gateway (GW) for PSTN trunking • E-SBC used to terminate SIP Trunk Legacy Telephony Vendor Legacy Telephony Vendor SIP TDM PSTN SIP PSTN PSTN – Lync call routing via IP-PBX & GW Lync Environment Lync Environment
  8. 8. Why keeping legacy vendors inLync call paths is a bad thing Keeping legacy voice vendors in call path can:  Introduce additional voice management costs  Impedes full migration to Lync enterprise voice  Complicate call troubleshooting  Limit future Lync calling features due to incompatibilities with IP PBX Legacy PBX vendors are fighting to keep their voice role  But why should Lync deployments be limited by this?  Shouldn’t enterprises be able to choose the call routing? Is there a better and UC vendor-neutral solution?
  9. 9. Introducing Session ManagementSolutions Optimized for Lync Enterprise Session Management is a function not a productNet-Net Session ManagerSolutionsEnterprise Session E-SBC provides security, interop,Director routing and dial plan management on one platform ASC provides routing, dial planApplication Session management and Web 2.0 integrationController on dedicated server platform
  10. 10. Two session management models Integrated model: Use session management on E-SBC  All SBC & session management features performed on E- SBC  Security, interop, routing on a single network element Standalone model: Use standalone session manager  E-SBC for security, interop, and control functions  Standalone session manager for dial plan management Integrated ESM Model Standalone ESM Models DMZ DMZ PSTN PSTN E-SBC & E-SBC Session Manager
  11. 11. Why both session managementmodels are needed? Customer requirements are not all equal Some customers want a integrated model  Leverage E-SBC investment for dial plan management and interop functions  May not need some of the advanced capabilities available on Acme Packet’s standalone models Other customers will prefer a standalone model  Volume of PBXs & complexities of multi-vendor UC environment drives the need for a separate element  Separation of security and routing functions
  12. 12. Migrating from TDM – Acme Packetview Session management helps move to SIP trunking  Lync calls get routed directly via ESM  Simplified dial-plan and call routing  No loss of functionality and improved interworking TDM Trunking SIP Trunking Enterprise Premises Enterprise Premises Legacy Telephony Vendor Legacy Telephony Vendor SIP SIP TDM SIP SIP PSTN PSTN SIP PSTN – Lync PSTN – Lync call routing via E-SBC & call routing IP-PBX & GW Session via Manager E-SBC & SM Lync Environment Lync Environment
  13. 13. Microsoft Lync &Acme PacketSessionManagementSolutionsDeploymentModels March 2012
  14. 14. Session managementdeployment models Multiple deployment models exist: 1. ESM integrated into E-SBC with On-Premises Lync 2. Standalone ESM with On-Premises Lync 3. SM integrated into E-SBC with Office 365-D Lync 4. Standalone SM with Office 365-D Lync More details in subsequent slides…
  15. 15. Use Case #1:ESM in E-SBC with On-Prem Lync ESM integrated into E-SBC model Enterprise Premises  Net-Net ESD performs security, Site A interop, and SM routing functions Legacy Telephony E-SBC & Session  SM routing functions = PSTN calls Manager to/from legacy systems & Lync PSTN  For calls to PSTN, IP-PBX & Lync DMZ dial plans send calls to E-SBC  For calls from PSTN, E-SBC sends Other enterprise UC apps requiring E-SBC support calls to legacy IP-PBX or Lync (i.e. legacy video conferencing) based on called party info  E-SBC can also route calls Enterprise between IP-PBX & Lync Premises Site B  Lync Media Bypass supports allows for media path efficiencies
  16. 16. When Use Case #1 would apply Use Case #1 applies when:  Customer is using on-premises Lync  Customer is using (or planning to use) an E-SBC for SIP trunking  Customer is OK with performing session routing, security, and any necessary interop fixups in the same E-SBC element  Customer is OK with routing internal sessions (i.e. between Lync and legacy IP-PBX) via the E-SBC element that is typically in the DMZ If the above conditions are not met, then a standalone ESM model would be more appropriate (Use Case #2)
  17. 17. Use Case #2:Standalone ESM with On-Prem Lync Standalone SM model Enterprise  SM functions separated from E- Premises Site A SBC element Legacy Telephony  E-SBC element performs security and interop functions Session Manager E-SBC  SM element performs routing & PSTN advanced dial plan management DMZ  For calls to PSTN, legacy IP-PBX & Lync dial plans send calls to SM (which routes to E-SBC) Other enterprise UC apps requiring E-SBC  For calls from PSTN, SM receives support (i.e. legacy video conferencing) calls from E-SBC and sends calls to legacy IP-PBX or Lync based on called party info Enterprise Premises  SM can also route calls between Site B IP-PBX & Lync  Lync Media Bypass supported
  18. 18. When Use Case #2 would apply Use Case #2 applies when:  Customer is using on-premises Lync  Customer is using (or planning to use) an E-SBC for SIP trunking  Customer wants to perform session routing and any necessary interop fixups in a ESM element separate from the E-SBC  Customer wants to route with internal sessions (i.e. between Lync and legacy IP-PBX) via a standalone ESM element (vs. other methods)
  19. 19. Use Case #3:SM with Office 365-DLync Office 365 (dedicated) model uses Net-Net ESD with integrated SM and Enterprise Premises E-SBC functions in a manner similar to On-Premises Lync model Legacy Telephony E-SBC used for security & interop E-SBC & and routing Session Manager Media bypass/TLS/SRTP All calls between PSTN, legacy PSTN IP-PBX and Lync are routed via DMZ E-SBC element Office 365 Lync Clients Lync Media Bypass supports Other enterprise UC apps requiring E-SBC support allows for media path efficiencies (i.e. legacy video conferencing)
  20. 20. Use Case #: Standalone SM withOffice 365 (dedicated) Lync Office 365 (dedicated) model uses a standalone SM in a Enterprise Premises manner similar to On-Premises Legacy Telephony Lync model  ESD provides E-SBC functions used for security & interop Session Manager E-SBC Media bypass/TLS/SRTP  SM used for routing PSTN DMZ All calls between PSTN, legacy Office 365 Lync Clients IP-PBX and Lync are routed via E-SBC + SM element Other enterprise UC apps requiring E-SBC support (i.e. legacy video conferencing) Lync Media Bypass supports allows for media path efficiencies
  21. 21. Acme Packet products forEnterprise Session Management For ESM integrated on E-SBC model:  Net-Net ESD-4500 appliance (500 – 16K sessions)  Net-Net ESD-3820 appliance (150 – 8K sessions)  Net-Net ESD-Server Edition SW (25 - 250 sessions) For standalone session management model  Net-Net ESD options listed above  Net-Net ASC software (up to 20K sessions) These products have been through UC OIP either via SBC or SIP trunking provider category  Acme Packet + Lync details:  Acme Packet product details:
  22. 22. Summary Acme Packet’s solutions for Lync are  Qualified via Microsoft UC OIP  Successfully deployed in Global 500 enterprise networks  Widely used by ITSP SIP trunk service providers Acme Packet’s solutions for Lync also provide:  Vendor-neutral session management capabilities  Supports key Lync enterprise voice features including media bypass, TLS/SRTP, DNS LB, etc.  A better means of deploying Lync enterprise voice
  23. 23. Acme Packet:Not just another E-SBC vendor Enterprise & service provider SBC market leader  Over 1,500 customers worldwide  Majority of UC OIP ITSPs are using Acme Packet  First vendor to be UC OIP qualified as an SBC  Also MS-qualified for Exchange UM & O365-D  Selected as SBC vendor for Lync Hosting Pack Flexible packaging (appliance or SW-only options)  Acme Packet hardware, third party server, and virtual machine packages  Scales from 25 to 16,000 concurrent sessions  Multiple session management solution options
  24. 24. Thank you