Able to find this denial in list trace
11:17:14 TRACE STARTED 11/19/2015 CM Release String cold-03.0.124.0-
11:17:34 Calling party trunk-group 2 member 12 cid 0x24a7
11:17:34 Calling Number & Name
11:17:34 active trunk-group 2 member 12 cid 0x24a7
11:17:34 calltype 2799#, no match
11:17:34 idle trunk-group 2 cid 0x24a7
this is caused by incorrect programming in Call type Analysis table
A similar issue would look like this but an entry may be missing from the aar analysis table. In this case it would look like this:
08:25:44 calltype 8880# match=8
08:25:44 calltype 1008880#, no match
08:25:44 calltype 1008880, no match
In this case there is a match in the calltype analysis table, but once the 100 is added to the number, it doesn't know where to route it. Adding 100 with a min and max length of 7 and the desired route patteern resolved the issue.
