You have been asking for more documentation for long... and now it's there! Patience pays, Peers documentation contains two parts: one for all SIP softphones and one for Peers source code. It's important to read both. The first part gives an overview and a technical background to cope with Peers source code. The second part first gives architecture overview, then many UML diagrams are provided to understand quickly Peers source code, and to illustrate Peers implementation.
Enjoy, and please give feedback by e-mail: yohann.martineau at gmail dot com.
Peers is back, with improved media, compatibility with asterisk and many other cool features. Here is the changelog:
New features:
Improved features:
Peers configuration is still done using a simple xml file. This provides a good flexibility for peers, regarding other softphones. For more information, please read README.txt in peers archive. Acts are better than words, download latest Peers resurrection release now!
I've commited INVITE challenges support and transparent 401 or 407 management on subversion repository. To work with Asterisk, I still have to manage re-INVITEs correctly on peers.
Hello,
User accounts have now been activated, you can now:
I've been looking at Asterisk compatibility. For the moment 407 are not supported on INVITEs, I will try to implement this feature as soon as possible. I've installed a local asterisk, and an opensips... So as soon as I find a few hours, I'll add this feature.
Stay tuned!
For your information, the following HTML tags are available in comments: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
Hello, I've enabled Peers - SIP Related Experiments - nomination in sourceforge community choice awards. You can nominate Peers in two categories (at least):
Academia because most of support requests I receive come from students, doing their thesis, PhD or internships... But it seems that peers is also often used just for its sip stack, with many GUI improvements by professional developers.
So, if you want to support and help peers, please nominate peers on sourceforge community choice awards with the following link:

Thanks, and happy hacking with peers!
I'm very glad to announce that a new Peers release is now available, as usual you can download it here.
This release includes REGISTER management, as well as challenges and Digest, as specified in RFC2617 and MD5 hash algorithm. Thus a user can now register on a sip network.
This release has been tested against: x-lite, openwengo, linphone and ekiga for user-agents and against openser with db and auth modules for registration authentication. For registration, initial register has been implemented, register refreshes have been implemented and unregister has been implemented. Thus, when the user close the main window, a register message is sent to the registrar configured in peers.xml. For the moment, the password is stored as clear text in configuration file.
Another good news: a new test framework has been used on this release: testng. This powerful framework now replaces junit in peers. It enables unit testing, thread testing, group testing... it generates html result files and has also many very useful features. Media has been slightly improved in this release as audio capture, data compression and rtp packetization are now implemented in different threads.
For an exhaustive release note, please read README.txt in peers archive file.
Thanks for using and reading. Peers is still growing and many exciting features are coming. Stay tuned...
A new release has been created for peers: 0.2.
This new release contains new features and many bug fixes. All bugs have not been reported on the tracker page because they are generally remarked during development phase.
The goal of this release was to add provional responses management for peers (101-199 response range). In this release the only provional response implemented is 180 Ringing. But this provisional response is the main provisional response and the first one to implement in new stacks... Thus, when an INVITE is received on peers, peers automatically generate a 180 response and send it to the remote User-Agent. This also means that a popup window is now displayed to the user to alert him of a new call. The user can now accept or reject the call. If the call is rejected a 486 Busy response is sent.
On the other hand, when a remote User-Agent-Server rejects a call initiated by peers, peers cleanly closes the frame corresponding to the call.
Also, those provisional responses previously mentioned requires that CANCEL method be implemented, because if a User-Agent-Server sends a provisional response (with a To-tag), it must be able to handle a CANCEL for call termination. That is why CANCEL management has been implemented in peers, both at client and server side.
This version has still been tested on windows and linux, and against X-Lite 3, a popular SIP User-Agent.
An XML configuration file enables simple SIP stack parameters management. A grammar has been defined for this configuration file.
As usual, the download page will provide source and binary package zip files.
You can now download a new version of Peers. Actually this is not really a new version but a fix to the first one, which startup scripts was misplaced... By the way, a few bugs have been corrected. If you want to try Peers, try this one, it's the last and like often, the best version.
First release, brand new web site, doubtless a new open source project is born! The first Peers release: Peers 0.1 is available for download. Peers is a very minimalist SIP User-Agent, implemented in java and with very few dependencies. To be honest this is not a complete RFC3261 implementation, but as all story, it starts with the beginning... You can call a peer on a local area network using this software. But you first need to install the Java Runtime Environement 6.