Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
jingle:
jabber does voip
peter saint-andre
stpeter@jabber.org
jingle
jabber does multimedia
what is jabber?
open technologies
real-time messaging
presence
powered by
streaming xml
jeremie miller
1998
tired
4 different im clients
multiple accounts
no interoperability
foster freedom of
   conversation
scratch an itch
open-source messaging
 and presence server
jabberd
january 4, 1999
more than a server
clients
libraries
add-on components
multiple server
 codebases
client-server
architecture
decentralized
  network
inter-domain
  messaging
like email
but really fast
with built-in presence
no server spoofing
and no spam
xml wire protocol
standardized
through ietf
extensible
messaging
and presence
protocol
(xmpp)
rfcs 3920 + 3921
more than protocols
50,000+ servers (?)
40+ million users (?)
clients
for every platform
libraries
for every language
deployed worldwide
wall street banks
u.s. government
hp, eds, fedex
orange, bell south,
sapo, ntt, sun rocket
google, apple, sun,
   live journal
and you
run your own server
write your own
 components
integrate with
your own systems
build competitive
    advantage
open technologies
this is a good thing
application server for
the real-time internet
layer 7 xml router
+ presence engine
low-latency
signalling channel
extensible from the
ground up (pure xml)
strong security
stable identities
dynamic capabilities
    discovery
and presence
“the new dial tone”
presence is boring!
presence is a catalyst
 for communication
jingle?
xmpp extensions
modular framework
multimedia session
  management
negotiate session
parameters over xmpp
use a binary-friendly
transport for media
pluggable transports:
rtp-ice, raw udp, etc.
pluggable session types:
    audio, video, etc.
sound familiar?
sip
why jingle?
community interest in
multimedia since 1999
enable jabber clients to
do voice, video, & more
need standards for
 interoperability
past approaches
h.323
proprietary xmpp
   extensions
“tins”
(sdp over xmpp)
dual-headed
xmpp+sip clients
issues
two centers of control
   (sip and xmpp)
addressing
(unicode in xmpp)
authentication
(mandatory in xmpp)
sender identity
(validated in xmpp)
traffic validation
(xmpp schemas)
manageability
(client-server in xmpp)
presence
(native in xmpp)
buddy lists [tm]
(native in xmpp)
presence subscriptions
 (long-lived in xmpp)
40+ million jabber users
    can’t be wrong
multimedia goodness
 to xmpp network
build a native xmpp
 signalling protocol
ensure interoperability
       with sip
not trying
to supplant sip
adding jabber users
to open voip networks
early version developed
      with sip guru
cto @ jabber inc.
  (they pay me)
google talk
standardization
   underway
jabber software
   foundation
specs in JSF’s
 XEP series
xep-0166 etc.
last call in progress
informational rfc
   (eventually)
support coming to...
google’s libjingle
 (c++ library)
many more
jabber clients
telepathy / gnome
freeswitch
various devices
(nokia 770, etc.)
providers, telcos,
hw/sw vendors
asterisk
federate pbx’s
over xmpp backbone
look ma, no bell!
(route around telcos)
gateways to
sip, h.323, pstn
open IETF standards
 + open extensions
open-source or
  commercial
mix and match
buy or build
deploy as you please
play with others
talk with everyone
innovate at the edges
no silos
no spam
no guano
open technologies
open network
the way life should be
join the conversation
let’s build the
real-time internet
Jingle
Jingle
Upcoming SlideShare
Loading in …5
×

Jingle

A basic introduction to Jingle, the Jabber-based VoIP technology.

