SIS 2.5 builds on the previous SIS releases from OpenCloud.
Some of the SIS 2.5 highlights are:
Based on CGIN — SIS 2.5 is now based on OpenCloud’s CGIN 1.5, and adds support for new functionality and more protocols.
ACN Rewrite — IN services can now be invoked with a different application context than the triggering protocol.
Interceptor Components — Interceptors can now be deployed as components and can be invoked directly by SLEE applications.
FCI Interaction — Pass-through has been added as a composition interaction option for handling
FurnishChargingInformationoperations from an IN service.
R-IM-SSF Enhancement — New functionality has been added to the R-IM-SSF to support more call scenarios.
consolidation — SIS 2.5 consolidates all bug fixes from all SIS 2.4 patch releases.
|SIS 2.5 can be used on Windows for development and evaluation!|
SIS 2.5 now uses OpenCloud’s CGIN 1.5.
⭐ The CGIN Connectivity Pack is OpenCloud’s product for integrating with SS7 networks and supporting functional and load testing of SS7-based applications. CGIN 1.5 is the latest revision of this product.
⭐ CGIN 1.5 adds a static
copyOf() method to all generated datatypes. This method creates a new object of the type the method is called on, cloning the values of common fields contained in the method argument. The SIS script elements
<array>, used to construct objects or arrays of arbitrary types, have been updated to support
⭐ SIS 2.5 includes new optional support for Siemens INAP 7m+.
|This means that SIS is now based on the latest OpenCloud technology, ensuring the product is both robust and easily extendable.|
IN services can now be configured to be invoked with a specific protocol application context name. The SIS will invoke the service using the specified application context, regardless of the triggering protocol.
⭐ This allows services implemented only for protocol X to be used in a SIS composition triggered by protocol Y.
|The SIS doesn’t natively perform any protocol translation. If translation of protocol messages is required then this still must be implemented separately using interceptors.|
Interceptor scripts can now be deployed as SIS components in their own right. Interceptor components have additional capabilities over interceptors embedded within a composition script:
⭐ Interceptor components can be invoked as a subroutine while evaluating an embedded interceptor or another interceptor component.
⭐ SLEE applications can invoke interceptor components as part of their business logic to allow external customisation and manipulation of protocol messages on dialogs not managed by the SIS, for example in applications performing protocol translation.
Pass-through has been added as a composition interaction option for handling
FurnishChargingInformation operations from an IN service.
⭐ This option simply allows all FCI operations from any service that sends them to pass through to the network without SIS interference.
New functionality has been added to the R-IM-SSF to support the following scenarios:
⭐ Parallel alerting is now supported if the SIP dialog is forked.
⭐ The SIP-AS can now initiate a new call in the IN using the R-IM-SSF.
⭐ Multiple participants may now be added to any call.
⭐ Call party hold and resume is now supported if an appropriate media change is detected in a re-
⭐ User interaction using a SIP MRF instead of an IN announcement device is now supported.
⭐ Mid-call user interaction is now supported.