The java.net site offers a utility called the Issue Tracker. Please use it to report bugs and suggest new features. In order to use the issue tracker you need to register as an observer of the sip-communicator project. You may also find it necessary to accompany your submitted issues with a letter to SIP Communicator's users or dev mailing lists.
We take bugs very seriously. To help us to quickly fix the bug, be sure to include as much information with your report as possible such as your platform, SIP Communicator logs or console output, configuration, and ethereal / tcpdump binary capture traces of your SIP Communicator sessions.
If you have a patch to submit, please mail it to the developer mailing list. Use the prefix "[PATCH]" on your message subject. Please include any relevant issue numbers. Diffs should be created with the "-u" option, for instance
cvs diff -u Main.java >> myPatchfile.txtdiff -u Main.java.orig Main.java >> myPatchfile.txtNote: You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file "patchfile.txt" but instead call it "foo-socket.txt". This makes it easier for developers who need to apply a number of different patches.