Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
After triggering the initial/update request, if there is a delay in receiving
the response by Oracle Communication Network Charging Control (OCNCC), then the same update request is again triggered(after
some time interval) with the same AUTH ID and SESSION ID.
Steps to re-produce
1. Create a Prepaid account
2. Send auth request, through PCM_OP_TCF_AAA_AUTHORIZE
3. Send update and auth req through PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE with session id and rating mode = 1
4. Send duplicate update and auth req through PCM_OP_TCF_AAA_UPDATE_AND_REAUTHORIZE with same session id and rating mode =1
Expected result:Update success response with the same reservation
object as in auth request(without creating any new reservation).
Actual result : When duplication session id is sent during Auth/Re-auth , its erroring out with PIN_ERR_DUPLICATE .
Same issue is applicable for telephony and sms services
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms