GV on Obi 1062 unreliable
A_Friend:
Quote from: billsimon on August 19, 2018, 12:11:52 pm
Still, I'd like to know why I'm getting it, and others apparently are not.
I think most of us would. Seriously, call your ISP and ask them if they're doing daily construction work on the system that might affect you. Time Warner was driving me nuts for a couple weeks earlier this year, shutting the 'net down for an hour or so a day in the middle of the day, and then they were done and everything is hunky-dory again.
And I did need to reboot the Obi's to get GV back after the outages. Both voip.ms and Callcentric came back on their own. That was under XMPP, not SIP, so I don't know if that's still related. We do know that the GV login/registration is more complicated than ordinary SIP because of the tokens. So, I'm guessing that has something to do with it.
billsimon:
After I posted this I decided I would wait until the problem happened again, and then make the DNS changes as an experiment. But for the last week, the problem has not resurfaced. So I am now in a "wait and see" posture. It may have been a short-term problem.
I noticed some other bugs with the 1062 last week that were cleared with a reboot:
* Call progress indicator got stuck on "Trying" even after the call was connected, and the timer did not increment
* Volume up/down button did not work correctly in call
After the reboot, again, the problem hasn't resurfaced. The firmware is the same.
I have worked alongside hardware and software QA teams in the past. These kinds of bugs are the worst because they are hard to reproduce and seem to appear without provocation or reason.
billsimon:
Yesterday and today the 1062 has unregistered itself (or failed to re-register, either way) from the configured SIP accounts as well as from the Obitalk dashboard, which reads "device is offline."
Two other SIP devices sitting right next to the 1062, with the same power source, connected to the same Asterisk SIP server and with long uptimes, are working fine.
I do not know what to make of this, but it is flaky.
SteveInWA:
I think you bought the phone less than a year ago, right? If so, I'd open a ticket with Polycom (don't laugh) and ask for a warranty replacement.
However, you can first check this: I ran into the symptom you describe in the past. The cause was the power supply. They may look the same as the ones supplied with the OBi ATAs or other gizmos, but they have a higher current rating. I was lazy and had plugged the phone into a power supply from an ATA, that was buried under my desk. The phone would crash as soon as it rang, and sometimes would not be able to reboot. The supplies for the ATAs are rated at one amp. The supplies rated for the 1000 series are two amps.
Navigation
[0] Message Index
[*] Previous page