Webrtc - rich communication - quobis - victor pascual
WebRTC: been there, done that
Quobis is a leading european company in the delivery of
carrier-class unified communication solutions with a
special focus on security, interconnection and identity
management for service providers and enterprises.
Seven years working on VoIP projects.
Three years developing own products.
Victor Pascual – Chief Strategy Officer (CSO) at Quobis
Main focus: help make WebRTC happen – involved in WebRTC
standardization, development and first industry deployments (on-going RFX's,
PoC's and field trials)
- IETF contributor (SIP, Diameter and WebRTC areas)
- IETF STRAW WG co-chair
- SIP Forum WebRTC Task Group co-chair
- WebRTCHacks.com co-founder and blogger
- Independent Expert at European Commission
What does Quobis provide? KNOW-HOW
“Set or RTC APIs
for Web Browsers”
Some discussion on the topic: http://webrtchacks.com/a-hitchhikersguide-to-webrtc-standardization/
WebRTC does not define signaling
Don’t panic, it’s not a bad thing!
from web server. Popular choices are:
SIP over Websockets
Extend SIP directly into the browser by embedding a SIP stack directly into the
WebSocket create a full-duplex channel right from the web browser
Standard mechanism (draft-ietf-sipcore-sip-websocket) – soon to be RFC
Popular examples are jsSIP, sip-js,
QoffeeSIP, or sipML5
Call Control API
proprietary signaling scheme based on
more traditional web tools and techniques
GSMA/OMA extending RCS “standard” API to include WebRTC support
Other alternatives based on XMPP, JSON or foobar
Some discussion on the topic: http://webrtchacks.com/signallingoptions-for-webrtc-applications/
each deployment/vendor is implementing
its own (proprietary) signaling approach
Media plane (1/2)
A browser-embedded media engine
– Best-of-breed echo canceler
– Video jitter buffer, image enhancer
– Audio codecs – G.711, Opus are MTI
– Video codecs – H.264 vs. VP8 (MTI TBD - IPR discussion)
– Media codecs are negotiated with SDP (for now at least)
– Requires Secure RTP (SRTP) – DTLS
– Requires Peer-2-peer NAT traversal tools (STUN, TURN, ICE) – trickle
– Multiplexing: RTPs & RTP+RTCP
Yes, your favorite SIP client implementation is compatible with most
of this. But, the vast majority of deployments
Use plain RTP (and SDES if encrypted)
Do not support STUN/TURN/ICE
Do not support multiplexing (ok, not really an issue)
Use different codecs that might not be supported
on the WebRTC side
WebRTC signaling and media is
incompatible with existing VoIP
deployments – gateways are required to
bridge the two worlds
Media plane (2/2)
How do applications access the WebRTC media engine in
the web browser?
– Currently working on 1.0
2.0: Backward compatibility?
Competing API: CU-RTC-Web (Microsoft)
Competing API: ORTC (Microsoft and others)
Some discussion on the topic:
the WebRTC API can have different
WebRTC Client: SIPPO from Quobis
API to build
3GPP architecture (under discussion)
SIPPO Server = WebRTC Portal + more things
Third Party WebRTC-SIP gateway
SIPPO Server: Control, provision, configure and
customize your WebRTC Clients
● RESTful APIs for management of users and web
● Seven modules: Authentication, Authorization,
Accounting, Contact mgmt, Branding, File
● Connection to LDAP/AD for Authentication,
Authorization and Contact Management.
● Integration with Facebook, Gmail, etc.
● Support for identity federation
● Diameter for integration with backend.
Sippo Web Collaborator
Corporate endpoint fully-interoperable with
SIP networks and 3rd party WebRTC gateways
- Interactive chat
- Contact list
- File transfer
- Screen sharing
VoiceInstant: WebRTC "Happy button"
The call is transferred to
contact center application.
Agent's can use the same
client and applications
Customer visiting the website clicks
on "Contact us" button.
No need to enter any personal
number or to install any software
Customer can also see the agent's
Agents can use its own softphone or
SIPPO (a webRTC endpoint)
Chief Strategy Officer
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.