Sentinel IP Short Message Gateway 2.5.1 Changelog

The IP-SM-GW now requests a UE Reachability for IP Notification on certain IMS delivery failures. This behaviour is enabled by default, and is configurable via the IP-SM-GW Shared Configuration.

Updated to Sh Cache RA 1.0.2.1. This newer version of Sh Cache RA supports subscription to UE Reachability for IP via Subscribe Notification Request/Push Notification Request (SNR/PNR) with the HSS.

Added IP-SM-GW behaviour when receiving a UE Reachability for IP Notification via Sh Push Notification Request (PNR) (IPSMGW-645).

Third Party Registration Flows for the IP-SM-GW now issue Ready For SM instruction to the HLR. This is enabled by the new Fetch IMSI Registration and Ready For SM Registration features that run in the REGISTER path (IPSMGW-674)

The IP-SM-GW now uses the MAP ReportSMDeliveryStatus operation as part of the MT Delivery Flows. This involves updates to the PS Delivery and CS Delivery features (IPSMGW-698, IPSMGW-668).

Added the Modify SRI Leg feature (IPSMGW-676). This feature runs after the MAP Proxy feature and prevents proxying of outbound Inform Service Centre messages. It also sets SM-RP-PRI=true in outbound SendRoutingInfoForSM requests. Both of these behaviours are configurable via the feature’s configuration profile.

Updated the IP-SM-GW Routing Information Cassandra schema used for MT Correlation storage to store entire SendRoutingInfoForSM Arg in addition to the already existing response (IPSMGW-730). This also involved corresponding updates to the Store Routing Info Cassandra and Fetch Routing Info Cassandra features.

Fixed attempted double-send of MtForwardSMError triggered in MtForwardSMRequest error handling logic (IPSMGW-709).

Improved behavioural consistency between CS Delivery and PS Delivery features (IPSMGW-671).

Both the CS Delivery and PS Delivery use fallback avoidance codes in their configuration. Refer to their respective configuration and behaviour sections for further details (IPSMGW-666)

The MSISDN is now made available in in Session State by the new Determine MSISDN feature (IPSMGW-670).

All features that initiate MAP requests towards the HLR can address the request based on a GT address formed from the subscriber’s MSISDN. This is configured in the Shared Configuration Profile.

Ensured correct RP Message Reference generation during simultaneous SMS delivery to a single IMSI in the Generate Message Reference feature (IPSMGW-719). This uses atomic Compare and Set with configuration regarding number of Compare and Set retries and back-off between retries.

Update the MAP proxy and ATM registration features to optionally address the HLR leg using a GT address formed from the inbound subscriber MSISDN. Controlled using an introduced useMsisdnAsHlrAddress option. (IPSMGW-654, IPSMGW-661)

The SMMA callflow now handles error responses to the SendRoutingInfoForSM request with appropriate responses instead of always responding with NETWORK_OUT_OF_ORDER (IPSMGW-633)

CDRs are now handled solely by features instead of the previously existing mappers. Several new features are available for this: CDRInfo, DiameterV8d0ServiceInfo, IpsmgwLegacyCdr and IpsmgwAvpCdr. The CDRInfo and DiameterV8d0ServiceInfo features populate session state with information consumed by the IpsmgwLegacyCdr feature (to write old 2.4.0 format CDRs) or by the IpsmgwAvpCdr feature (to write new 2.5.0 format AVP CDRs).

Added SM-Delivery-Not-Intended configuration for FetchImsi feature (IPSMGW-619).

Improved SRI error handling (IPSMGW-633).

Fixed potential for incorrect origination address in outbound HLR dialogs (IPSMGW-655).

Added module packs for CDR features.

Update SDK infrustructure to 2.5.0

Sentinel Registrar dependency updated to 2.5.0

Sentinel SIP dependency updated to 2.5.0

Sentinel Common dependency updated to 2.5.0

Determine the message type of SIP MESSAGE request based only on message content (and not sescase) (IPSMGW-600)

IP-SM-GW will act as a routing B2BUA for RP messages where the direction is network to MS (IPSMGW-603)

Implemented Online IEC charging for SMS MT messages. For details please refer to MT Online Charging Flows.

The OCSS7 TCAP stack is now supported, and installer support for TCAPSim has been removed.

SM Delivery Reports received from the UE in response to MT SMS-over-IP messages are now used to determine if delivery was successful.

The fallback mode for MT traffic is configurable, allowing PS-to-CS fallback, CS-to-PS fallback, or PS and CS only modes. For details please refer to MT Delivery Flows.

SIP Messages containing an RP-SMMA body are now supported, and will trigger a ReadyForSM notification to the HLR For details please refer to Short Message Memory Available Flows.

Sentinel Registrar dependency updated to 2.4.0

