Jiplet Container Release Notes and TODOs

This page lists the Jiplet Container releases that are available for download from our web site and their content. The TODOs section describes what are the things that are planned for upcoming releases.

Jiplet Container R 0.2.0

This is a stable release.

The following are the highlights of the 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 )

Jiplet Container R 0.1.1b

This is a beta release. We think that the release is stable enough to be used in a development environment. 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.

Jiplet Container R 0.1.0b

This is a beta release. We think that the release is stable enough to be used in a development environment. The following are the highlights of the release.

  1. The software has been tested with Jboss 4.0.5.GA.
  2. The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
  3. The new listening point architecture has been integrated into the Jiplet Container SIP connector. One connector can now use more than one IP address for SIP messaging.
  4. Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
  5. The Jiplet Container message proxying has been updated to work in a multi-homed environment.

Jiplet Container R 0.0.9b

This is a beta release. We think that the release is stable enough to be used in a development environment. The following are the highlights of the release.

  1. The Jiplet Console (system administration user interface) has been re-written using the Google Web Toolkit (GWT). The console now provides an easy to use interface taking full advantage of the rich user interface that GWT provides.
  2. The directory structure has been refactored to divide the project into logical components with the idea that each of these components can be treated as separate projects that can be built independently.
  3. The automated tests for the project now works properly.
  4. A number of bugs that were found have been fixed.

Jiplet Container R 0.0.8b

We have graduated this release to be a Beta release. It means that we think the release is stable enough to be used in a development environment. We will do further system-level testing and load testing before we declare the release as a production-grade release. The following are the highlights of the release.

  1. The software has been tested with Jboss 4.0.4.
  2. The thread pool framework has been refactored to be more efficient and be more tolerant to higher SIP message load.
  3. The reference application has been modified to work with additional and newer versions of SIP phones from various vendors.
  4. The Jiplet Console (system administation use interface) now uses a secure connection for higher security.
  5. A number of other bugs have been fixed.

Jiplet Container R 0.0.7a

This is an Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. The software is now tested with Java 1.5. Note that it is not backward compatible with Java 1.4 any longer.
  2. The startup scripts for Windows for the standalone version can now handle blank spaces in the path names.
  3. The proxy code has been enhanced to handle the ACK and CANCEL messages for a stateful proxy.
  4. Enhancements have been made to the Container Managed Authentication (CMA) code.
  5. A small bug relating to the SUBSCRIBE message found in the NIST JAIN-SIP stack has been fixed and included with this package.
  6. A number of other bugs has also been fixed.

Jiplet Container R 0.0.6a

This is an Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. The jiplet container now works with JBOSS 4.0.2 instead of JBOSS 4.0.0.
  2. Enhanced the SIP proxy functionality to include cancelling of proxy requests as well as other enhancements.
  3. Changed the packaging structure of the Jiplet Console and the reference application packages.
  4. Many bugs were fixed and the code underwent significant refactoring.

Jiplet Container R 0.0.5a

This is an Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. Improved support for Enteprise Archives (EAR). You can now load EJBs from a jiplet context located inside an EAR.
  2. The jiplet container JBOSS service is now a single deployable “sar” file instead of a “sar” directory. This will make it easier to install the service in the JBOSS environment.
  3. Initial support for naming contexts has been added when running as a JBOSS service.
  4. Support for external entities sending messages to jiplets has been added.
  5. A number of bugs found in the earlier releases have now been fixed and we have re-organized the packaging.

Jiplet Container R 0.0.4a

This is an Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. Support for deployable realms: Now you can deploy your own realms using context-like deployment and undeployment. You can also use the jiplet console for deploying and undeploying realms.
  2. The jiplet container running as a JBOSS service now supports bundling of SIP archives (SPR) and SIP realms (SRR) into a Enterprise Archive (EAR).
  3. The system admin can now override the context mapping while installing a jiplet context. The mapping is specified in the deployment descriptor and this mapping can now be overridden. This allows a service provider to have better control of jiplet contexts from multiple vendors running in a service provider’s system.
  4. A number of improvements have been made to the jiplet console. You can now add and remove realms, override context mapping, view the properties of the connectors, etc.
  5. A number of bug fixes were also made.

