yozh
Member
- Joined
- Nov 9, 2010
- Messages
- 71
- Reaction score
- 3
Upgrade script has bunch of errors, have to go thru them, but otherways I think its good ... Reverting snapshot now to test again. Im wondering what changed on google side and broke this.
Upgrade script has bunch of errors, have to go thru them, but otherways I think its good ... Reverting snapshot now to test again. Im wondering what changed on google side and broke this.
I don't think we have a good understanding of the root cause. DSLReports VoIP Tech forum has reports from Obihai owners getting locked out of Google Voice yesterday and Asterisk users as well. Some Asterisk users updated their systems and the problem went away. Others claim to have done nothing and the problem went away.
My own perspective on it is that it is important to have the most up-to-date TLS, because Google is one of the leaders in deprecating old SSL/TLS suites that are less secure, as well as OAUTH2, because Google has been pushing for this for several years. I will not be surprised when Google forces the issue requiring the most current TLS schemes as well as OAUTH2 and abandoning user/pass auth.
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
Would you mind sharing the edits you made to make this upgrade work? Bracing myself to upgrade from 11.12 to 11.22.
Intresting. Let me go back to my original box again and see if it just works without an upgrade.
WOW, so here is the thing
This is amazing !!!! Went back to my original box, and guess what, its working !!!! So whatever it is google was doing it's either done, or there is another wave coming....
Now I`m not sure if 11.4 upgrade to 11.22 fixed it or was it fixed on google side before that... (meaning when 11.4 was not working and 11.22 was or were they both working)
Welcome to the circus, @silox...I registered just to post in this thread and add to the conversation.
Thanks for the welcome! I remember with 1.8 I had problems connecting to gv and after i upgrade to 10 things We're working again. Maybe that too was just a matter of time. If I remembered correctly I had an easier time configuring motif than jabberWelcome to the circus, @silox...
The lesson I take from everything that happened (and that has similarly happened on a couple of prior occasions) is to do nothing for a few days to see if things automagically correct themselves. If things go back to normal, fantastic! If not, well, then you can follow the path blazed by the early adopters who groped for solutions in the dark, oftentimes heading down the wrong path.
2 years ago, in May of 2014, the sky was falling because Google was dropping the hammer and everything was supposed to break. I stayed pat with my Obi100 and my Motif PBX trunks and the world did not come to an end. The same scenario has replayed several times since then. This time around many folks expended a lot of effort upgrading Asterisk, SSL, building completely new PBXes, upgrading Obi devices to firmware that locks-out manual GV set-up and that only permits GV use if connected to Obihai's ObiTalk portal, etc. 36 hours later the XMPP error corrected itself.
While things were SNAFU my incoming GV worked fine. I don't terminate incoming GV to Google Chat-connected devices. Such calls instead simul-forward to my cell (Free via RingPlus!) and a free CallCentric NY DID registered to an old PAP2T plugged (along with my router and cable modem) into a hefty UPS. To make outgoing calls I used my free R+ cell (which sends GV number) and, for a brief period of time, I amused myself by using the old-school "call-back" method from the GV portal. Or, I used FireRTC (which spoofs my GV number). A bit later I flipped service to my Dockstar PBX running the PogoPlug image with Motif GV trunks. When that also broke I went back to cell and call-back. Multiple paid VoIP providers that charge virtually nothing (much less than a penny per minute -- can you say CircleNet?) were waiting in the wings, but I never had to go there.
There are many smart people around here. I am not one of them. So I take a vacation until the smart people figure it all out. Doing so saves me a great deal of grief as well as the impact of possibly irreversible actions.
pbx asterisk[28793]: WARNING[28813]: res_xmpp.c:3640 in xmpp_client_thread: JABBER: socket read error
That seems to be normal and not a reason for concern. Asterisk reconnects if the connection is broken. As long as it is reconnecting successfully you don't have to do anything.So after going back to the original box, I started getting a lot of errors like below,
It would still stay connected, but errors would popup. I setup splunk to kill asterisks when I get this errors, so I had to go back to 11.22 clone. Which seems to be stable, but once in awhile the error above pops up. The accounts actually stay connected (have a script that checks connections prior to killing asterisks process), so I dont understand where the errors coming from ?Code:pbx asterisk[28793]: WARNING[28813]: res_xmpp.c:3640 in xmpp_client_thread: JABBER: socket read error
That seems to be normal and not a reason for concern. Asterisk reconnects if the connection is broken. As long as it is reconnecting successfully you don't have to do anything.
As for why the connection breaks, there are a lot of possibilities, but remember that this is a TCP connection so you will see every network error, as opposed to UDP (probably most or all of your SIP traffic) where you are only notified of problems after a lot of retries.
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.