June 18, 2018, 05:31:47 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi200 Stability?  (Read 946 times)
Time_Lord
Newbie
*
Posts: 8


« on: May 15, 2018, 08:41:03 am »

I've had an Obi200 for a while, I set it up about 16 months ago and didn't really using it until about 3 months or so ago.  Nice move on my part, let the warranty expire before actually using it, regardless, the unit seems to work exactly as advertised.

The one problem I seem to have noticed is with the unit's stability, the device never seems to be up for more than 2 weeks.  I've made no changes to my configuration however the last reboot reason code is a "3" meaning "Reboot after New Profile Invoked".

Software is currently 3.2.2 (Build: 5859EX)

So the question is, does OBitalk randomly refresh the configuration on the unit triggering a reboot or is something else going on?

-TL
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 4630



« Reply #1 on: May 15, 2018, 01:54:07 pm »

Your device was automatically upgraded to the new firmware level necessary to support Google Voice.  That upgrade required a reboot.  This isn't a routine thing; it is a major update to the Google Voice service that necessitates new firmware.

As for "the device never seems to be up for more than 2 weeks", no, that's not normal, but it could be caused by many different things.  For example, power sags on your building's 120V wiring, a failing "wall wart" AC/DC adapter (try another one if you have one with the same voltage and plug style), or a problem with your Internet Service Provider.
Logged

Time_Lord
Newbie
*
Posts: 8


« Reply #2 on: May 16, 2018, 12:23:34 pm »

Your device was automatically upgraded to the new firmware level necessary to support Google Voice.  That upgrade required a reboot.  This isn't a routine thing; it is a major update to the Google Voice service that necessitates new firmware.

Fair enough, I understand why it was done, however the timing was probably not the best as it was restarted in the middle of the afternoon, I think my uptime pointed to a little after 12pm.  Granted I don't make or receive too many calls on the device so it is really a non issue for me.  Hopefully there is some sort of logic that kicks off a reload when the device is idle.


As for "the device never seems to be up for more than 2 weeks", no, that's not normal, but it could be caused by many different things.  For example, power sags on your building's 120V wiring, a failing "wall wart" AC/DC adapter (try another one if you have one with the same voltage and plug style), or a problem with your Internet Service Provider.

I'll have to pay attention to it, it has always been "available" whenever I've either dialed out or received a call (no unaccounted for missed calls).  I know power has been stable, I currently use an 802.3af compliant switch and splitter which takes ethernet in and supplies 12volts and ethernet out and my switch has been up for 6 weeks (since last reboot) and prior to that about a year. 

Maybe I'm simply seeing something that isn't there, I'll have to keep an eye on it.  I am now aware of the restart reason which I wasn't aware of previously so that will shed some light on the maybe non-issue.

-TL
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 4630



« Reply #3 on: May 16, 2018, 01:08:55 pm »

I currently use an 802.3af compliant switch and splitter which takes ethernet in and supplies 12volts and ethernet out and my switch has been up for 6 weeks (since last reboot) and prior to that about a year. 

I'm not clear on how you are using a POE switch with a OBi 200.  The POE standard is 48 volts.  Aside from that, whatever you are doing to drop that voltage (if you are!) may be failing.  If you can plug in an ordinary power "wall wart" 12VDC power adapter and use that instead, it would be worth it for diagnostic purposes.  I had an intermittently failing POE device a couple years ago, and it caused frequent reboots of the OBi until I replaced the POE injector.
Logged

Time_Lord
Newbie
*
Posts: 8


« Reply #4 on: May 19, 2018, 09:39:57 am »


I'm not clear on how you are using a POE switch with a OBi 200.  The POE standard is 48 volts.  Aside from that, whatever you are doing to drop that voltage (if you are!) may be failing.  If you can plug in an ordinary power "wall wart" 12VDC power adapter and use that instead, it would be worth it for diagnostic purposes. 

Trust me on this one, I have an adapter that takes PoE in and splits it to ethernet and power for none PoE devices.  Plus if it was a power related issue the reboot code would be 0 (zero).

Just checked the Obi200 a few minutes ago and again the uptime was reset to "0 Days 1:17:18 (3)"

The reset code of 3 says "3: Reboot after New Profile Invoked"  I made no changes, certainly not within the last hour and 17 minutes, and the Software version is still 3.2.2 (Build: 5859EX), same as it was when I started the thread.

So my question remains what new profile is obi pushing that requires a restart, and why are they pushing profile changes?

-TL
Logged
LTN1
Sr. Member
****
Posts: 490


