Random Reboot OBI202 3.0.1 (Build: 4269)
giqcass:
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.
CoalMinerRetired:
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.
fizikz:
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.
sdb-:
I had another spontaneous reboot last night at about 00:55. This time apparently unrelated to g'talk:
Code:
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...
CoalMinerRetired:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page