Jingle

  1. 1. jingle: jabber does voip
  2. 2. peter saint-andre
  3. 3. stpeter@jabber.org
  4. 4. jingle
  5. 5. jabber does multimedia
  6. 6. what is jabber?
  7. 7. open technologies
  8. 8. real-time messaging
  9. 9. presence
  10. 10. powered by streaming xml
  11. 11. jeremie miller
  12. 12. 1998
  13. 13. tired
  14. 14. 4 different im clients
  15. 15. multiple accounts
  16. 16. no interoperability
  17. 17. foster freedom of conversation
  18. 18. scratch an itch
  19. 19. open-source messaging and presence server
  20. 20. jabberd
  21. 21. january 4, 1999
  22. 22. more than a server
  23. 23. clients
  24. 24. libraries
  25. 25. add-on components
  26. 26. multiple server codebases
  27. 27. client-server architecture
  28. 28. decentralized network
  29. 29. inter-domain messaging
  30. 30. like email
  31. 31. but really fast
  32. 32. with built-in presence
  33. 33. no server spoofing
  34. 34. and no spam
  35. 35. xml wire protocol
  36. 36. standardized through ietf
  37. 37. extensible
  38. 38. messaging
  39. 39. and presence
  40. 40. protocol
  41. 41. (xmpp)
  42. 42. rfcs 3920 + 3921
  43. 43. more than protocols
  44. 44. 50,000+ servers (?)
  45. 45. 40+ million users (?)
  46. 46. clients for every platform
  47. 47. libraries for every language
  48. 48. deployed worldwide
  49. 49. wall street banks
  50. 50. u.s. government
  51. 51. hp, eds, fedex
  52. 52. orange, bell south, sapo, ntt, sun rocket
  53. 53. google, apple, sun, live journal
  54. 54. and you
  55. 55. run your own server
  56. 56. write your own components
  57. 57. integrate with your own systems
  58. 58. build competitive advantage
  59. 59. open technologies
  60. 60. this is a good thing
  61. 61. application server for the real-time internet
  62. 62. layer 7 xml router + presence engine
  63. 63. low-latency signalling channel
  64. 64. extensible from the ground up (pure xml)
  65. 65. strong security
  66. 66. stable identities
  67. 67. dynamic capabilities discovery
  68. 68. and presence
  69. 69. “the new dial tone”
  70. 70. presence is boring!
  71. 71. presence is a catalyst for communication
  72. 72. jingle?
  73. 73. xmpp extensions
  74. 74. modular framework
  75. 75. multimedia session management
  76. 76. negotiate session parameters over xmpp
  77. 77. use a binary-friendly transport for media
  78. 78. pluggable transports: rtp-ice, raw udp, etc.
  79. 79. pluggable session types: audio, video, etc.
  80. 80. sound familiar?
  81. 81. sip
  82. 82. why jingle?
  83. 83. community interest in multimedia since 1999
  84. 84. enable jabber clients to do voice, video, & more
  85. 85. need standards for interoperability
  86. 86. past approaches
  87. 87. h.323
  88. 88. proprietary xmpp extensions
  89. 89. “tins” (sdp over xmpp)
  90. 90. dual-headed xmpp+sip clients
  91. 91. issues
  92. 92. two centers of control (sip and xmpp)
  93. 93. addressing (unicode in xmpp)
  94. 94. authentication (mandatory in xmpp)
  95. 95. sender identity (validated in xmpp)
  96. 96. traffic validation (xmpp schemas)
  97. 97. manageability (client-server in xmpp)
  98. 98. presence (native in xmpp)
  99. 99. buddy lists [tm] (native in xmpp)
  100. 100. presence subscriptions (long-lived in xmpp)
  101. 101. 40+ million jabber users can’t be wrong
  102. 102. multimedia goodness to xmpp network
  103. 103. build a native xmpp signalling protocol
  104. 104. ensure interoperability with sip
  105. 105. not trying to supplant sip
  106. 106. adding jabber users to open voip networks
  107. 107. early version developed with sip guru
  108. 108. cto @ jabber inc. (they pay me)
  109. 109. google talk
  110. 110. standardization underway
  111. 111. jabber software foundation
  112. 112. specs in JSF’s XEP series
  113. 113. xep-0166 etc.
  114. 114. last call in progress
  115. 115. informational rfc (eventually)
  116. 116. support coming to...
  117. 117. google’s libjingle (c++ library)
  118. 118. many more jabber clients
  119. 119. telepathy / gnome
  120. 120. freeswitch
  121. 121. various devices (nokia 770, etc.)
  122. 122. providers, telcos, hw/sw vendors
  123. 123. asterisk
  124. 124. federate pbx’s over xmpp backbone
  125. 125. look ma, no bell! (route around telcos)
  126. 126. gateways to sip, h.323, pstn
  127. 127. open IETF standards + open extensions
  128. 128. open-source or commercial
  129. 129. mix and match
  130. 130. buy or build
  131. 131. deploy as you please
  132. 132. play with others
  133. 133. talk with everyone
  134. 134. innovate at the edges
  135. 135. no silos
  136. 136. no spam
  137. 137. no guano
  138. 138. open technologies
  139. 139. open network
  140. 140. the way life should be
  141. 141. join the conversation
  142. 142. let’s build the real-time internet

×