1. 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 ITEXPO January 2015 Miami By:Karl Ståhl CEO Ingate Systems AB (and Intertex Data AB, now merged) karl.stahl@intertex.se

2. 2 So Far SIP Trunking Has Been About Replacing Telephony Wires With IP Wires What’s Next? 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 Communication (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®

3. 3 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 WebRTC is a game changer: More and Richer. The CPE of the “SIP Trunk” is where to do it SIP Trunks for POTS Connectivity Hosted with desktop phones on LAN Enterprise PBX with desktop phones

4. 4 Enabling WebRTC Usage in the Enterprise (WebRTC may be blocked or give bad quality) Problems to solve when using cloud based WebRTC services:  Restrictive enterprise firewalls block WebRTC For WebRTC demonstration/evaluation, Carrier’s today have to use their guest WiFi instead of their own LAN…  Data-crowded enterprise firewalls means bad quality, QoS Carriers Deploy SIP Trunks Via SBCs (to reach the PBX/UC). For WebRTC Carriers can provide quality pipes for more valuable communication. (Remember - No one can be without WebRTC!)

5. 5 LAN Company Web Server WebRTC - Like All Real-Time Communication Protocols - has a NAT/Firewall Traversal Problem LAN Company Web Server  Firewalls do not allow unknown incoming signaling and media is a “surprise” (just like SIP)  SBCs are Firewalls that know SIP and take it into the LAN, but WebRTC prescribes ICE/STUN/TURN to fool the firewall to let the real- time traffic through (similar to Skype.)  Websockets, WS/WSS, often used to hold the signaling channel open  There are media issues… a)Getting through b)Quality media ICE media STUN TURN SERVER signaling WS/WSS

6. 6 Ingate Has Been Driving the Idea of a TURN Server PARALLEL to the Firewall (Q-TURN) Upcoming standards for network provided TURN servers will allow: Knock-knock; Give my media a Quality Pipe Regard ICE as a request for real-time traffic through the firewall. Have the TURN server functionality PARALLEL to the firewall and setup the media flows there under control. Security is back in the right place – Where you have the firewall. The enterprise firewall in itself can still be restrictive. The Carrier provides a “WebRTC- SBC” in the Trunk CPE Q- TURN Q-TURN Enables QoS and More: Prioritization and traffic-shaping Diffserv or RVSP QoS over the Net Authentication (in STUN and TURN) Accounting (usage of this pipe)

7. 7 Ingate Has Been Driving the Idea of a TURN Server PARALLEL to the Firewall (Q-TURN) Upcoming standards for network provided TURN servers will allow: Knock-knock; Give my media a Quality Pipe Regard ICE as a request for real-time traffic through the firewall. Have the TURN server functionality PARALELL to the firewall and setup the media flows there under control. Security is back in the right place – Where you have the firewall. The enterprise firewall in itself can still be restrictive. The Carrier provides a “WebRTC- SBC” in the Trunk CPE Q- TURN Q-TURN Enables QoS and More: Prioritization and traffic-shaping Diffserv or RVSP QoS over the Net Authentication (in STUN and TURN) Accounting (usage of this pipe) Q-TURN (a Network Provided TURN server) will be added in future releases of the Ingate SIParator®. Awaiting standards to be used by browsers: ietf-tram-turn-server-discovery draft-schwartz-rtcweb-return-04 WebRTC browsers will then use the network provided TURN server crossing the enterprise firewall.

8. 8 Can The Carrier Also Offer The WebRTC Features to the Enterprise? 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 video conferencing clients  The browser is the most superior remote client – always available and anywhere  Send http-links as invitations: to be called, or call into a conference bridge etc.

9. 9 But Remember: Enterprises Want The WebRTC Calls Into the Contact Center Carriers can provide a WebRTC-SIP gateway in the trunk CPE, so WebRTC calls goes into the existing auto attendant, queues, forwards, transfers, conference bridges and PBX phones. The same gateway can integrate WebRTC clients WebRTC by itself bypasses the enterprise SIP UC infrastructure. Voice/Video/Telepresen ce, from passed links and click-to-call buttons etc.

10. 10 With Good WebRTC Soft Clients For Smartphones Wireline Carriers Can be OTT Virtual Mobile Operators We hardly use desktop phones (no matter how good) anymore Mobile smartphones are used everywhere  Superior remote connectivity: Use WebRTC everywhere you can surf  WebRTC smartphone clients OTT over LTE and WiFi is all you need and far superior to the mobile voice we know. With smartphone WebRTC clients connected to the enterprise SIP trunked PBX and UC (Unified Communications) 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. 11 Offering Web Click-to-Call Into the Enterprise Call Center Using the Carrier Supplied CPE With WebRTC Gateway Adding WebRTC click-to-call buttons to the enterprise website is simply to copy some JS-code into the enterprise website. Deployment and installation will be the same as for SIP trunking – with the trunk CPE already at the demarcation point (with WAN and LAN PBX connection) the interface is the same as for carrier SIP trunking using an CPE edge device with the WebRTC gateway.