Random Reboot OBI202 3.0.1 (Build: 4269)
My Obi is still having issues.
I have two Obi 202s, installed build 4269 11 days ago and neither have rebooted since. Let's see if we make it to 15 days.
It's clearly time for me to set up syslog. I had not had issues with the older firmware.
Quote from: giqcass on December 28, 2013, 10:32:37 PM
Random Reboot OBI202 3.0.1 (Build: 4269)
My Obi is still having issues.
Build 4269 seems to have fixed the reboots I was getting after 10 days, but those did not seem completely random. Maybe it also depends on the specific services on the OBi that are being used.
Meanwhile I'm still running 4142 and I think I'll wait while for a bit longer before installing 4269. Let you all discover the issues. 8)
I did have a surprise reboot early A.M. last Sunday (4 days, 6hrs ago) but other than that it has been good.
I've reached 15 -1/2 days uptime. But I did have a random disconnect on a call today, for that alone I'm not totally convinced all past issues are solved.
Quote from: CoalMinerRetired on January 02, 2014, 10:23:13 AM
I've reached 15 -1/2 days uptime. But I did have a random disconnect on a call today, for that alone I'm not totally convinced all past issues are solved.
Do you have any of the adapters plugged in to your Obi? I have been considering the possibility the additions might be part of the problem. I had a small thumb drive and BT adapter plugged in via a hub last time I had a reboot. I'm at just under 5 days uptime right now with only the bt adapter connected.
No adapters. For each of the two Obi202s, only SP1 and SP2 are in use, GV on SP1 and CC on SP2, per the popular CC with CNAM arrangement on here.
Interesting tidbit, one of the units is HardwareVersion 1.2 and the second is HardwareVersion 1.4.
I would encourage syslogging even if you get too much detail. When I did it to troubleshoot issues in the past, it can point you to various commonalities, that may (or may not) occur before each reboot or dropped call.
No adapters on my '202.
And speaking of syslog... I have GV as SP1, and it appears my spurious reboot sunday morning was related or coincidental with checking GV voice mail:
Dec 29 02:36:15 obi202.internal GTALKVM:Checking VM....
Dec 29 02:36:15 obi202.internal GTALKVM:state changed from 0 to 1
Dec 29 02:36:19 obi202.internal TCP:Connect OK(lhttpc)39
Dec 29 02:36:19 obi202.internal Trying to connect ssl
Dec 29 02:37:00 obi202.internal IP Address= 172.31.0.8
Dec 29 02:37:00 obi202.internal Gateway = 172.31.0.1
Dec 29 02:37:00 obi202.internal Netmask = 255.255.255.0
Dec 29 02:37:00 obi202.internal VBAT Up = 59.111 v
Dec 29 02:37:00 obi202.internal VBAT Up = 58.482 v
The reboot happened between 02:36:19 (last normal line) and 02:37:00 (first line of the init).
Anybody else see anything similar around their reboots?
Have had 2 different obi202's, first one would reboot every few days then had a power supply failure. Since power supply failures are common with obi, I decided to use a cisco modem adapter with the second obi202 and have never had a problem since.
Using SoftwareVersion 3.0.1 (Build: 3932) This version has been rock solid
Quote from: jjtricket on January 03, 2014, 08:49:07 AM
Have had 2 different obi202's, first one would reboot every few days then had a power supply failure. Since power supply failures are common with obi, I decided to use a cisco modem adapter with the second obi202 and have never had a problem since.
I thought the adapters might be pulling too much power and that was one of the reasons I asked if others were using them.
Quote from: jjtricket on January 03, 2014, 08:49:07 AM
Using SoftwareVersion 3.0.1 (Build: 3932) This version has been rock solid
I had been thinking of purchasing an Obiline adapter so like an idiot I upgraded to a firmware that supported Obiline. I wanted to see the new options on the control panel but it seems there are none unless they appear after the device is plugged in. Now I am considering forcing my Obi to downgrade if this doesn't improve. I have archived copies of many firmware releases including the one you are running. Obi doesn't allow a downgrade after OBi202-3-0-1-4142.fw but I think I can kludge it one way or another.
EDIT: Goodbye 3.0.1 (Build: 4269)
Hello 3.0.1 (Build: 4142) it was simpler then I thought.
Quote from: giqcass on January 04, 2014, 12:41:45 AM
EDIT: Goodbye 3.0.1 (Build: 4269)
Hello 3.0.1 (Build: 4142) it was simpler then I thought.
I am still seeing random disconnents of in-process calls. Well, maybe not so random, it happens after app. 15 minutes on incoming (i.e., incoming on the CC forwarding number) calls. So I'm not so sure how random.
Reloading an older firmware seems quicker and easier than doing any syslogging myself or contacting OBI support with the issue, ... not to knock them, they do come through, but a firmware re-load seems the least labor intensive all things considered.
I'll post back here if I try this approach.
I'm now at almost 22 days uptime with build 4269 on my Obi202, hardware version 1.4, using the original Obi power adapter. I have not noticed any call drops/disconnections. I'm not using GV though, or any Obi adapters or USB drives on the USB ports.
I had another spontaneous reboot last night at about 00:55. This time apparently unrelated to g'talk:
Jan 9 00:33:57 obi202.internal GTALKVM:VM:0
Jan 9 00:36:21 obi202.internal SNTP->10.0.0.9
Jan 9 00:55:22 obi202.internal si3226x : Channel 0 : Chip Rev 3
Jan 9 00:55:22 obi202.internal si3226x : Channel 1 : Chip Type 28
Jan 9 00:55:22 obi202.internal si3226x : Channel 1 : Chip Rev 3
Jan 9 00:55:23 obi202.internal ==== Networking is ready ====
I'm on 4142 and getting about ready to try 4269...
I'm also at 22 days uptime on two Obi202s. And as an aside, I have an Obi110 at 77 days uptime.
Have been paying attention to the disconnects. My observations are:
-They occur in app. every other, (i.e., 1 in 2) incoming calls.
-When calling the CC DID number directly, no disconnects.
-Outbound calls via GV I have not observed any disconnects. Although I'm suspicious on this point.
Preliminary conclusion: Disconnects have something to do with incoming calls from GV forwarded through the CC DID number. Or something to do with the Obi device it itself. Or both.
The disconnects have gone beyond acceptable in that I have conf. calls for work a few hours each day. And so I am seeing disconnects a few times a day.
Update. I'm now at 71 days of uptime on two different Obi202s.
That seems like an all time record, I never remember older builds being this stable or getting this long an uptime.
A few conclusions in this:
-The past random reboots and stability problems in hindsight seem totally (i.e., 100%) related to the build. We always thought that was the case, I think this long run of uptime proves it.
-The random disconnects and dropped calls are no longer. Obvious conclusion is these are also totally related to the firmware.
-It's ironic this build seems the most stable and robust (in the time I've been involved) yet the end of the line for GV on an Obi is nearing. They just got it working right near the very end.
13 days ago my Obi202 rebooted for reason 4 Reboot after Parameter Value Change or Firmware has changed and invoked via device web page.
I haven't changed anything so not sure what might have happened.
I've been on Build 4269 for a while with no problems.
I just took a chance and upgraded to 4303. It went smooth and I make a test call out just fine. Too soon to tell if I'll have any new problems.
Any idea of what "enhancements" are on build 4303? I archived a copy of it. I like to save a copy of each build.
That's incredibly odd timing, the very same day I post about the stability one f/w version a new version comes out.
giqcass, the updates in this thread (http://giqcass) usually list notable new features. Since it only says "enhancements" I'd conclude nothing very bold or new is being added.
LOL that is the post I stole the word "enhancements" from when I phrased the question. They didn't announce Bluetooth in the release notes and as a veteran of this forum you know how well they document things. Sometimes people see hints of thing to come. I'm kind of expecting a 3.1.0 or 3.0.2 firmware coming up around April.
I've not read anything more on what the enhancements are.
So since I'm having a nice run of uptime (on the 4269 build), I'm going to see if I can get to 90 days on both units before jumping to the latest firmware.
Well it looks like they left something important out of the release logs for build 4303. It would have broke my setup if I had upgraded.
Quote from: OBiSupport on March 01, 2014, 08:49:35 PM
The latest firmware has a new option to help fight against a problem commonly known as "ghost calls", where a hacker may be scanning for SIP devices. The new option will enforce that the SIP INVITE received by the OBi must have the request userid matching the SIP account ID as configured on the device. Older firmware does not enforce this behavior previously, but the new firmware does. Most service providers should compliant to this behavior, so that it will be a lot harder for a hacker to scan for SIP devices.
To get the old behavior, you can follow these simple steps:
1. Open your OBi device web page (from web browser, enter IP address of the device. You can dial ***1 to listen to the IP address of your OBi
2. Navigate to the SPx Service Page (x=1,2,3,4), and uncheck this option: X_ForeceRequestUserID
3. Submit the change (press the submit button on the page), and reboot the device (press the reboot button on the page).
Thank you – Obihai Support