Missing Sig_digits_next_field In Ascii Output For Art Billing

(Doc ID 879172.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Network Mediation - Version: 5.1.1 to 5.1.1
Information in this document applies to any platform.

Symptoms

Problem Statement

The rulefiles for decoding ART AMA billing files do not output the sig_digit_next field for the
term_open_digits_1and the term_open_digits_2 field, also not for the orig_open_digits_1&2 fields.
The complete subscriber number is given out by the DMS using ISN09 software, in 2 parts. The
values in the sig_digit_next field indicates how much digits must be taken from the
term_open_digits_2 field, counting from the right to the left to complete the terminating
subscriber number which begins in the term_open_digits_1 field.
Only one time a significant _digits_in_next_field is given out but to which part does it belong?

When you decode the binary Data with the amadump tool, the sign_digit_next_field is always given
out together with the corresponding orig_open_digits_1 and orig_open_digits_2 field and vice versa
with term_open_digits field 1&2. When we take an ASCII output from NMD which is coming from the
ART switch and read it in e.g. Excel or Scalc and define commas and tabs as separators we can see
the results.

Here in the ASCII output we only find one sign _digits_in next field. So we have to clarify how
the originating and terminating number hast to be given out. The easiest and best way would be the
following: combine the 2 number parts with the help of the sign_digits_next field whenever they occur. This
can also be in the modules which can be given out depending on the type of call. Otherwise we need
to have the parts of every numbering parts completely given out inclusive the coresponding
sig_digits_next_fields.

Steps To Reproduce


In the ASCII DC node using Rule File "DMS-100 MMP AMA ISN09" check that some of the fields are not getting populated in the output of DC node.
The fields are like : Significant_digits_in_next_field, Significant_digits_in_next_field_for_orig, Significant_digits_in_next_field_for_term.


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