Instruction manual
Page 1040 of 3156 CIS ANI Digits Manipulation and Gateways Enhancements
553-3001-306 Standard 10.00 January 2002
Gateways Enhancement feature functionality (Release 24)
The gateway enhancements are composed of the following new
functionalities, which are described in this section:
• Mapping of the received calling number to ANI:
— Mapping CNI to ANI, ANI to CNI
— Mapping CLID to ANI and OLI to ANI
— Mapping ANI to ANI in gateway CIS to CIS
• Building ANI for interfaces without calling number
Mapping of the received calling number to ANI
To map any Calling number to ANI the idea is to be able to manipulate the
received Calling Number when tandeming it into ANI. In a gateway situation
the incoming trunk is the originator of the outgoing call. So the Calling
Number is manipulated by assigning an ANI table entry to the incoming
route. An ANI table entry is also assigned to route types whose connectivity
does not give the possibility to receive a Calling Number. For these routes,
the ANI table entry allows to build the outgoing ANI using only information
pertaining to the incoming route.
CIS Gateway Enhancement introduces a list of ANI entries applicable to
incoming route considered for the gateway with CIS, or incoming and
outgoing route. When package CIST is equipped, an ANI entry is attached to
each applicable route. An entry for routes is configured with prompt:
R_ENTRY.
Some of the fields defined in ANI table entry were already existing in route
configuration. ANI table entry fields that were already existing on route
(RDNL, ANDN) are suppressed from the route. It must be noticed that
prompt RDNL of Route Data Block is replaced by prompt DNLG in ANI
table entry. A new prompt is added on Route data configuration to defined
ANI table entry: ANIE. During upgrade to Release 24, former Route Data
Block prompt values are moved into a ANI table entry and this table entry is
assigned to the route.
Several routes can have the same tandeming information configured. The
data has been moved from Route Data Block to Customer Data Block. In case
no ANI table entry is configured, the default table entry (0) is used.