I have long been hesitant about Kannel and things like ksmppd, maybe I should say why. It is definitely cool to integrate with mobile telco functions and having control over them. But I would love it more if it pulled away from their communication islands and integrate with other open source protocols and software.
I looked into ksmppd in the hope to find a link to Internet-style tools. In this case, a XMPP component could be useful, or perhaps a Kamailio / OpenSIPS plugin module for SIP MESSAGE routing. They could help to seemlessly integrate with VoIP infrastructure. Would love to have SMS for desktop phones and softphones, but even more to integrate it with plain XMPP chat. And it looks like ksmppd is close to that kind of use case.
I have been thinking if SMPP could be a protocol between domain names; I suppose for ENUM it can make sense (unfortunately an Internet Draft to that end didn't get completed) but there is no way SMS could compete with XMPP. Using the numbers however, can be a way to divert from WhatsApp and other number-based applications. This is where I come from, we designed generic authentication, self-provisioned online identity with Realm Crossover and a group mechanism with group member aliases that could be used like that, but on open protocols & software that users can control (instead of having the protocol control them).
Did I miss integration attempts between Kannel / SMPP / mobile telephony with open source protocols and software? I'd love to be proven wrong with a pointer to such code :) or otherwise I'd love to inspire a direction for ksmppd to be better integrated than a manually operated webinterface :)
I have long been hesitant about Kannel and things like
ksmppd, maybe I should say why. It is definitely cool to integrate with mobile telco functions and having control over them. But I would love it more if it pulled away from their communication islands and integrate with other open source protocols and software.I looked into
ksmppdin the hope to find a link to Internet-style tools. In this case, a XMPP component could be useful, or perhaps a Kamailio / OpenSIPS plugin module for SIPMESSAGErouting. They could help to seemlessly integrate with VoIP infrastructure. Would love to have SMS for desktop phones and softphones, but even more to integrate it with plain XMPP chat. And it looks likeksmppdis close to that kind of use case.I have been thinking if SMPP could be a protocol between domain names; I suppose for ENUM it can make sense (unfortunately an Internet Draft to that end didn't get completed) but there is no way SMS could compete with XMPP. Using the numbers however, can be a way to divert from WhatsApp and other number-based applications. This is where I come from, we designed generic authentication, self-provisioned online identity with Realm Crossover and a group mechanism with group member aliases that could be used like that, but on open protocols & software that users can control (instead of having the protocol control them).
Did I miss integration attempts between Kannel / SMPP / mobile telephony with open source protocols and software? I'd love to be proven wrong with a pointer to such code :) or otherwise I'd love to inspire a direction for
ksmppdto be better integrated than a manually operated webinterface :)