ejabberd - Robust, Scalable and Extensible Realtime Server using XMPP, MQTT and SIP
-
-
@jdaviescoates This or prosody I'd accept. Both are great XMPP servers.
The server should support at least Push (mainly for iOS/Android clients), HTTP upload, and PubSub.
And for the web interface, I'd vote for either converse or movim
-
@murgero I can't find the link now, but what led me to ejabberd was something about an update to Conversations now doing audio and video calls based on a recent update to ejabberd.
-
@jdaviescoates Ejabberd is more robust that prosody, but prosody is simpler to configure. I would prefer ejabberd as well tbh - Conversations is a nice app for Android.
-
Sounds like Conversations audio and video features working pretty well:
-
Just a few links that may be helpful if someone wants to try packaging it :
- https://docs.ejabberd.im/admin/configuration/database-ldap/#relational-databases
- https://docs.ejabberd.im/admin/configuration/database-ldap/#ldap
- https://github.com/processone/docker-ejabberd/blob/master/ecs/Dockerfile
- https://wiki.jabberfr.org/Intégration_de_LDAP_dans_ejabberd
On first glance, it seems quite packageable. The only thing that I think may be a bit of trouble would be some kind of web interface, to at least provide the Cloudron healthcheck.
I may end up trying to package it up if I have the time some day. But if anyone else wants to give it a go, be my guest!
-
@mehdi Interesting, I guess the SIP could be used with Jami? https://forum.cloudron.io/topic/2311/jami
-
@marcusquinn Honestly, not sure. I'm more interested in ejabberd for the XMPP.
But from a quick look at Jami, it doesn't seem that it needs a SIP server, only that it may use one. I think the point of connecting it to a SIP server is more for connecting to the actual phone system, so there wouldn't really be any point to connect Jami to ejabberd's SIP.
