Friday, March 5, 2010

Jingle Nodes - So far

After Jingle Nodes got submitted to 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 inbox:
  • In 2010, we have the specification accepted as 'Experimental' on
  • Server Side Component 100% ready to use - Check for Download and Sources
  • Client Side API (60% done) -  Check 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
  • - The free IM service 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!


  1. Will this be compatible with Empathy/Telepathy? There, the Jingle works well now even through firewall...

  2. I can participate in the early adopter programme. Iam a good java programmer too .....

    Please send me further details :