Diameter T-flag for CCR-U and CCR-T Messages Set Unexpectedly
Last updated on FEBRUARY 06, 2018
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (OCNCC) Version 5.0.2, it is observed that the Diameter Charging Driver(DCD) always handle the first Credit Control Update Request(CCR-U) and Credit Control Terminate Request(CCR-T) messages as failed and the T-flag(retransmit flag) for these CCR-U and CCR-T messages are being unexpectedly set even when there are no re-transmissions on the network.
This is observed while using the DCD to allow communication of billing requests from a Service Logic Controller(SLC) to a billing platform, using the DIAMETER protocol.
This is affecting the call setup time due to more operations required in the billing engine side to handle the enabled T-flag.
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