PLNOG 4: Pranav Desai - SIP Trunking
0 likes59 views
The document discusses SIP trunking and issues related to its implementation. It describes SIP trunking technology, issues around quality of service, survivability, network management, integration with legacy PBXs, and IP PBX interoperability. Solutions discussed include the SmartNode DownStreamQoS, auto-provisioning, and the SmartNode SN4960 gateway and SN5200 session border controller to address these issues and provide SIP trunking capabilities to different PBX environments.
PLNOG 4: Pranav Desai - SIP Trunking
- 1. SIP Trunking
- 2. Page 2 Overview • Introducton • Technology phase shif - TDM to IP • SIP Trunking • SIP Trunking Issues • Solutons • Conclusion/ Questons
- 3. Page 3 SIP Trunking • SIP Trunking is basically routng calls over the IP Network of the provider (ITSP) • SIP Trunking features typically include – Integrated Local and Long-distance calling – Unifed Communicatons – E911 type Emergency Calling Services
- 4. Page 4 Technology Phase Shif – TDM to IP • Technology shifing from TDM to IP • Service oferings and usage are changing at diferent paces • Resultng transiton phase is the current VoIP market TDM IP TDMIP Communicatonserviceuse Communicaton service oferings Past: All TDM 10 years ago Future: All IP In 10 years In the meantme: Need for gateways In the meantme: Need for gateways Technology Perspectve
- 5. Page 5 Old PSTN and Data Network • Three Bills every month for the Business User – Local Calling – Long Distance Calling – Most Expensive stll
- 6. Page 6 SIP Trunking • Single Bill for the Business user – Reduced Long distance calling ($$$) • Enable legacy or IP PBX to use VoIP • Create a single conduit for voice and data
- 7. Page 7 Why ofer SIP Trunking? • Infonetcs predicts a CAGR of 89% • Bind Customers through Service Diferentaton • Bind Customers with Bundled Services • Cut Operaton Costs through Converged Service Delivery • Increase ARPU and Reduce Churn • So What‘s stopping you? 773/19/10
- 8. SIP Trunking Issues: General
- 9. Page 9 Issue: Downstream Voice Quality • The Internet only supports best efort packet forwarding • No diferentaton between tme critcal IP packets such as VoIP and other trafc such as web pages mail etc • Problem: • Downstream is overloaded • VoIP and other packets get discarded with same Access Link Internet Web Server VoIP CPE
- 10. Page 10 Soluton: SmartNode DownStreamQoS™ • SmartNode DownStreamQoS™ • Introduces a dynamic virtual botleneck at the customer premises • Discard non-real tme trafc before it starts to block the voice trafc in the edge router “Virtual Botleneck” Internet Web Server VoIP
- 11. Page 11 Issue: Survivability • The Legacy PSTN network has high availability/ survivability features • Enterprise want survivability in SIP trunking as well • Enterprises care about this because – Business contnuity and thus communicaton contnuity is key – If the IP network fails, business communicaton is down1111 3/19/10 SmartWare
- 12. Page 12 Soluton: SmartNode Survivability Features • SmartNodes pioneer in Telephony Survivability • Leading Call Routng / Fallback Engine • Survivable paths for voice a) PSTN Fallback 1212 3/19/10
- 13. Page 13 Issue: Network Management Problem • Confguring and maintaining a large number of VoIP CPEs is tme consuming and expensive • The VoIP service customer is not trained to do the maintenance of his/her SmartNodes Soluton • Auto-Provisioning • No manual confguraton efort by the provider or the customer
- 14. Page 14 Soluton: SmartNodes Auto- Provisioning Provider StockCustomer ...... ...... Customer subscribes via web form Customer data is stored in database Script generates individual SmartNode confguraton from customer data and Template Confguraton is matched with ID and stored on confguraton server SmartNode is shipped: ID from barcode SmartNode is plugged in and automatcally confgured ID ID
- 15. Page 15 Fax over IP IP A/D D/A Fax Bypass, T.30 Fax over G.711, 96Kb Fax-Relay, T.38 packets 1) Fax Bypass, G.711 T.30 Fax T.30 Fax The Fax tones are terminated in the gateway, relayed in packet form and re- modulated at the far end. + Uses less bandwidth + Is reliability(ofers redundancy) The Fax is carried in a G.711 voice channel just like a regular phone call. + Is interoperability with any gateway - Uses more bandwidth - Is less reliability 2) Fax Relay, T.38
- 16. SIP Trunking Issues: Legacy PBX
- 17. Page 17 Legacy PBX Issues • Legacy PBX is a huge Investment – Enterprises would stll like to use their old PBX • Legacy PBX doesn’t understand IP – SIP/ VoIP are IP based oferings ? IP Carrier PSTN Soft Switch
- 18. Page 18 Legacy PBX Issues • Needs: • Integrate diferent legacy PBX’s using a single platorm • Enable SIP Trunking in Legacy PBX • Phased Migraton for the Enterprises 18183/19/10 P B X Carrier Switch VoI P VoI P PR I Enterprise ?
- 19. Page 19 Soluton: SmartNode SN4960 Gateway • Use legacy PBX while enjoying benefts of SIP Trunking • End users don’t realize they are using VoIP • Easy Phased Migraton – Simple Number Portability using the SN4960 Call Router – Run IP and legacy services together during migraton – Move to IP services completely when desired 19193/19/10 P B X Carrier Switch VoI P VoIPPR I Enterprise PSTN PR I
- 20. SIP Trunking Issues: IP PBX
- 21. Page 21 IP PBX Issues: Interoperability • SIP is an Open Standard protocol • Typically interpretaton and implementaton of SIP is diferent for diferent partes involved – Many SIP methods/ extensions might be supported by an IP PBX but not by an ITSP and vice versa – Enterprises might want to use diferent codecs for diferent scenarios (e.g. G.711 for Internal calls and G.729 for External calls) • Need: A mechanism to ensure interoperability between the partes involved (e.g. ITSP and the IP PBX)
- 22. Page 22 IP PBX issues: Survivability • Survivability for an Integrated Access Device • Data Network Design is always Survivable • In above case, Calls start failing if IP PBX fails • Calls start failing if connectvity to ITSP fails • Need: Survivable telephony based SIP Trunking
- 23. Page 23 Multple Requirements at the Edge • Typical Requirements needed to be satsfed – QoS • Using Data and Voice together mandates an Actve QoS mechanism – WAN • Need for a separate WAN router • Efcient utlizaton of WAN bandwidth for LAN to WAN calls – DHCP server
- 24. Page 24 Solution: Session Border Controller SN5200 • Enable up to 32 SIP sessions simultaneously • SIP Session Negotator for SIP Trunking Services – Use appropriate Codec depending on the nature of the call (LAN to LAN or LAN to WAN) – Mediate SIP extensions and methods between the ITSP and the IP PBX • Downstream QoS to handle Voice and Data Trafc • Secure Enterprise VPN Router Soluton • Integraton with your existng Firewall
- 25. Page 25 PSTN SmartNode as a Service Provider CPE IP Carrier Customer premise Legacy or IP SIP Sof Switch SmartNode § Scenarios § TDM PBX to SIP § ISDN PBX to SIP § Analog to SIP § IP PBX to SIP § Advantages § Active QoS traffic shaping § Survivability § Fax and POS support § Special DECT functionality § Smooth migration Connectng a PBX to a VoIP operator H.323
- 26. Page 26 SmartNode as a Service Provider CPEExample § Widely deployed since 2001 § References § UPC § T-Com § O2 Business § Avantel § Welcome Italia § Telekom Austria § Telkom South Africa § And Many More
- 27. Page 27 • Thank you