Connect Failed: No Response (as of today 3/9) Across MULTIPLE OBI 508's
loumarjr:
Quote from: transam98 on March 16, 2019, 07:51:56 pm
nope DEAD here the fix didnt actually FIX anyones ;(
Everyone gets the same thing.... CONNECTED and then you DIAL and DEAD AIR...
As for localphone I dont know what that is (lol) never used it...
So maybe firmware only fixed "localphone" and also now makes GV say connected but thats it ??? ??? ???
No, it fixed nothing. I forgot with the obi508, you can prefix a number with **1 to call the number from SP1, and you can do the same with SP2,3, and 4. But you cant **8 and have the service dial out on SP8. You have to dial with speed dial to use SP8 unless you have the config to default to the port you are using. localphone is just another phone provider.
Hopefully GV will be fixed soon.
Transam98, if you want to PM me, I can show you a temporary work around for GV calling on obi, it is not perfect, but works well.
transam98:
LoumarJr: I sent ya a PM !
Ive done more and more reading.,....
What I believe has happened is UNAUTHORIZED "PBX" people.... (I dont know what the PBX Software is) but sounds like a software comparable version of a SIP setup like Obi... Well I believe what was done is someone ripped off like a certificate or credentials or something similar to OBI using some part of OBI Stuff again... like a certificate...
and were USING it to access GV VIA SIP (or something close) and GV only wants AUTHORIZED people accessing thier system using only AUTHORIZED equipment (aka obi)... so they blocked however or whatever was done... fallout is it CUT OFF all OBI... and here we are waiting 2 weeks later (well a few days into week 2).
so in reason ... the reason it DOESN'T WORK is someone tried to beat the system I guess... downside is it screwed us.... But rather GV talking to their AUTH provider(obi) and OBI having a FIX READY... they Killed off the MASSES and take action and FIX Later I guess was the approach.....
Since this is the way they did it I can only guess is it must have been massive what "pbx" or whatever its called did....
S.R.:
Quote from: transam98 on March 18, 2019, 10:11:13 pm
Ive done more and more reading.,....
What I believe has happened is UNAUTHORIZED "PBX" people.... (I dont know what the PBX Software is) but sounds like a software comparable version of a SIP setup like Obi... Well I believe what was done is someone ripped off like a certificate or credentials or something similar to OBI using some part of OBI Stuff again... like a certificate...
and were USING it to access GV VIA SIP (or something close) and GV only wants AUTHORIZED people accessing thier system using only AUTHORIZED equipment (aka obi)... so they blocked however or whatever was done... fallout is it CUT OFF all OBI... and here we are waiting 2 weeks later (well a few days into week 2).
so in reason ... the reason it DOESN'T WORK is someone tried to beat the system I guess... downside is it screwed us.... But rather GV talking to their AUTH provider(obi) and OBI having a FIX READY... they Killed off the MASSES and take action and FIX Later I guess was the approach.....
Since this is the way they did it I can only guess is it must have been massive what "pbx" or whatever its called did....
Where did you read this? I was using PBXes GVSIP till it was shut down recently.
https://www2.pbxes.com
transam98:
I had googled so I don't recall the exact page it was some forum message boards and that is why yours probably went off as something in your software that "made" it work was supposedly STOLEN from OBI's software as they are the ONLY one authorized to be using GV and HARDWARE together as a SIP Provider (unless you use google hangouts)... I guess the PBXES software was ahack to make it work on GV from what I read a few days ago and against the TOS, that's why GV intervened, its only allowed to work on OBI hardware as they are supported OFFICIALLY.
Mango:
Quote from: transam98 on March 18, 2019, 10:11:13 pm
What I believe has happened is UNAUTHORIZED "PBX" people....
The real reason is most likely nowhere near that fantastic.
The OBi5 firmware does not support SNI, an extension of TLS. (Google it if you're unfamiliar - the Wikipedia article is pretty informative.) The firmware is simply old and has not been upgraded like the 20x firmware has to keep up with Google's changes.
A version of the hacked firmware has been made by a volunteer that corrects this. Unfortunately it's unhelpful for you because we don't know how to flash it using new versions of the official firmware. It only works if you are upgrading from an older version of the hacked firmware.
Navigation
[0] Message Index
[#] Next page
[*] Previous page