Sentinel SIP dependency updated to 2.4.0

Sentinel Common dependency updated to 2.4.0

Generate an RP-ERROR for SMS-MO when CGIN throws an exception (IPSMGW-485).

SMS-MT flows in IP-SM-GW Architecture Guide now show correlation IMSI (IPSMGW-481)

PS Delivery now retrying correctly after failure (SIS-1074,SIP-372)

For originating SMS, the MSISDN from P-Asserted-Identity is now added to the SM-RP-OA field (IPSMGW-511)

Sentinel Common dependency updated to 2.3.1.16

Sentinel Registrar dependency updated to 2.3.1.14

Sentinel SIP dependency update to 2.3.1.16

Initial release implementing transport layer interworking for SMS over IP, as defined in 3GPP TS 24.341 v12.6.0.

This version has a dependency on Sentinel Common 2.3.1.13

This version has a dependency on Sentinel Registrar 2.3.1.11

This version has a dependency on Sentinel SIP 2.3.1.13

Fixed a binder bug in which bind-with-deps could bind modules into different sets of services depending on traversal order. (SDKTOOLS-140)

The binder no longer generates or installs empty bindings descriptors for library and profile modules. (SDKTOOLS-136)

Fixed a bug where unbind would fail to unbind a module from a service when the module was bound into that service due to a bind-with-deps operation on a downstream module. (SDKTOOLS-135)

Fixed bug which caused binding to fail on some file systems such as eCryptfs due to long file names, and improve failure handling in the binder. (SDKTOOLS-134)

Fixed bug where mapper classes with multiple mappers were not getting renamed properly during module creation from module packs (SDKTOOLS-130)

Fixed provider injection warning from PromotionsCommitUsedUnits feature (STLCORE-54).

Fixed incorrect JNDI context being used in subsequent pojo feature execution when the initial execution cycle was initiated by an SBB feature event handler (STLCORE-46).

Improved handling of how the top-level module is renamed when using the 'create-module' command (SDKTOOLS-92)

Changed behaviour of sdkadm -f and -e arguments. These will now exit sdkadm after executing the specified commands unless the new -i (force interactive) argument is specified.

Added -q option to sdkadm which will suppress some command processing logging.

Renamed default resolvers to online-resolvers.xml. Added offline-resolvers.xml.

Split local resolver configuration out into local-resolvers.xml.

Added support for property injection during <default-module-build> macrodef execution. Any properties written to ${generated}/build.properties prior to <default-module-build> will be available during annotations processing.

Renamed 'clean' target to 'clean-module', and renamed all non-branch publish-* targets to 'publish-*-module'. All targets named *-module now operate only on a module, whereas all targets named *-branch will operate recursively. e.g. publish-local-module will publish the current module, whereas publish-local-branch will publish the current module and all nested children. (BLDSUPP-19)

Certain targets (clean, publish-*) are now 'dynamic' and will behave differently based on where they are executed. e.g. executing 'publish-local' in a module which has nested modules will publish all nested modules (i.e. a publish-local-branch), whereas running 'publish-local' in a module with no children will invoke 'publish-local-module'. The non-dynamic behaviour can still be explicitly invoked via the *-module or *-branch target variants (BLDSUPP-19).

IDE setup targets (idea-setup, eclipse-setup, idea-clean, eclipse-clean) are now only available in the root of an SDK (STLPACK-182).

Relevant targets for each module build are now determined automatically based on module type and content. Old build files should be modified to remove imports of 'build/default-branch-targets.xml' and 'build/default-targets.xml' and instead import the unified 'build/targets.xml'. The old import statements will continue to work to enable backwards compatibility with 2.3.1 SDKs, but they will produce a runtime warning on each build.

All temporary build infrastructure artifacts are now written to the build/target directory. Repositories created by go-offline will be put into the repositories directory. Module build output remains in MODULE/target/. (BLDSUPP-34, STLPACK-35)

Added example Python script for REST API interactions to build/bin/

Updated the SentinelRAAToRoOcsRAA and SentinelRAAToDccaOcsRAA mappers to use application specific message factories so that RAAs sent by Sentinel will include the right Diameter Application-Id. (STLCORE-38)

Update the SIS dependency to 2.5.2.21

Support overriding of db.type and postgres.jdbc.dir in the installer (OCS-338)

Update the HTTP RA dependency from 2.2.0.6 to 2.2.0.11

Update Rhino SDK dependency to 2.4.0.14

Avoid find error when initialising SDK

Fix go-offline script when it is run through the installer

Disallow conflicting go-offline repository names

Enhancements to the Sentinel SDKs for Undeploying modules and redeploy commands. See General Development Cycles

Improvements to the user experience through the addition of a Logical Service ID for each Service

Support for custom CGIN and SIS versions has been added. The installer will scan for custom versions and use those if present.