« Reply #5 on: May 19, 2018, 12:28:25 pm »


I'm not clear on how you are using a POE switch with a OBi 200.  The POE standard is 48 volts.  Aside from that, whatever you are doing to drop that voltage (if you are!) may be failing.  If you can plug in an ordinary power "wall wart" 12VDC power adapter and use that instead, it would be worth it for diagnostic purposes.  

Trust me on this one, I have an adapter that takes PoE in and splits it to ethernet and power for none PoE devices.  Plus if it was a power related issue the reboot code would be 0 (zero).

Just checked the Obi200 a few minutes ago and again the uptime was reset to "0 Days 1:17:18 (3)"

The reset code of 3 says "3: Reboot after New Profile Invoked"  I made no changes, certainly not within the last hour and 17 minutes, and the Software version is still 3.2.2 (Build: 5859EX), same as it was when I started the thread.

So my question remains what new profile is obi pushing that requires a restart, and why are they pushing profile changes?

-TL

Rather than asking people on this forum how to troubleshoot something that could possibly be related to using PoE in an OBi200 device not created to do PoE, why don't you use the original power adapter (and remove the PoE) for the OBi200 for a day or more and see if you get the same issues? If the same issue exists, we can rule out the PoE. If the issue doesn't continue, then it could be the PoE causing a glitch.
Logged
Time_Lord
Newbie
*
Posts: 8


« Reply #6 on: May 19, 2018, 01:10:38 pm »

I've enabled syslog and I'm forwarding it to another system,  I'm accepting all messages and the obi sends debug level messages so maybe I'll get something of value to see what is being sent that is causing a reload "type 3".

-TL
Logged
Time_Lord
Newbie
*
Posts: 8


« Reply #7 on: June 14, 2018, 06:34:14 am »

I though I had an uptime record, the OBI was up for 23 days, I checked this morning at it restarted again, reason "3" configuration change.  "0 Days 7:38:22 (3)"  This puts the reload at about 1:15am this morning, I can assure you I was not making changes to the device.

Because I started syslog (see below) I was able to obtain some information, apparently a configuration check/push was done from obi which then a reload was issued.

What changes is obi pushing to the device?

This at least proves that my power is stable even with my PoE adapter as the reboot was commanded not caused by power.

-TL

at 1:16am -

Jun 14 01:16:47 172.18.19.19  Obi200: PNNCOMM:Receive sync req, set auto config
Jun 14 01:16:47 172.18.19.19  Obi200: We will check OBt config in 10 s
Jun 14 01:16:57 172.18.19.19  Obi200: PROV: Start to download files ...
Jun 14 01:16:57 172.18.19.19  Obi200: TCP:Connect OK(HTTP GET)40
Jun 14 01:16:57 172.18.19.19  Obi200: Trying to connect ssl
Jun 14 01:16:57 172.18.19.19  Obi200: TC:ssl connected
Jun 14 01:16:57 172.18.19.19  Obi200: HTTPC: Server responses: 200
Jun 14 01:16:58 172.18.19.19  Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19  Obi200: PROV: Start to download files ...
Jun 14 01:16:58 172.18.19.19  Obi200: TCP:Connect OK(HTTP GET)40
Jun 14 01:16:58 172.18.19.19  Obi200: Trying to connect ssl
Jun 14 01:16:58 172.18.19.19  Obi200: TC:ssl connected
Jun 14 01:16:58 172.18.19.19  Obi200: HTTPC: Server responses: 200
Jun 14 01:16:58 172.18.19.19  Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19  Obi200: PROV: Update Config with (0, 1)
Jun 14 01:16:58 172.18.19.19  Obi200: PARAM have been changed 2...
Jun 14 01:16:58 172.18.19.19  Obi200: Reboot is scheduled in 1 second(s)
Jun 14 01:16:58 172.18.19.19  Obi200: We will check OBt config in 86400 s
Jun 14 01:16:58 172.18.19.19  Obi200: PARAM Cache Write Back(256 bytes)
Jun 14 01:16:59 172.18.19.19  Obi200: Reboot checking.....
Jun 14 01:16:59 172.18.19.19  Obi200: Final Cleanup before reboot....
Jun 14 01:17:00 172.18.19.19  Obi200: TCP:Broken Connection(spreg) 32 -1
Jun 14 01:17:00 172.18.19.19  Obi200: REG:HandleTcpEvent 3;wc=0
Jun 14 01:17:00 172.18.19.19  Obi200: SP2:Restart TCP Connect:ac121313:5889->4009f2ac:5061
Jun 14 01:17:00 172.18.19.19  Obi200: TLS-EXT Hostname:obihai.telephony.goog
Jun 14 01:17:00 172.18.19.19  Obi200: TCP:Connect OK(spreg)32
Jun 14 01:17:00 172.18.19.19  Obi200: Trying to connect ssl
Jun 14 01:17:00 172.18.19.19  Obi200: TC:ssl connected
Jun 14 01:17:00 172.18.19.19  Obi200: REG:HandleTcpEvent 2;wc=1
Jun 14 01:17:00 172.18.19.19  Obi200: Goodbye! Reboot Now. (reason: 3)
Logged
ProfTech
Sr. Member
****
Posts: 404


