Partial Type Indicator Is Not Populated Properly In Case Of Assembled Calls
(Doc ID 797132.1)
Last updated on MARCH 23, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and laterInformation in this document applies to any platform.
This problem can occur on any platform.
Symptoms
-- Problem Statement:
For inbound roaming, usage generated for roaming partner's subscriber is sent to roaming partner in TAP file format. According to TAP standard (TD 57), "Partial Type Indicator" field should contain either of these values: F, I or L
BRM's TAPOUT grammar (TAP3_v11_OutGrammar.dsc) populates this field according to what is
received in LONG_DURATION_INDICATOR field.
When using BRM call assembly process, this process updates LONG_DURATION_INDICATOR field with either of the following values in case of partial call: C,SL,P,XC,XO,XP.
These values are not according to TAP standards and so violates the standard. According to standard it should be populated with values F,I or L.
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 |