Version 3.1.2.1

Improvements

  • Support replicated client charging session failover regardless of CC-Session-Failover support reported by server. (DIA-603)

    • Selected Diameter peer for client charging sessions is now replicated and maintained across failover.

Version 3.1.2.0

  • Add support for session replication via the Rhino 2.6.2 Key-Value Store storage model.

    • Includes support for session ownership tracking and adoption when using application-initiated persistence using the new Rhino based session ownership API. Diameter Credit-Control Fault Tolerance.

    • Supports application initiated persistence of Credit-Control sessions such as Ro. Each session is assigned a tracking key for linking to the application session in a session ownership record.

  • Add SAS logging for request retransmission. (VOLTE-5940)

  • Add endActivity() method to Diameter Sh activities. (VOLTE-7155)

Version 3.1.1.0

New features

  • Metaswitch Service Assurance Server (SAS) support. (DIA-563)
    See the documentation for more information.

Fixes

  • Fixed a bug that resulted in extra null elements being included when getting AVPs from a message or grouped AVP. (DIA-558)

Version 3.1.0.3

Fixes

  • Fixed issue in Diameter Gx that meant AVPs were not converted to specific types (DIA-561).

Version 3.1.0.2

Fixes

  • Fix all base Diameter AVPs so they are not sent with the 'P' header bit set. RFC 6733 states that this bit should always be unset. (DIA-559)

Version 3.1.0.1

Fixes

  • Fixed a bug that allowed RA entity properties to be set to invalid values in some cases. (DIA-551)

Version 3.1.0.0

New Features

  • Added optional Slee3GPPVersion RA entity property to Diameter Ro and Rf. This can be used to configure a different Ro/Rf version to use in the SLEE for events, messages, and types than the Ro/Rf version used on the wire. If specified, and if set to a different Ro/Rf version, the messages and AVPs will be converted on the fly as messages come on and off the wire. (DIA-541 [Ro] and DIA-543 [Rf])

API and deployment changes

  • Added isRecognizedAvp method to message factories to check if a DiameterAvp is recognized by that message factory. (DIA-532)

  • Added getConfiguredTGPPVersion method to all Diameter provider factories. (DIA-531)

  • Removed the CCA and Base types from the Diameter Rf RA Type jar. The CCA Types are still included in the final Diameter Rf RA deployable unit, but they are now referenced as libraries instead of having them included directly in the Rf RA Type jar. There is also a new no-cca variant of the Diameter Rf RA deployable unit that can be co-deployed with the Diameter CCA RA. (DIA-547)

Fixes

  • Fixed Diameter Rf AVP type conversion so it ignores extension AVPs. Previously, extension AVPs that used the same code as an actual Rf AVP (but with a different vendor ID) would be changed into the actual Rf AVP. (DIA-548)

Version 3.0.0

Note As of release 3.0.0, the Diameter resource adaptors require Rhino 2.4.0 or later.

RFC 6733 Compliance

  • Add support for Capabilities-Update-Request and Capabilities-Update-Answer, defined in RFC 6733 and RFC 6737.

  • Add extension AVPs to all Base Diameter messages.

  • Remove Capabilities-Exchange-Request / Capabilities-Exchange-Answer support from "Open" peer state.

  • Add handling of Vendor-Specific-Application-Id in Capabilities-Exchange-Request.

  • Add new AVPs to Error-Answer message.

  • Add new AVPs to Accounting-Request and Accounting-Answer.

  • Minor change to election process.

  • New SSL/TLS support. Backwards compatibility for TLS support in accordance with RFC 3588 is controlled using AllowTLSDowngradeToRFC3588 configuration parameter.

Other Compliance

  • Add support for 3GPP Rel12. (DIA-491)

  • Add support for multiple Sh UserData schema versions. (DIA-289)

API and deployment changes * New Java types have been added for Re-Auth and Abort-Session requests and answers used by credit control applications (Diameter CCA and Ro). SBBs that declare event handlers for these messages will need to use the classes in the org.jainslee.resources.diameter.cca.types package instead of org.jainslee.resources.diameter.base.types. This was done so that the messages contain the correct Application ID for a credit control application. (DIA-339) * Diameter message factories now expose methods to encode and decode AVPs to and from byte arrays. (DIA-483) * Add support for extension AVPs to all Grouped AVPs. Be aware that adding extension AVPs to a Grouped AVP that does not explicitly specify ABNF line * [AVP] may result in interoperability problems with products that strongly validate the incoming message against the specification. (DIA-479) * Diameter MBean name changed to more standard com.opencloud.diameter:type=Entity,name=<entityname>. (DIA-218) * Assign static OIDs to Diameter statistics parameters. (DIA-482)

Improvements

  • Diameter alarms are now registered in the alarm catalog. (DIA-465)

  • Added support for new method getConfiguredTGPPVersion() available on provider factories for Sh, Ro, Rf and Gx. The return value is a hex string representing the version configured for the resource adaptor entity, irrespective of the version of the provider implementation. (DIA-531)

Fixes

  • Fix permission failures allocating Netty buffers under certain conditions. (DIA-435)

  • Fix handling of retransmissions for Credit Control sessions where CreditControlFailureHandling is set to TERMINATE. (DIA-527)