SLC Replying With Error Code 31 Instead Of 4012 For Data Sessions (Doc ID 2718634.1)

Last updated on AUGUST 12, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.

Goal

From the data Control Plan, whenever a DISC (Disconnect Call) node with an error code 31 is triggered, noticed that the SLC (Service Logic Controller) responds with an error code 31 in diameter instead of RESULT_CODE=4012. It seems that when using a conversion in one of the AVP's (Attribute Value Pair), the default error codes are not working anymore.

Why is this happening?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

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

SLC Replying With Error Code 31 Instead Of 4012 For Data Sessions (Doc ID 2718634.1)

Applies to:

Goal

Solution

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

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