A JAIN-SIP Instant Messaging Client For the People!

A JAIN-SIP Instant Messaging Client for the People!

1. What's in this package?

This package contains the source code of a JAVA based SIP IM client built on top of the JAIN-SIP-1.1 API.
The client is a pure JAIN-SIP application: it does not need proprietary nist-sip classes in addition of those defined in JAIN-SIP 1.1, you can substitute the NIST-SIP stack by another JAIN-SIP compliant stack and plug the client on top of it. This application was successfully tested with Microsoft Messenger, Siemens user agent, Cisqo User Agent and our SIP proxy, registrar, presence server

2. Client capabilities

3. The configuration frame

The client has a frame in the menu for initializing the client. Here are a description of each of the parameters that you can set up.

4. The XML buddies file

The XML file where to define the buddies to upload to the list. Here are a description of each of the parameters that you can set up. An example "buddies.xml" is given in the configuration directory.

5. The XML authentication file

The XML file where to define the user/password for a certain realm. Here are a description of each of the parameters that you can set up. An example "passwords.xml" is given in the configuration directory.

6. Start the client

Use the makefile (targeted for Linux) provided in this directory to start the client. The command to execute is: make imgui .
This command will start the JAVA process: java -Djava.security.policy=./configuration/policy examples.instantmessaging.InstantMessagingGUI -cf ./configuration/dagan.properties .

7. Build Instructions

You can rebuild the client using the command: make all in case of you wish to modify the source.

IMPORTANT:

if you get this exception when you start the client:

rebind : //129.6.50.116:0/nist-sip/gov.nist.javax.sip.stack.MessageLogTableImpl
class gov.nist.javax.sip.stack.MessageLogTableImpl exception: Connection refused to host: 129.6.50.116; nested exception is:
java.net.ConnectException: Connection refused: connect
java.rmi.ConnectException: Connection refused to host: 129.6.50.116; nested exception is:
java.net.ConnectException: Connection refused: connect

then you will not be able to see the traces using the viewer application. To remedy, you have to start the rmiregistry on a separate console and restart the client:
jdk1.3.1_06/bin/rmiregistry -J-Denv.class.path=c:/nist-sip-1.2/classes

If you experience any problems contact us at: Authors