A talk about me discovering new architectures, new ways of building scalable realtime platforms #SIP #WebRTC #Kamailio #MQTT #NODERED Watch it live at https://www.youtube.com/watch?v=BbfUXUWtxIg

1. Having fun with
new stuff.
MQTT, SIP, Kamailio, Baresip, Janus, Node-Red
- what a lovely platform! Kamailio World 2018, BerlinOlle E. Johansson
@oej

2. Or:
“I should have
listened to
you all”

3. Life changes and you
gotta change with it.

4. Think.

5. Getting
restless…

6. Home automation
is dangerous.

7. …it will cause a lot of
boxes coming home
in your mail…
Solarpowered
Raspberry PI and pump
for my garden.

8. It’s a mess
Pretty much
like the early days of
VoIP
Z-wave
OpenThread
Unprotected
433
Zigbee
BLE
LoraWan
Wifi
6lowpan

9. Multiprotocol message
engines
The Open Source Asterisks of this world
Domoticz, Home Assistant and many more

10. No focus on security at all
Pretty much like the
early days of VoIP.

11. Found a gem: Node-red
nodered.org

13. Started to hack and get used to event
driven development outside of Kamailio
A lot of fun!

14. Brought Node Red to work.
Create a lot of cool stuff quickly.
Had a lot of fun.

15. But Node-red is one server only… What
if we add networking. Events over a
network.

16. In comes a message bus

17. The task
Transport data from sender
to one or many recepients

18. The requirement
Decouple sender and receiver.
They do not have to be aware of each other.

19. The Oppurtunity
When you make data streams available,
development will happen, integration will happen.
Without a lot of time-consuming meetings.

20. Multiple choices (again)
AMQP
SIP
COAP
MQTT

21. SIP
PubSub is, well, hrrmpf, not up to par when it comes
to interoperability
Has a lot of the features needed for intelligent message
routing
Sucks when it comes to security
Not many 3rd party libraries available

22. COAP
Developed for IoT
An IETF standard, HTTP-inspired
Not that many implementations and libraries yet
Has a lot of bling

23. MQTT
Developed for IoT
Not an IETF standard, which shows
Runs on tiny devices
TCP and TCP/TLS
Many open source brokers and client libraries
Lacks almost all bells and whistles, which may be a good
thing

24. Surprise: the Will
Client Server
Client
will
When client for some reason is
disconnected, the server will publish
the will.
At connect, the
client may publish a will

25. Data: JSON - 95% of the
time spent.
{
“version” : “1”,
“device” : “lh-101-01”,
“event” : “boot”,
“device-type” : “transporter”,
“ip4address” : “192.168.0.1”,
“ip6address” : “”,
“coreversion” : “1234”,
“sysversion” : “123”
}

26. Important lesson
Your choice of protocol is not the
biggest investment to protect.
It’s the data formats and the topic/
channel structure that matters
Most of the time, you can bridge
between protocols.

27. We picked MQTT
Simple starting point.

28. Added MQTT to our Janus
MQTT control (and admin) channel existed
MQTT event API support added
Connected that to Node Red

29. Added MQTT to our
Kamailio
Failed miserably in writing a Kamailio module.
Mistakenly tried based on AMQP module code.
Gave up and use exec to run mosquitto Publish from
shell.
Publish registration and dialog events

30. Added MQTT to BareSIP
Remote control of BareSIP user agent
RTCP stats during a call
Connected to node red

31. Testing
Node red based services
MQTT
Kamailio Janus BareSIP
Other
apps
MySQL
Grafana
GUI
Push/
SMS

32. What’s the benefit

33. No more
monoliths
Big fat applications
with integrated web UI
Stats, presentation, events, logs,
control of devices
EVERYTHING!

34. Message
bus
Producers Producers Producers
Consumers Consumers Consumers

35. Yeah I know.
You tried telling me. Sorry.

36. So where now?

37. Security
Authentication
Integrity
Confidentiality
There’s a lot of
work to be done.

38. How far will Node red go?
We don’t really know yet.
But development quickly gets spaghetti-like when
things grow
Looking for a new architecture to complement
and scale and not loose control while still doing
load balancing and having failover and… All good
things.

39. Microservices!
Trying to find a
platform for scaling
with microservices.
Docker, LXC etc
Seems like a world
focused on HTTP
with port forwarding
over IPv4 NATs

40. What I am
looking for
Multi protocol
IPv6 infrastructure
TLS security built in
Identity handling
API-controlled

41. Finally I get it.
Kamailio event
routes
Kamailio KEMI
Kamailio AMQP Kamailio NOSIP
Kamailio HTTP Kamailio JSON api
As always, Daniel is way
ahead of me.

42. Kamailio is already aboard,
more than ready for this.
Are you?
I wasn’t.

43. Reminders
The PBX is dead.
IPv4 is dying fast. Get aboard IPv6 now.
#MoreCrypto - TLS everywhere!
Kill the monoliths. Build for scale.
Join OpenfreeLibPRI.org - now with ISDN over WebRTC
datachannels
Have fun!
@oej