Erlang Version of Jingle Nodes Services is Working!

We are moving very fast with the Erlang version of the Jingle Nodes Services API, after 2 weeks of finishing the Pure Java Version, with great help from contributors, we have a working Erlang Version.
I invite you to check the code at: Jingle Nodes Source
It is based on the excellent exmpp library which besides being rich featured, is also pretty straight forward to use and reliable.

The current version can provide fully working relay channels, but still lacking some features:

• Detect Inactive Channels
• Purge Inactive Channels
• Tracker Services Provider

And indeed we have some bugs to be catch.

Contributions are really welcome!


How to Contribute?
Check the current opened issues: Jingle Node Issues
Send me an email with your intentions or if you wanna go one step ahead, patches are also accepted.

Erlang RTP Proxy

If you question yourself why move to an Erlang RTP Proxy if you are using openSER, Asterisk, or any other SIP based service. I can also say that the benefits don't seen so clear too.

But it turns out to be coolest solution for Jingle Raw-UDP Proxies! As you can integrate with your EJabberd as a module.

Check http://code.google.com/p/erlrtpproxy/ for the RTP Proxy application.

I've developed several RTP Proxy based on XMPP for the last few years, including Openfire RTP Bridge, which is pure Java and embed in all Openfire deploys.

Stay tuned! I will publish the RTP Proxy Module for EJabberd soon!

But I can give you a hint that this one looks specially promising: