![]() ![]() The following extracts maybe useful from the Internet Engineering Task Force (IETF), PROPOSED STANDARD document, Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN), at: if you want to test it, Conversation or Movim clients already support XEP-0215. It means that ejabberd can now be used by modern clients with audio/video calls features. To promote this usage, STUN/TURN service is now enabled by default in ejabberd. It also allows (non-XMPP) WebRTC applications to use ejabberd’s built-in STUN/TURN support. Therefore, in addition of the ejabberd’s built-in STUN/TURN support, the module can also be used with external STUN/TURN servers that support the same draft (such as coturn or restund). The format of the temporary credentials handed out to clients is described in an IETF draft. In addition to various bugfixes and improvements, this release massively improves audio and video calls support.Įjabberd now implements XEP-0215: External Service Discovery, via the new mod_stun_disco module, which allows XMPP clients to discover STUN/ TURN services and to obtain temporary credentials for using them. We are pleased to announce ejabberd 20.04. Interestingly a new release of eJabberd (20.04) came out two days ago (30th April 2020) and in the accompanying press release it says the following: Is there anything obviously wrong with my eJabberd STUN/TURN setup? Or any idea how I might verifiy my setup would be gratfully I wonder if you might be able to shed any light on this? I had the following reference to STUN and TURN connecting, but have been unable to replicate: 00:50:00.339 failed to process callback function ejabberd_stun:udp_init(#Port, [ Turn_ip: "MY-EXTERNAL-HOME-IP" # Your IP address (I can’t remember if the above line was the default or not!) "/etc/ejabberd/letsencrypt/MY-DOMAIN-NAME/ejabberd.pem"
0 Comments
Leave a Reply. |