LICENSE
This software is released under GPL License version 3 or any later version. Please read this license in gpl.txt if not already done.
SPECIFICATION
Peers is a software phone (softphone) compatible with the following specifications:
PREREQUISITES
This software has been developed using Oracle Java Development Kit version 7. You should install the latest Java Runtime Environment on your computer if you just want to run the application. If you want to compile the sources yourself, you should use the JDK. In both cases, you can download the installation files here: http://www.oracle.com/technetwork/java/javase/downloads/index.html
CONFIGURATION
Your SIP account credentials can be configured in conf/peers.xml. Please read comments in this file for configuration details. This configuration file is ruled by a grammar file: peers.xsd. Thus to modify this file, you can use jEdit with XML and Error list plugins. You can download jEdit here: http://www.jedit.org/index.php?page=download This provides xml completion and grammar checking which can be very useful to avoid simple configuration errors. You can also configure your SIP account using graphical user interface.
RUNNING
If you are a Windows user you can use the .bat batch script in root directory, if you use any Unix compatible sytem, you can use the .sh script. You can also double click .jar file. You can then call any IP address using SIP protocol, if the remote host does not listen on the default SIP port (5060), you can use the following example URI: sip:192.168.1.2:6060 For some softphones, it is necessary to add a userpart to the called sip uri, for example: sip:alice@192.168.1.2:6060
If you configured a sip account in configuration file or using gui, you can also place calls with usual sip uris: sip:bob@biloxi.com
Advanced users can run several peers instances on the same computer.
In this case a folder should be created in peers root directory for
each peers instance. This folder should contain three directories:
conf, logs and media. conf should contain peers.xml and peers.xsd for this
instance. peers.xml will need to be updated with this instance
parameters, peers.xsd can be copied from root conf directory. You will
need to do this for each instance.
Here is an example configuration:
peers/ user1/ conf/ peers.xml peers.xsd logs/ media/ user2/ conf/ peers.xml peers.xsd logs/ media/
Once all those files have been created and updated, each instance can be run providing a java system property giving peers home directory:
java -classpath build/classes -Dpeers.home=user1 net.sourceforge.peers.gui.MainFrame
As a Main-Class has been defined in jar manifest, you can also use the following command line:
java -jar build/peers.jar -Dpeers.home=user1 net.sourceforge.peers.gui.MainFrame
HISTORY
2007-11-25 0.1 First release
minimalist UAC and UAS.
2007-12-09 0.1.1 First release update
moved startup scripts in root directory
2008-03-29 0.2 Second release
New features:
2008-06-08 0.3 Third release
New features:
2009-09-23 0.3.1 Peers resurrection
New features:
2010-12-13 0.4 Peers GUI
New features:
2011-05-19 0.4.1 Bug fixes
Bugs fixed:
2011-07-04 0.4.2 Bug fixes
Bugs fixed:
2011-09-06 0.4.3 Various improvements
New features:
Bugs fixed:
2014-05-01 0.5 Maven release
AUTHOR
Yohann Martineau yohann.martineau@gmail.com