Jiplet Container R 0.0.3a

This is an Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. Support for the proxy functionality has been added. Most SIP server-side applications require proxying capability. Keeping that in mind, classes to support proxying have been added. In addition, a standard proxy jiplet has been included for most standard proxying needs.
  2. The reference application has been enhanced to include a simple presence server. This will enable the reference application to be used as a chat server among others.
  3. The reference application now partly supports Microsoft Windows Messenger clients.
  4. Any modifications to the memory realm (CMAA) no longer requires the jiplet container to be re-started for the modification to take effect.
  5. The jiplet console now displays security constraint parameters for the jiplets.
  6. Number of bugs in the areas of forwarding and general functionality have been fixed.

Jiplet Container R 0.0.2a

This is the second release of the Jiplet Container. This is an early Alpha release to give users a preview of the system. The following are the highlights of the release.

  1. Container-managed authentication and authorization: Allows jiplet applications to specify security-constraints. The container handles security (authentication and authorization) on behalf of the application based on SIP specifications.
  2. A new JMX implementation has been put in place that supports the “remote” API.
  3. A number of changes have been made to the reference application.
  4. The class-loader architecture for the standalone jiplet container has been changed. Any classes and jar files placed under the common directory under the home directory is now loaded automatically. This feature allows users to easily replace the SIP stack, plugin authentication databases, etc.
  5. Many bugs have been fixed.
  6. Many changes to the documentation have been made.

Jiplet Container R 0.0.1a

This is the first release of the Jiplet Container. This is an early Alpha release to give users a preview of the system. The following features have been implemented.

  1. Standalone Jiplet Container Server РA standalone Java process that serves as a container for jiplet applications. See the features FAQ for more details.
  2. Jiplet Container Server as a JBOSS service – A JBOSS service archive has been provided for plugging into the JBOSS environment.
  3. Support for scoped variables – application, session, transaction, dialog, event.
  4. Support for forwarding SIP events from one jiplet to another.
  5. Jiplet and context mapping of SIP messages and events.
  6. Jiplet container management using the Jiplet Console as well as a JMX interface for integration with exisiting management applications.
  7. Jiplet API for developing jiplet applications.
  8. Multiple connector support.
  9. Logging and tracing.
  10. Script for adding the container as a Windows/Linux service.
  11. Jiplet developer package including class libraries, API documentation and a custom Ant task to build SPR archives.

TODOs

The following features are planned for near-term upcoming releases:

  1. Support for high-level API for sending SIP messages (in addition to the JAIN-SIP API that is already available).
  2. Allow jiplets to receive additional events now available through JAIN SIP API v1.2 – IOException, transaction terminated and dialog terminated.
  3. Support for naming context and EJB references for the standalone jiplet container.
  4. Automated test suite for the jiplet container using SipUnit.
  5. Clustering support for the jiplet container: It will be possible to cluster multiple jiplet container installations to scale up and to achieve high availibility.
  6. Fine tuned access to system resources and security for jiplet applications defined by administrators.

Long-Term TODOs

We are planning to do the following although they have not been planned out yet. If you would like to contribute toward these projects, please contact us by sending an e-mail to info@CafeSip.

  1. Create an Xdoclet for generating the deployment descriptor – jip.xml and jboss-jip.xml.
  2. Create an Eclipse plugin for jiplet development.
  3. Develop binding with other J2EE servers.
  4. Support multiple languages for the jiplet console application.
  5. Administrator-defined quotas for jiplet application.
VN:R_U [1.9.20_1166]
Rating: 0.0/10 (0 votes cast)

Leave a Reply