FYI Confused on Google Voice

[wardmundy]

dziny: Rebuilt new VM. Exact same error skipping that block of code. Sorry.

 

[dziny]

I'll have a look at it tomorrow. I could potentially give you access to my sanitized image on EC2 for you to see my config.

 

[dziny]

Btw. Had just one thought. After patching asterisk source I usually run

autoconf
./bootstrap.sh
./configure
make menuselect

Here is an explanation why it's a good idea http://lists.digium.com/pipermail/asterisk-users/2013-May/278866.html to run bootstrap.
What the patch does is basically make lib jasson from asterisk 12 available in asterisk 11. It's a significant change so it's probably a good idea to generate new configuration script for asterisk. Give it a shot.

 

[wardmundy]

Btw. Had just one thought. After patching asterisk source I usually run

autoconf
./bootstrap.sh
# WM NOTE: had to add next step to get ICE working with Asterisk
make distclean
./configure
make menuselect

Here is an explanation why it's a good idea http://lists.digium.com/pipermail/asterisk-users/2013-May/278866.html to run bootstrap.
What the patch does is basically make lib jasson from asterisk 12 available in asterisk 11. It's a significant change so it's probably a good idea to generate new configuration script for asterisk. Give it a shot.

THAT was a MAJOR IMPROVEMENT and got us close but still no cigar. Everything now loaded correctly. But, when a call was placed, I got this:

[2015-06-26 07:07:25] ERROR[3507][C-00000001]: chan_motif.c:1768 jingle_request: Endpoint 'gmygvaccountnamegmailcom' does not exist.
[2015-06-26 07:07:25] WARNING[3507][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type 'Motif' (cause 6 - Channel unacceptable)

motif.conf and xmpp.conf looked fine with matching context names [gmygvaccountnamegmailcom] and xmpp showed the trunk was connected so it appeared Asterisk's endpoint identifier wasn't working properly with motif.

But then there was a big hint. On an inbound call, I got "Received Google transport information on session but ICE support not available." Tried adding icesupport=yes in FreePBX, in rtp.conf general, and in sip_general_custom.conf, but I still got the error. The problem is that once you add ICE support, you also have to add a STUN server, and that fixed it after adding make distclean before ./configure step. Then putting these two lines in sip_general_custom.conf did the trick:

icesupport=yes
stunaddr=stun.counterpath.net

This was on the Ubuntu platform so I still need to test on CentOS, but I think it probably will work fine now. THANKS FOR ALL YOUR HELP!!!

We'll roll this into the new Incredible PBX builds shortly.

 

[dziny]

Happy you've got it working

 

[wardmundy]

Happy you've got it working

Now on to CentOS...

 

[wardmundy]

dziny: And CentOS now works as well. Tutorial available here for all. Thanks again.

 

[tycho]

This is "Incredible." Thanks to all! Kudos to wardmundy, dziny, and Ryan Tilton. billsimon too!

 

[wardmundy]

dziny: Looks like everything works as expected EXCEPT the Google TTS app from lzaf. I'm assuming your OAUTH patch for Google Voice may have changed the handshake with Google on all accounts. Correct??

 

[dziny]

dziny: Looks like everything works as expected EXCEPT the Google TTS app from lzaf. I'm assuming your OAUTH patch for Google Voice may have changed the handshake with Google on all accounts. Correct??

Only for the xmpp (google chat). I'm not familiar with Google TTS, how it authenticates. If it is using the password from the xmpp.conf file then this might be the source of the issue. But you can still authenticate the old way (until google decides to remove it) so for one app you can use oauth2 and for another the old way (plain password) on the same account.

 

[wardmundy]

dziny: Turns out it wasn't your brilliant code after all. It was my brilliant f*ckup. sox was missing. Everything works fine now.

 

[qtlnx]

Hello @wardmundy, before I open a new question let me ask here - Just installed fresh 13.13 from .ova into a KVM. Configuration went fine with no issues. Question: is google OAuth2 enabled by default or something extra needs to be done? Are there docs on your site that I missed?

 

[briankelly63]

Shades of GV past..... this is why it's probably easier to use the GW with a one time charge.... Better it be his headache to deal with changes.

 

[wardmundy]

Hello @wardmundy, before I open a new question let me ask here - Just installed fresh 13.13 from .ova into a KVM. Configuration went fine with no issues. Question: is google OAuth2 enabled by default or something extra needs to be done? Are there docs on your site that I missed?

Yes. Yes.
http://nerdvittles.com/?p=24347

 

[qtlnx]

http://nerdvittles.com/?p=24347 is the Incredible PBX 13-13 for VMware page where I originally found your .ova image and installation instructions. It says noting about OAuth2 other then a link to http://nerdvittles.com/?p=19169 which is titled Google Voice with OAuth 2 Comes to Incredible PBX for XiVO. Are OAuth2 instructions on the XiVO page directly applicable to Incredible PBX 13-13 VMware image?

 

[qtlnx]

Comparing code with instructions I concluded that all OAuth2 changes have already been made in VMware image, gvoice connection shown active after entering refresh token. Now I need to figure out how to copy my configuration from 13.2 to this 13.13 but it is a different story...