Topic: Problem with routes

[charlien]

I'm new to Asterisk and am having a problem understanding dialing routes to send a call out an analog pots line. I researched what I thought was the correct way to set up an out going route but am way off base and upsetting the person I keep accidentially calling. Here is what I did:

My primary path is Zap1-1, which is the X100P card in the server connected to my home line.
My route plans are _91NXXNXXXXXX _9NXXXXXX
I'm dialing from the US an need to dial either a 7 digit "local" number or 1 + Area Code + 7 digit number for long distance.

From my Xlite client I dialed 91414773???? (when I dialed I completed the number).
When someone answered I knew they were not at the number I dialed. I asked what area code I dialed and was told 262. I am in the 262 area code.

I'm way off base. Can someone give me a hint.

[SARK devs]

Hi

I guess the first question is... why are you requesting a 9 at the beginning of your dial string?

I would have thought that _1NXXNXXXXXX and NXXXXXX would be sufficient to get you where you want to go.  Otherwise, you are going to have to remove the 9 in the trunk mask (9:). 

To see what asterisk is actual sending you can fire up the asterisk console and watch what's going on. Fire up a linux console and do

asterisk -rvvvv

Do your dial and you'll see what digits asterisk is shoving out over the circuit.

Kind Regards

S

[charlien]

Selintra,

Thanks for the help. Removing the "9" was what I needed to do. I put the "9" in the dialing string because I've spent 30 years in the traditional PBX industry and have always had "9" as the trunk code. Guess I need to start to think differently.

Charlie

[SARK devs]

Yup, I'm an old AT&T boy myself  .  There isn't any concept of line or trunk seize in asterisk (although we are often requested to simulate it by our customers 'cos they just can't get used to not dialling a 9). 

It's just number-patterns acting as the switching fabric.

Kind Regards

S