Last updated on JULY 24, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Roaming
The user was using OOB "ISC_TAP_0311_Validations.isc" and "ISC_TAP_0312_Validations.isc" iScripts to process TAP 3.11 and TAP 3.12 files.
It looked like the TAP Roaming Manager was expecting an uppercase name for the Recording Entity Identification for MSC. However, the TAP 3.11 and TAP 3.12 specifications did not specify that it should be an uppercase name and even provided an example with lowercase and space characters.
For MSC encoded as one of the following according to the requirements of the Sender PMN:
• The MSISDN of the entity (See Annex C – CS Domain Charging and PS Domain Charging) for example 44836100456
• The signalling point code (See Annex C – CS Domain Charging and PS Domain Charging) for example 253464
• A name for example “HELSINKI” or “Switch 1”.
When processing TAP 3.11 or TAP 3.12 files, below warning message was in the stream logs:
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