Tuenti + WebRTC Telco 2.0´s Challenges

1. Tuenti + WebRTC
Telco 2.0 ’s Challenges
!
!
!
!
Pablo Ruiz
pruiz@tuenti.com
!
!
!
!
Pedro Álvarez
palvarez@tuenti.com

2. Why we are here?
Recount our journey, from the very
beginning to our success.. :P

3. Our Mission!
Provide the best
over-the-top
experience to
Tuenti’s customers.

4. An inbound & outbound VoIP service
… Using the customer’s already existing GSM number!
… With no additional data charges!
… Working on any environment condition!
… With the best voice quality available!
… Integrated with existing Tuenti features (like chat, social app, etc.)
… Available on any platform (iOS, Android & Web)!

5. why choosing
WebRTC in first place? 0

6. …Or, what’s wrong with
using a SIP SoftPhone?

7. already using
WebRTC
for
App2App calls

8. THE CHALLENGES

9. Challenge #1: Multiples platforms..

10. Challenge #2: The signaling..
WebRTC has no ‘official’ signaling…

11. Challenge #2: The signaling.. (II)
Why not reusing our XMPP / Chat
infrastructure…
…as our signaling transport?

12. Challenge #2: The signaling.. (III)
<tangle action='session-initiate' sid='dd'>
<sdp>
<![CDATA[
Tangle!
signaling protocol
over XMPP
SDP
]]>
</sdp>
</tangle>

13. Challenge #2: The signaling.. (IV)
Got it, but…
What’s wrong with WebRTC + SIP?
WebRTC
+
SIP

14. Challenge #3: Talking SIP..
However, we should be talking SIP
to our SBCs… but, how?

15. Challenge #3: Talking SIP.. (II)
And, how can we develop an ALG?
Say hello to Mobicents Java Stack

16. Challenge #4: Telco incompatibilities
WebRTC has quite funny requirements
• SRTP
• TURN
• STUN
• ICE

17. But don´t worry,
your vendor is there
to help you!

18. Challenge #5: The codec..
• G.729?
• G.723?
• iLBC?
iLBC, for the win?

20. GGSN
SBCs
BSS
SMSC
HLR
OCS
AuC
STP
FreeSwitch
Kamailio
This was our existing environment…
WAS
DataBase
REST / WS
. HAProxy
IM / Chat
…with the void we had to fill

21. Attempt
Let’s ¿KISS?! 1

22. GGSN
SBCs
BSS
SMSC
HLR
OCS
AuC
STP
Our first attempt looked like:
DataBase
REST / WS
. HAProxy
IM / Chat
Beautifully simple, isn’t it?
. HAProxy . HAProxy
ALG+MLB
ALG+MLB
ALG+MLB
ALG+MLB

23. Session replications?
Only if you use Jboss 5.1
(released on 2009)

24. Well, not really.. even using Jboss
5.1, session replication is not
available at Mobicents’ master

25. Mobicents LB.. WTF?
Houston, we need a (real) load balancer

26. ABORT!!
ABORT!!
MISSION!!!

27. Attempt
This time using a real
load balancer 2

28. GGSN
SBCs
BSS
SMSC
HLR
OCS
AuC
STP
Our second attempt looked like:
DataBase
REST / WS
. HAProxy
IM / Chat
ALG+MLB
ALG+MLB
ALG+MLB
Ok, still a somewhat ‘simple’ setup…
ALG#1
ALG#2
ALG#3
ALG#4
Kamailio Kamailio
. HAProxy . HAProxy
ALG+MLB

29. But.. humm.. ehmm.. ehem..
our SBCs support ICE?

30. Ooops.. ABORT!

31. Attempt
We need to handle
media too… 3

32. GGSN
SBCs
BSS
SMSC
HLR
OCS
AuC
STP
Our third attempt looked like:
DataBase
REST / WS
. HAProxy
IM / Chat
Kamailio Kamailio
May be not so KISS, anymore.. :(
ALG#1
ALG#2
ALG#3
ALG#4
. HAProxy . HAProxy
RTPEngine
RTPEngine

33. ISSUES
ISSUES EVERYWHERE

34. Well in the end RTPEngine was
too good to be true ™, and not
‘mature enough’..

35. … ABORT! …

36. Attempt
FreeSwitch as media
transcoder FTW! 4

37. GGSN
SBCs
BSS
SMSC
HLR
OCS
AuC
STP
Our fourth attempt looked like:
DataBase
REST / WS
. HAProxy
IM / Chat
RTPEngine
Kamailio
Kamailio
RTPEngine
Dude this is starting to look a bit messy..
ALG#1
ALG#2
ALG#3
ALG#4
. HAProxy . HAProxy
Trans #1
Trans #2
Trans #3
Trans #4

38. SUCCESS!! o/
CHALLENGE
ACCOMPLISHED

39. Achieving nirvana!
Yes.. success! But this is
really the ‘best experience’
we were looking for? 5

40. iLBC they said..

41. Do all codecs perform the same on every
platform? Not really.. :(
OPUS ISAC OPUS
(NB, 8k, VBR)

42. And even in some extreme cases,
some terminals had not enough
power to move WebRTC (with
any valuable codec)

43. (Codec) Performance testing

44. !
Diagnosing…
what’s going on in our house?

50. Devastating
Victory

51. Summarizing
when using WebRTC against your
favorite telco...

52. Do not believe it when a SBC/
Switch vendor tells you it
‘supports’ WebRTC.

53. Avoid SIP/TLS if you can..
(or at least do not try to do SIP/TLS
end2end against your telco stuff)

54. Try to setup something in between
in charge of SRTP, ICE & Media
Transcoding..

55. Choose carefully the codecs and
their parameters..

56. Consider implementing a feature
capabilities mechanism into your
application..

57. Setup a smart load-balancing
& failover strategy..

58. Thanks!