[WM: Yes, indeed. In fact, we’ll have a new version of PBX in a Flash out later today that incorporates the patch for Asterisk 1.8.1. And the patch already is included as part of any new Incredible PBX 1.8 install.]

I am wondering that if Google wants to kill Asterisk systems from attaching, then it would be easy for them to parse the status messages like:

"I am an Asterisk PBX", "Incredible PBX", etc.

Instead, I modified jabber.conf in /etc/asterisk to say:

statusmessage="Away";

and restarted the box.

Wouldn’t this help? Just my 2 cents on this.

Is there any way to add gvout to * 1.6? Or am I stuck getting a 1.8?

Also, I’m wondering why not integrate everything into one iso?

It’s pain to sit and wait for all those extra multi-hundred MB downloads on a slow connection after I got PIAF iso and was hoping it’s going to be a quick install.

[WM: Asterisk 1.6 will be obsolete in 3 months when IPv4 is no longer an option, so we don’t plan to spend much effort enhancing it. As for speed, PIAF builds your system from source so that it can easily be enhanced/expanded to meet your future needs. If you prefer a quick install without this flexibility, then there are other Asterisk aggregations out there that might better meet your requirements. As most women would tell you, quick is almost never better. 😉 ]

[WM: If you’re just getting started, simply follow the steps in the original article. All of the downloads are current. I thought we made that clear in the first paragraph. 🙄 ]

[WM: Asterisk 1.8 looks pretty solid to me. Go for it unless it’s in a business environment where every minute (and dollar) counts. This is not a warranty obviously. 🙂 ]

[WM: Yes. It is.]

I just want to report that when I issued 3 new commands to permanently fix the outbound calling issue, the problem still persisted but a little bit different. After few seconds of silence, it says "Number is not answering and hangup".

Issued amportal retart & /root/jab then it worked again. PIAF in VMWare Workstation.

[WM: Apply the fixit.sh script first and then the new commands to address the outbound calling issue.]

[WM: Sure. Edit the [gvoice-johndoe] context at the bottom of extensions_custom.conf and comment out the second line (pls-wait-connect-call) by inserting a semicolon at the beginning of the line. Then reload the dialplan. Incidentally, unlike the previous version to which you alluded, this prompt in the current release plays in the background so it doesn’t delay the connection at all. We thought that was preferable to 4 seconds of silence which might confuse some users.]

Step #6: Modify the GoogleVoice Outbound Route in FreePBX: Setup, Outbound Routes, GoogleVoice. Change the existing Trunk Sequence entry to: gvoice-johndoe.

If now I change to the second account, I will always dial out with the second account not first. Incoming works fine.

[WM: Sorry. I’m the dense one. Add another Trunk Sequence below gvoice-johndoe for gvoice-marydoe. Then, the first call will go out through the first Google Voice trunk. And, when that trunk is busy, the next call will be routed out through the second Google Voice trunk. You also can tie trunks to specific extensions for outbound calls using Custom Contexts. Visit the PIAF Forums for details on this approach.]

[WM: Everywhere you see johndoe, replace it with your second Google Voice credentials, not your first set of credentials. When we said repeat the steps, we meant with your second account’s credentials. These are what should have been entered on your second Cheat Sheet.]

Thanks again for all the help!

There must be something really obvious that I’m missing.. in the fixit.sh script, is it OK that my Gmail call notification address is the same as my dedicated GV email? Or does that need to be different?

After it said "Logging out of voice", outbound call went thru.

However, before that amportal restart & /root/jab seemed not to help. And now after each reboot, the combo amportal restart & /root/jab seems to work nicely. Thanks.

Btw, how to put this combo into startup script?

[WM: Adding to startup script doesn’t work unfortunately.]

It doesn’t make any difference on Google whether you use abc.def or abcdef. Google accepts both as the same valid user. Try yourself logging in as abcdef.

Best regards.

amportal restart
/root/jab

I’ve tried embedding it in the startup script, and that doesn’t suffice.

If you still have problems, try issuing the following command with your credentials and then repeat the two commands above:

gvoice -e username@gmail.com -p gvpasswordhere call 8431234567 username@gmail.com 9

I have noticed that several guys have had the same symptom. Now sure why. My gmail email has this pattern: abc.def@gmail.com. Does "." make any difference? System with the same email worked flawlessly previously.

I am running PIAF on a VMWare, btw.

Thank you very much for your hardwork for the calling freedom. I have learnt alot. Should have known this before we purchased Fonality system. Now we are stuck with Fonality with thousands of biz cards printed with their numbers. FML.

[WM: Same fix adapted for Incredible PBX. Haven’t tried multiple outbound calls using the same trunk. But, if I were in Google’s shoes, it would make some sense to limit it.]