Mystery reboots Obi 110 build 2774
ProfTech:
I tried several ATA's before I ended up with the Obi 110. It is the only adapter at its price point that supports the PSTN. I tried an SPA 3102 which hasn't been updated since 2009 and it was junk as far as the PSTN was concerned, and apparently no longer supported. After several firmware revs I am pretty happy with the 110 overall. I hate to say it, but maybe the Cisco SPA122 might be a better choice than the 202. It is new but several s/w revs have gone through so maybe they are getting the bugs worked out as well. Except for the 202 having Google Voice capability I think they are pretty close to apples to apples.
CoalMinerRetired:
One more update in this never ending series of frustrations. I also want to post this before moving on to a new firmware in case the issues just disappear … or god forbid get worse.
In summary, it’s still not fixed, but evidence is pointing to the two CellCentric SPs interfere with each other, in some as yet unexplained manner.
The details: I formally reported the issue to Obi Customer Support. Getting a direct answer, or even a response after multiple mails has been a challenge, which of course adds to the frustration. Support replied with the usual: try **0 Option 27 (100 Mp full duplex), then connect the Obi directly to my Cable Modem (no can do for days at a time in my case) and then ‘try a new router’. My response to this last was “I just spent $150 on a new SOHO router four weeks ago, do I really need to try a third one?”
After some back and forth messages, many of which went unanswered and then some more prodding, they replied to change the registration periods for the two CC SPs to 600 and 615 seconds. I tried that, but it was in vain, I believe, because on the System Status page for the two CC SPs it would show expires in XX seconds, where XX was never more than 60. They did not acknowledge this in an email response (to the original ‘try 600 and 615’ reply), but since I was at wits end I deduced to try 59 seconds and 60 seconds, with the intent to change to 53 and 59 seconds (the greatest prime numbers less than 60) the next time I purposely reboot.
The change to 59 and 60 seconds are correctly reflected in the CC SPs on the main status page, and the conclusion here is there’s a 60 second maximum registration period (for CC or all SIP providers? Nothing I could fin din the admin manual). Even more encouraging, the change to 59 seconds and 60 seems to have ‘reduced’ the problem, but not completely eliminate it in my uptime test so far.
After six days of uptime, I had one episode with no dial tone and unresponsive via the 192.168.xxx.yyy Obi WebPage. After about a minute or two got dial tone back, and the 192.168.xxx.yyy started to respond. Unlike past episodes, this one did not result in a spontaneous mystery reboot, and uptime is now at 8 days, which is a new record. So those two points are progress (although small), in my experience.
In addition to the change to 53 and 59 seconds, (after I see how far I can go with the uptime using 59 and 60), I think I’ll add two backup DNS servers, Google Public DNS, which I think will be used in priority order ahead of my ISP’s (Comcast) dynamically assigned DNS servers, based on the way I read the Admin Manual.
ProfTech:
FYI, the maximum re-register time for CallCentric is 120 seconds. The thing is, the Obi 110 re-registers when 1/2 of whatever time you specify has expired. So the 110 will register every 60 seconds if you have it set to 120. You can go as big as you want but anything 120 or larger will cause the unit to register every 60 seconds. I looked at this a bunch a year or so ago and ended up setting mine for 120 every time. Not sure if the 202 works the same or not. The Mediatrix adapter I looked at allowed you specify how far in advance of expiration you wanted to re-register but I ended up sending it back because it kept dropping registration and wouldn't stay registered at all.
CoalMinerRetired:
Now that you mention it, I think you (or someone else) posted this 1/2 the max time thing somewhere on here before.
My update here is the reboots no longer happen (and I'm not exactly sure why, several recent firmware releases play into this) but I still get the predecessor to the reboot, dead air and an unresponsive unit that will not 'hangup' or otherwise end a call for several minutes. Looking back at the timestamps on this thread, I've been fighting this since February, and at it's height it was incredibly frustrating.
This past weekend I setup a new approach. I previously had one Obi202 with
SP1 = GV1, SP2 = CC1
SP3 = Gv2, SP4 = CC2,
The two CC are used for the CNAM and E911.
I have a spare Obi202 available for a few weeks (from a friends and family installation that is postponed for a while), based on some things Obi support suggested to try (see above posts) so I decided to try this arrangement with only one CC SIP on one Obi:
Obi202 #1: SP1 = GV1, SP2 = CC1
Obi202 #2: SP1 = GV2, SP2 = CC2.
SP3 and SP4 are not configured on either unit.
I had high hopes for this, but alas today I got another episode of dear air while on an important conference call. The call was outbound on GV2, so CC was not in use.
I hope this was a one-off fluke, because it did not behave like the past episodes did, this one just became dead air, with no reboot, and unlike in the past I could hangup the call, however for several minutes neither GV1 or GV2 would accept an outbound call, just more dead air when anything was dialed. In hindsight I should have tried 933, which is the only outbound call I can make on a CC SIP, all other calls are incoming only on CC.
I am aiming for 10 days uninterrupted uptime as something of a huge milestone, but today's episode shattered that idea. This week is heavy on conf. calls so we'll see how the remaining seven or eight days go.
ProfTech:
This is kind of an old thread but I thought I would post an update. After reading some posts about Callcentric issues I decided to try disabling ProxyServerRedundancy and SecondaryRegistration for Callcentric, while making sure X_DnsSrvAutoPrefix was checked. I'm happy to say the crashes have stopped. At this point I have been unable to detect any other differences between 2774 and 2776. I'm assuming the differences are minor since Obihai has never posted an update for 2776.
Navigation
[0] Message Index
[#] Next page
[*] Previous page