3.0.1 (4303) Can No Longer Receive Calls
MikeHObi:
Quote from: gderf on March 02, 2014, 03:31:19 pm
Quote from: MikeHObi on March 02, 2014, 03:29:55 pm
upgraded my 202. Working fine for incoming and outgoing. Is currently using GV for both the incoming and outgoing due to the GV issues with fowarding through providers like Anveo and Callcentric.
There was never a firmware problem with GV for outgoing or incoming.
Just confirmed problem when using either Anveo or Call centric forwarding. Note when I check the webpage to find the X_EnforceRequestUserID thing to disable, it is currently disabled, so that tells me the Obi is not obeying what it is being told regarding that flag.
sigh... obi, it's called quality control. I wonder if they are jacking with this just to make providers scramble like GV has made Obi scramble.
Syslogs show:
Dial GV number, it fowards to CallCentric and the obi does:
SIP DLG reject: 486
RTP:Del Channel
MikeHObi:
This type of problem has me thinking Obi will be Dead to me. Sorry folks, but your inability to follow any sort of even have standards of quality control has me wondering were the future is for the company. Between the lack of response, and the faulty firmware seems to indicate a lack of ready for prime time behavior.
IrwinFamily:
Quote from: Mango on March 02, 2014, 09:09:39 am
They locked the other thread because it was a duplicate of this one. We can still post here.
Give downgrading a try and let us know how it works.
http://www.obihai.com/firmware/OBi202-3-0-1-4269.fw
I see OBI released an updated firmware to resolve this issue. Sadly, it did not. :(
HOWEVER... Downgrading the firmware DID WORK! :D
THANK YOU Mango!!!!!
Mango:
My pleasure; in fact I received the link from iamhere at the DSLR forum. Thanks for testing the updated firmware. I don't have an OBi202 so have just been sitting here watching the fun.
giqcass:
This is why I keep copies of old firmware. I have quite a collection now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page