Instruction manual

CIS ANI Digits Manipulation and Gateways Enhancements Page 1041 of 3156
Features and Services
With Release 24 implementation, ANI is built as follows:
If outgoing route does not allow use of ANI table entry assigned on incoming
route (ANIC prompt of outgoing CIS route is set to NO), Calling number is
built as before. Notice that part of the received Calling Number (DNLG) and
ANDN INC route are configured in ANI table entry of the incoming route.
1 If outgoing route allows to use ANI table entry assigned on incoming
route (ANIC is set to yes on CIS outgoing route), ANI is built as LEC inc
route + ADDG inc route + (part of) received Calling Number or, when
calling Number not available.
Note: With new implementation “part of received calling Number”
indicates N least significant digits of received Calling Number, where N
is the value configured against prompt DNLG in the ANI table entry
associated to the incoming Route Data Block.
2 LEC inc route + ADDG inc route +ANDN inc. route
ANI has a predetermined size, configured on outgoing CIS route. It can
happen that ANI built is smaller or longer than the ANI configured size. This
is handled the same way as for ANI built when call originator is a set.
When the ANIC of the outgoing route is set to yes, data from the ANI table
entry configured for the incoming route is used, even if empty. Thus it is up
to the craftsman to ensure that the ANI built using the ANI table entry is
correct.
Mapping CNI to ANI, ANI to CNI
On MFC routes, prompt ANDN is currently defined. This prompt is removed
and replaced by prompt ANIE which allows configuring the ANI table entry
number.
Both CNI and ANI contain a CAC field. The value and meaning of the field
in both cases are not the same.