2.8.0.4

Dependency updates

  • Update the Rhino dependency to 2.6.1.4

  • Update the SIS dependency to 2.6.1.13

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.2

Dependency updates

  • Update the SIS dependency to 2.6.1.5

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

  • Update the Diameter dependency to 3.1.1.0

  • Update the FSM Tool dependency to 1.2.0.0

  • Update the HTTP dependency to 2.4.0.1

  • Update the Rhino dependency to 2.6.0.0

  • Update the REM dependency to 2.6.0.0

  • Update the SIS dependency to 2.5.5.2

2.7.0.8

  • Fix bug in DigitTree that caused it to not accept '*' characters. (VOLTE-5613)

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.4

  • Improve handling of the CC-Money AVP in the DiameterSessionCounterHelper. (STLCORE-95)

2.7.0.3

  • Update Normalization component to skip short codes. (VOLTE-4630)

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.9

  • Fixed protobuf Ivy dependency for sentinel-avp-cdr-format module pack. (VOLTE-3780)

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.6

  • Update the SIS dependency to 2.5.4.3

  • Update the Rhino dependency to 2.5.0.2

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 the repositories directory. Module build output remains in MODULE/target/. (BLDSUPP-34, STLPACK-35)

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

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 and postgres.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 and redeploy-all tasks (SDKTOOLS-71 and SDKTOOLS-72)

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

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

  • Make go-offline work on a Mac

  • Prompt for confirmation by default for all undeploy tasks

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

  • Enable terminal echo in the installer (VOLTE-1962)

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

  • Minor performance improvements when using Sentinel Selection Key’s Iterator

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

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

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 existing e:deployorder, it defines the modules as a comma separated list of module names. For both e:configureorder and e:deployorder, the module itself can now be included at any point in the given order. I.e. the module itself can be configured/deployed either before or after its dependencies.

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

  • Add support for module property propagation between modules that publish properties

  • Fix go-offline local repo name rewriting

  • Run init-sdk if necessary

  • Use an SDK specific Ivy cache rather than the default

  • First 2.3.1 release for Sentinel Express

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

  • Fix bugs in several sentinel-core module packs

  • Rewrite the installer in Java (VOLTE-1692)

  • Initial Sentinel 2.3.1 series release, included in Sentinel VoLTE

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

2.3.1.0

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

Previous page Next page