Bad Number Of Seconds Priced In Prepaid Event
(Doc ID 2994417.1)
Last updated on DECEMBER 28, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
A prepaid product configured with 3 Quantity ranges like this:
1. Quantity range 0-5 secs
- Fixed charge 0 per minute
- Charge 131.9625 CRC per minute
2. Quantity range 5-60 secs
- Fixed charge 0 per minute
- Charge 131.9625 CRC per minute
3. Quantity range +60 secs
- Fixed charge 0 per minute
- Charge 131.9625 CRC per minute
NOTE: Product settings always round to 60 sec in all ranges. The parameter supportOriginalBeat="true"
A roaming voice session is started using the Impact Category = PRE_IC_VOZ_ROAM_MT_CENTROAMERICA_PAN where a total of 35 seconds are used.
TEST STEPS:
1. A prepaid voice session is started starting at 2026-03-20 14:16:01.
2. The voice session ends at 2026-03-20 14:16:36.
RESULTS:
Two impacts are generated as follows.
Impact 1 Duration: With a quantity of 65 seconds and charge 0.
Impact 2 Duration: With a quantity of 65 seconds and a charge of 142.95938 CRC.
EXPECTED RESULT:
Impact 1 Duration: With a quantity of 60 seconds and charge 0.
Impact 2 Duration: With a quantity of 60 seconds and charge 131.9625 CRC.
It is expected to rate the equivalent of 60 secs since, according to the ranges configured in the offer, an event of 0 – 60 secs charges 131.9625.
But charging 5 seconds more.
Cause
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
Symptoms |
Cause |
Solution |
References |