2.7.0.9
-
Update diameter service context Id value from
8.32274@3gpp.org
to12.32274@3gpp.org
. (VOLTE-5686) -
Update callers of deprecated CassandraRow.getDate() to use CassandraRow.getTimestamp(). (VOLTE-6119)
-
Add metadata to support product rolling upgrades:
-
Configuration changes
-
Required Rhino properties
-
Required non default properties used by the SDK installer. (VOLTE-4613)
-
Dependency updates
2.7.0.7
-
Fix IPSMGWStoreRoutingInfo to handle AbsentSubscriber error in separate DialogMessage Tcap block from OpenAccept. (IPSMGW-902)
-
FetchRoutingInfo will attempt PS Delivery if the CS routing info was only partially retrieved or could not be decoded, but the MSISDN was correlated successfully. (IPSMGW-892)
-
Update to permit PS delivery when receiving AbsentSubscriber SRI error and InformSc in a single Tcap block. (IPSMGW-901)
-
Update default SRI4SM SipThirdParty_Request feature script to permit PS delivery when receiving AbsentSubscriber SRI error with InformSc.
-
Fix issue in ModifySRILeg feature that meant it would not discard InformSc correctly.
-
-
Fix NullPointerException that occurs in StoreRoutingInfo feature when the
MTCorrelatedId
is not present in session state. If the session state field is not set StoreRoutingInfo will send a system error in response to the received SendRoutingInfoForSM request (IPSMGW-899). -
Minor: update DetermineSessionPlan to always set the MTFSMDeliveryOrder session state field, and use it rather than the configured value within DetermineSRIForSMResultFailure. (IPSMGW-883)
-
Added functionality to permit PS delivery on SendRoutingInfoForSM Absent Subscriber error case where the subscriber registered for SMS over IP. (IPSMGW-4917)
-
Update IPSMGWGenerateMtCorrelationId to allocate a correlation Id based on the new MCC and MNC configuration added to Sip Sentinel Configuration in the event of a failed SRI for SM. This new configuration is network or platform operator specific and must to be configured manually.(IPSMGW-884)
-
Update the default MTFSM feature scripts to run IPMSGWFetchRoutingInfoCassandra in the system feature pre script instead of the user script, so that it can modify plan Id prior to selecting the user script. (IPSMGW-883)
-
Update PS and CS Delivery features to rely on new session state field MTFSMDeliveryOrder instead of DeliveryOrder configured in IPSMGWSharedConfig as the plan Id is subject to change. (IPSMGW-883)
-
Add feature to Determine SRIForSM Result Failure to allow PS delivery when subscriber is registered for SMS over IP. (IPSMGW-886)
-
Generate message reference per MSISDN instead of IMSI. The MSISDN is stored in the IPSMGWGenerateMessageReference table’s imsi field. (IPSMGW-893)
-
Update StoreRoutingInfo to store just the MT Correlated ID as IMSI and the MSISDN for PS-only delivery on SRI for SM failures. (IPSMGW-881)
-
Update FetchRoutingInfo to change plan Id to MTFSM_PS when the SRI for SM Result is missing in cassandra and PS was one of the available delivery modes. (IPSMGW-883)
-
-
Update PSDelivery feature to improve handling of RpAck messages which contain no User Data. (IPSMGW-897)
-
Update IPSMGWSharedConfig and MapProxyConfig profile verification such that
Nature of Address
andNumbering Plan Indicator
are not checked forA7
addresses. (IPSMGW-911)
Dependency updates
2.7.0.6
-
Fix a licensing issue where the IP-SM-GW registrar service would erroneously require a Sentinel-SIP license to function. (VOLTE-4660)
Dependency updates
2.7.0.3
-
Add support for GT routing when using non C7 addressing, this included changes to IP-SM-GW Shared Configuration:
-
'HlrAddres' is now used as a template address in which the configured digits are replaced by the subscriber MSISDN when 'UseMsisdnAsHlrAddress' is configured and is now required by all features that create outbound HLR legs.
-
'TemplateSmscAddress' to support templating of HLR and SMSC SCCP addresses. (IPSMGW-876)
-
-
Add Template Smsc Address configuration option to the installer. (IPSMGW-876)
Dependency updates
2.7.0.2
-
Ensure properties of the ReportSM_DeliveryStatus sent by IPSMGW match the most recent delivery attempt. (IPSMGW-827)
Dependency updates
2.7.0.1
-
Implement support for a default rejection message in the USSI
-
Implement support for a default rejection message in the USSI
-
Update MO Submission CDRs to include the MSISDN of the SMS recipient in the Recipient-Info AVP and the MSISDN of the SMS sender Originator-Received-Address AVP. (IPSMGW-853)
-
Update MT CCRs and CDRs to include the MSISDN of the SMS originator in the Originator-Received-Address AVP. (IPSMGW-854)
-
Fix an issue where an unnecessary ReportSMDeliveryStatus message would be sent by the IPSMGW to the HLR when an SMS was successfully delivered over CS. In this case the MSC rather than the IPSMGW is responsible for generating ReportSMDeliveryStatus. (IPSMGW-828)
-
Add support for multipart content bodies to Sentinel IPSMGW and Sentinel USSI. (VOLTE-4272)
-
Extend USSI user digits regex to be more permissive. (VOLTE-4347)
-
Ensure MAP MTFSM More-Messages-To-Send flag is set to 'None' for CS Delivery. (IPSMGW-844)
-
Fix bug with successful PS delivery where the IP-SM-GW would send a TC-End without TCAP level ReturnResultLast towards the SMSC. (IPSMGW-843)
-
Update the charging features:
-
Add MO flow charging
-
Extended the MT flow charging to CS network
-
Change the installer questions to set the new charging modes
For more information on MO charging see gxref:ipsmgw-architecture-guide/mo-submission-flows[MO Submission Flows]. For more information on MT charging see gxref:ipsmgw-architecture-guide/mt-online-charging-flows[MT Online Charging Flows].
-
-
Add new feature IPSMGWExtractNetworkInfo to extract the MCC and MNC from the signaling or from the 3rd party registration data. See IPSMGW Extract Network Info Feature.
-
Add network information for Ro messages and AVP CDRs:
-
Visited network
-
Access network
-
MCC and MNC
-
Dependency updates
2.7.0.0
-
First release of the 2.7.0.x series
-
Third Party Registration features for the IP-SM-GW have been re-worked to function according to the updated Third Party Registration support in Sentinel SIP
-
Update the Diameter dependency to 2.7.0.x
-
Update the Sentinel SIP dependency to 2.7.0.x
-
Update the Sentinel Common dependency to 2.7.0.x
-
Update the Sh Cache RA dependency to 1.0.3.0
2.6.0.7
-
Update the Sentinel Common dependency to 2.6.0.9
-
Update the Sentinel SIP dependency to 2.6.0.10
-
Update the Sentinel Registrar dependency to UNRESOLVABLE BXREF: sentinel-registrar-changelog#2-6-0-9[2.6.0.9]
2.6.0.6
-
Add Recipient-Info AVP for CCR and CDR. (IPSMGW-821)
-
Implement consistent error handling for USSI. (VOLTE-3936)
-
Remove the GPRS Support indicator in proxied SRI-SM messages. (IPSMGW-838)
-
Update the Sentinel Common dependency to 2.6.0.8
-
Update the Sentinel SIP dependency to 2.6.0.9
-
Update the Sentinel Registrar dependency to UNRESOLVABLE BXREF: sentinel-registrar-changelog#2-6-0-8[2.6.0.8]
2.6.0.5
-
Fix case where the session-type is not set on the Sentinel selection key. (IPSMGW-824)
-
Update the Sentinel Common dependency to 2.6.0.7
-
Update the Sentinel SIP dependency to 2.6.0.8
-
Update the Sentinel Registrar dependency to UNRESOLVABLE BXREF: sentinel-registrar-changelog#2-6-0-7[2.6.0.7]
2.6.0.4
-
Fix a bug where a feature’s desired originating SCCP address was being overwritten and set to the default for the CGIN RA entity for outgoing TC-BEGIN messages sent by the IP-SM-GW (IPSMGW-820).
-
Adjust JVM tuning information in the Configure Rhino and the JVM documentation. This provides improved latencies (VOLTE-3618).
-
Add support for Cassandra v2.1.17 (or later in the 2.1.x series) alongside existing Cassandra version support (VOLTE-3619).
-
Update Cassandra CQL RA to 1.1.0.1
-
Update SIS version to 2.5.4.3
-
Update Rhino version to 2.5.0.2
2.6.0.3
New capabilities
-
Add support for interworking of USSD over IMS (USSI) with GSM MAP for User Initiated USSD (STLUSSI-19). See the USSI statement of compliance, and the supported flows for details.
Improvements
-
Add configuration to force the use of global title routing in the SCCP calling party address of dialog OpenAccept messages, overriding point code addressing (IPSMGW-759).
-
Add appropriate SSN and set national flag to false, for all outgoing MAP messages (IPSMGW-757, IPSMGW-758).
-
Correctly populate Sm-DeliveryFailureError causes depending on MAP version being used (IPSMGW-756).
-
Fetch Routing Info feature will now extract the IMSI from the Destination Reference of the MAP-Open if required (IPSMGW-755).
-
PS Delivery now correctly uses the service centre address instead of the MSISDN received in the MAPSM_RP_OA (IPSMGW-754).
Dependency updates
-
Update SIS version to 2.5.4.2
-
Update CGIN dependency to 1.5.4.2
-
Update the Sentinel Common dependency to 2.6.0.3
-
Update the Sentinel Registrar dependency to UNRESOLVABLE BXREF: sentinel-registrar-changelog#2-6-0-3[2.6.0.3]
-
Update the Sentinel SIP dependency to 2.6.0.4
2.6.0.2
-
The configurer will no longer affect the diameter-sentinel-internal RA entity, as it is always needs to be active in order to provide diameter factories to various features. (IPSMGW-765)
-
Use cassandra-third-party-reg RA entity from Registrar for all registration storage, update cassandra-cql-ra RA entity to be named cassandra-ipsmgw. (IPSMGW-762)
2.6.0.1
-
Update the REM dependency to 1.5.0.3
-
Update the Sentinel Common dependency to 2.6.0.1
-
Update the Sentinel Registrar dependency to UNRESOLVABLE BXREF: sentinel-registrar-changelog#2-6-0-1[2.6.0.1]
-
Update the Sentinel SIP dependency to 2.6.0.1
2.6.0.0
Improvements
-
Allow smooth combinations of Element Manager modules into a single REM by converting the IP-SM-GW Element Manager to a new style Rhino Element Manager (REM) plugin
-
Replaced the DetermineChargingInfo feature with the StoreHeaderInfo feature, which is capable of tracking additional SIP header information on a per-leg basis.
Dependency updates
-
Update Sentinel dependencies to the 2.6.0.x series
-
Update the Sentinel SIP and Sentinel Common dependencies to 2.6.0.x
-
Updated Rhino Element Manager (REM) version to 1.5.0.1
-
Updated Rhino version to 2.5.0.x
-
Updated CGIN version to 1.5.4.1
-
Updated OCSS7 version to 2.0.0.x
-
Updated SIS version to 2.5.4.1
2.5.1.0
New capabilities
-
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).
Improvements
-
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.
2.5.0.0
-
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
-
Update Diameter dependency to 2.7.0.x
2.4.0.5
-
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)
2.4.0.3
-
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)
1.0.0.2
-
For originating SMS, the MSISDN from
P-Asserted-Identity
is now added to theSM-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
1.0.0.0
-
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
Sentinel Common 2.7.0 Changelog
2.7.0.9
-
Fixed a packager issue in which paths used for profile imports could be miscalculated. (VOLTE-5139)
-
Update Ant Ivy Helpers dependency to 1.3.15. (BRM-742)
Dependency updates
-
Update the Diameter dependency to 3.1.0.4
-
Update the SIS dependency to 2.5.4.16
2.7.0.7
-
Fixed a packager issue in which paths used for profile imports could be miscalculated. (VOLTE-5139)
-
Update Ant Ivy Helpers dependency to 1.3.15. (BRM-742)
-
Extend DigitTree so that it supports full Hex numbers (by adding e and f). (VOLTE-5289)
-
Allow the XCAP User Identifier (XUI) to contain a user=phone parameter. (VOLTE-5190)
Dependency updates
-
Update the Diameter dependency to 3.1.0.3
-
Update the HTTP dependency to 2.2.0.13
-
Update the SIS dependency to 2.5.4.10
-
Update the CGIN dependency to 1.5.4.6
2.7.0.5
-
Add ability for custom XCAP implementations to detect Diameter-Sh Out-Of-Sync error responses separately from other error responses when performing a Profile Update Request. (VOLTE-4735)
2.7.0.2
-
Update Installer to validate SccpAddresses using CGIN (VOLTE-4695)
Dependency updates
-
Update the SIS dependency to 2.5.4.7
-
Update the CGIN dependency to 1.5.4.4
2.7.0.1
-
Fix a bug in the XCAP server related to idempotence of values resolved by XPaths. (VOLTE-4357)
-
Add the following single custom AVPs:
-
OC-MCC-MNC
-
OC-Age-Of-Information
-
and the following custom grouped AVPs:
-
OC-Visited-Network-MCC-MNC
-
OC-MCC-MNC
-
OC-Age-Of-Information
-
-
OC-Access-Network-MCC-MNC
-
OC-MCC-MNC
-
OC-Age-Of-Information
-
-
OC-IMSI-MCC-MNC
-
OC-MCC-MNC
-
OC-Age-Of-Information
-
See Sentinel AVP Definitions for more information.
-
Fixed feature provisioning UI for features with array type fields. (VOLTE-4489)
-
Restore the ability to read binary CDRs from the Sentinel 2.6.x series using the list-cdrs tool. (VOLTE-4492)
2.7.0.0
-
Update the Sentinel Core Mediation and Diameter Ro support to use 3GPP Rel 12 rather than 8.13.0
-
Update the Diameter dependency to 3.1.0.x
-
Remove the Hector Resource Adaptor. The Cassandra CQL Resource Adaptor should be used instead.
-
Remove the unused Cassandra based Promotions support (that used the Hector Resource Adaptor). Non-Cassandra promotions remain supported.
2.6.0.8
-
Update Correlation RA so that active correlation state is preserved during configuration updates. (STLCORE-87)
2.6.0.7
-
Deprecate one of the RATypeBinding annotation’s attributes due to a misspelling - instead of activityContentInterfaceFactoryName, use activityContextInterfaceFactoryName (VOLTE-3923)
2.6.0.3
-
Update the SIS dependency to 2.5.4.2
-
Update the CGIN dependency to 1.5.4.2
-
Update the Sentinel Common dependency to 2.6.0.3
2.6.0.1
-
Improvements to standalone packages to support packages created from various different types of "deploy" models
-
Add OC-Session-Start-Time, OC-Session-Established-Time and OC-Session-End-Time AVPs (VOLTE-3462)
-
Updated the REM dependency to 1.5.0.3
-
Update the Sentinel Common dependency to 2.6.0.1
2.6.0.0
-
Added standalone packages for Sentinel. A standalone package is a zip file that can be used to deploy, bind and configure modules into Rhino without access to Ivy or creating an SDK. Standalone packages are created inside the SDK. For further information please refer to the Sentinel SDK documentation.
-
Miscellaneous improvements to build infrastructure to enable Standalone Packages.
-
Enable use of Rhino’s arbitrary CMP fields in all Sentinel features (VOLTE-3028)
-
Removed no-args constructor from com.opencloud.sentinel.util.TableExistsVerifierImpl (STLCORE-70). New implementation requires a ProfileFacility as an argument. This is primarilly an internal change, and is only mentioned in case feature unit test implementations are directly instantiating the class for test purposes.
-
Fix bug causing invalid feature code generation for features defining multiple pojo FSMs (STLCORE-71).
-
Update the CGIN dependency to 1.5.4.1
-
Update the REM dependency to 1.5.0.1
-
Update the SIS dependency to 2.5.4.1
-
Update the Sentinel Common dependency to 2.6.0.x
2.5.0.0
-
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).
2.4.0.3
-
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 therepositories
directory. Module build output remains inMODULE/target/
. (BLDSUPP-34, STLPACK-35) -
Added example Python script for REST API interactions to build/bin/
2.3.1.16
-
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
andpostgres.jdbc.dir
in the installer (OCS-338) -
Update the HTTP RA dependency from 2.2.0.6 to 2.2.0.11
2.3.1.13
-
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
2.3.1.9
-
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
andredeploy-all
tasks (SDKTOOLS-71 and SDKTOOLS-72) -
Remove use of cascade-uninstall from the binder (SDKTOOLS-71)
-
Change
undeploy
andundeploy-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)
2.3.1.8
-
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
2.3.1.5
-
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 existinge:deployorder
, it defines the modules as a comma separated list of module names. For bothe:configureorder
ande: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.
Sentinel SIP 2.7.0 Changelog
2.7.0.11
-
Ensure IMS-Information Timestamps AVP includes information relevant to the latest Sip-Request and associated Sip-Response. (VOLTE-6028)
-
Update default configuration for the
sip-sis-ra
entity to setRFC3263:failover_enabled
to true. (VOLTE-6081) -
Ensure IMS-Information Cause-Code AVP is only present in CCR-T, CCR-Event, ACR-STOP and ACR-Event messages. (VOLTE-5985)
-
Update B2BUAScurPreChargingFeature to use Reporting-Reason
QUOTA_EXHAUSTED
in CCR-Update messages when currently Granted-Units have been consumed. (VOLTE-5981) -
Update diameter service context Id value from
8.32260@3gpp.org
to12.32260@3gpp.org
. (VOLTE-5686) -
Update tracking of session established time to better handle upstream forks. (STLSIP-1259)
-
Update DiameterPerLegInfo feature to use the outgoing Request-URI to set the Called-Party-Address AVP for a given leg. (VOLTE-5701)
-
Add extra verification of Play Announcement configuration. (VOLTE-4094)
-
Check new isInviteTerminated() method when attempting to send a BYE. (VOLTE-4786)
-
Add method to Leg to pass a MessageBody to endSubscription(). (VOLTE-4786)
-
Use event name only in Allow-Events. (STLSIP-1274)
-
Add configuration to the announcements profile to allow one way media to be enforced between the MRF and the played party. (VOLTE-6332)
Dependency updates
2.7.0.10
-
Update SipMidCallAnnouncement feature to bring the passive party off of hold following termination of a call hold announcement if necessary. (VOLTE-5381)
-
Update SipMidCallAnnouncement feature to send 491 with 'OC-Retry-After' header when it receives and INVITE while connecting the played party to the MRF. (VOLTE-5301)
Dependency updates
-
Update the Sentinel Common dependency to 2.7.0.8
2.7.0.9
-
Fix an issue in SequentialForkedSDPMediation feature affecting mediation on unlinked legs. Required to fix an issue observed during early media announcements (VOLTE-5170)
-
Update DetermineCallType to detect orig term in URI of route header (not as a parameter) (VOLTE-5210)
-
Use the latest sent SDP on a leg when doing a session refresh re-INVITE. (VOLTE-5095)
-
Update the SDP transformer function in sentinel-sip-spi so that when SDPRewriter feature zeroes a conflicting media line, it will add a zeroed connection line at the media level as well. (VOLTE-5085)
-
Update SipMidCallAnnouncement feature to use latest sent SDP for leg when putting passive party on hold. (VOLTE-5076)
-
Add Remove Headers From Outgoing Messages Feature feature to remove SIP headers and
Supported
header values from outgoing messages based on configuration. (VOLTE-5091) -
Update SIP features the following SIP features to consider synthesised OC-Term-P-Access-Network-Info:
-
Update B2BUACharging feature to suspend all legs while charging is underway. (VOLTE-4754)
-
Update the Session Refresh feature to allow the use of the UPDATE SIP method to perform session refresh. As part of this change UPDATE requests are now rejected if received between an INVITE and the corresponding PRACK or ACK and if an UPDATE transaction is already in progress. (VOLTE-5089)
-
Update the DiameterServiceInfo and DiameterPerLegInfo features to store calling party address data at session level rather than at per-leg level. (VOLTE-4912)
-
Update the SDP Monitor so that multiple SDP answers from the IM-SSF are handled correctly. (VOLTE-5300)
Dependency updates
2.7.0.8
-
Update both SipMidCallPlayAnnouncement and SipPlayAnnouncement features to set LocalContactAddress on MRF session to played party contact. (VOLTE-5009)
2.7.0.7
-
Added announcement configuration to allow session termination on early media announcement failure. (VOLTE-4939)
-
Update the SequentialForkedSDPMediation feature to mediate SDP on a forked 2xx response. (VOLTE-4934)
-
Expanded SIPUtil API for dealing with SIP message content bodies. (VOLTE-4598)
Dependency updates
-
Update the Sentinel Common dependency to 2.7.0.5
2.7.0.6
-
Update SipMidCallPlayAnnouncement feature to use a unique leg name for each MRF dialog. This ensures a clean session UAC leg FSM is used for each announcement. (VOLTE-4811)
-
Fix SequentialForkedSDPMediation feature to send UPDATE upstream when called party confirms that preconditions are met. (VOLTE-4748)
-
Added support for playing a queue of early media announcements to SipPlayAnnouncement. As part of adding this functionality, the redundant internally used session state field 'FirstTriggerOnSession' has been removed.(VOLTE-4718)
-
Added support for playing a queue of mid call announcements to SipMidCallPlayAnnouncement (VOLTE-4811)
-
Update default configuration of DetermineCallType feature to check the Request-URI cause parameter and History-Info when determining if a call has been forwarded. (VOLTE-4583)
-
Update SipUtil to set SDP attribute current remote qos status to
none
for outgoing initial INVITEs (VOLTE-4821) -
Update SipShortCode address list naming to bring it in line with provisioning standards. Any existing list entries will need to be migrated, see the Jira issue for details on how to do this. (VOLTE-4749)
Dependency updates
-
Update the Sentinel Common dependency to 2.7.0.4
2.7.0.3
-
Update the feature waiting API to allow a feature to indicate that it is waiting on more than one activity. (VOLTE-4673)
-
Fix a bug in the DetermineCauseCode feature where it would it would report the incorrect
INVITE
error response code. (VOLTE-4673) -
Update SIPNormalization Feature to skip normalization of short codes. (VOLTE-4630)
-
Fix a bug in DiameterPerLegInfo so it can find the initial requested party. (VOLTE-4628)
-
Fix a NPE in SipMidCallPlayAnnouncement when playing an announcement to any party after the calling party has left the call. Now it creates the MRF INVITE from the played party initial INVITE instead of the calling party INVITE (VOLTE-4765)
Dependency updates
-
Update the Sentinel Common dependency to 2.7.0.3
2.7.0.2
-
Update to B2BUAScurFeature when credit reservation instructed, session also established if applicable. (VOLTE-4567)
-
Improve ExtractNetworkInfoFeature stats. (VOLTE-4532)
-
Update DiameterServiceInfo to set P-Access-Network-Info AVPs based on registration. (VOLTE-4531)
-
Fix SequentialForkedSDPMediation feature to send UPDATE downstream when called party requests confirmation that preconditions are met. (VOLTE-4551)
-
Fix an issue where the SipMidCallPlayAnnouncement feature could generate incorrect SDP. (VOLTE-4509)
-
Add additionalCallForwardingDetection configuration to Determine Call Type feature. (VOLTE-4495)
Dependency updates
-
Update the SIS dependency to 2.5.4.7
-
Update the Sentinel Common dependency to 2.7.0.2
2.7.0.1
-
Expanded SIPUtil API for dealing with SIP message content bodies. (VOLTE-4272)
-
Add support for handling SDP content embedded in multipart content bodies. (VOLTE-4272)
-
Reject requests with 500 if Refer-To header is invalid. (VOLTE-4061)
-
Update Sentinel Sip Configuration to include ISOCode, MCC, MNCs. (VOLTE-4430)
-
Add new feature ExtractNetworkInfo to extract the MCC and MNC from the signaling and 3rd party registration data. (VOLTE-4376) See Extract Network Info Feature.
-
Add new profile MobileCountryCodeInformation with MCC and MNCs from operators extracted from http://mcc-mnc.com. (VOLTE-4389)
-
Update Ro, Rf and AvpCDRs to include the OC-Visited-Network-MCC-MNC, OC-Access-Network-MCC-MNC and OC-IMSI-MCC-MNC when applicable. (VOLTE-4378, VOLTE-4390)
Dependency updates
-
Update the Ant XJC dependency to 1.1.2
-
Update the SIS dependency to 2.5.4.4
2.7.0.0
-
First release in the 2.7.0.x series.
New Capabilities
-
Add support for Diameter Rf out of the box. Rf support can be selected at install time. Rf support includes replay of buffered CDRs when the Charging Data Function is not available. Support for Rf is enabled by the Rf Control Resource Adaptor.
-
The Rf Control Resource Adaptor includes out-of-the-box Alarms.
-
AVPs used on the Rf interface are described in the Charging Information section of the Administration guide.
-
The Interim CDR Feature can now be configured use the Rf Control Resource Adaptor, as well as AVP CDRs.
-
Out-of-the-box Diameter AVPs for Ro and CDRs are now based on 3GPP Rel 12, rather than 3GPP Rel 8.13.0 as in earlier releases. Rf AVPs are Rel 12.
-
The Diameter Ro Resource Adaptor has been updated to the 3.1.0.x release series, enabling AVP version downgrade/upgrade between Rel 12 and older versions. The Ro Resource Adaptor can now be configured with a SLEE API version that is different to the "wire" protocol version for the OCS. Downgrading from Rel 12 is supported as far back as Rel 8.13.0. For further information refer to Diameter Resource Adaptors Changelog.
-
The Sentinel Registrar service has been re-written in terms of Sentinel SIP. This means 3rd Party Registration features are programmed the same way as other SIP features, simplifying development. In previous releases general 3rd Party Registration functionality was only available as part of Sentinel VoLTE and Sentinel IP-SM-GW applications. As of this release it is available in Sentinel SIP. For further information refer to Sentinel Registrar Overview and Concepts
Dependency updates
-
Update the Diameter dependency to the 3.1.0.x series. See Diameter Resource Adaptors Changelog
-
Update the Sentinel Common dependency to the 2.7.0.x series
2.6.0.10
-
Update early media SipPlayAnnouncement feature to support forwarding calling-party UPDATE requests to the MRF. (VOLTE-4270)
-
Fix bug in SipAddressUtil where escaped '#' characters are not handled when extracting phone numbers from SIP URIs. (VOLTE-4173)
-
Update Diameter service information feature to record URI parameters in Called-Party-Address and Calling-Party-Address AVPs. (VOLTE-4174)
-
Update the Sentinel Common dependency to 2.6.0.9
2.6.0.9
-
Update early-media play announcement feature to allow an announcement to the calling party to be interrupted if the called party answers the call. (VOLTE-4188)
-
Update the Sentinel Common dependency to 2.6.0.8
2.6.0.8
-
Update SequentialForkedSDPMediation to copy Contact header from 183 into UPDATE on calling party leg (VOLTE-3948)
-
Update SequentialForkedSDPMediation to maintain consistent SDP session ID on calling party leg (VOLTE-3961)
-
Update SipPlayAnnouncement so that a consistent Record-Route is sent in all dialog-creating responses sent upstream (VOLTE-3925)
-
Update the Sentinel Common dependency to 2.6.0.7
2.6.0.7
-
Add documentation for the SDP Rewriter Feature.
-
Add I-CSCF configuration to the Sentinel SIP Service configuration (VOLTE-3785) This change enables features to not have their own I-CSCF configuration values. Features with their own I-CSCF configuration values still use those values.
-
Add support for precondition callflows to the Early Media Play Announcement feature (VOLTE-3609)
-
Enhance SDP conflict management to support static SDP payload types from RFC 3551 (VOLTE-3668)
-
Update the Sentinel Common dependency to 2.6.0.6
-
Update the SIS dependency to 2.5.4.3
-
Update the Rhino dependency to 2.5.0.2
2.6.0.3
-
Improved handling of payload type conflicts in SDP bodies (VOLTE-3425)
-
Improved handling of SDP bodies with differing numbers of media lines (VOLTE-3424)
-
Add support for handling SDP inside multipart/mixed SIP message bodies (STLUSSI-30)
-
Update the SIS dependency to 2.5.4.2
-
Update CGIN dependency to 1.5.4.2
-
Update the Sentinel Common dependency to 2.6.0.3
2.6.0.1
-
Add support for the OC-Session-Start-Time, OC-Session-Established-Time and OC-Session-End-Time AVPs to the AVP CDR features (VOLTE-3462)
-
Add a retry-after header to 500 error responses generated when an SDP offer is received whilst an offer is in progress (VOLTE-3408)
-
Update the REM dependency to 1.5.0.3
-
Update the Sentinel Common dependency to 2.6.0.1
2.6.0.0
-
Add support for Interim CDRs through the Interim CDR Feature. A description of Interim CDRs is available in the Interim CDRs section of the administration guide.
-
Document disk storage requirements in the Sizing AVP CDRs section.
-
Add new SipSetLanguage feature. See Sip Set Language Feature
-
Add Language support for announcements. The user can define the same announcement Id with multiple languages. See SIP Play Announcement Feature and SIP Mid Session Play Announcement Feature
-
Rename DetermineChargingInfo feature to StoreHeaderInfo, and retrieve additional data from the triggering messages. See Store Header Information Feature.
-
Update the REM dependency to 1.5.0.1
-
Update the SIS dependency to 2.5.4.1
-
Update the Sentinel Common dependency to 2.6.0.x
2.5.0.0
-
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)
2.3.1.17
-
Fix a bug related to re-writing the Event header of NOTIFY requests when Sentinel acts as a B2BUA. (STLSIP-1122)
2.3.1.16
-
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)
2.3.1.15
-
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)
2.3.1.13
-
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
2.3.1.12
-
Update Sentinel Common dependency to 2.3.1.12
-
Included SIP Example module-pack (STLPACK-40)
2.3.1.9
-
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
2.3.1.5
-
Update Sentinel Common dependency to 2.3.1.5
-
Fix a bug in the SIP Determine Network Operator module pack
2.3.1.0
-
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.