Upgrade to Pro — share decks privately, control downloads, hide ads and more …

immmr - transition from a commercial CPaaS to an open-source communications backend

immmr - transition from a commercial CPaaS to an open-source communications backend

immmr - transition from a commercial CPaaS to an open-source communications backend

Presented 2019-05-07 at KamailioWorld in Berlin, Germany

Sebastian Schumann

May 07, 2019
Tweet

More Decks by Sebastian Schumann

Other Decks in Technology

Transcript

  1. immmr - transition from a commercial CPaaS to an open-source

    communications backend Sebastian Schumann | Kamailio World Berlin | 2019-05-07
  2. immmr Our transition to an open-source based communications backend 2

    ▪ immmr was a DT company, founded 2015, closed 2018 ▪ immmr mashed up traditional carrier telephony with 21st century voice and video for new communication experiences ▪ Server-side: AWS, private Kandy.io instance, own micro-services based backend (integration stack for INAP, SIP, REST; OSS; BSS), privacy & security compliance ▪ Client-side: web/iOS/Android with Kandy.io SDK, immmr SDK ▪ 04 - 07/2018: Kandy.io replacement with (mostly) open SIP based components
  3. Stack Transition Our transition to an open-source based communications backend

    3 immmr SDK PortSIP SDK immmr facade micro services immmr comms core interconnect immmr SDK Kandy SDK immmr facade Kandy API micro services comms core interconnect
  4. ▪ AWS EC2 ▪ AWS Lambda ▪ AWS API gateway

    ▪ Node.js ▪ JSSIP SIP SDK (web, server-side) ▪ PortSIP SIP SDK (iOS) ▪ Kamailio SIP server ▪ rtpengine media server ▪ coturn TURN server ▪ Homer capture & monitoring server Comms Core Replacement Stack Our transition to an open-source based communications backend 4
  5. 5 Homer Kamailio rtpengine coturn Core Comms VoIP rest-gw MySQL

    http_client HTTPS REST SIP/WSS SIP/UDP SIP/UDP SIP/TLS SRTP RTP rest2sip
  6. Positive Experience & Gaps Our transition to an open-source based

    communications backend 6 ▪ Replacement was quick, Kamailio’s flexibility help to adapt quickly ▪ On-net voice + PSTN/SMS break-in/-out working well ▪ iOS <> web interworking challenging (=> Homer) ▪ Client-side challenging for dev’s ▪ Open: Production readiness (orchestration, automation, HA, Push) ▪ Modern Programmability of Kamailio stack to be improved Marten Sebastian We are looking forward to discussing with you! 2019-05-07 v4