Fix a bug in the go-offline script when the installer runs interactively (OCFE-3766)

Fix a NoClassDefFoundException in the Diameter Mediation layer (STLCORE-30)

Enable the installer to install against production Rhino (VOLTE-1385)

Add a SuppressOCSInteraction feature. This feature was originally added later in the Sentinel 2.1.0.x series and has now been added to the 2.3.1.x series (STLCORE-22)

Fix a bug when OCS finalisation is not required (STLCORE-19)

Upgrade to GWT 2.7.0

Use of REM 1.4.0.8 or later is recommended

Use of REM 1.4.0.7 or later is recommended

Add ability to see which services would be affected by a redeploy operation (SDKTOOLS-43) Usage: ant -Dredeploy.only-show-services=true redeploy-all

Add redeploy and redeploy-all tasks (SDKTOOLS-71 and SDKTOOLS-72)

Remove use of cascade-uninstall from the binder (SDKTOOLS-71)

Change undeploy and undeploy-all tasks to not use cascade-uninstall (SDKTOOLS-44)

Make go-offline work on a Mac

Prompt for confirmation by default for all undeploy tasks

Updated the required Rhino version to be 2.4.0.14 (or later)

Enable terminal echo in the installer (VOLTE-1962)

Fix a memory leak with various tracers when using the Multi FSM SBB (STLCORE-14)

Minor performance improvements when using Sentinel Selection Key’s Iterator

Increase the available memory for a GWTC compile for user feature extensions to REM

Update DB Query RA dependency to 1.4.0.3 (VOLTE-1721)

Quieten log levels by default for SDK tools (SDKTOOLS-45)

Quieten Ivy by default for the SDK

Quieten Ivy bootstrap unless specified otherwise

Add support for dry-run propagation through a number of commands

Create a verbose logfile when performing builds

Miscellaneous bugfixes and improvements

Add deploy-module, bind-module and configure-module commands to sdkadm

Improve user control over the configurer’s and deployer’s dependency traversal order (SDKTOOLS-40). Module authors can now specify e:configureorder to control the traversal order of a module and its dependencies. Much like the existing e:deployorder, it defines the modules as a comma separated list of module names. For both e:configureorder and e:deployorder, the module itself can now be included at any point in the given order. I.e. the module itself can be configured/deployed either before or after its dependencies.

Adjust some memory properties for the default Rhino SDK. Set the max new size to 512MB, and set the heap minimum and maximum size to 2048MB

Add support for module property propagation between modules that publish properties

Fix go-offline local repo name rewriting

Run init-sdk if necessary

Use an SDK specific Ivy cache rather than the default

First 2.3.1 release for Sentinel Express

Handle the case where sessionState.getLatestOcsAnswer() is null (STLIN-35)

Fix bugs in several sentinel-core module packs

Rewrite the installer in Java (VOLTE-1692)

Initial Sentinel 2.3.1 series release, included in Sentinel VoLTE

For users migrating from Sentinel VoLTE 2.2.x, or Sentinel 2.1.x the SDK has been completely replaced with a brand new vastly simpler SDK.

First release of Sentinel Common infrastructure in the 2.3.1.x series

Fix an issue where the JNDI context was incorrect during sbb feature upcalls (STLCORE-46)

Update CDR RA dependency to 2.3.0.0

Update Diameter dependency to 2.7.0.4 (STLCORE-47)

Fix a multi-thread safety bug working with XML documents to store Third Party Registration state in HSS transparent data (STLREG-17)

Add ESRVCCReregistration feature to handle loading ESRVCC data into session state at reregistration, and to update the ATCF in the event the ATU-STI has changed. (STLPACK-157)

The handling of P-Associated-URI implicit sets in third party registrations has been improved:

Update Sentinel Common dependency to 2.3.1.16

Update Diameter dependency to 2.6.0.16 (STLCORE-38)

Update Sh Cache RA dependency to 1.0.1.13

Update MMTel Standard Schema dependency to 1.0.1.8

Update SIS dependency to 2.5.2.21

Fix a bug in the interpretation of empty vs non-existant documents in Sh Transparent Data. The new behaviour is consistent with 3GPP TS 29.328 (VOLTE-2051)

Update Sentinel Common dependency to 2.3.1.13

Update SIS dependency to 2.5.2.20 (STLPACK-59)

Update Sh Cache RA dependency to 1.0.1.11 (STLPACK-64)

Update MMTel Standard Schema dependency to 1.0.1.7 (STLPACK-64)

Update Diameter dependency to 2.6.0.15 (STLPACK-64)

Update GWT dependency to 2.7.0 (STLPACK-67)

Update REM dependency to 1.4.0.8 (STLPACK-67)

