1
Session Abstract While WebRTC is powerful and has huge open opportunities on the Internet, most enterprises are just now deploying SIP as a way to normalize and reduce costs in their communications infrastructure. This session will focus on the challenges and methods of integrating WebRTC into SIP, wither through a vendor solution or the open options available. It will discuss the relative benefits of direct media interoperation versus using a media server of translation as well as the emerging support from vendors for WebRTC components like VP8. This session is essential to mapping out your integrations strategy between WebRTC and SIP. 2
SIP and WebRTC Working Together? Session E3-3 E. Brent Kelly, Ph.D. President and Principal Analyst KelCor, Inc. Vice President and Principal Analyst, Constellation Research bkelly@kelcor.com; brent@constellationr.com twitter: @ebkell 3
Speakers Nancy Maluso VP & GM Application Solutions Sonus Alan Percy Senior Director Marketing, NA AudioCodes 4
WebRTC Session Management and SIP The Good, The Bad and the Ugly. Alan Percy Senior Director, Marketing AudioCodes 5
Why do we care about SIP? Service Provider Networks (SIP Trunking) Thousands of Existing Applications Unified Communications Contact Centers Conferencing/collaboration IP-PBX 6
SIP - The Good, Bad and Ugly The Good Mature, well documented, well understood, flexible The Bad NAT Traversal Issues, security holes, firewall challenges The Ugly Interoperability issues persist flexibility is its weakness STUN, TURN 7
Vision We see developers choosing one of four paths forward 8
Pure Greenfield Applications No legacy interoperability Proprietary peer connection Let s Talk Gaming Social Media Peer to Peer Right-on! WebRTC Client Media WebRTC Application 9
Brownfield SIP Applications With SIP over Web Sockets and SBC SIP & WebSockets [INVITE] [200 OK] Session Border Controller Transcode & Encrypt Media INVITE 200 OK Contact Centers UC & IP-PBX SIP Phones SIP G.711 WebRTC Client Opus G.711 SIP Application 10
WebRTC-enabled SIP Applications Proprietary peer connection Media transcoding Let s Talk Right-on! SBC or Media Server SIP Phones SIP G.711 Opus G.711 WebRTC Client Transcode & Encrypt Media WebRTC-enabled SIP Application 11
WebRTC-enabled SIP Applications and Endpoints Application supports WebRTC and SIP End-points support Opus Let s Talk Right-on! SIP Phones SIP Opus WebRTC Client Opus Media Opus WebRTC-enabled SIP Application 12
Vision Method SIP/WebSockets Required Transcoding Vision Greenfield Applications No No Strong Brownfield SIP Applications Yes Optional Poor WebRTC-enabled SIP Applications No Optional Medium WebRTC-enabled SIP Applications and Endpoints No No Strong 13
CONNECTING THE EXISTING ENTERPRISE Nancy Maluso VP & GM Sonus Networks 14
Enterprise Network Architecture Web Services WebRTC enabled Browser (HTTP) (SRTP/DTLS) and STUN Checks (HTTP) SIP Web Server (1) WebRTC Gateway (2) (SDP & ICE) SBC (3) (SIP) IPPBX/ Telephony Application Server (RTP / UDP) STUN/ TURN Server (4)
Web Services (HTTP) Web Server (1) WebRTC enabled Browser (SRTP/DTLS) WebRTC Gateway (2) SBC (3) (Dial-out only) PSTN (SIP) STUN/ TURN Server (4) (RTP)
Component Roles WebServer (1) WebRTC Gateway (2) SBC (3) ICE: STUN and TURN (4) Provide HTML and Java Script to the Browser include webrtc code Host applications and services Communicate to separately hosted applications via RestAPI Provide SDK Receive requests for communications Convert HTTP requests to SIP Send SIP request to appropriate entity May be part of SBC Or attached to PBX or other comm components Secure the network Provide interoperability: Transcode media Transrate media Translate protocols Normalize SIP Implement and enforce network policy (routing rules) May also host applications and services (eg. Recording) ICE is the process that enables NAT (firewall) traversal STUN: uses discovery to provide public IP address TURN provides port information May be part of SBC 17
Packaging IPPBX/ Telephony Application Server WebRTC Gateway (2) SBC (3) WebRTC Gateway (2) STUN/ TURN Server (4) 18
Enterprise Network Architecture Web Services Web Server (1) WebRTC enabled Browser WebRTC Gateway (2) IPPBX/ Telephony Application Server SBC (3) (RTP / UDP) STUN/ TURN Server (4)
Multiple Back End Systems Web Services Web Server (1) WebRTC enabled Browser SBC (3) 20
Questions 21