My Oracle Support Banner

mipt Doesn't Set SCTP PPI When Testing M3UA (Doc ID 2939363.1)

Last updated on OCTOBER 25, 2024

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 to 15.0.0.0.0 [Release 6.0 to 15.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 15.0.0.0.0 [Release 4.3 to 15.0.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 15.0.0.0, the Messaging over Internet Protocol Tester (mipt) has the ability to send Message Transfer Part Level 3 (MTP3) User Adaptation (M3UA) over Stream Control Transmission Protocol (SCTP) directly to the m3ua_if processes on the Service Logic Controllers (SLCs).

This provides users with the ability to run tests against all the areas of the SLC without the need for third party test tools and/or dedicating expensive network equipment for running tests against a test environment.

There is a limitation in mipt however where it does not set the SCTP Payload Protocol Identifier (PPID) value so it ends up defaulting to 0 or "Reserved by SCTP".  The correct PPID value for M3UA is 3 as defined in the Stream Control Transmission Protocol (SCTP) Parameters.

The only impact this has is packet sniffers such as Wireshark are not able to determine what the SCTP payload is and will just display the data as a raw hex stream.

The NCC applications will correctly handle and process the incoming data.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.