Peer-to-Server Media in WebRTC (Enterprise Connect 2014)

COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED.

Peer-to-Server Media in WebRTC

Chad HartEnterprise Connect 2014

COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 2

Peer-to-Peer vs. Peer-to-Server

client client

signa

ling

signalingmedia

media

Media Server

Signaling Server

Peer-to-Server

Server

client client

signalin

gsignaling

media

Peer-to-Peer


Design Trade-offs – Cost vs. Performance vs. Location

Application Performance

Server Performance

Client Performance

Higher infrastructure

costs

Battery lifeSpeed

Quality expectations


When does server-side WebRTC make sense?

Limited bandwidth

Expensive bandwidth

Power limitations

Regulatory requirements


PowerMedia™ XMS

Multi-party mixing InterworkingTranscoding

Stream processing Person-to-machineRecording

WebRTC Media Processing Use Cases


Case Study – the Airline

6

Airline

Airline

TravelAgent


Video-enabling a Contact Center

Web App Server

Media Control

WebRTC Signaling

HTTP/REST

Media Interface

SBC Media Server

SIP

RTP

Contact Center

WebRTC Signaling

SRTP

PSTN

PSTN Customers

Agents

ACD

Kiosk Customer

SRTP

RTP

SIPHTTP

HTTP/REST


Case Study – the Airline

8

TravelAgent

TravelAgent

TravelAgent

Lessons Learned:• Applications are viable today when you have

end-to-end control• Leveraging existing infrastructure shortens

time-to-market• Assume you will have poor connectivity• Be careful with variable cloud latencies

192.168.1.122Kindle Fire HDX

RFC5766-TURN-Server

ec2-54-227-235-160.compute-1.amazonaws.com

SBC?

na4.edge-gacd.amazon.com

Port 45563

Port 29548RTP - G.711u

Port 59522

Port 3478RTP Type -116, RTCP

RTP Type -100, RTCP

Web Signalin

g

Kconnect-us.amazon.com

Port 443

HTTPS

Port 46011

TLSPort 443

Port 40787

Port 29549RTCP

Amazon Kindle HDX Mayday button Wireshark trace

http://webrtchacks.com/mayday-trace/

192.168.1.122Kindle Fire HDX

RFC5766-TURN-Server

ec2-54-227-235-160.compute-1.amazonaws.com

SBC?

na4.edge-gacd.amazon.com

Port 45563

Port 29548RTP - G.711u

Port 59522

Port 3478RTP Type -116, RTCP

RTP Type -100, RTCP

Web Signalin

g

Kconnect-us.amazon.com

Port 443

HTTPS

Port 46011

TLSPort 443

Port 40787

Port 29549RTCP

Amazon Kindle HDX Mayday button Wireshark trace

http://webrtchacks.com/mayday-trace/

Audio

Video


PowerMedia XMS

Virtualized Cloud-ready

AudioVideo

WebRTC

Robust Developer APIs

Standardized Production Interfaces

real-time media processing platform


SIP Web Java Speech

Audio Video WebRTC CPA

PowerMedia™ XMS

Media Platform for Developers & IT

RESTful

Java (JSR.309)

VXML

MSML

NETANN

MRCPv2

JavascriptPow

erfu

l Med

ia A

PIs

PowerMedia XMS

Diverse Developer Audiences

Extensive Capabilities


WebRTC Gateways


“Legacy” Telephony Gateway Functions

HTTP-to-SIP(H2S)

Media GW

Transcoder

NetworkWebRTC Users Phone User

User-defined Signaling

WS/COMET/BOSH

SRTP-DTLS

UDP/TCP

SIP

RTP/SRTP-SDES

UDP

OPUS/VP8 G.7XX/H.264


WebRTC Gateways Come in Many Packages

HTTP-to-SIP(H2S)

Media GW

Transcoder

HTTP-to-SIP(H2S)

Media GW

Transcoder

HTTP-to-SIP(H2S)

Media GW

Transcoder

HTTP-to-SIP(H2S)

Media GW

Transcoder


Will One H2S Gateway be Sufficient?

Retail Click-to-Call

Enterprise Click-to-Call

Residential Web Phone

RCS Web Client

Developer API exposure

Remote Agent

Remote Worker

HTTP-to-SIP(H2S)

IMS/RCS

RFC3261 SIP

Microsoft SIP

Application specific APIs work best SIP is sort-of standard


Media Requirements More Uniform than H2S

H2S

Media GW

Transcoder

NetworkWebRTC Users Phone Users

Web Signaling

SRTP-DTLS

UDP/TCP

RTP/SRTP-SDES

UDP

OPUS/VP8 G.7XX/H.264

H2S

H2SSIP

H2S

Control Interfaces

Peer-to-Server Media in WebRTC (Enterprise Connect 2014)

Technology

company confidential

server peer

media requirements

media processing platform

turn server

h2s gateway

best sip

packages http