June 24, 2012,
Raleigh, NC.

We are pleased to announce the public release of SipUnit 2.0.0. This is a stable release with technology updates, new functionality and extensive testing performed. Feedback from the development community is encouraged for further enhancing the system.

In addition, we are pleased to announce that SipUnit leadership is changing hands – to TeleStax, Inc. The project will be led by George Vagenas, a longtime contributor and core team member to Mobicents and TeleStax, who is already leading the CDI Telco Framework and SIP Servlets Arquillian extension projects. The SipUnit source code and documentation will soon be moved accordingly.

SipUnit provides a test environment geared toward unit testing SIP applications. It extends the JUnit test framework to incorporate SIP-specific assertions, and it provides a high-level API for performing the SIP operations and messaging needed to interact with the application or network element under test.

The following are the highlights of the release. Thanks to George Vagenas for his recent major contributions to SipUnit and also to S. Pitucha for contributing patches.

1. MESSAGE handling has been added, including support for authentication and MESSAGE with or without an existing dialog.
2. JUnit 4 support was added with static assertions in new SipAssert class.
3. SipUnit is now mavenized!
   
4. Convenience methods were added to get the contact URI as javax.sip.address.URI from SipContact, the call ID from SipCall, and retransmission count from SipStack, among others.
5. TLS support has been verified.
6. JAIN SIP stack was updated.

If you have any questions about the SipUnit project, please refer to the SipUnit link on the TeleStax project page or send an email to sipunit@CafeSip.

– CafeSip Team. 

In this release:

1. The automated test coverage has been significantly expanded using SipUnit to verify SipExchange call handling in the areas of proxy, presence, subscriber and domain features, and CDR generation.
2. The existing unit tests were upgraded to JUnit 4.x.
3. A number of bug fixes have been incorporated into the release.

In this release:

1. GWTCOMP now supports GWT 1.5 and Java 1.5.
2. Chronoscope – the underlying charting library has been replaced with GChart.
3. Extensive amount of testing has been done and the release is now considered stable.

We are pleased to announce the public release of SipUnit 1.0.0. This is a stable release with tracker bugs fixed and extensive testing performed. Feedback from the development community is encouraged for further enhancing the system.

SipUnit provides a test environment geared toward unit testing SIP applications. It extends the JUnit test framework to incorporate SIP-specific assertions, and it provides a high-level API for performing the SIP operations and messaging needed to interact with the application or network element under test.

The following are the highlights of the release.

1. Support added for REFER handling (outbound, in- or out-of-dialog, with implicit subscription support).
2. JAIN SIP stack upgraded to rev. 1.2.119 and JUnit library upgraded to JUnit Release 4.7.
3. JAIN SIP objects (transaction, dialog) are now accessible from high level SipUnit classes (SipCall, etc.).
4. Bug fixes.

If you have any questions about the SipUnit project, please contact us by sending an email to sipunit@CafeSip.

– CafeSip Team. 

We are pleased to announce the release of SipExchange r1.0.0b. This is a Beta release to give users a working system to evaluate and test. Feedback from the development community is encouraged for further enhancing the system. In this release, we have introduced major features that will be beneficial to companies and service providers who wants to provide VoIP service to their employees or customers. Highlights of the release include:

1. We have introduced a Web Portal which enables subscribers and administrators to access, manage and fine-tune all aspects of SipExchange. Subscribers can view their calling records, manage their profile & contact list and manage their features like call forwarding and call screening. Administrators can provision and monitor the system from the portal. Based on the Jboss Portal technology, it enables system administrators to completely customize the look and feel and add new applications to the portal. It enables users to customize the look and feel and manage application dashboards.
2. An extensive set of web services have been introduced that enables external management and billing systems to manage user records, billing records and system configurations. This feature allows SipExchange to be integrated into existing infrastructure and enterprise services. In addition, since all the SipExchange user interface applications are portlets, elements of the user interface can be integrated into existing portals.
3. An installer/upgrade tool has been introduced. The installer uses a command-line wizard tool to setup the basic configuration of the system. This reduces the number of steps an installer had to perform to setup SipExchange. The upgrade tool enables SipExchange to be upgraded without losing any data.
4. Extensive set of automated unit tests have been added. In the next release, we want to extend this further and introduce benchmark tests.
5. The call processing engine has been tested extensively and number of bugs found while testing has been fixed.

