SIS 2.6 builds on the previous SIS releases from OpenCloud.
Some of the SIS 2.6 highlights are:
-
Based on CGIN — SIS 2.6 is now based on OpenCloud’s CGIN 2.0.0.
-
Split SIS packages — Split IN and SIP packaging.
-
SIP session replication — Replication of SIP session state.
SIS based on CGIN 2.0.0
SIS 2.6 now uses OpenCloud’s CGIN 2.0.0.
The CGIN Connectivity Pack is OpenCloud’s product for integrating with SS7 networks and supporting functional and load testing of SS7-based applications.
Please note that SIS only supports the component-oriented event model offered by CGIN. SIS does not support the message-oriented event model introduced by CGIN 2.0.0. Please see the CGIN documentation for more information about these event models.
Split SIS packages
The IN and SIP SIS variants have been repackaged to be completely independent from each other. SIS-IN no longer depends on any SIP components and SIS-SIP no longer depends on any CGIN components. Both SIS-IN and SIS-SIP may be installed side-by-side in Rhino for those requiring SIS services for both IN and SIP.
As a side effect of this split, the SIS administration tools included within a SIS install are now specific to the type of SIS install they belong to. That is to say the tools included in a SIS-IN install can only operate on SIS-IN SIS instances, and those included with a SIS-SIP install can only operate on SIS-SIP SIS instances.
SIP session replication
The SIS-SIP now supports replication of SIP sessions. This means if a SIS cluster node fails, SIP sessions (dialogs) can continue on other nodes in the cluster. See SIP Session Replication in the SIS Overview and Concepts Guide for more information.