7 digit dialling with google voice

[tiggerpaws]

Is this possible?

I can't do it, I have:
PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = Asterisk 10.0.0-beta1 │
│ Asterisk Source Version = 10.0.0-beta1 │
│ Dahdi Source Version = 2.5.0+2.5.0 │
│ Libpri Source Version = 1.4.12 │
│ IP Address = 192.168.0.63 on eth0 │
│ Operating System = CentOS release 5.6 (Final)

free pbx version is 2.8.1.4

I tried putting my country and area
code in the prepend box ie, 1 then 3 digit
area code, then the NXXXXXX in the
match pattern box.

I notessed in the terminal log it said
it passed just the 7 digit number to the
trunk, so I see why it is effing up,
it only pass 7 digits to google voice
which is not right, how do i get this
thing to OBEY?

I have 2 GV trunks under one outbound route,
is that not right? will that confuse it?

ps: I tried this in both the outbound route,
then the dial manipulation rules in the trunk,
then both, and still broken.

Thanks.

 

[heykoopa]

I am not a guru but I have had the same issues and resolved them by doing the following in my trunk under: Dialed Number Manipulation Rules. I added the following rules you would change my area code to yours.


I tried showing you photos but couldnt get it to upload correctly


1231 NXXXXXX

(1231) + Prefix) |NXXXXXX


Then under Outbound routes I have the following.

NXXXXXX


As far as having 2 Trunks under 1 outbound route it is my understanding that all that will happen is if trunk 1 fails then it goes to 2 or that if you have different route manipulations then it would use the one for that route as in my case I have a international trunk that I use that just has an international dial plan and I have that as my 2nd trunk. My first trunk dials my US numbers.

Andrew

 

[MichiganTelephone]

I hate to barge in on this but I can see why it is not working, however I don't do the stupid little boxes that they put in the outbound routes and trunks in F---PBX 2.8 and later — I use the Swiss Army Knife module (for which I am incredibly thankful) to get the old-style text boxes back.

So assuming you do the same, what I do in my outbound routes (not trunks, though you could probably do it there as well) is have a rule like

1234+NXXXXXX

where 234 is replaced with your area code. So when you dial seven digits, the outbound route rule adds the area code.

The main reason I do it at the route level is so if you have more than one extension and one happens to be in a different area code you can make a separate rule for that. For example, let's say you had an off-site extension 222 in area code 567, you could do:

1567+NXXXXXX/222
1234+NXXXXXX

So extension 222's calls should be caught by the first rule and their 7-digit calls would have 1567 prepended, while everyone else's 7 digit calls should have 1234 prepended. You can't do something like that at the trunk level.

If you don't have the Swiss Army Knife module, you're on your own with the stupid little boxes. Hopefully you can figure it out but if not please don't ask me to explain it; I simply want nothing to do with that part of F---PBX anymore, ever.

 

[tiggerpaws]

Cannot be done.

Installed sak, that functions,
but will not dial with 7 digits,
says all srkits are bizzy.

I guess it just cannot be done,
thank you guys for all your
input, and going thru the
trouble, I am very sorry if
I accidentally wasted any of
your time, but I saved the
info to my HDD in case it does
work for another box, another day.

Thank you very much for trying,
its much appreciated.

 

[mainenotarynet]

Tigger don't give up just yet as my PBX periodically gives me the same BS - try either an 'amportal restart' if all circuits are still busy then try a 'shutdown -r now' but the restart usually fixes the circuits busy message.

I have disabilities too ( I read your post on yours from a while ago) ---I can help with this if you would like me to.

the SAK is right bit I am unsure if google needs the 1 in front of the area code or not. so an option could be 234+NXXXXXX and see if that works/

Michighan -- thanks for the tip on just the Outbound route patterns. but I for some reason can't figure out the /cid part. see I run a pbx for 3 different groups and want an outbound route for each set of extensions so I tried (example of 7 digit for my area) 207+NXXXXXX/_1[0-1][1-9]XX

I read somewhere you could do patterns buy putting an underscore as the first character in the pattern. this doesn't seem to work for me as when looking at a call on my FOP2 (I paid for the unlocked version and love it) it shows the call going out the wrong trunk for the extension.

Any suggestions as to how to get this to work would be great.

One other question (caveat?) If I use google and they require the 1AC#Tel# and I have another provider trunk in the same outbound route that does not would I then need to strip the one in the trunk only then? I could see that causing a circuits busy error as well as it cannot complete the call due to usibng the wrong pattern.

Thanks

 

[mainenotarynet]

Thanks, yes I did know the breakdown and that seeing it this way told me I have a flaw in my logic (it won't work for the 110xx branch and will allow the 118xx branch which is a separate animal all together.

101-116 are one group 118 is a separate entity. I guess one way would be to put 1207+NXXXXXX/118XX in a route ABOVE the 1207+NXXXXXX/1[01]XXX route (yes I forgot of 110 so this one corrects that) It does however inclue the 118XX but if that route is separate and triggered first that shouldn't matter.

Just fyi runing Piaf-Purple with FPBX 2.10 (just upgraded that a few days ago. So you are saying I do not need the underscore anymore? with 1.8?

I would love to try Asterisk 10 with PIAF2 and incredible3 but my PBX is on a VPS in new York and I can't use an ISO (it is OpenVZ though) so until there is a version I can send my people I guess I am OK for now.

Thanks.