My Oracle Support Banner

Tap 3.2 Call Reference Field (Doc ID 2899141.1)

Last updated on SEPTEMBER 29, 2022

Applies to:

Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Symptoms

Following is the test scenario, customer are getting CallReference longer than 8 bytes error.

1. Customer are having OCOMC and Pipeline setup for Roaming to generate Tap-Out.
2. Receiving raw Call Details Records (CDRs) from network and processing through Oracle Communication Offline Mediation Controller (OCOMC) to Elastic Charging Engine (ECE) for rating. After that OCOMC is generating ASCII CDR after rating.
3.The OCOMC generated ASCII CDR sending to Pipeline to generate tap-out.
4. Customer are generating tap 3.2 successfully but facing issue with call reference field from the input cdr.
5. Customer are giving field value as "127D" and it has generated the  tap file "".






Changes

 

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
Changes
Cause
Solution
References


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