Configuration issue.
The system uses the information from “IXC” field on the ‘route-pattern’ form for calls that the system routes through an IXC, and for the Call Detail Recording (CDR) feature.
So the route pattern shows:
display route-pattern 222 Page 1 of 3
Pattern Number: 222 Pattern Name: SIP VP 0800
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 151 0 1 n user
2: 153 0 1 n user
3: 155 0 1 n user
4: n user
5: n user
6: n user
And by default the ‘ixc-codes’ form is set as:
display ixc-codes Page 1 of 2
INTER-EXCHANGE CARRIER ACCESS CODES
IXC Codes Assignments (Enter up to 15)
CDR IXC CDR IXC
IXC access IXC access
code number IXC Name code number IXC Name
1. 9.
2. 10.
3. 11.
4. 12.
5. 13.
6. 14.
7. 15.
8.
display ixc-codes Page 2 of 2
EQUAL ACCESS CARRIER CODE FORMATS
IXC Prefix IXC Code Format
1. 101 xxxx
2.
So when the dialed numbers are like: 91014917961, leading 9 is chopped as it is the ARS FAC, so 1014917961 is sent to ARS. However, 101 happens to match the default “IXC Prefix” and the code format ‘xxxx’ (meaning any other 4 digits). As the IXC info is used for marking calls for routing by particular IXC the prefix and the code form together serves as a match pattern and a steering/routing info. Thus 101 in IXC Prefix is matched and leading 101xxxx part of the number is chopped as it is considered to be only steering/routing info, leaving the called number to be “961”. Now again leading 9 is chopped as it is the ARS FAC so all is left from the original called number is: “61” and for this indeed SM will not find a route and respond with “404 Not Found (No route available)” which in turn trigger CM denial: “denial event 1166: Unassigned number”