The SCC-AS ATU-STI and STN-SR can now be set to a unique value per cluster node. Installer support is included (VOLTE-1955)

Added support for configuring the access key when querying the HSS for STN-SR. A choice of MSISDN or IMPU, and optionally the IMPI can be configured (VOLTE-1925)

Update Sentinel Common dependency to 2.3.1.10

Update Diameter dependency to 2.6.0.12

Update Sh Cache RA dependency to 1.0.1.10

Update MMTel Standard Schema dependency to 1.0.1.6

Update SIS dependency to 2.5.2.18 (VOLTE-1329)

Update Rhino SDK dependency to 2.4.0.14 (VOLTE-1329)

Updates to Sentinel Registrar to store P-Access-Network-Information in Third Party Registration data (VOLTE-1320)

Removed an experimental capability from Sentinel Registrar, where Third Party Registration data could be stored in JSLEE Profiles. The options are storage in the HSS via Sh, or storage in the Cassandra DB via CQL (VOLTE-1549)

Update Sentinel Common dependency to 2.3.1.8

Sentinel Registrar updated to allow storage of Third Party Registration data in Cassandra. See Inside Sentinel Registrar. The capability is experimental in this initial release (VOLTE-1320)

New feature FetchMSRN (VOLTE-1518)

Update Sentinel Common dependency to 2.3.1.4

Update SIS dependency to 2.5.2.14 (VOLTE-1318)

Update FSMTool dependency to 1.1.0.11

Update Sh Cache RA dependency to 1.0.1.9 (VOLTE-1318)

Update MMTel Standard Schema dependency to 1.0.1.5 (VOLTE-1318)

Update FSMTool dependency to 1.1.0.10 (VOLTE-1403)

Initial release of Sentinel Registrar 2.3.1.x series

This version has a dependency on Sentinel Common 2.3.1.3

Add new Diameter service information feature. See Diameter Service Info Feature.

Add feature that notes time of initial request and response. See Record Timestamps Feature.

Add DetermineChargingInfo feature. See Determine Charging Information Feature.

Update CDR RA dependency to 2.3.0.0.

The CDR feature in Sentinel SIP has been refactored to not use mappers and instead populate the CDR directly with values obtained from the session state. The legacy behaviour and CDR format have been turned into their own features. See AVP CDR Feature and Legacy CDR Feature for more information about the features.

The format of the CDRs that Sentinel SIP creates has changed. See CDR Formats

Added a new system feature SequentialForkedSDPMediation (STLSIP-1151)

Enhance the SDP Comparison Feature allowing it to ignore named legs. (VOLTE-2397)

In cases where a SIP UA sends a REFER request and does not respond to the triggered NOTIFY request, allow a subsequent NOTIFY to pass through the B2BUA. (VOLTE-2056, VOLTE-2267)

Update the Diameter dependency to 2.7.0.4 (STLCORE-47)

Update from Diameter Ro v8.2.0 to v8.13.0 (VOLTE-2228)

Fix a bug where the SDPMonitor feature incorrectly re-writes the session-id in SDP origin information. (STLSIP-1121)

Fix a bug related to re-writing the Event header of NOTIFY requests when Sentinel acts as a B2BUA. (STLSIP-1122)

Update Sentinel Common dependency to 2.3.1.16

Update SIS dependency to 2.5.2.21

Update HTTP RA dependency from 2.2.0.6 to 2.2.0.11

Fixed an issue where RFC3263 config properties were not passed through to the SIP stack. (SIS-1074)

Failed servers are no longer blacklisted when RFC3263 failover is disabled. (SIP-372)

Update Sentinel Common dependency to 2.3.1.15

Fix a set of bugs in the SIP stack where client DNS procedures were not being followed correctly according to RFC 3263 (SIP-253, SIP-314)

Update Sentinel Common dependency to 2.3.1.13

Update Diameter dependency to 2.6.0.15

Update SIS dependency to 2.5.2.20

Update Sentinel Common dependency to 2.3.1.12

Included SIP Example module-pack (STLPACK-40)

Update Sentinel Common dependency to 2.3.1.9

The B2BUA System Feature properly handles the Max-Forwards header. Out of the box feature execution scripts updated as appropriate

Update SipNormalizationFeature and SipSubscriberDetermination to use getAddressHeaders for P-Asserted-Identity (VOLTE-1862)

Performance improvements such that performance is on par with the 2.2.0.x series

Update Sentinel Common dependency to 2.3.1.8

Improve extraction of phone numbers from URIs

Update Sentinel Common dependency to 2.3.1.5

Fix a bug in the SIP Determine Network Operator module pack

Initial release of Sentinel SIP 2.3.1 series

Sentinel SIP is now capable of all uses of the ISC interface. For an overview of the enhancements please refer to Sentinel SIP Enhancements.