SOLVED GV stopped connecting today

[yozh]

You'll probably need to follow the tutorial to implement Google Voice OAUTH 2 authentication on your server before attempting to register an account.

Thats what I followed.

 

[billsimon]

So, followed instructions, id everything. Now getting this errors below.

Same error? Then it still seems like there's some issue with OpenSSL, or Asterisk. Since you're testing on a new box, can you upgrade?

 

[wardmundy]

If that also fails, then it may be an Asterisk XMPP problem. Only alternative is Simonics SIP to Google Voice Gateway.

 

[wardmundy]

You might also want to try the Incredible PBX ISO which has the option to install with GV OAuth support. Then you'll know for sure whether it's an Asterisk problem or "operator error."

FWIW: My Incredible PBX servers with GV OAUTH still work fine.

 

[yozh]

You might also want to try the Incredible PBX ISO which has the option to install with GV OAuth support. Then you'll know for sure whether it's an Asterisk problem or "operator error."

FWIW: My Incredible PBX servers with GV OAUTH still work fine.

Anyway to upgrade from my current version ? I run other things on this box as well.

Going to try the latest ISO just for the heck of it.

 

[yozh]

Same error? Then it still seems like there's some issue with OpenSSL, or Asterisk. Since you're testing on a new box, can you upgrade?

Doesnt look same. Well my question is same, can I upgrade ?

 

[RPi-Fan]

I'm using FreePBX + Asterisk 11.22.0 and Google Voice via default XMPP (non-OAuth2) is working normally on three Google Voice numbers.

 

[Huckda]

I'm using FreePBX + Asterisk 11.22.0 and Google Voice via default XMPP (non-OAuth2) is working normally on three Google Voice numbers.

mine is old Purple install... Asterisk 1.8.something... dare you restart and see if it breaks?
I was fine this morning until I updated OSS Endpoint manager to deploy some new T46gs...then *POOF* no more gvoice

 

[RPi-Fan]

dare you restart and see if it breaks?

I just rebooted. Everything came right back up and is operational, including the three Google Voice trunks (I successfully made outgoing calls on each).

 

[Huckda]

is there some CLI method of checking for GVoice connectivity?
the errors have disappeared from the logs... but I still have no calls routing out through GV

** Guess I was wrong:

[2016-06-14 21:15:34] WARNING[20059] res_jabber.c: JABBER: socket read error
[2016-06-14 21:15:34] WARNING[20059] res_jabber.c: JABBER: socket read error
[2016-06-14 21:15:38] ERROR[20059] res_jabber.c: JABBER: Failure in TLS.
[2016-06-14 21:15:38] ERROR[20059] res_jabber.c: JABBER: Failure in TLS.


it's baaaaack...

 

[RPi-Fan]

xmpp set debug {on|off} Enable/Disable Jabber debug
xmpp show connections Show state of clients and components

 

[Huckda]

What I gots installed...*old and musty*???


PIAF Installed Version = 2.0.6.2 under *HARDWARE* │
│ FreePBX Version = 2.11.0.43 │
│ Running Asterisk Version = 1.8.13.0 │
│ Asterisk Source Version = 1.8.13.0 │
│ Dahdi Source Version = 2.6.1 │
│ Libpri Source Version = 1.4.12 │
│ IP Address = 10.1.3.228 on eth0 │
│ Operating System = CentOS release 6.2 (Final) │
│ Kernel Version = 2.6.32-220.17.1.el6.i686 - 32 Bit │
│ Incredible Version = 403

and BELOW is the pertinent log info I presume:

