Instruction manual

CIS ANI Digits Manipulation and Gateways Enhancements Page 1043 of 3156
Features and Services
MFC routes were given a CAC prompt on which was configured the CAC
value of incoming route when tandeming to CIS. This data has no more utility
on incoming MFC route as a CAC conversion table is configured against
prompt CAC_CONV. Thus, CAC prompt is removed from MFC incoming
routes. On upgrade from Release 24 with new release, former CAC prompt
value is moved into a CAC conversion table, and this table is assigned to the
route.
In the gateway side CIS to R2MFC, the purpose of this mapping is to convert
the 10 CIS CAC meanings into R2MFC CAC value. For this, a conversion
table is defined.
Before Release 24, the CAC sent was defined in the R2MFC table (Overlay
94). In this R2MFC table, it is the same value for all non-tie incoming trunks.
In Overlay 15, for CAC conversion table, the same range (1-10) and default
value (6) than in Overlay 94 are used. The value 0 is also allowed, it means
that the value defined in R2MFC table for incoming non-Tie trunk has to be
used.
Table 33
CAC conversion table entry 0 for R2MFC route
MFC CAC CIS CAC CIS CAC description
CAC0 3 CIS value corresponding to MFC CAC DGT0
CAC1 3 CIS value corresponding to MFC CAC DGT1
.... 3
CAC8 3 CIS value corresponding to MFC CAC DGT8
CAC9 3 CIS value corresponding to MFC CAC DGT9
Default 3 CIS value used when MFC CAC has not been
received, or MFC CAC received is not in the
MFC CAC list of this table