« Reply #8 on: June 14, 2018, 07:56:58 am »

To: Time_Lord According to your syslog this certainly appears to be tied to Google Voice and the portal. Google is in the process of changing their entire protocol [that is why they installed new firmware in your Obi] and this is supposed to be complete June 18. I would recommend waiting until after then and see what happens. I don't use Google voice any more precisely due to all of this so can't shed any light but if the issue persists after June 18 you might be able to stop it by removing the Obi from the portal but I don't know if that is possible in Googles new scheme.
Logged
chilirock
Full Member
***
Posts: 82


« Reply #9 on: June 14, 2018, 12:24:52 pm »

Strange. I manage two devices on my account. I just checked and it looks like both rebooted early morning today. The reason code as viewed from ObiExpert mode on the portal is not showing for either.

As a side note, I've had the Uptime on my Obi200 go as high as 8 - 9 weeks. Usually, it's shorter because I've made a setting change or applied new firmware that results in a reboot.
Logged
GPz1100
Sr. Member
****
Posts: 284


« Reply #10 on: June 14, 2018, 12:46:36 pm »

I'd be curious to know what change was pushed that caused the reboot.

@Time_Lord  Do you have a backup settings you can compare to?  If not, now's a good time to make one.  Is your firmware version still 3.2.2 build 5859EX?

@ProfTech I'm running the unofficial firmware on both of my obi's for about a week now with no issues.  Both devices were migrated to and successfully provisioned to the new gv sip format, all without using obitalk portal.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 4630



« Reply #11 on: June 14, 2018, 04:04:17 pm »

OBiTALK has the ability to push parameter changes (i.e. to fix some setting error), via XML files.  It doesn't have to be a firmware update.  For example:  when I beta tested the new firmware, I found a critical setting bug.  I fixed it on my devices manually, and then they pushed out the fix to everyone else.
Logged

GPz1100
Sr. Member
****
Posts: 284


« Reply #12 on: June 14, 2018, 05:02:07 pm »

Steve, I wouldn't mind setting updates.  It's unsolicited firmware updates that is the issue.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 4630



« Reply #13 on: June 14, 2018, 05:13:34 pm »

Steve, I wouldn't mind setting updates.  It's unsolicited firmware updates that is the issue.

Like you scolded me yesterday, stay on topic.  The user wanted to know why their device rebooted.  I answered that question.  This isn't a debate or bitch session about how firmware is managed.

If you don't like Polycom's model for supporting devices, then don't use Google Voice.
Logged

Time_Lord
Newbie
*
Posts: 8


« Reply #14 on: June 14, 2018, 06:46:21 pm »

software is still 3.2.2 (Build: 5859EX)

Fair enough OBI/Polycom (or whatever name they are going by now) can push updates to resolve a configuration issue or update firmware.  My only gripe is it appears as if it can happen at any time based upon the uptimes I've seen, I've even seen a reload at around noon. 

I suspect (and hope) the push/reload can only happen when the device is idle granted I don't have a lot of calls in and out of the device however It would still be nice to be able to schedule reloads.  eg Obi pushes a change at noon however adapter delays any reload until say 2am.

Mystery partially solved.

Oh the PoE adapter? they are all over eBay for example https://www.ebay.com/itm/112904337292 I have 6 or 7 of them, different voltages (5V-micro usb, 12v, & 5v), I've only had one fail in the 3+ years I've been using them.

-TL
Logged
restamp
Full Member
***
Posts: 213


« Reply #15 on: June 14, 2018, 06:50:50 pm »

Just an observation -- off-topic, but not really worth starting a new thread over -- but from my perspective, if the OBi developers would just allow the changes made from the built-in web server to be fed back to OBiTalk, it would make the OBiTalk interface a lot more palatable.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC