1. Release Notes
  2. New Features in Offline Mediation Controller

2 New Features in Offline Mediation Controller

Learn about the new features in Oracle Communications Offline Mediation Controller 15.0.

Topics in this chapter include:

New Features in Offline Mediation Controller 15.0.1

Offline Mediation Controller 15.0.1 includes the following enhancements:

Support Added for TLS 1.3

Offline Mediation Controller now supports TLS 1.3, which is faster and more secure than TLS 1.2. TLS handshakes in TLS 1.3 require only one round trip instead of the usual two, shortening the process by a few milliseconds. In cases where you have already connected to a website, the handshake will have zero round trips, making HTTPS connections faster. It also cuts down latency and improves your overall experience.

Your existing KeyStore certificates may have used the default DSA algorithm, which is no longer supported by TLS 1.3. Therefore, you must regenerate any KeyStore certificates from previous versions of Offline Mediation Controller.

See the following links for information on how to enable TLS 1.3 support for Offline Mediation Controller:

Support and Certification 15.0.1

Offline Mediation Controller now supports the following software:
  • Oracle Linux, x86-64 (64-bit) 8.9
  • Red Hat Enterprise Linux, x86-64 (64-bit) 8.9
  • Oracle Database Server Enterprise Edition 19.21
  • Oracle Java Platform Standard Edition (Java SE) 8 (1.8.0_401)

Secure RADIUS Client Configuration

For RADIUS EI Nodes, client configuration (hostnames and secrets) was previously stored together in a configuration file named ipsecrets.cfg. The new model enhances security by separating this information:

  • Hostnames remain in a file now named iphosts.cfg.
  • Secrets are moved automatically to a secure wallet solution.

Note:

If you created RADIUS CC nodes before upgrading to release 15.0.1, you need to re-save the node configuration to ensure secrets are migrated to the wallet and removed from the iphosts.cfg file.

Changes to Offline Mediation Controller REST Services Manager

The following endpoints have been removed from the Offline Mediation Controller REST API:

  • GET /nodes/{id}/startNode (Start a Node)
  • GET /nodes/{id}/stopNode (Stop a Node)

New Features in Offline Mediation Controller 15.0.0

Offline Mediation Controller 15.0.0 includes the following enhancements:

Support and Certification

Offline Mediation Controller now supports the following software:

  • Oracle Linux, x86-64 (64-bit) 8.7

  • Red Hat Enterprise Linux, x86-64 (64-bit) 8.7

  • Windows (64 bit) 8.1, 10, and 11

  • Oracle Database Server Enterprise Edition 19.20

  • Helidon 1.4.13

  • Oracle Unified Directory 12.2.1.4.0

  • Oracle Java Platform Standard Edition (Java SE) 8 (1.8.0_381)

See Offline Mediation Controller Installation Guide for information on other software support.

Offline Mediation Controller REST Services Manager

You can now integrate Offline Mediation Controller with external client applications using the new Offline Mediation Controller REST Services Manager. The REST Services Manager allows you to perform the same operations as the NMShell application. For example, you can use it to do the following:

  • Manage Nodes

  • Manage Node Managers

  • Retrieve a list of node chains

  • Compile and save the NPL rules file

  • Export node configurations and customizations

See REST API Reference for Offline Mediation Controller for more information on REST Services Manager.

Cloud Native Enablement for Offline Mediation Controller REST Services Manager

Offline Mediation Controller cloud native now supports Offline Mediation Controller REST Services Manager. You can deploy both CORE Offline Mediation Controller and the new REST Services Manager using a consolidated values.yaml file and unified Helm chart.

See "About Offline Mediation Controller REST Services Manager" in Offline Mediation Controller Cloud Native Installation and Administration Guide for more information.