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.
Upcoming SlideShare
TCP/IP
TCP/IP
Loading in …3
×
1 of 76

The secret of TCP/IP and how it affects your PBX

24

Share

The PBX was invited more than 50 years ago, SIP over 10 years. And we still just implement ISDN over IP. Time for a reboot, time to raise the bar and use the standards that has been developed during the last 10 years.
This talk, originally presented at Voip2day + ElastixWorld in Madrid 2012, presents the Edvina SIP 2012 reference profile, the thoughts behind it and where we are heading.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

The secret of TCP/IP and how it affects your PBX

  1. The hidden secret of TCP/IP and the Internet. And how it affects your realtime platform. Olle E. Johansson * oej@edvina.net * Twitter oej Copyright Edvina AB, Sollentuna, Sweden 2012. All rights reserved.
  2. 1995. The revolution starts.
  3. 17 years later and we’re still imitating a PBX. Time to change.
  4. The PBX • Key line systems was introduced in the 50’s • One phone, multiple lines • The enterprise PBX was introduced in the 1960’s • Lowered the cost • internal calls where free • reduced need for outside lines Photo: Joseph A. Carr
  5. The PBX was the heart of the company. And the receptionist knew everything worth knowing in the company.
  6. • This is old stuff. Photo: City Light Photographic Negatives (Record Series 1204-01),
  7. And the PBX is no longer in the center.
  8. Cell phones Facebook E-mail IM / Chat Skype Presense
  9. What’s the theme here? The glue that makes this architecture work.
  10. TCP/IP
  11. What powers TCP/IP?
  12. INTEROPERABILITY
  13. What does this long word mean? INTEROPERABILITY
  14. INTEROPERABILITY INTEROPERABILI EROPERABIL The glue that keeps the Internet going.
  15. An agreement. INTEROPERABILITY.
  16. A promise. INTEROPERABILITY.
  17. A lot of work. INTEROPERABILITY.
  18. What drives it?
  19. Customers. Without customers controlling us, we can do whatever we want. And what our marketing people want.
  20. Results in the 90’s: After many years of work.
  21. TCP/IP E-mail WWW LDAP TLS
  22. TCP/IP E-mail Solutions we rely on. WWW Every day, every minute. LDAP TLS
  23. Where and when did it go wrong?
  24. Facebook Twitter Skype XXYY FaceTime
  25. Trademarks. Companies with one service. No interoperability. No distribution. Total dependency.
  26. We’ve gone backwards. I’m old enough to remember the past.
  27. IBM SNA Novell IPX Microsoft Lan Manager CC mail MS Mail DecNet
  28. IBM SNA Novell IPX This is exactly what Microsoft Lan Manager customers wanted to avoid. CC mail MS Mail Customer pressure delivered the PC, Unix and TCP/IP DecNet from vendors. networks. Freedom from lock-ins Saving money by protecting your investment.
  29. Who took over? Venture capital. Large companies. Ask yourself.
  30. How does this affect the PBX?
  31. We’re moving backwards in time.
  32. No focus on interoperability. Lync. Skype. Many others.
  33. Failed interoperability. For years. SIP SIMPLE Presense and IM.
  34. Proprietary telephone provisioning protocols. Digium - the ”open” telephony company
  35. WebRTC won’t help. WebRTC just makes it easier to provide proprietary communication systems.
  36. It’s time for all of you to wake up. Good morning!
  37. WAKE UP!
  38. Stop blaming the vendors. They sell what you buy. It’s in their best interest to lock you in. Keep you in control.
  39. The one with money has control. You are the customers. Use your power!
  40. <break> Think about it for a while. Do you really want to be controlled in your business? Limit your choices?
  41. What has happened in the world of SIP? Quite a lot. And nothing.
  42. 2002 RFC 3261 was published in 2002. Implemented to 80%. 2012
  43. 2002 SIP is based on the IETF architecture for TCP/IP. 10 years. And we still need to learn. 2012
  44. 2002 Distributed. Domain-based federation. A network of networks. 2012
  45. 2002 Scalable. Stupid core. Intelligent endpoints. 2012
  46. 2002 Connected. All hosts should be able to contact any other connected host. 2012
  47. 2002 Extensible. SIP solves one problem: Session management. What you do with it is up to you. 2012
  48. Where and when were these rules defined? Stupid core. Intelligent endpoints. Connectivity end2end.
  49. the goal is full "open system interconnection": an Internet host must be able to interoperate robustly and effectively with any other Internet host, across diverse Internet paths. RFC 1122, 1989
  50. However, isolated LANs seldom stay isolated for long; they are soon gatewayed to each other, to organization-wide internets, and eventually to the global Internet system. In the end, neither the customer nor the vendor is served by incomplete or substandard Internet host software. RFC 1122, 1989
  51. So where did we go wrong? We’re stuck with a 50 year old PBX architecture. A telco model forced onto the TCP/IP architecture.
  52. I have at least five chat apps, six voip apps. Using separate islands of communications. It’s way too complicated for someone soon 50 years old. E-mail doesn’t work that way.
  53. Take control of our communication. After 50 years with the PBX, we need to think in new ways for IP based realtime communication.
  54. 1. No inside/outside BYOD and 3G devices killed that paradigm.
  55. 2. Be able to trust the system. Apply Security.
  56. 3. No vendor lock-ins Be in control of your communication system.
  57. 4. Don’t trust yourself. Be open for innovation and evolution.
  58. 5. It’s personal. Focus on the individuals.
  59. 6.Video everywhere. With WebRTC two-way video will be in every browser.
  60. 7. Build for global communication. TCP/IP is both IPv4 and IPv6 today. Internet growth in Europe will only happen in IPv6.
  61. Keywords:
  62. IP TLS/DTLS Open SIP federation SIP in the organization Client diversity Realtime applications
  63. ”Computer! Localize Chief O’Brien” Speech is an important part of the future.
  64. ”We need something SIP-ish” Best effort procurement with poor specs. Known and proven to give bad results.
  65. SIP 2012. Much more than RFC 3261. WebRTC. Session timers. Opus. ICE. SRTP/DTLS. SIP Identity OUTBOUND. GRUU. And more...
  66. Stuff I’ve never seen in call for tenders. It’s time for change. WebRTC. Session timers. Opus. ICE. SRTP/DTLS. SIP Identity OUTBOUND. GRUU. And more...
  67. SIP2012 :: Defining modern requirements Helping customers procure better systems.
  68. Interoperability in realtime communications. SIP done right. As required by customers.
  69. Here’s what I want you to do.
  70. Aim to retire the PBX. Your company will survive.
  71. Migrate away from one-company-one- brand systems. Require interoperability.
  72. Update your specifications. Refer to the SIP2012 reference profile when buying SIP equiment and software.
  73. For SIP trunks: Refer to SIP Connect from the SIP Forum.
  74. Customers: Please take control.
  75. I want to be free. If you don’t want to be free, call your nearest <large company> representative today and ask him what you should buy next. And give him full access to your credit card too. www.open-stand.org
  76. Thank You. TACK! Mina damer och herrar! Photographs Copyright Olle E. Johansson http://edvina.net/sip2012

Editor's Notes

  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • ×