WebRTC provides a simple and elegant solution for real-time communication. At the same time, it leaves all signaling and architectural questions open. What can companies do to close this gap in WebRTC infrastructure and how will it assist the ecosystem to grow and flourish?
You can find my impressions and more details about the conference here: http://bloggeek.me/webrtc-conference-wrapup/
9. Leave the web page
● Dial tone
● Numbering plan
● Identity system
9
10. Gatewaying
WebRTC Other
Transport SRTP RTP,
SRTP,
Circuit Switched
Codecs VP8 H.264
G.711, G.7xx,
Opus AMR-NB/WB, …
Signaling ? SS7, SIP, H.323, …
10
11. Gatewaying: Client Included
GW SIP / IMS
HTML5 Client
JS SIP / Other WebSocket
WebRTC SRTP
PSTN
● Gateway vendor offers the client side (SDK, Widget or
other)
11
12. Gatewaying: Programmable
My-service
GW SIP / IMS
HTML5 Client
?
WebRTC SRTP
PSTN
● Gateway vendor offers control APIs
● Customer build the client as he sees fit, interacting with
the gateway’s APIs from his own web server
12
13. Telephony:
Voice as we know it
● Conferencing
● IVR
● Recording
● Follow me
●…
13
14. How do we Add Telephony Services?
1. Gateway to PSTN
2. Gateway to SIP (VoIP)
3. Natively in new WebRTC media servers
15. Analytics
● Video
● Object tracking
● Face recognition
● Voice
● Text to speech
● Speech to text
● Sentiment from voice
http://bitly.com/bundles/tsahil/2
15