Rating Through Radius When Processing An Usage Record With More Than 2 GB
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 22.214.171.124.0 to 126.96.36.199.1 - Release: 7.3.1 to 7.3.1
Information in this document applies to any platform.
In real time rating when the radius packets are received with data volume more than 2 MB, then the packets are processed but the data volume is stored as negative value in the database and the negative value is displayed in the customer center.
In reference to ANS:1, if all the tariff plans are defined in MB hence the mod_unit should be set to 3 as a solution for this problem, then why the packets with more than 2 GB fails to process correctly why doesn't that fail with packets with more than 1 GB itself.
Here the expectation is to get a solution where rating should be successful even if the tariff plans are defined in megabytes/ gigabytes. I.e. "The unit defined in tariff should not depend on mod_unit. Even though mod_unit is in bytes and tariff unit is in MB it should rate correctly." In other words the expectation is that the product should support successful rating when processing the usage records with more than 2 GB without code customization of config file each time a different unit of measurement is used in the tariff plan.
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