Request Details In QoS API From Client Is Not Logged For Trace (Doc ID 2005842.1)

Last updated on AUGUST 31, 2016

Applies to:

Oracle Communications Services Gatekeeper - Version 5.1.0 to 5.1.0 [Release 5.1]
Information in this document applies to any platform.

Symptoms

Cannot trace API request parameters in QoS.log. Only see Rx-RR-Request and Rx-RR-Answer for Diameter.
IT should contains request parameters and assigned keys to relate all requests and responses within a QoS action
both internally and external to RESTful client and PCRF.

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