Routing trouble

[sjforcum]

Hello,

I've just started in a new position with a larger definity than I'm used to. It seems I'm having trouble with a call being routed over the wrong trunks. I'm assuming the problem lays in the ARS table...but I'm not familiar with ARS.

When a caller dials a long distance telephone number, the calls are supposed to head over a T1 and the user should be prompted for a pin.

But I have a user trying to dial a phone number with a 269 area code...and when he does, the call makes it to our local telco (SNET) and they tell him the number is incomplete.

How can I re-program the switch to force this call over the long distance T1?

Thanks a ton!
Steve Forcum

 

[jaymzter]

list ars route chosen (the phone #). What route pattern does it take? is it the right one? if not, change ars analysis 269 and set the proper route. i'm assuming other numbers go out the proper way so you have a route pattern that works.

 

[sjforcum]

I tried using the list ars route chosen but it says the phone number is not a valid indentifier.

Should this happen?

 

[randyb19]

Use the same command line and make sure that you inputting the phone number as you would dial it on the phone (but without the 9) in its entirety. Make sure you are adding a 1 if it is long distance. Then you should be verifying the route that 1269 is taking to get out of the switch (if the 1 is needed). From there you should be able to choose the appropriate route pattern to have the call go out your T1.

(Just in case the route listed for the chosen number looks like pxx, xx being a number, that is a partition group. Just disp partition-r xx and that will show you the partition route)

Hope this helps.