Different "Origin-Host" AVP Values Between Diameter Message Types

(Doc ID 2420935.1)

Last updated on JULY 10, 2018

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
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), it is possible for diameter messages through the Diameter Charging Driver (DCD) to contain different Origin-Host values between the Credit Control Requests (CCR) and the Capabilities Exchange Requests (CER)/Diameter Watchdog Requests (DWR) messages.

This may cause issues with the diameter server if it is validating the Origin-Host in the CCR message with the Origin-Host in the original CER message.

Changes

 

Cause

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 hundreds of Community platforms