Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNIS Misrouting? 1

Status
Not open for further replies.

n25

Technical User
Nov 4, 2004
234
US
Here's the problem: There are currently 3 toll-free numbers that terminate to one of our trunks and those get misrouted when they're called from Canada. In contrast, those numbers get routed to the correct VDNs when called from the US.

The misrouting occurs because the switch somehow "treats" the DNISs as AAR codes if called from Canada as seen on one of the number's traces (in red):

LIST TRACE

time data

22:50:48 Calling party trunk-group 233 member 89 cid 0x2dfe
22:50:48 Calling Number & Name 905629xxxx NO-CPName
22:50:48 active trunk-group 233 member 89 cid 0x2dfe
22:50:48 dial 5101 route:UDP|AAR
22:50:48 term trunk-group 50 cid 0x2dfe
22:50:48 dial 51015 route:UDP|AAR

22:50:48 route-pattern 110 preference 1 cid 0x2dfe <- it already got lost in here
22:50:48 seize trunk-group 50 member 113 cid 0x2dfe
22:50:48 Calling Number & Name 905629xxxx NO-CPName
22:50:48 Proceed trunk-group 50 member 113 cid 0x2dfe
22:50:49 Alert trunk-group 50 member 113 cid 0x2dfe
22:50:49 G729 ss:eek:ff ps:30 rn:50/101 10.10.213.16:29112 10.20.223.15:30848
22:50:49 xoip: fax:Relay modem:pT tty:US 10.20.223.15:30848 uid:0x50e7c
22:50:49 active trunk-group 50 member 113 cid 0x2dfe
22:50:53 idle trunk-group 50 member 113 cid 0x2dfe
....


Here is a trace for the same number when called from the US and what should be the proper routing:

LIST TRACE

time data

22:58:16 Calling party trunk-group 233 member 73 cid 0x2f17
22:58:16 Calling Number & Name 314658xxxx TEST x1279 Rm
22:58:16 active trunk-group 233 member 73 cid 0x2f17
22:58:16 dial 15193 <- got routed to the correct VDN
22:58:16 term announcement 15607 cid 0x2f17
22:58:16 active announcement 15607 cid 0x2f17
22:58:16 xoip: fax:eek:ff modem:eek:ff tty:eek:ff 10.20.223.15:30872 (igc)
22:58:16 xoip: fax:eek:ff modem:eek:ff tty:eek:ff 10.10.223.53:16996 (igc)
22:58:16 hear annc board 49A02 ext 15607 cid 0x2f17
....

Here is the incoming call handling treatment for trunk 233 which shows DNIS 51015 should go to VDN 15193:


display inc-call-handling-trmt trunk-group 233 Page 1 of 30


INCOMING CALL HANDLING TREATMENT
Service/ Called Called Del Insert Per Call Night
Feature Len Number CPN/BN Serv
mega800 5 51015 5 15193


As you could see both calls are coming to the same trunk group which means both should be treated the same way, unfortunately that's not the case. What could be causing this? Is it something in the switch/programming that could cause this or is it on the carrier side?



 
On the inc-call-handling-trmt screen add an entry for 'other' with the same paramaters as mega800. You may want to also add an entry for 'i800'. Can't hurt.

Kevin
 
Thanks for the tip Kevin! I'll try and add those and see if it changes anything.
 
It seems that did the trick! We'll be monitoring this til next week, thanks again Kevin!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top