4.0.0.10
-
Use none scope for SAS
SIP_ALL_REGISTER_MARKER
, using trace scope incorrectly correlates multiple REGISTERs into one trace. (#176204)
Dependency Updates
4.0.0.9
-
Fix an issue where a
TcOperationProviderError
in response to MT-FSM was not handled correctly. The error was not forwarded upstream to the SMSC.
Dependency Updates
4.0.0.6
-
Handle SRI success result and InformSC request received in single TCAP block. (IPSMGW-1017)
-
Fix issue in CS Delivery feature with respect to MT-Forward-SM result handling. When received in a separate TCAP block to the close we fail to proxy the result. (IPSMGW-1019)
Dependency Updates
4.0.0.5
-
Fix NPE in CS Delivery feature that can occur when
sm-DeliveryFailure
error does not include ansm-Enumerated-Delivery-Failure-Cause
. (IPSMGW-1006) -
Update default sip-sis-ra configuration to send 100 Trying responses for non-INVITE transactions: after 3500ms on UDP; 1000ms on TCP and other reliable transports. (VOLTE-9906)
Dependency Updates
4.0.0.2
-
Changed default SAS resource ID from ipsmgw-1.0 to rhino-smo-4.0.0. (OPT-3293)
Dependency Updates
4.0.0.1
-
A new SAS bundle should be installed into SAS to take into account IPSMGW-1002 and IPSMGW-1003 mentioned below.
-
Reject MAP Open Requests that have a Calling Party SCCP Address equal to the SCCP Address that IPSMGW uses when sending MAP Open Requests . This is to stop a particular class of routing loop that can occur with undesirable STP configuration. When such an Open Request is detected a Warning level message is logged, and a new type of Message sent to SAS. (IPSMGW-1003)
-
Enhance SAS diagnostics for the IPSMGW by adding the SCCP Calling and Called Party addresses to MAP Open Requests that are received by and sent from the IPSMGW. These parameters are available in the "Detailed events" view in SAS. This means a new SAS bundle needs to be uploaded to SAS in order to view these parameters in SAS. (IPSMGW-1002)
Dependency Updates
4.0.0.0
-
Update IPSMGW replication strategy in Cassandra schema to SimpleStrategy. (IPSMGW-999)
-
Change the keyspace that IPSMGW uses for registrations to allow VoLTE and IPSMGW registrations in the same cassandra instance (VOLTE-8727)
-
Rename feature SCCPWhitelist to SCCPAllowlist. (IPSMGW-1001)
Dependency Updates
3.1.0.1
-
Add flag to suppress HLR interaction (IPSMGW-997)
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.1
3.1.0.0
-
First release in the 3.1.0.x series.
-
Rename SBB feature artifacts from
-du.jar
to.du.jar
. (VOLTE-8239)
Dependency updates
3.0.0.2
Dependency updates
-
Update the Rhino dependency to the 2.6.2.7
-
Update the Rf Control RA dependency to 1.0.2.2
3.0.0.0
-
First release of the 3.0.0.x series
-
Add support for answering an SRI for SM request without first proxy-ing the request to the HLR. (IPSMGW-954)
-
If configured for PS preferred delivery (PS_THEN_CS or PS_ONLY) and the subscriber is IMS registered IP-SM-GW will not query the HLR on receipt of an SRI SM. An SRI SM query will only be sent to the HLR when CS delivery is required. (Section 5.3.3.3. from 24.341)
-
-
Add support for tracking third-party registration ownership between multiple geo-redundant IP-SM-GW sites. (IPSMGW-956)
-
Add support for splitting generated RP message reference numbers across multiple geo-redundant IP-SM-GW sites into unique per-site ranges. (IPSMGW-961)
-
Add originationReference and destinationReference to USSD MAP OPEN message. OriginationReference is set to the Sentinel IPSMGW Address configuration. DestinationReference is set to the IMSI of the registered user (or unset if that is invalid). (IPSMGW-979).
-
Fix minor issue in IPSMGWCSDelivery feature that caused ActivityEndEvents to be unnecessarily processed for ReportSM dialogs during CS_THEN_PS fallback. (IPSMGW-989)
Dependency updates
2.9.0.0
-
First release of the 2.9.0.x series
-
The Sh Cache RA has been removed, and replaced by the Sh Cache Microservice. See Changes in Major Release for details.
-
Added MO Submission Location feature. (IPSMGW-945)
-
Add support for network initiated/timed out deregistration. (VOLTE-6985)
Dependency updates
-
Added dependency on the Sh Cache Microservice 1.0.0.x series
-
Updated Sh Cache RA dependency to the 1.0.5.x series (RA type only)
-
Update Cassandra CQL RA dependency to 1.2.0.2
-
Update the Sentinel Common dependency to 2.9.0.0
-
Update the Sentinel SIP dependency to 2.9.0.0
-
Update the Rhino dependency to the 2.6.2.x
-
Update the SIS dependency to the 2.6.2.x series
-
Update the MMTel Standard Schema dependency to the 1.1.3.x series
2.8.0.3
-
Update callers of deprecated CassandraRow.getDate() to use CassandraRow.getTimestamp(). (VOLTE-6119)
-
Use v3 MAP dialog in FetchIMSI if SriSmDeliveryNotIntended is set to true, and change default to false. (IPSMGW-944)
-
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
-
Update the Sentinel Common dependency to 2.8.0.3
-
Update the Sentinel SIP dependency to 2.8.0.3
-
Update cassandra-cql dependency to 1.2.0.1
-
Update the Rhino dependency to 2.6.1.3
-
Update the SIS dependency to 2.6.1.6
-
Update the Diameter dependency to 3.1.1.2
-
Update the Sh Cache RA dependency to 1.0.4.3
2.8.0.0
-
First release of the 2.8.0.x series
-
Added Metaswitch Service Assurance Server (SAS) support to the IPSMGW and USSI products.
-
Remove deprecated methods, classes, and legacy modules. (VOLTE-5332) See Changes in Major Release for details.
-
Add support for tracing calls to Metaswitch Service Assurance Server.
-
Use ADDRESS_E164 address type for SmsInformation.*-SCCP-Address CDR fields. (IPSMGW-866)
Dependency updates
-
Update the Sentinel Common dependency to 2.8.0.0
-
Update the Sentinel SIP dependency to 2.8.0.0
-
Update the Rhino dependency to 2.6.1.1
-
Update the CGIN dependency to 2.0.0.0
-
Update the SIS dependency to 2.6.1.2
-
Update the Sh Cache RA dependency to 1.0.4.1
-
Update the MMTel Standard Schema dependency to 1.1.2.2
2.7.1.2
-
First release of the 2.7.1.x series
-
Update diameter service context Id value from
8.32274@3gpp.org
to12.32274@3gpp.org
. (VOLTE-5686)
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
-
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)
Sentinel Common 4.0.0 Changelog
4.0.0.15
Dependency Updates
-
Update the Cassandra Cql dependency to 2.0.0.3
-
Update the Sis dependency to 3.0.0.13
4.0.0.14
Dependency Updates
-
Update the Rhino dependency to 3.0.0.21
-
Update the Sh Cache Microservice dependency to 4.0.0.9
-
Update the SIP dependency to 3.0.0.12
-
Update the SIS dependency to 3.0.0.12
4.0.0.13
-
Added a class
FeatureStatsBucketSet
to support feature stat bucket sets. (#223772)
Dependency Updates
-
Update the CGIN dependency to 3.0.0.3
-
Update the Diameter dependency to 4.0.0.1
-
Update the Rhino dependency to 3.0.0.19
-
Update the Sh Cache Microservice dependency to 4.0.0.8
-
Update the SIP dependency to 3.0.0.9
-
Update the SIS dependency to 3.0.0.11
4.0.0.12
Dependency Updates
-
Update the Rhino dependency to 3.0.0.18
-
Update the Sh Cache Microservice dependency to 4.0.0.7
-
Update the SIP dependency to 3.0.0.6
-
Update the SIS dependency to 3.0.0.10
-
Update the OC SS7 dependency to 4.0.0.3
4.0.0.11
Dependency Updates
-
Update the Rhino dependency to 3.0.0.17
-
Update the Sh Cache Microservice dependency to 4.0.0.6
4.0.0.10
-
Added createZipFile and zipOutputPath arguments to create-package Ant task (RRE-1123)
Dependency Updates
-
Update the CGIN dependency to 3.0.0.2
-
Update the Rhino Element Manager (REM) dependency to 3.0.0.4
-
Update the Rhino dependency to 3.0.0.16
-
Update the Sh Cache Microservice dependency to 4.0.0.5
-
Update the SIP dependency to 3.0.0.5
-
Update the SIS dependency to 3.0.0.9
4.0.0.9
Dependency Updates
-
Update the Rhino Element Manager (REM) dependency to 3.0.0.2
-
Update the Rhino dependency to 3.0.0.14
-
Update the SIP dependency to 3.0.0.4
-
Update the SIS dependency to 3.0.0.7
4.0.0.8
-
Added setContextClassLoader runtime permission to MySQL library jar. (RRE-1044)
Dependency Updates
-
Update the Rhino dependency to 3.0.0.12
-
Update the Sh Cache Microservice dependency to 4.0.0.4
-
Update the SIP dependency to 3.0.0.3
-
Update the SIS dependency to 3.0.0.5
4.0.0.7
Dependency Updates
-
Update the Rhino dependency to 3.0.0.10
-
Update the Sis dependency to 3.0.0.3
-
Update the Docker Support dependency to 2.0.0.4
4.0.0.6
Dependency Updates
-
Update the Cassandra Cql dependency to 2.0.0.2
-
Update the Rhino dependency to 3.0.0.9
-
Update the Sh Cache Microservice dependency to 4.0.0.3
-
Update the Sip dependency to 3.0.0.2
-
Update the Sis dependency to 3.0.0.2
4.0.0.4
-
Fix issue in indirect run and runcritical feature script statements where the incorrect feature could be executed under load conditions (VOLTE-9546)
-
Fix
sentinel-management
RA to not unregister MBeans during declarative config import. (VOLTE-9370)
Dependency Updates
-
Update the Rhino dependency to 3.0.0.6
-
Update the Sh Cache Microservice dependency to 4.0.0.2
4.0.0.3
-
Update run and runcritical feature script statements so the feature to be executed may be resolved from a session state field (RRE-649)
4.0.0.1
-
Fixed an issue that prevented packages from setting tracer levels during installation (VOLTE-9224)
-
Standard module build will now generate SAS enums if a SAS bundle file is present. (RM-858)
-
Upgraded bundled Apache Ivy version to 2.5.0-rc1 (from 2.3.0). (BRM-837)
-
Added support for building modules in parallel to reduce build time. To enable, add
-Dbuild.multithreaded=true
to Ant commands or setbuild.multithreaded=true
insdk.local.properties
. (BRM-837) -
First release in the 2.7.0.x series.
-
Improve support for http proxies in the Sentinel SDK tools. (VOLTE-3215)
-
Miscellaneous improvements to build infrastructure to enable Standalone Packages.
-
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) -
Avoid
find
error when initialising SDK -
Fix go-offline script when it is run through the installer
-
Disallow conflicting go-offline repository names
-
Make go-offline work on a Mac
-
Prompt for confirmation by default for all undeploy tasks
-
Quieten Ivy bootstrap unless specified otherwise
-
Add support for dry-run propagation through a number of commands
-
Create a verbose logfile when performing builds
-
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
-
Upgrade to Java 11
-
Change
AddressListConfigurationProfile
profile specificationversion
attribute from typelong
toString
to support UUID-based address list versioning. (OPT-2252) -
Improve SAS reporting when running a feature execution script to include the name of the execution point that the script is running at. (STLSIP-1300)
-
Add API for features to manage rate limiter filter conditions. (VOLTE-8468)
-
Used to flag specific types of messages (access transfer invites and emergency calls, for example) as unlimitable.
-
-
Add support for features to perform periodic work unrelated to an active session. (VOLTE-8469, VOLTE-8784)
-
Introduces a new
PeriodicWorkInterval
setting in theSentinelConfigurationTable
. -
Used by features to initially configure and update rate limiter filter conditions.
-
Dependency Updates
-
Update the Cassandra CQL dependency to 2.0.0.0
-
Update the CDR RA dependency to 3.0.0.0
-
Update the CGIN dependency to 3.0.0.0
-
Update the DB Query RA dependency to 2.0.0.0
-
Update the Diameter dependency to 4.0.0.0
-
Update the Easysip Ratype dependency to 3.0.0.0
-
Update the FSM Tool dependency to 2.0.0.0
-
Update the HTTP RA dependency to 3.0.0.0
-
Update the MMTel Standard Schema dependency to 2.0.0.0
-
Update the OC Schema Generator dependency to 2.0.0.0
-
Update the OCSS7 dependency to 4.0.0.0
-
Update the RA Infrastructure dependency to 3.0.0.0
-
Update the REM dependency to 3.0.0.0
-
Update the Rf Control dependency to 2.0.0.0
-
Update the Rhino dependency to 3.0.0.2
-
Update the Sentinel Common dependency to 4.0.0.1
-
Update the Sh Cache Microservice dependency to 4.0.0.0
-
Update the Sh Cache RA dependency to 2.0.0.0
-
Update the SIP dependency to 3.0.0.0
-
Update the SIS dependency to 3.0.0.0
3.1.0.4
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.4
-
Update the Mmtel Standard Schema dependency to 1.3.0.1
-
Update the Rf Control dependency to 1.0.3.2
3.1.0.3
-
Fixed an issue in which the create-package command was not escaping commas in String profiles or config properties (VOLTE-8561)
-
Fixed an issue in which the create-package command failed when the specified component was not configurable (VOLTE-9125)
-
Fixed an issue in which the create-package command built a package that could not be deployed due to missing sdk.component.version property (VOLTE-9125)
-
Handle nulls appropriately in binding step (VOLTE-9126)
-
Removed hardcoded repo path for sync task
-
Fix dbquery-ra deployment issue where it deletes the jar file. (RRE-272)
Dependency Updates
-
Update the Diameter dependency to 3.1.3.1
-
Update the OC Schema Generator dependency to 1.0.1.4
-
Update the REM dependency to 2.7.0.2
-
Update the RF Control dependency to 1.0.3.1
-
Update the Rhino dependency to 2.7.0.3
-
Update the Sh Cache Microservice dependency to 3.1.0.3
-
Update the Easysip Ratype dependency to 1.7.2
3.1.0.2
-
Standard module build will now generate SAS enums if a SAS bundle file is present. (RM-858)
-
Truncate long debug trace lines in Correlation RA to avoid problems with OOMError in LogRollover (RHI-5889)
-
Add setContextClassLoader runtime permission to MySQL library jar. (RRE-10)
Dependency Updates
-
Update the Cassandra CQL dependency to 1.2.0.3
-
Update the CGIN dependency to 2.0.0.4
-
Update the SIP dependency to 2.7.0.1
-
Update the Sis dependency to 2.7.0.1
-
Update the DB Query RA dependency to 1.4.0.6 (RRE-22)
3.1.0.1
Dependency Updates
-
Update the fsmtool dependency to 1.3.0.1
-
Update the rem dependency to 2.7.0.1
-
Update the rhino dependency to 2.7.0.2
-
Update the sh-cache-microservice dependency to 3.1.0.1
3.1.0.0
-
First release in the 3.1.0.x series
-
Upgraded bundled Apache Ivy version to 2.5.0-rc1 (from 2.3.0). (BRM-837)
-
Added support for building modules in parallel to reduce build time. To enable, add
-Dbuild.multithreaded=true
to Ant commands or setbuild.multithreaded=true
insdk.local.properties
. (BRM-837) -
Rename SBB feature artifacts from
-du.jar
to.du.jar
. (VOLTE-8239) -
Use ExtendedTracer instead of Tracer in features. (VOLTE-8308)
-
Fix issue in
BaseHomePlmnIdConfigurer
in the installer where duplicate MCCs could be added. (VOLTE-8066) -
Fix issues with Correlation ID Pool profile tables where invalid profiles could be added. (VOLTE-6064)
-
Fix issue in the XCAP server where it would reply to a malformed request with a 500 response instead of a 4xx response. (VOLTE-6620)
-
Add new Diameter AVP for recording when a session fail-over has occurred. (STLSIP-1293)
-
Add new Companion Device Extension AVPs. (VOLTE-8067)
Dependency Changes
-
Update the Rhino dependency to 2.7.0.0
-
Update the REM dependency to 2.7.0.0
-
Update the Diameter dependency to 3.1.3.0
-
Update the SIP dependency to 2.7.0.0
-
Update the SIS dependency to 2.7.0.0
-
Update the Rf Control RA dependency to 1.0.3.0
-
Update the Sh Cache RA dependency to 1.0.6.0
-
Update the Sh Cache Microservice dependency to 3.1.0.0
-
Update the MMTel Standard Schema dependency to 1.3.0.0
3.0.0.2
-
Fix a rare NullPointerException that could cause threads in Rhino versions older than 2.6.2.4 to go into an infinite loop. (OCFE-3769)
Dependency updates
-
Update Rhino dependency to 2.6.2.6
3.0.0.1
-
Fix validation in
BaseHomePlmnIdConfigurer
to allow a MCC with no MNC. (VOLTE-7938)
Dependency updates
-
Update the Rhino dependency to 2.6.2.3
3.0.0.0
-
First release in the 3.0.0.x series
-
Added support for
runcritical
statement in Feature Execution Script Editor. (VOLTE-7351)
2.9.0.2
Dependency updates
-
Update the Rhino dependency to 2.6.2.2
-
Update the Diameter RA dependency to 3.1.2.1
-
Update the HTTP RA dependency to 2.5.0.1
2.9.0.1
-
Added ability to search address list entries in REM. (VOLTE-7084)
-
Improved paging of feature configuration and address list entries in REM. (VOLTE-7265)
-
Fixed error that could occasionally occur in VoLTE EM when accessing the Feature Configuration page. (VOLTE-7356)
Dependency updates
-
Update the Rhino dependency to the 2.6.2.1
2.9.0.0
-
First release in the 2.9.0.x series
-
Allow Sentinel front-ends to use Diameter Ro session replication (PRD-1070). This includes:
-
Arming of the
Validity-Time
andTcc
timers in redundant mode if the session is replicated -
Exposing the
ActivityContextInterface
for the Diameter Ro session in the mediation client state machine
-
-
Add Announcement-Information AVP and child AVPs from 3GPP Release 13 as extension AVPs. (VOLTE-5057)
-
Rename various Sentinel AddressList profiles such that the configured PlatformOperator and NetworkOperator match the profile name. (VOLTE-7098, VOLTE-7255)
-
Add validation of shortcode address list configuration entries. (VOLTE-7025)
-
Only DTMF digit strings permitted for shortcode.
-
Only RFC 2806 phonedigits (and optional '+' prefix) permitted for TranslatedAddress.
-
-
Fixed a bug that could cause REM feature configuration to display the wrong information. (VOLTE-3774)
-
Add feature functional groups for easing configuration in the Element Manager web UI. (VOLTE-6878)
Dependency updates
-
Update the Rhino dependency to the 2.6.2.x series
-
Update the Rhino Element Manager dependency to the 2.6.2.x series
-
Update the Diameter dependency to the 3.1.2.x series
2.8.0.3
-
Fix parsing of 'else' statements in feature scripts in REM. (VOLTE-6262)
-
Load normalizer component and its configuration into XCAP, and add support for caching general Rhino profiles. (VOLTE-6211, VOLTE-6212)
-
Deprecate the subscriptionType session state field and introduce new subscriptionIdType and subscriptionId session state fields for use in charging. (VOLTE-2692)
Dependency updates
-
Update the Rhino dependency to 2.6.1.3
-
Update the Diameter dependency to 3.1.1.2
-
Update the SIS dependency to 2.6.1.6
2.8.0.1
-
Fixed an issue in which the create-package command would fail for modules which contain byte array profile attributes. (VOLTE-6107)
Dependency updates
-
Update the Rhino dependency to 2.6.1.2
-
Update the SIS dependency to 2.6.1.4
-
Update the Diameter dependency to 3.1.1.1
2.8.0.0
-
First release in the 2.8.0.x series
-
Added OC-Billing-ID custom AVP. See Sentinel AVP Definitions for more information. (VOLTE-5056)
Dependency updates
-
Update the Rhino dependency to 2.6.1.1
-
Update the Rhino Element Manager dependency to 2.6.1.1
2.7.1.3
-
Reorganise common SAS log events. (VOLTE-5703)
Dependency updates
-
Update the HTTP dependency to 2.4.0.2
-
Update the SIS dependency to 2.5.5.3
2.7.1.2
-
First release in the 2.7.1.x series
New Capabilities
-
Added Metaswitch Service Assurance Server (SAS) support
-
Tracing selection keys, feature scripts and any features reporting featureFailedToExecute, featureCannotStart, featureIssuedWarning or featureTimeOut.
-
Dependency updates
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)
-
Change all extension AVPS to have MandatoryRule and ProtectedRule values to 1 = MAY. (VOLTE-5972)
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 4.0.0 Changelog
4.0.0.16
-
Session-Expires header, Min-SE header and "timer" value of the Supported header are now copied to the MRF INVITE in the Play Announcement feature. (#519194)
-
Fixed a bug in the SIP Play Announcement features which caused URI parameters in the configured ICSCF URI to be ignored. (#641218)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.15
4.0.0.15
-
Address B2BUA issue observed when a PRACK is received on the upstream leg for
rel100
response after the downstream leg has already been terminated. (#206770) -
The Sip Play Announcement (Early Media) feature runs twice in the MMTel-Term SIP Access Response feature script. It would queue the same response twice. If the message contains SDP, it can interact badly with the SDP Monitor and cause issues with subsequent SDP negotiation. (#359032)
-
This addresses a CDIV announcement regression introduced by changes to SDP Monitor. (VOLTE-10166)
-
-
Fix a bug in SequentialForkedSDPMediation feature when handling an ACK during mediation. (VOLTE-7976)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.14
4.0.0.14
-
Update StoreHeaderInfo to set the IsOCTerminatingDomainPresent flag to true if 'OC-Terminating-Domain' header is present. (#233441)
-
Update RecordTimestampsFeature to record the timestamp of an initial INVITE 180 Ringing. The timestamp is used by VolteNetworkKPI to calculate Post Dial Delay. (#195142)
-
Fix an issue in the B2BUA SCUR feature that allowed rounding errors to accumulate over time. When the rounding error accumulates to a full second value the next CCR will include a greater number of
Used-Service-Units
than granted in the previous CCA. (VOLTE-8788) -
As a result of this fix the
OC-Cumulative-Granted
counter (present in CDRs) will report a partial second value if at some point during a session credit is invalidated. -
Fix issue with parsing of P-Associated-URI, where earlier it was taking the entire value of the field eg. "<sip-uri>;param=val", vs now it would take only the part inside of angle braces (<sip uri>). (#257024)
-
Fix a typo in SAS bundle for 2 events in SipMidCallPlayAnnouncement feature so that the leg name is displayed in the summary as intended, and one in SipPlayAnnouncement feature so that UNABLE_TO_LINK_LEGS correctly shows the exception message if one is provided. (#257684)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.13
4.0.0.12
-
Fix issue where post mid call announcement the passive party would receive SDP answer containing
m=
lines not present in the SDP offer. This could happen if the played party negotiated different media to those agreed for the original call. (VOLTE-9212) -
When Normalizing numbers from national to international format, allow for the possibility that the Country Code on the output number matches the National Dial Prefix on the input number, as is commonly the case for US numbers. (VOLTE-9949)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.11
4.0.0.11
-
Update SDPMonitor to execute FSM on all outbound messages for a leg. Previously you could use
leg.sendMessage()
to send both an SDP error response and a new SDP offer in the same transaction. The offer would not be detected by the SDPMonitor feature and associate leg SDP accessors would not be updated. (VOLTE-10166) -
Fixed an issue in SequentialForkedSDPMediation feature where a preconditions UPDATE arrives from calling party while updating preconditions in called party, causing an exception and leaving FSM in a bad state. (VOLTE-10150)
-
Add support in the leg manager for storing and retrieving the most recent INVITE 18x response on each leg, and for tracking whether there are reliable provisional responses on a leg that have yet to be acknowledged with a PRACK request. (VOLTE-10132)
-
Add support in the leg API for querying the progress of the INVITE session setup on that leg. (VOLTE-10133)
-
Ensure session replication isn’t altered after determined for session. (STLSIP-1327).
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.10
4.0.0.10
-
Fix error that occurs in Sentinel SIP when forwarding a request if multiple SIS RA entities are used. (VOLTE-9855)
4.0.0.9
-
Update VerticalServiceCode feature to provide an annotated version of the incoming dialled number for other features to use when doing dialled number analysis. Annotated elements include service codes and country/network related dialling codes. (VOLTE-10077)
-
Add the NorthAmericanNumberingPlan feature, which examines dialled numbers based on information from the normalizer to identify numbers that are within the North American numbering plan and load additional geographic information when a geographic area code is detected. (VOLTE-9962)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.9
4.0.0.8
-
Added a number of ServiceInformationSessionState fields containing various aggregated and extracted values for use as sources of data for Service-Specific-Info AVPs. (VOLTE-9894)
-
Add support for including customizable Service-Specific-Info AVPs in Diameter charging messages. (VOLTE-9893)
-
Fixed an issue in SequentialForkedSDPMediation feature where media changes present in a caller UPDATE response to a mediated 183 were not passed on to the callee. (VOLTE-9825)
-
Allow configuration of the Service-Id and Rating-Group AVPs through the DetermineCharging profile. (VOLTE-9892)
-
Allow configuration of the RequestUnitsSeconds in Credit-Control-Requests through the DetermineCharging profile. (VOLTE-9924)
-
Added SAS tracing to Session Tracking feature. (VOLTE-9914}
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.8
-
Update the Sentinel Sip Service Information Session State Library dependency to latest.integration
-
Update the Sentinel Sip Determine Charging dependency to latest.integration
4.0.0.6
-
Remove warnings in sending SIP messages for where one of the legs in the call has already been properly terminated. (VOLTE-9718)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.6
4.0.0.4
-
Update early-media play announcement feature to interrupt announcement if the called party responds with an error. (STLSIP-1313)
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.4
4.0.0.2
-
Extend Vertical Service Code feature to allow VSCs in SIP URIs with globally formatted (+) parameters for numbers in the home country code. (VOLTE-9164).
-
Update the mid-call announcement feature so that it ignores disabled media streams (port = 0) when placing the passive party on hold. (VOLTE-9321)
4.0.0.1
-
This release is built on and requires JDK 11. It requires Rhino 3.0 or later releases.
-
Improvements to handling of reason headers on CANCEL requests. (STLSIP-1310)
-
Extended SIP leg API to make it easier for features to specify Reason headers when explicitly instructing Sentinel to generate an outbound CANCEL request.
-
Update the SIP service to populate Reason headers when automatically generating a CANCEL request due to a leg ending. The header values will match the Reason headers on the last received CANCEL request, or a default value if none have been received.
-
-
Modified handling of activities when a feature enters the waiting state. Previously all activities would be suspended and then activities that the feature is waiting on would be resumed, but this can cause issues when a feature has activity contexts from different transactions. So now activities will only be suspended if they will stay that way, activities that the feature is waiting on will never be suspended. (VOLTE-9290)
-
Log ICID to SAS with double quotes (STLSIP-1314) SAS requires markers to be raised with identical data for it to correlate trails. Both Clearwater and CFS raise ICID with surrounding double quotes so Sentinel is modified to do the same.
Dependency Updates
-
Update the Sentinel Common dependency to 4.0.0.1
3.1.0.3
-
Update
SdpTransformerFunction
to include attributes for a zero’dMediaDescription
(VOLTE-8515). -
Make interim CDR trigger generation overridable by subclasses (RRE-219)
-
Extend SDP rewriting to also update username, address and address-type in o= lines. (VOLTE-8789)
-
Add support in SipMidCallPlayAnnouncement feature for alternative ways of handling the passive party during an announcement. (VOLTE-9170) The feature now offers the following options, which can be chosen by features when they queue an announcement:
-
NO_HOLD
: The passive party is not put on hold during the announcement, media streams are left as they were. -
BLACK_HOLE_ONLY
: SDP is renegotiated with the passive party so that for the duration of the announcement, all media streams are directed to a black hole IP. -
FULL_HOLD
: SDP is renegotiated with the passive party so that for the duration of the announcement, all media streams are directed to a black hole IP; additionally the passive party is put on hold by setting the stream status tosendonly
orinactive
. This is the old behaviour and remains the default.
-
-
If a Reason header is present on an incoming CANCEL request, it will now be copied onto any corresponding outbound CANCEL request on the linked SIP leg. Additionally, when a feature creates a new outbound CANCEL request with Reason header, the header will now be correctly included when the message is sent. (STLSIP-1301)
-
Make the Sentinel SIP service handle outstanding PRACK requests as per RFC 3262 (STLSIP-1298). Outstanding PRACK requests that match acknowledged reliable provisional responses respond with a 200 response irrespective of if a session has ended.
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.3
3.1.0.2
-
Improve
MediaDescription
comparison inSdpTransformerFunction
so that a media descriptionrtpmap
attribute which includes an explicit channel declaration (/1) is considered equivalent to the samertpmap
attribute that implies a single channel is in use (without /1). (VOLTE-8810) -
Update
ChargingInstanceToCCR
mapper andSipAvpCdrUtil
to ensure CCR-Us and ACR-Is includeTimestamps
AVP based on theSipTimestampAvpPresenceMode
attribute from theDetermineChargingConfigProfileTable
. (VOLTE-8493) -
Fix NPE in SequentialForkedSDPMediationFeature when triggering leg not available. (STLSIP-1306)
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.2
3.1.0.1
-
Ensure IMS-Information Timestamps AVP is populated when the final response is received on a forked leg. (VOLTE-7610)
-
Improved post-execution heap retention behavior of most pojo feature FSMs though use of new
registerActionImplementationForNextExecute
FSM method. (VOLTE-8690) -
Add
oc-ue-contact
parameter to the Contact header stored in third party registration to indicate the UE’s contact. (VOLTE-8674)
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.1
3.1.0.0
-
First release in the 3.1.0.x series.
-
Update the ErrorCodeAnnouncement feature to add a new custom header to the final response after it has played an announcement. This header will prevent the feature from repeating the announcement if it runs again on an upstream node. (VOLTE-7945)
-
Remove ICSCFURI from announcement profiles. Announcements will now use ICSCFURI value from SipSentinelConfigurationTable profile. (VOLTE-8036)
-
Rename SBB feature artifacts from
-du.jar
to.du.jar
. (VOLTE-8239) -
Write new Extension AVP to CCR and ACR messages as well as CDRs stating whether a session failover has occured. (STLSIP-1293)
-
Updated leg manager to ensure Leg ACI mapping is removed when leg ends. (VOLTE-8601)
-
Add the ability to trace in detail a selected subscriber’s SIP sessions. This can be enabled for a random proportion of SIP sessions or via operator specified screened URIs participating in these sessions. (VOLTE-7549).
-
Fix bug in SentinelSipMultiLegFeatureEndpoint.featureWaiting where an internal error (incorrect SessionState) would occur when processing simultaneous events. (VOLTE-8496)
-
Add extensions column to cassandra ASSOCURIS table to store PATH values from 3rd Party Register. (VOLTE-8358)
Dependency Updates
-
Update the Sentinel Common dependency to 3.1.0.0
3.0.0.2
-
Modify the SDP Monitor to ignore repeated SDP answers on the same SIP INVITE transaction. (STLSIP-1290)
-
Fix a bug in SequentialForkedSDPMediation feature when handling an ACK during mediation. (VOLTE-7976)
Dependency Updates
-
Update the Rhino dependency to 2.6.2.7
-
Update the Rf Control RA dependency to 1.0.2.2
-
Update the SIP dependency to 2.6.0.9
-
Update the SIS dependency to the 2.6.2.9
3.0.0.1
-
Fix a bug where local numbers that contained characters that are not allowed in international format numbers would be normalized to international format anyway. (STLSIP-1288)
-
Fix to allow the PLMN ID analyser to handle 2 digit MNCs that are padded with a leading 0. (VOLTE-7879)
Dependency Updates
-
Update the Rhino dependency to 2.6.2.3
3.0.0.0
-
First release in the 3.0.0.x series.
New Capabilities
-
Added ContinueCallOnOCSFailure flag to DetermineChargingConfigProfileTable. (VOLTE-7389)
-
Add support for playing early media announcements on receipt of specified INVITE error responses during call setup. (VOLTE-7450)
Other Changes
-
Fixed an issue where RecordTimestamps would not update latest timestamps when a message was sent due to a leg ending instruction. (VOLTE-6348)
-
Fixed a problem where SDPMonitor did not clear Leg’s HasOutstandingSDPOffer state when sending a failure response. (VOLTE-7336)
-
Fixed a problem where SipMidCallPlayAnnouncementFeature would attempt to rewrite SDP (in ACK to passive party) twice causing an IndexOutOfBoundsException. (STLSIP-1285)
-
Renamed DetermineCharging feature’s package and removed unused erroneous stats. (VOLTE-7389)
-
Fix an issue in Early Media Play Announcement feature where
PRACK
requests from the calling party could be ignored. (STLSIP-1266) -
Ensure IMS-Information Timestamps AVP is populated when the final response is received on a forked leg. (VOLTE-7610)
-
Add session state variable to allow setting access network information as determined by application features. (VOLTE-7614)
-
Start directly invoked features with supplied ACI. (VOLTE-7561)
-
Pass ExtensionEvent ACI to features when trigerred on LocalEvents, if the feature was originally triggered by an out-of-the-blue extension event
-
Remove ESRVCC capabilities from DetermineRegistrationSessionType. (IPSMGW-981)
-
Update SequentialForkedSDPMediation to handle downstream forking. (VOLTE-7539)
Dependency Updates
-
Update the SIS dependency to the 2.6.2.4
-
Update the Sentinel Common dependency to 3.0.0.0
2.9.0.2
-
Fix state leak of ChargingManager and LegManager Predicates. (VOLTE-5297)
-
Fixed an issue where RecordTimestamps would not update latest timestamps when a message was sent due to a leg ending instruction. (VOLTE-6348)
-
Update LegManager isLegEnding and isInviteSessionEnding methods to handle releaseLeg instruction (VOLTE-7475)
-
Update sentinel-example-feature to remove HTTP response event handler and create a sentinel-sip-http-response-event-handler sbb-part module
-
Update sentinel-sip-example feature to replace HTTPResponse event handler with Diameter ReAuthAnswer event handler (VOLTE-7170)
-
Dependency Updates
-
Update the Rhino dependency to the 2.6.2.2
-
Update the Diameter RA dependency to 3.1.2.1
-
Update the Rf Control RA dependency to 1.0.2.1
-
Update the HTTP RA dependency to 2.5.0.1
-
Update the Sentinel Common dependency to 2.9.0.2
2.9.0.1
-
Remove History-Info header support from the SipShortCode feature. (VOLTE-7324)
-
Fix an issue with SAS tracing for the
ExtractNetworkInfo
feature. (VOLTE-7344)
Dependency Updates
-
Update the Rhino dependency to the 2.6.2.1
-
Update the SIS dependency to the 2.6.2.2
-
Update the Sentinel Common dependency to 2.9.0.1
2.9.0.0
-
First release in the 2.9.0.x series.
New Capabilities
-
Fix an issue in SipPlayAnnouncement and SipMidCallPlayAnnouncement features where announcements configured with an empty string locale were not handled gracefully (VOLTE-7187)
-
Add VerticalServiceCode feature. (VOLTE-6081)
-
Add support for Ro and Rf failover to Sentinel SIP (PRD-1070). See Changes in Major Release for details.
-
Add support for Vertical Service Codes. See Changes in Major Release for details.
-
Add SipProxyAndDoNotRecordRoute feature. (VOLTE-7158)
-
Add support for network initiated/timed out deregistration (VOLTE-6985)
-
Add support for History-Info header to the SipShortCode feature (VOLTE-7089)
-
Add SAS logging to
DetermineChargeableLeg
feature. (VOLTE-6030)
Other Changes
-
Update SipAddressUtil to remove
phone-context
when updating a URI with an internationally formatted number. (VOLTE-7110) -
If a Rf Control Activity is incorrectly cleared by liveness check (when
ACR:Acct-Interim-Interval > (2 * ACA:Acct-Interim-Interval)
) a NPE is no longer thrown. Instead the new interim CDR statRfControlActivityLost
is incremented and the interim CDR feature fails withInvalidSessionState
. The previously unused statCdrNotSent
has been removed. (VOLTE-6516) -
Update SipAnnouncement feature and SipMidCallAnnouncement feature to ensure
OC-Play-Announcement-Id
AVPs are added in CDRs for each announcement the features are invoked to play. (VOLTE-6278) -
Change SipPlayAnnouncement and MidCallPlayAnnouncement to use new session state queues of announcement objects. (VOLTE-6058)
-
EarlyMediaAnnouncementQueue, MidCallAnnouncementId, an MidCallAnnouncementQueue session state fields are deprecated.
-
EarlyMediaAnnouncementInfoQueue and MidCallAnnouncementInfoQueue should be used instead.
-
EarlyMediaAnnouncementInProgress and MidCallAnnouncementInProgress can be used to inspect if an announcement is underway.
-
-
Update MidCallPlayAnnouncement to allow charging to be resumed and suspended between announcements. (VOLTE-6344)
-
Remove IMS-Information Carrier-Select-Routing-Information AVP from ACRs, CCRs, and CDRs, and from SessionState (VOLTE-4483)
-
Update B2BUA feature to respond with 491 if a re-INVITE or UPDATE request cannot be forwarded due to a transaction in progress on the linked leg. (VOLTE-6529)
-
Updates to use of repeating timers for the
SessionRefresh
andMaxCallDuration
features. (VOLTE-6056)-
Add support for using periodic timers with the Service Timer Provider.
-
Update the
SessionRefresh
feature to use a periodic timer instead of setting a new timer each time the previous one expires. -
Folded the functionality of the
MaxCallDuration
feature into theSessionRefresh
feature, theSessionRefresh
feature will set its timer to repeat until the max call duration is reached, at which point it will end the call. -
Deprecated the
MaxCallDuration
feature and removed it from the standard feature execution scripts.
-
-
Update ExtractNetworkInfo feature to determine the ISO country code for the served user’s access network. (VOLTE-6548)
-
Update SipShortCode feature to remove the home country’s network prefix before attempting short code translation.
-
If a number is international and not prefixed by the home country’s network code no translation will occur.
-
The SipShortCode package is moved to com.opencloud.sentinel.sip.feature.initialtrigger.shortcode. (VOLTE-6842)
-
-
Add utility classes for manipulating History-Info headers (VOLTE-7052)
Dependency Updates
-
Update the Rhino dependency to the 2.6.2.x series
-
Update the Rhino Element Manager dependency to the 2.6.2.x series
-
Update the SIS dependency to the 2.6.2.x series
-
Update the Sentinel Common dependency to 2.9.0.0
2.8.0.3
-
Ensure SAS markers for internationally formatted numbers are reported with leading
+
(VOLTE-6132) -
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) -
Check new isInviteTerminated() method when attempting to send a BYE. (VOLTE-4786)
-
Add method to Leg to pass a MessageBody to endSubscription(). (VOLTE-4786)
-
Move SipNormalizationFeature normalization behaviour to a dedicated util class. (VOLTE-6216)
-
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)
-
SAS log phone numbers in SIP headers even if the user=phone parameter is not provided. (VOLTE-6406)
-
Add User-Equipment-Info AVP to Rf Accounting-Requests. (VOLTE-6427)
-
Use E164 numbers for the SubscriptionId AVP when possible. (VOLTE-2692)
-
Update BaseSipInterimCdr feature to add the OC-Charging-Result AVP to ACRs. (VOLTE-6577)
Dependency updates
-
Update cassandra-cql dependency to 1.2.0.1
-
Update sdp-parser dependency to 1.0.0.5 (VOLTE-6399)
-
Update the Rhino dependency to 2.6.1.3
-
Update the SIS dependency to 2.6.1.6
-
Update the Diameter dependency to 3.1.1.2
-
Update the Rf Control dependency to 1.0.1.2
-
Update the Sentinel Common dependency to 2.8.0.3
2.8.0.2
-
Add simple SAS event example to the
sentinel-sip-example
feature module. (BLDSUPP-48)
Dependency updates
-
Update the SIS dependency to 2.6.1.5
-
Update the Sentinel Common dependency to 2.8.0.2
2.8.0.1
-
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 DiameterPerLegInfo feature to use the outgoing Request-URI to set the Called-Party-Address AVP for a given leg. (VOLTE-5701)
-
Update SipNormalization feature SAS log levels. (VOLTE-5956)
-
Add extra verification of Play Announcement configuration. (VOLTE-4094)
-
Add SAS logging to the SentinelSip service. (VOLTE-5229)
Dependency updates
2.8.0.0
-
First release in the 2.8.0.x series.
New Capabilities
-
Added support for tracking information about SIP legs in the new Rhino Session Ownership Facility.
-
Extended the
Leg
API to allow features to manipulate what legs and information should be tracked. See Sentinel SPI Javadoc for details. -
Added a new SIP system feature named External Session Tracking which is responsible for storing/updating/deleting leg information in the Session Ownership Facility.
-
-
Add support for triggering session replication at certain points during SIP session setup.
-
Triggers are configured in the
SipSessionReplicationConfigProfileTable
. -
A new feature called Determine Session Replication is responsible for reading the configuration and arming triggers.
-
Leg state information has been moved from storage on
SipSession
attributes to CMP so it will be replicated. -
A KV Store and Session Ownership Facility must be configured for session replication to function.
-
Other Changes
-
Added SentinelSipAVPs enum to the name and code for custom AVP definitions. Updated all uses of createAVP or similar to use new enum contant values. (VOLTE-5056)
-
Add new
LegManager
API to allow the importing of new legs using a handover INVITE request. The new API will automatically populate SDP data on the new leg from the request. (VOLTE-4947) -
Remove deprecated methods, classes, and legacy modules. (VOLTE-5332) See Changes in Major Release for details.
Dependency Updates
-
Update the Rhino dependency to 2.6.1.1
-
Update the Rhino Element Manager dependency to 2.6.1.1
-
Update the SIS dependency to 2.6.1.2
-
Update the Sentinel Common dependency to 2.8.0.0
2.7.1.3
-
Add SAS logging to SipShortCode feature. (VOLTE-5810)
-
Improve handling of removal of parameters from URIs. (STLSIP-1257)
-
Update tracking of session established time to better handle upstream forks. (STLSIP-1259)
2.7.1.2
-
First release in the 2.7.1.x series.
-
Fix an issue around call waiting with preconditions. (VOLTE-5236)
-
SipAddress and SipAddressUtil moved to the
sentinel-sip-spi
module and thesentinel-sip-address-util
module has been removed. (VOLTE-5326) -
Update the MaxCallDuration feature to allow the max call duration to be overridden with a session state value (VOLTE-5401)
-
Add event handlers to the SentinelSip service for incoming HTTP request methods DELETE, HEAD, and PUT. (RM-84)
-
Update diameter service context Id value from
8.32260@3gpp.org
to12.32260@3gpp.org
. (VOLTE-5686)
New Capabilities
-
Added Metaswitch Service Assurance Server (SAS) support to features:
-
B2BUA
-
B2BUAIECPreFeature, B2BUAIECPostFeature
-
B2BUAScurPreFeature, B2BUAScurPostFeature
-
B2BUAEcurPreFeature, B2BUAEcurPostFeature
-
SDPRewriter
-
SequentialForkedSDPMediation
-
SipNormalization
-
SipMidCallPlayAnnouncement
-
SipPlayAnnouncement
-
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)
-
Added announcement configuration to allow session termination on announcement failure. (VOLTE-4939)
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.