Obi110 frequently rebooting tonight...?
Ostracus:
I've been wondering since the news broke if a SIP proxy would help isolate the ATA from the problem?*
*Some other advantages as well.
Hortoristic:
PEDRO - I use voip.ms for e911 - $1.50 a month. I've even had opportunity to call 911 and it worked well.
fathom:
Quote from: pedro on October 23, 2012, 04:49:03 pm
Mines doing the same thing. I disabled Callcentric from my device and it stopped rebooting itself. I have submitted another worthless ticket to CC about it. I'm sure they'll blame it on the hackers.
Anybody know of another (stable) e911 service?
Ditto, doing that just today with my obi202 .
I was using callcentric free calling out just for a fax line.
Deleted the callcentric sp3 and problem solved.
I was going crazy up to this point!
ProfTech:
Wednesday night 10/25 - My 110 did indeed begin rebooting spontaneously, randomly, and frequently tonight. I had noticed that registration times began looking odd when this all started with CC 3 weeks ago. Since we have seen all of the flap about DNS SRV and having experienced some issues along that line myself, I decided to experiment with some settings. I set ProxyServer, RegistrarServer, OutboundProxy, and UserAgentDomain ALL back to "callcentric.com". Next I turned Off [UNchecked] ProxyServerRedundancy AND X_DnsSrvAutoPrefix. I also reset my DNS Server entries in the Obi to my standard ISP DNS servers as I had determined a day or two ago that they should be working fine. After a reboot, it was quite enlightening. My re-register times now look normal. They begin at about 85 seconds after a reboot and increment by 1 second upon each re-register. As of last count it was at 131 seconds. Note that the Obi [110] will always re-register when 1/2 of the time has expired. I currently have the "RegistrationPeriod" set at 250 which will cause the Obi to reboot every 125 seconds if the CC servers will allow it to increment that high. Have to wait and see.
SECONDLY: The reboots immediately stopped. Will have to wait a day or two to see if it remains stable. Maybe this info can help someone else.
*EDITED* With the settings above [including X_DnsSrvAutoPrefix NOT checked] the unit only registered on port 5060 which didn't seem quite right so I left everything shown as above but Checked X_DnsSrvAutoPrefix. Now the unit appears to be following Callcentrics suggestions regarding both which server and which port to use. It seems like ProxyServerRedundancy and registering to a second server may have been driving the OBI crazy. Have to wait and see.
Navigation
[0] Message Index
[*] Previous page