OBI200 operation unreliable since May 2018
SteveInWA:
Quote from: NoObiKnObi on September 10, 2018, 08:17:46 pm
Steve, I just sent Polycomm an email to look at this thread because others besides me are having the same problem. I suggested that rather than push service contracts as a solution they might look into a firmware update. My workaround above, namely power cycle the OBI after the router finishes its boot procedure seems to be restoring stable operation for me. Your suggestion is good, and I'll check that as well when I get a chance. Thanks.
That's nice, but why not perform my test already? It's been weeks. At least, you'd be able to point the finger at your particular LAN configuration vs. whatever other site you use to test it.
NoObiKnObi:
I understand Steve, but it seems that others with completely different environments are having the identical problem that I'm having. I've already spent hours getting to the solution that I found which seems to be working for me, and I think others. I could go to greater testing efforts for further characterization for PolyCom but my time for this is limited and I think there are enough additional data points here for PolyCom to work with such that the ball is appropriately in their court. Let's see how they respond....
hamfastgamgee:
I actually seem to be experiencing an issue where one of the following two things will happen:
1) The green light dies, and I have to power cycle the Obi after leaving it unplugged for some time.
2) The Obi will randomly revert back to 5896 from 5898EX. Once it reboots, it'll get 5898EX again and fix itself.
To say it's annoying would be a massive understatement. :)
howardjeffrey:
I have been using Obihai for ~7 yrs. now, first the 110, then the 200 for the last couple years, with Google Voice.
I have also set up these devices for numerous folks, also for use exclusively w/GV.
I have had virtually no problems that were not user error, firmware update, or product failure related.
That has dramatically changed since sometime in the spring: the most persistent problem now is that incoming calls are lost after the 3rd or 4th ring.
This happens with two other people whose Obihai 200 I setup.
I have checked all possible settings on the Obitalk dashboard & w/GV: no problems there.
The clearest indication that the problem is w/Obihai firmware: if I dial the other Obihai 200 devices directly (using **9) the same problem presents with 4 to 5 rings, and I then get my own voicemail (not the voicemail of the person I am calling).
Current firmware is 3.2.2.5898
SteveInWA:
Quote from: howardjeffrey on September 28, 2018, 05:52:18 pm
I have been using Obihai for ~7 yrs. now, first the 110, then the 200 for the last couple years, with Google Voice.
I have also set up these devices for numerous folks, also for use exclusively w/GV.
I have had virtually no problems that were not user error, firmware update, or product failure related.
That has dramatically changed since sometime in the spring: the most persistent problem now is that incoming calls are lost after the 3rd or 4th ring.
This happens with two other people whose Obihai 200 I setup.
I have checked all possible settings on the Obitalk dashboard & w/GV: no problems there.
The clearest indication that the problem is w/Obihai firmware: if I dial the other Obihai 200 devices directly (using **9) the same problem presents with 4 to 5 rings, and I then get my own voicemail (not the voicemail of the person I am calling).
Current firmware is 3.2.2.5898
Nobody, as far as I can recall, has ever reported that problem. It's not firmware-related. If you dial **9 to call another OBi, you can't possibly get to voicemail; there is no voicemail for the OBiTALK service.
You have a user error in setup.
Navigation
[0] Message Index
[#] Next page
[*] Previous page