Instruction manual

CIS ANI Reception Page 1075 of 3156
Features and Services
ANI Gateways
The ANI digits which are received from the CIS CO party as a response to the
automatic ANI request are propagated to the Meridian 1 terminating party if
it is capable of receiving the CNI digits.
The ANI digits are propagated to the following terminating types:
• R2MFC trunks - the ANI to R2MFC CNI mapping is performed in the
following way: all the ANI digits except for the ANI Calling Party
Category Code (CAC) are used for the CNI composition, the ANI CAC
is converted to the Multi-frequency Compelled (MFC) CNI CAC
according to the CAC conversion tables.
• ISDN trunks - Meridian Customer Defined Integrated Services Digital
Network (MCDN), EuroISDN: European Integrated Services Digital
Network (EURO), Q Signaling (QSIG), DPNSS - the ANI to CLID/OLI
mapping is based on the R2MFC CNI to CLID mapping.
• CIS trunks - the ANI to ANI mapping is implemented in the framework
of the CIS ANI Digits Manipulation and Gateways Enhancements
feature described in this document. The ANI information that is received
from the incoming CIS DTI2 trunks is used by the CIS Gateways
Enhancements feature to compose the ANI information to be
downloaded to the outgoing CIS trunks.
ANI Digits Display
The ANI digits are displayed on the display of the Meridian 1 proprietary set
or of the attendant console. The ANI digits are displayed starting from the left
side of the display. The CAC display option is configured on the route data
block level and it may be set to one of the following options (see Figure 22):
• display CAC before the ANI number
• display CAC after the ANI number
• do not display CAC