TTC Not Expected When Only Bytes RUM Is Used For Rating
(Doc ID 2880008.1)
Last updated on JULY 04, 2022
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On Elastic Charging Engine (ECE) 126.96.36.199.4 version it was observed that Time-Tariff-Change flag (TTC) is set on a data session when only Bytes RUM is used for rating.
TTC should be set only in conjunction with Conditional RUM: Simple Conditional RUM or Multi RUM(Bytes and Conditional).
Credit Control Answer message sent by Diameter Gateway looks like this:
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