How do I force a leading '1' for piaf trunk?

[edisoninfo]

I have a piaf trunk via iax that works great. (United States) My one problem is that it requires a '1' at the beginning of every number dialed. Even tho we can dial xxx-xxx-xxxx numbers without the leading '1' for most numbers we dial, they all get rejected with congestion from PIAF unless it has a leading '1'. I presume this is due to PIAF being from Spain so in reality all numbers here in the US are long distance?

I can't just pre-pend a 1 because sometimes the user has added the 1 already.

 

[tabbertmj]

That is easy enough. In the trunk dial Rules, you should be bale to use something similar to:

1+NXXNXXXXXX
1NXXNXXXXXX



That should do the trick

 

[jroper]

Hi

Most VoIP carriers do insist on the full international code.

If you dialled say 555 NXXXXXX - we would try and deliver that call to Brazil, so we need you to dial 1 555 NXXXXXX

In the trunk dial rules, you only need 1+NXXNXXXXXX, there is no need to put anything in there unles you are actually manipulating the dialled digits.

You can go further and create a rule to allow 7 digit dialling for your local area as well. eg if your area code is 555, then if any one dials NXXXXXX - the rule would be 1555+NXXXXXX

Joe

 

[edisoninfo]

I only have 8|. in my outbound route for PIAF. I tried changing it to 8|1+. and now it won't dial at all.

I have a pstn line via the cable company that includes unlimited long distance. I know "why the voip lines then?" Well, because I like using the latest technology and before I got the cable line, I had to have VoIP for affordable long distance. I also like to test everything so I can recommend the right solution for each customer.

All that to say, I have the NXXNXXXXXX and 1NXXNXXXXXX in the PSTN outbound routes and just 8|. and 9|. in the Vitelity and piaf outbound routes. Works great except for forcing the leading 1 on piaf. Vitelity and QuantumVoice must add the 1 themselves because this setup works with them.

Edit:
Ok I just tried this and it will dial fine if I add the 1, but goes to congestion if I do not dial the 1. So the 1+ is not working....

8|1+NXXNXXXXXX
8|1NXXNXXXXXX

 

[GlenPittman]

Edit:
Ok I just tried this and it will dial fine if I add the 1, but goes to congestion if I do not dial the 1. So the 1+ is not working....

8|1+NXXNXXXXXX
8|1NXXNXXXXXX

In my opinion, you would place the "8|." or "NXXNXXXXXX" in your dial patterns of the OUTBOUND ROUTE.

Then under the dial rules of your TRUNK you would insert the "1" for long distance by a rule of 1+NXXNXXXXXX

Glen Pittman

 

[edisoninfo]

Wow! What timing! I was just typing my next question when you replied Glenn, and you already had the answer! I have my outbound routes set to use the PSTN / ZAP line by default and if it is already in use, then try the PIAF and then the Vitelity trunk. Any amount of dial pattern changes would fix dialing out the Zap channel but break dialing out PIAF and vice versa. I needed a way to only add a leading 1 if it was trying to use the PIAF trunk. Your suggestion fixed all of the issues of this thread. Thanks!!!!

 

[jroper]

Hi

The basic rule is -

You use Outbound routes dial patterns to select which trunks you want to use for which routes. You do this from the point of view of the user - e.g. what are they likely to dial. You may or may not manipulate the digits here, for instance you may remove the "9 for an outside line"

The Trunk dial Rules are there to manipulate the digits in a way that your carrier will accept them.

It is pointless putting anything in the dial rules, unless you are going to change the dialled digits.

Joe