1 What’s Next For SIP Trunking? Carriers Enabling and Bringing WebRTC Features With Their Trunks © 2015 Ingate Systems AB Prepared for:Ingate SIP Trunking, UC and WebRTC Seminars What’s Next For SIP Trunking? ITEXPO October 2015 Anaheim By:Karl Ståhl CEO Ingate Systems AB (and Intertex Data AB, now merged)

© 2013 Intertex Data AB 2 Picture by Henry Sinnreich Integration with existing PBX What’s Next? Did we just not go all the way, when IPfying /cloudifying/web ifying telephony? SIP trunking of the PBX was part of the solution in 2002 already! Ingate and Intertex have been SIP trunking since 2002! Here the Worldcom ”Advantage” service /0204voip.html Ingate SIParator®

3 Ingate’s SIP Trunking Seminars Since 2006 But name has changed: SIP Trunking, UC and WebRTC Seminars Co-sponsors Anaheim 2015:

4 So Far SIP Trunking Has Been About Replacing Telephony Wires With IP Wires It’s about how we connect beyond the LAN. SIP Trunking has brought:  Lower cost, connecting to POTS, improved business continuity, disaster recovery etc. That isn’t the end.  Good E-SBCs connecting remote users to the PBX/UC is another step. But what’s next to come?  More federation? Unified Communications (UC) beyond the LAN  UC/multimedia global connectivity? IMS (RCS, VoLTE) – Will those even peer?  WebRTC extensions - What’s that? MPLS SIP System Data & VoIP LAN SIParator®

5 MPLS PBXs has become UC (Unified Communications solutions) and enterprise SIP servers became more proprietary like LCS/OCS/Lync/SfB while getting hard phones and POTS SIP trunks SIP System Data & VoIP LAN SIParator® LAN SIP Why don’t we have UC everywhere? WebRTC will help. “Everywhere you can surf”

6 Today Carriers Offer Voice Services Over Their SIP Trunks WebRTC Opens For Offering More And Better Typically delivered via a CPE (e.g. an E-SBC) as a demarcation point SIP Trunks for POTS Connectivity Hosted with desktop phones on LAN Enterprise PBX with desktop phones But seldom…

7 Tomorrow Carriers Could Bring UC To The Devices We Already Have Then delivered via a CPE (e.g. an E-SBC + WebRTC & SIP Companion Gateway) as a demarcation point

8 Tomorrow Carriers Could Bring UC To The Devices We Already Have Then delivered via a CPE (e.g. an E-SBC + WebRTC & SIP Companion Gateway) as a demarcation point And all these devices become the clients we want for the enterprise UC solution. With mobile devices, failover, backup, disaster recovery of the UC can come automatically

9 Can Service Providers Really Bring WebRTC Features to the Enterprise PBX / UC Solution? The Enterprise PBX / UC environment will benefit from:  Click-to-call buttons on the company website (context sensitive) New! = The Call Center killer WebRTC application!  High quality videoconferencing clients  The browser is the most superior remote client (or a WebRTC app for the smartphone) – always available and anywhere  Send http links as invitations to be called, or call into bridge etc.: Over IM or an ,

10 With Good WebRTC Soft Clients For Smartphones Wireline Carriers Can be an OTT Virtual Mobile Operator We hardly use desktop phones (no matter how good) anymore Mobile smartphones are used everywhere  WebRTC’s superior remote connectivity: Talk everywhere you can surf  WebRTC smartphone clients OTT over LTE and Wi-Fi is all you need and WebRTC is far superior to the mobile voice we know With smartphone WebRTC clients connected to the enterprise SIP trunked PBX and UC environment the SIP trunk provider becomes a virtual mobile operator! WebRTC soft clients – both as web clients and as apps are coming, even for iPhone. Be aware!

11 MPLS Premise-Based (CPE) or Cloud-Based? A “WebRTC & SIP Companion” instead of just an E-SBC The Companion Gateway is Fine in the CPE SIP System Data & VoIP LAN SIParator® LAN Company Web Server SIP Pass a WebRTC link over IM or an , asking people to click-to-call you or something. All functionality can be on premise in the CPE with an WebRTC & SIP Companion Gateway & E-SBC

12 MPLS Cloud-Based: A Network-Provided TURN Server: “Q-TURN Firewall” is Often Required for Quality and NAT/Firewall Traversal of WebRTC SIP System Data & VoIP LAN SIParator® LAN Company Web Server SIP Pass a WebRTC link over IM or an , asking people to click-to-call you or something. If functionality is in the cloud the enterprise often needs a Q-TURN firewall CPE (in the E-SBC) for WebRTC

13 The Network-Provided TURN Server: “Q-TURN Firewall” Standard & Usage for WebRTC in Progess A novel Ingate view: Knock-knock; Give my media a quality pipe Regard ICE as a request for real-time traffic through the firewall. Interpret the STUN & TURN signals in the firewall Have the STUN/TURN server functionality IN the firewall and setup the media flows under control Security is back in the right place - The firewall is in charge of what is traversing The enterprise firewall can still be restrictive Q- TURN Q-TURN Enables QoS and More: Prioritization and traffic-shaping Diffserv or RVSP QoS over the Net Standard for WebRTC browser- usage in progress Accounting (usage of this prioritized quality pipe)

14 What’s Next For SIP Trunking? Carriers Enabling and Bringing WebRTC Features With Their Trunks © 2015 Ingate Systems AB Thank You!