What is SipExchange?
SipExchange is an open-source softswitch that provides standard SIP services like location, proxy and presence. Using the SipExchange application, service providers can offer VoIP telephone services to their subscribers as well as other services based on voice, video and instant messaging. SipExchange supports many of the standard subscriber features offered by the traditional telephone exchanges and PBXs. In addition, SipExchange supports external call control capabilities using which service providers and software developers can create new features and services rapidly and plug them into the SipExchange application. SipExchange provides a portal-based user interface using which system administrators can manage subscribers and features as well as perform other routine operations.

If you have any questions on SipExchange, please contact sipexchange@cafesip.org.

– CafeSip Team

We are pleased to announce the first public release of the Upgrader Tool. This is an Beta release to give users a preview of the system.

Upgrader is a simple Java-based tool that enables applications developers to add software upgrade capability into their applications. An upgrade process typically involves replacing the old version of the binaries with new version of the binaries and performing data upgrades. It may also need to perform changes to the directory structure. The data upgrade outlined above may involve changes to the configuration files and/or database changes if the application uses a database. This tool provides framework using which application developers can keep track of changes to the application. Every time, there is a change in the database schema or configuration files, the application developers can create a “patch” script and add it to the “patch list”. The Upgrader tool may be bundled with the application and is typically invoked during the installation/upgrade. When it is invoked, it determines the current patch level of the system, determines the patch scripts that are needed to be executed, sequence the patch scripts and apply them.

We are using the tool for the SipExchange project.

If you have any questions about the Upgrader project, please contact us by sending an email to common@cafesip.org.

– CafeSip Team.

In this release:

1. The Jiplet Admin Console has been ported to GWT (Google Web Toolkit) release 1.5 and also refactored to use the cafesip GWTCOMP project library. (Tracker IDs: 2402418, 2407944)
2. The ESR (Enterprise SIP archive) deployer has been removed since JBoss 4.x can now handle any arbitrary deployments inside an EAR, including Jiplet SPR and SRR archives. (Tracker ID: 2462949)
3. A number of bugs were fixed. (Tracker IDs 2046405, 2497810 , 509663 ).

In this release:

1. GWTCOMP now supports GWT 1.5 and Java 1.5.
2. Chronoscope – the underlying charting library has been replaced with GChart.
3. Extensive amount of testing has been done and the release is now considered stable.

The following are the highlights of the release.

1. The software has been tested with JBoss 4.2.1.GA.
2. The Jiplet Admin Console now uses GWT (Google Web Toolkit) release 1.4 RC2.
3. The JAIN-SIP stack used by the Jiplet Container has been upgraded to version 1.2.72.
4. The Jiplet reference applications have been verified to work with the new stack version.
5. Fixed the horizontal splitter that was broken by style-sheet element re-naming in GWT 1.4 RC2.
6. Cleaned up some of the jiplet classes.
7. Modified the build scripts so that the build scripts do not require the environment variable – CAFESIP_HOME.
8. The build script does not delete the staging files any longer.
9. Update CANCEL proxy handling to use the original server transaction for finding the transaction mapping entries.
   
10. In places where we propagate cancellation, use the client dialog’s sip provider for sending the client (outbound) CANCEL request.
11. Fix proxying so that a SipExchange CFNA (Call Forward Not Available) call does not result in SIP dialog and ‘To’ header tag mismatch.
12. Update ResponseForwarding status code check to match the JAIN-SIP API renaming from NOT_ACCEPTABLE to SESSION_NOT_ACCEPTABLE.
13. Provide a method to allow a leg to be dropped out of a forked call.