Jingle Nodes Updates

Jingle Nodes will complete 9 months of official Specification published. As suggested by @luissoeiro, I will summit what happened so far.

• Erlang Relay based on exmpp fully compatible with ejabberd and Tigase
• jn_erl_0.1.0.tar.gz
• Openfire Plugin, it is a simple and plug and play Plugin for Openfire
• jingleNodes.jar
• OneTeam client from process-one with full support for Jingle Nodes
• http://oneteam.im/
• Talkr.im a public XMPP Server from process-one with full support for Jingle Nodes
• http://talkr.im/
• Professional Logo contributed by Fernando Lins
• Jingle Nodes Selo.png
• Jingle Nodes Presented in 3 key events and confirmed other
• FOSDEM 2010
• SeaBeyond
• FISL11
• Campus Party Brazil 2011
• SIP Communicator announced Jingle Nodes Support is being added to main Version
• http://sip-communicator.org/
• Special thanks to NLNet that sponsored contributions and ignited the project
• http://www.nlnet.nl/

How to contribute to Jingle Nodes:

• Writing Code and Discuss the Specification - All fixes, patches and suggestions are always welcome (Jingle Nodes Group)
• Talk about the project - Talk about Jingle Nodes simplicity and how it's easier than other alternatives
• Propaganda - Add a Jingle Nodes Image to your Blog or Website (Jingle Nodes Selo.png)
• Write a Tutorial - Describe how you are making use of Jingle Nodes
• Testing and giving feedback - Your opinion matters!

Jingle Nodes at FISL 11

New Jingle Nodes Specifications will be presented at FISL 11. Besides the regular updates about the specifications, it will also be discussed Jingle Nodes adoption plan and current implementations.

FISL takes place in Porto Alegre and it is the biggest OpenSource and OpenStandards event of Latin America.

Other XMPP topics like Openfire and ejabberd deployments (presented by the current Openfire maintainer Guus der Kinderen), and also clients like OneTeam/SIP Communicator Jingle Nodes Demo etc.

Especial Thanks to:

• NLnet Foundation who sponsored the development of the prototype APIs for Server and Client. And the whole campaign of the specification publish.
• Fernando Lins for the awesome and professional new Jingle Nodes Logo.

STUN Discovery via JIngle Nodes

After a few months finally I got time to review and update Jingle Nodes Specifications. It is not yet submitted to xmpp.org, but you can sneak peak for now at: Jingle Nodes [Temp]
The most relevant change is that Jingle Nodes now will support STUN Tracking, which means that users can also share known STUN Servers. This is very handy and most of all, it is very easy to access STUN Servers as they not require authentication for Public IP Discovery.
After all, the most popular XMPP Servers in the market already offers embedded STUN Service (ejabberd STUN).
Google Talk Network also provides STUN Services, so they can also be shared through Jingle Nodes.

Another minor fixes and changes were also added.
Please fell free to read and submit critics and comments to it.

Jingle Nodes - So far

After Jingle Nodes got submitted to XMPP.org inbox, the number of visits on the website and the Specifications grow at least 100%. This is a great step towards an OpenStandard P2P VoIP.
Imagine that the very first implementation was in Openfire in 2006, which was kind of rejected by several Jingle Developers(due STUN/TURN promiss) but accepted and used by SIP Community back there(which knew STUN/TURN are painful for P2P). 

In summary we already accomplished:

• In 2010, we have the specification on XMPP.org inbox: http://xmpp.org/extensions/inbox/jingle-nodes.html
• In 2010, we have the specification accepted as 'Experimental' on XMPP.org: http://xmpp.org/extensions/xep-0278.html
  
• Server Side Component 100% ready to use - Check http://xmppjingle.org for Download and Sources
• Client Side API (60% done) -  Check http://xmppjingle.org for Download and Sources
• Demo Client (Under Selection) - If you are a Client developer of an OpenSource XMPP Client and have interest on Jingle Nodes supports, you are a potential candidate. Contact us.
• Sea Beyond - Paris, 17th December 2009: Jingle experimenting session and a presentation, which is a new technical event that explores the future of real-time communication technology. It is organized by ProcessOne, an authority in XMPP and real-time communication software. 
• FOSDEM 2010 - XMPP Devroom @FOSDEM 2010 Presentation and Investigation about other P2P Solution adopted by Jingle Developers
• Talkr.im - The free IM service Talkr.im is running a public Jingle Nodes for their users. 

Special thanks:

NLnet foundation financially supports organizations and people that contribute to an open information society. And NLnet is sponsoring Jingle Nodes Contributions and Developments which also explains the fast development and accomplishments of the project. The community of OpenStandards and Specially all involved with Jingle Nodes project are proud and thankful for having such a great foundation helping and incentive towards XMPP and Jingle Freedom.
Jingle Nodes is a specification based on implementation and deployment needs, meaning that we have it first running and compiling, for later publish of the complete specification. Which makes it a ready to use technology and not only a technology paper. Thanks NLnet :)

What we have in the horizon:

• An Official recommend demo Client.
• A New Better Professional Logo contributed by Fernando Lins
• More Corporate and Public Deployments.
• Specification Improvements and Approval.
• Adoption in major Jingle Clients.
• Events. We LOVE Events and Invitations!

Running Code

It has been just a few days since Jingle Nodes alpha XEP was dropped in XMPP.org inbox, and we already have running code :)
Talkr.im announced today that they are running a Jingle Node Public Relay in their Server, and every Talkr.im user can make use of it for Jingle Calls.

They are running the code from http://xmppjingle.org (Erlang Version), which holds main Jingle Nodes Contributions.

In order to consume their Relay services you just need one IQ Packet (see http://xmpp.org/extensions/inbox/jingle-nodes.html )

Lets see who will be the first to distribute a Jingle Client with Jingle Nodes support!