Look what Java and SIP can do
 (SIP)Java =
Home     News     Projects     Downloads     Support     Contact

SipUnit Home



Release Notes, TODOs, and Known Limitations

Release Notes for release 0.0.6b of SipUnit:
  1. Added support for running SipUnit tests from behind a NAT firewall or router while communicating with a SIP server on the internet. See SipSession.setPublicAddress(host,port) comments and TestWithStun.java for an example.
  2. Deprecated getLocalViaHeaders(), getLocalContactInfo() in favor of getViaHeaders(), getContactInfo().
  3. Incorporated enhancement allowing multiple SIP stacks to be created independent of IP address.
Release Notes for release 0.0.5b of SipUnit:
  1. Added additional high level class method signatures to take extra parms (body/headers) for request/response message sending.
  2. Incorporated the final release (version 1.2) of the SIP stack Reference Implementation kindly made available by National Institute of Standards and Technology (NIST).
  3. Fixed miscellaneous bugs.
Release Notes for release 0.0.4b of SipUnit:
  1. Incorporated the latest version (1.2) of the SIP stack Reference Implementation made available by National Institute of Standards and Technology (NIST).
  2. Added some SIP messaging enhancements (RE-INVITE, other misc.).
  3. Added an ant script for grouping tests together and overriding default test class parameters.
  4. Minor bug fixes.
  5. Moved to beta status.
Release Notes for release 0.0.3a of SipUnit:
  1. Added client-side SUBSCRIBE/NOTIFY handling (Type II).
  2. Added an utility class to simulate a presence server for the purpose of testing a Type II client.
  3. Added an asynchronous version of makeCall() and more SipTestCase methods: assertAnswered(), assertResponseReceived(x), etc.
  4. Fixed example directory structure in binary distribution packaging.
  5. Fixed miscellaneous bugs:
    - [ 1231719 ] SipRequest.isXXX() is bugus
    - incorrect Request URI in outbound REGISTER
    - incorrect routing of ACK when proxy sets LR param in record route header
    - added authentication challenge handling to SipCall.disconnect() (for callee BYE through proxy)
    - corrected 'is it for me?' check in SipSession.processRequest()
    - fixed SipSession synchronization problems.
  6. Known Limitations: some scenarios not tested, for example: a SipPhone with both a call and buddy list active.

Release Notes for release 0.0.2a of SipUnit:
  • Software changes for authentication/authorization:
    • fixed registration authentication handling shortcomings
    • added support to handle challenge(s) at unregistration
    • outbound calling authentication support
  • Documentation:
    • Updates for authentication (diagrams, new sub-section)

The list of TODOs as of this moment, in no particular order:
  • add more SIP methods - CANCEL, OPTIONS, REFER, etc. Also PUBLISH, watcher info package support.
  • add whatever support would be handy for Jiplet testing, including asserts for verifying Jiplet scoped variables.
  • allow more than 1 SipCall per SipPhone (partial support is there).
  • Add a new method SipCall.endCall() which will be very similar to SipPhone.makeCall() in that it will take parameter response code, and block until the user-specified response code has been received. It will be the same as SipCall.disconnect() but with authentication challenge handling included and the blocking just mentioned. For both SipCall.endCall() and SipPhone.makeCall() usage: add incoming call and incoming BYE "auto-respond" capability so that a test program can handle both sides of a call while making use of makeCall() and endCall(), both of which block, without having to use a separate thread - ie, something like SipCall.sendIncomingCallResponse() with the same parameters but it can be called in advance (before calling makeCall() on the outgoing side), and do the same for disconnect.
  • figure out what other functionality is needed to make SipUnit really useful.
There are some TODOs in the code such as adjusting the test failure stack (hide SipUnit stack entries).

A suggestion was given to reconsider forcing the user test class to extend SipTestCase, instead make SipTestCase an utility class (static methods); however, since the user program would need to extend JUnit TestCase anyway, this was not changed.

You can contribute by identifying other things that need to be added to SipUnit. If you like, you may contribute by implementing an item in the list. Please contact us by sending an e-mail to info@cafesip.org

Search this website 


Send questions or comments about this web site to webmaster@cafesip.org.
Copyright © 2005, CafeSip.org.
Licensed under the CafeSip License.
The CafeSip.org projects, web site and web facilities have been sponsored by QUIK Computing

Top of page