Instruction manual

Page 1042 of 3156 CIS ANI Digits Manipulation and Gateways Enhancements
553-3001-306 Standard 10.00 January 2002
On the gateway side of the R2MFC to CIS, the purpose of this mapping is to
convert the 10 MFC CAC meanings into CIS CAC meanings, or to define a
default CIS CAC value. For this, a conversion table is defined. Conversion
tables are defined in overlay 15. Up to 32 tables can be configured. A
conversion table can be assigned on each MFC route. For this, the prompt
CAC_CONV is added to the MFC incoming route configuration. If no CAC
conversion table is configured on the MFC route, default table (number 0)
will apply to the MFC incoming route.
A CAC conversion entry contains the following data:
• CAC0 to CAC9: against CAC0 prompt is configured the CIS CAC value
to be sent if an R2MFC CAC of value 0 has been received.
• DFLT: against this prompt is configured the CIS CAC value to be sent if
the R2MFC CAC has not been received or is not in the correct range.
When CNI has not been received at the time ANI is built, a default value must
also be used. This default value is defined in the CAC Conversion table. On
CIS trunks, 10 CAC values can be sent, from 0 to 9. Each one has a particular
meaning (see Table 33).
Default table is number zero and is configurable. After upgrade this table is
defined in memory as shown in table below. The craftsman must be aware
that modifying this default table after conversion will modify the CAC
generated for all gateway cases where the incoming route had a CAC set to
three (before upgrade).
In this default table all fields are set to three, as it is the current CIS CAC
default value. A value of three for CIS Category Code means the caller is
residential, business or hotel subset with the access to local network and
without access to automatic regional, toll, international network and to
chargeable service numbers.