Mystery reboots Obi 110 build 2774
ProfTech:
I sent a ticket to Obi and they loaded 2776 into my 110. I have a 100 that I manage remotely via the portal and I noticed that the default is Auto Firmware update Off. I turned it On and of course the unit reboots whenever you make a change via the portal. I will check later and see if it updated.
*Edited* The unit did not update when it rebooted. But then I realized that the URL field appears to be blank by default. I think someone else reported that Auto Firmware update does not work on the 100/110. I think they said if set to "Periodically" it causes the unit to reboot every time it runs even though it never updates anything.
CoalMinerRetired:
I have to vent on the 3.0.1 (Build: 3741) on my Obi202.
It's exhibiting an increasingly annoying assortment of bugs that are (mostly) random and not repeatable:
- The time sync takes an hour or two to update after a reboot. This one is not random it is repeatable. Thus I have multiple calls in history starting at 01/01/2010. I even have a few of these "01/01/2010 19:08:05" seeming to indicate it is taking 7 hours after a reboot to get the correct time. Using the same time server in my router works without issue, as it had been on earlier releases on the Obi.
- Out of nowhere today I got an SMS notification via Caller ID at 10:46 AM. Problem is I got that same SMS notification yesterday when the txt was first sent, and the txt message thread is archived in GV, and marked read. Both SMS messages are in the Obi call history.
- For the last week I sometimes have to forcibly power down for the Obi to get a DHCP address, such as after a config change reboot fails to get an address. No change in my router whatsoever.
- In the past five working days I have had three calls 'go dead' where the device stops responding in the middle of a call and I have to power cycle to reboot. Then hope the preceding acquire DHCP step works. Or else it takes 10 minutes to get back up and dialed back into a conf. call.
- I'm noticing numerous calls that 'drop' right after the dialed number connects to an auto attendant on the other end. I call the same number a lot during working hours, and this never happened before. It's either the auto attendant (no one else dialing in to the AA sees it) or my Obi. Call History shows the Call Ended originates by the phone on the Obi.
- On a positive note, I'm not seeing mystery reboots. On a bad note that is likely due to I have to manually reboot/power cycle once a day, on account of the above, for the last two weeks.
QBZappy:
CoalMinerRetired,
I submit nomination for CMR as beta tester!
CoalMinerRetired:
This is beyond an annoyance and out of hand right now.
- Between 5:00 pm and 7:00 pm this evening I had another mystery reboot. Also had a received call which shows in the Call History with a timestamp of "01/02/2010 23:05:35" which contradicts the working theory that the time after reboot starts as 01/01/2012 12:00:00. As of 7:00 pm the time is synced and correct again. The timestamp for the caller id on my desk phone shows 01/02 11:05 pm.
- Forgot to add a prevalent but not repeatable issue to the above list: Can't hangup a call! When on some calls I can't 'hang up', even if I disconnect the phone cord to the handset. When I do hangup the handset, I can pick up again 10 or 20 seconds later and the call is still connected. The phone port light(s) on unit are flashing clearly indicating the phone is in use. If the call is to a live person, I wait till they hangup, if I connect to some auto attendant, the only way to get out is a forced reboot. On a few rare occasions this has manifested itself by the device simply hanging in the middle of a call, and again the only option is a power cycle reboot.
- Things like the above make you want to scream and give up on the whole thing! Which this week I seriously considered doing. The only thing that stopped me was the ability to make calls directly from Gmail in a browser, and the Gmail doesn't have to have GV.
I'll be curious if anyone else sees any of these, even one, of these issues on an Obi202 with "3.0.1 (Build: 3741)"
Ostracus:
Obviously, have you thought about regressing your firmware?
Navigation
[0] Message Index
[#] Next page
[*] Previous page