JABBER: hucks1stpbx OUTGOING: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='gmail.com' version='1.0'>
[2016-06-14 21:46:05] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx OUTGOING: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='gmail.com' version='1.0'>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx INCOMING: <stream:stream from="gmail.com" id="some long string here" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"><stream:features><starttls xmlns="urn:ietfarams:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietfarams:xml:ns:xmpp-sasl"><mechanism>X-OAUTH2</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx INCOMING: <stream:stream from="gmail.com" id="some long string here" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"><stream:features><starttls xmlns="urn:ietfarams:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietfarams:xml:ns:xmpp-sasl"><mechanism>X-OAUTH2</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx OUTGOING: <starttls xmlns='urn:ietfarams:xml:ns:xmpp-tls'/>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx OUTGOING: <starttls xmlns='urn:ietfarams:xml:ns:xmpp-tls'/>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx INCOMING: <proceed xmlns="urn:ietfarams:xml:ns:xmpp-tls"/>
[2016-06-14 21:46:09] VERBOSE[21870] res_jabber.c:
JABBER: hucks1stpbx INCOMING: <proceed xmlns="urn:ietfarams:xml:ns:xmpp-tls"/>
[2016-06-14 21:46:09] ERROR[21870] res_jabber.c: JABBER: Failure in TLS.
[2016-06-14 21:46:09] ERROR[21870] res_jabber.c: JABBER: Failure in TLS.
[2016-06-14 21:46:10] WARNING[21870] res_jabber.c: JABBER: socket read error
[2016-06-14 21:46:10] WARNING[21870] res_jabber.c: JABBER: socket read error
[2016-06-14 21:46:10] VERBOSE[21870] res_jabber.c:

 

[Huckda]

This is my jabber.conf file if that helps determine cause:

[general]
debug=yes
autoprune=no
autoregister=yes

[hucks1stpbx]
type=client
serverhost=talk.google.com
[email protected]/Talk
secret=password
port=5222
priority=1
usetls=yes
usesasl=yes
status=Available
statusmessage="No Information Available"
timeout=100
keepalive=yes

 

[RPi-Fan]

FWIW, I just tested Asterisk 13.9.1 and it's also working properly with Google Voice.

It appears that Google made an SSL related change that requires one or more of the SSL related changes made in more recent versions of Asterisk. A user on DSLR who was running 11.13.0 had the same problem which was resolved by upgrading to 11.22.0.

 

[masterautomate]

FWIW, I just tested Asterisk 13.9.1 and it's also working properly with Google Voice.

It appears that Google made an SSL related change that requires one or more of the SSL related changes made in more recent versions of Asterisk. A user on DSLR who was running 11.13.0 had the same problem which was resolved by upgrading to 11.22.0.

I agree that this is a change with Google but what was the change and how can we patch older installs? I have an older 1.8.13.0 box that I would rather not have to rebuild at the moment if we can figure out what has changed. This has to be something in the handling of iksemel.

 

[dziny]

I have an older 1.8.13.0 box that I would rather not have to rebuild at the moment if we can figure out what has changed.

You really don't have to rebuild the whole box to upgrade asterisk. In your case you are on asterisk version that is EOL unfortunately.

 

[masterautomate]

Ok well I did something completely insane and upgraded from 1.8.13.0 to 11.22.0 using a completely nonstandard method (on a live system with minimal backup without wiping and starting fresh). While this caused some issues and things are not working as they should right after the upgrade it fixed the jabber tls issue and my gvoice accounts logged in. So if you are having issues with jabber tls updating is your solution. Now to go fix all the new problems I created.

 

[yozh]

How can I upgrade on green from 11.4 to 11.22 ?

EDIT: Trying with the script from here http://pbxinaflash.com/community/threads/original-asterisk-upgrade-script.12560/

Had to edit the file a bit was getting error: "Sorry. Asterisk compile from source not supported by SHMZ OS."

PIAF Installed Version = 2.0.6.4 under *VMWARE* x
x FreePBX Version = 2.11.0.31 x
x 2.11 x
x Running Asterisk Version = UNKNOWN x
x Asterisk Source Version = 11.4.0 x
x Dahdi Source Version = 2.6.2 x
x Libpri Source Version = 1.4.12 x
x IP Address = XXXXX on eth0 x
x Operating System = CentOS release 6.4 (Final) x
x Kernel Version = 2.6.32-358.6.2.el6.i686 - 32 Bit

 

[yozh]

Yep, upgrading to 11.22 did it. It works now again. Going to try few things and possibly put this back in prod.

Thanks for the help guys

 

[billsimon]

Yep, upgrading to 11.22 did it. It works now again. Going to try few things and possibly put this back in prod.

Thanks for the help guys