My Oracle Support Banner

UATB Node Does Not See Remaining Units If VWS Returns Last Chunk (Doc ID 2830451.1)

Last updated on JANUARY 04, 2022

Applies to:

Oracle Communications Network Charging and Control - Version and later
Information in this document applies to any platform.


On Oracle Communications Network Charging and Control (NCC), version,

Universal Attempt Termination with Billing (UATB) Feature Node does not see remaining units if Voucher and Wallet Server (VWS) returns last chunk.

Consider a Subscriber has a credit for 120 seconds of call (11,20Kč = 112000 value in General Cash).

Here the Call rate for destination is 5,60Kč/minute, Minimum length for the call is 60seconds, Billing Resolution is configured as 60seconds and "ReleaseIfDurationExceeded" flag is set.

The call scenario assigns tariff and goes to UATB node . But VWS allocates 900ds for the Initial Reservation Request (IR), but rejects the Subsequent Reservation Request (SR) with Release Call. It does not allocate the remaining 300ds.


NCC should allocate the available/remaining balance for the call if "ReleaseIfDurationExceeded" flag is set.

1. On NCC 12.0.3 Version, Create a subscriber with General Cash Balance only for a call of 120 seconds .
2. Use a Control Plan with Start-->UATB-->End Node
3. Using Slpit, trigger the above control plan .
4. Check if this scenario aborts and NCC allocates the IR successfully, but rejects the SR (with Release Call).
5. Verify if it does not allocate the remaining balance for the call.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.