SOLVED GV stopped connecting today

[ws2000]

Man, you saved my life!!

I was desperate because my Google Voice stopped working yesterday and I was following this thread anxiously hopping someone could give me a light about how to workaround this issue. Finally I've read your post and thought: it's a too simple solution to doesn't try and it just worked like a charm! Just edit res_xmpp.c and replace SSLv3_method() to SSLv23_method() and recompile asterisk (actually it just recompiled this module). By simply doing this, my Google Voice is now working again!



Thanks again!!

Where is res/res_xmpp.c located? Could you please provide some newbie friendly directions? I'm stumped.

Found the file and edited it with WinSCP. How do I recomplile it? Still No GV.

Thanks

 

[Kennybell]

Thanks, @tenortim. On really old systems, you'll need to make the SSLv3_method() to SSLv23_method() change in res/res_jabber.c instead of res_xmpp.c.

Where and how do I do this??? I'm not a Linux expert.

PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* ¦
¦ FreePBX Version = 2.8.1.4 ¦
¦ Running Asterisk Version = 1.8.7.2 ¦
¦ Asterisk Source Version = 1.8.7.2 ¦
¦ Dahdi Source Version = 2.5.0.2+2.5.0.2 ¦
¦ Libpri Source Version = 1.4.12 ¦
¦ IP Address = 192.168.XX.XX on eth0 ¦
¦ Operating System = CentOS release 5.7 (Final) ¦
¦ Kernel Version = 2.6.18-238.9.1.el5 - 32 Bit

 

[gavimobile]

did this issue come back for you all, or is it just me this time?

 

[ws2000]

Can anyone please tell me what steps they took after updating res_xmpp.c? I changed to v23 but still no GV.

 

[billsimon]

Can anyone please tell me what steps they took after updating res_xmpp.c? I changed to v23 but still no GV.

After changing source code you would rebuild it by going to the root of the asterisk source and running "make" then "make install".

 

[24bit96khz]

If you do that, you really ought to add the extra two lines from later releases that block SSLv2/v3 viz:
ssl_opts = SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3;
SSL_CTX_set_options(client->ssl_context, ssl_opts);
(and declare ssl_opts as a long back at the beginning of the function).

Wow it actually worked! However, I did not get the quoted part of your instructions. I'm a real Linux lightweight. I pasted in those first two lines into the res_xmpp.c file and was unable to compile it with make until I removed them. Can you or someone explain like I'm five and just tell me the exact two lines to put in and where?

It may not be needed as it's working right now but if you advise it I'll do it.

 

[billsimon]

Wow it actually worked! However, I did not get the quoted part of your instructions. I'm a real Linux lightweight. I pasted in those first two lines into the res_xmpp.c file and was unable to compile it with make until I removed them. Can you or someone explain like I'm five and just tell me the exact two lines to put in and where?

It may not be needed as it's working right now but if you advise it I'll do it.

You probably missed this part:

(and declare ssl_opts as a long back at the beginning of the function).

-----

I'm wondering why people are doing this and not just updating to a current version that has the fix.

 

[24bit96khz]

You probably missed this part:



-----

I'm wondering why people are doing this and not just updating to a current version that has the fix.

Because I typed update-programs and update-fixes and it never works. All the mirrors it tries connecting to fail and it never actually downloads or updates anything. Well, I fixed it and made a video for others like me who don't know what they're doing.

 

[ws2000]

After changing source code you would rebuild it by going to the root of the asterisk source and running "make" then "make install".

Thank you!!! Its working now.

 

[ws2000]

Because I typed update-programs and update-fixes and it never works. All the mirrors it tries connecting to fail and it never actually downloads or updates anything. Well, I fixed it and made a video for others like me who don't know what they're doing.

Thank you for making a video. This would have saved me hours. The little details kill me.

 

[docgreen]

Because I typed update-programs and update-fixes and it never works. All the mirrors it tries connecting to fail and it never actually downloads or updates anything. Well, I fixed it and made a video for others like me who don't know what they're doing.

You sir, are my hero!

 

[VaHam]

Thanks, @tenortim. On really old systems, you'll need to make the SSLv3_method() to SSLv23_method() change in res/res_jabber.c instead of res_xmpp.c.

I changed only the one line containing SLv3_method() to SSLv23_method() as you suggested on my very old Asterisk v1.18.11 box by executing the following commands. My Google voice is connecting again. Thank you for saving me hours and hours.

cd /usr/src/asterisk/res
sed -i 's/SSLv3_method()/SSLv23_method()/g' res_jabber.c
amportal stop
cd /usr/src/asterisk
make
make install
amportal start

 

[MisterQ]

Best $4.99 you'll ever spend. Seriously!

Just trying to understand the benefit of a gateway connection to GV rather than the previous direct connection approach...

 

[wardmundy]

Just trying to understand the benefit of a gateway connection to GV rather than the previous direct connection approach...

It's pure SIP. It works on any platform supporting SIP. It insulates you from the majority of these outages and lets @billsimon worry about it.

 

[MisterQ]

It's pure SIP. It works on any platform supporting SIP. It insulates you from the majority of these outages and lets @billsimon worry about it.

Done, but now I am continuing with the GV Setup - I am the point where it is going to upgrade to a full voice account, but needs a US Phone Number to verify against. It used to be that one could quickly hack that with IPKALL, but they have gone out of business - is there another approach.

 

[billsimon]

Done, but now I am continuing with the GV Setup - I am the point where it is going to upgrade to a full voice account, but needs a US Phone Number to verify against. It used to be that one could quickly hack that with IPKALL, but they have gone out of business - is there another approach.

US POTS or cellular line only. Validation or pick-a-number will fail with VoIP lines. Google has gotten strict about issuing new Google Voice numbers.

 

[wardmundy]

@MisterQ: Just use one of your existing GV accounts. I know you have some.

 

[wardmundy]

Another option is Pinger/TextFree to get a U.S. number. Forum thread here.

 

[MisterQ]

Oh, damn this is fun, and convoluted - yup, I have existing GV number, but I wanted to create a new one, not tied to my mainstream Google Account.

Firstly, hint for young players - GV will Geolocate you, so you need to be working through a US web proxy before the GV Screens will even come up.

Secondly, using existing GV number as the "base number" - nope, it doesn't like that...

Set up a Pinger number (in Alabama), but it seems in order to hook it in, I need either a Jailbroken ANdroid - nope, we are a 100% Apple house, or running Bluestack - all of the documentation talks about bluestack on Windows, but a quick glance says it will run on OSX, so I am off to explore that, so as to tick the box for the GV Account, and then turn on the Simonics GW.

Failing that, set up a Virtualbox VM of windows on my mac, then load blustack, then....

I am reminded of a computer game of the 80's - You are in a maze of twisty little passages, all alike.

 

[gavimobile]

FYI - once again, I didn't touch anything and everything is back to normal again. hope they don't continue messing with this.