Workaround Needed to Issues with the Authorize AAA Phase

(Doc ID 727258.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 17-Mar-2010
Checked for relevance on 23-Apr-2012
Checked for relevance on 30-Oct-2013

Symptoms

This issue arised as a follow up to a know problem on the present product version (7.3), already reported with Metalink <Note 562743.1>

A products has a voice event with minimum event quantity and rounding increment of 30 seconds, and the PIN_FLD_INCR_QUANTITY defined in pin_config_reservation_aaa_prefs is 30 seconds, and
one want to authorize quantities of 30 or zero seconds.

Looking for a workaround, as per documentation regarding PCM_OP_ACT_POL_PRE_AUTHORIZE:

"By default, receives an input flist from PCM_OP_ACT_AUTHORIZE and returns it with a retry flag (PIN_FLD_FLAG_RETRY_CALC_MAX). The flag specifies whether authorization requests for prepaid
services should be retried in CALC_MAX mode if they fail when initially rated in CALC_ONLY mode.

PIN_FLD_FLAG_RETRY_CALC_MAX can be set to the following values:
* 0 = Do not retry the request.
* 1 (default) = Retry the request."


By changing the policy opcode, adding the following lines, in order to avoid the CALC_MAX mode and authorize only if the CALC_ONLY is more than the current balance:

int64 x = 0;
PIN_FLIST_FLD_SET(*r_flistpp, PIN_FLD_FLAG_TRY_CALC_MAX, &(x), ebufp);

the result is the same as with the standard policy, and the reverse rating (hence the authorize) is performed, even if there is not enough credit on the account balance.

Cause

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