News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi202 loses IP address

Started by dhoppy, January 15, 2019, 03:17:15 AM

Previous topic - Next topic

dhoppy

I have an Obi202 that has never worked properly, I have to frequently reboot it.  It will work fine for a day or so and then it will lose its IP address, from what I can tell (because I can't login to the WAN interface, or ping the device).  After a reboot I am able to ping it and login through the WAN interface.

Last night I setup a syslog server to see if I could capture what is going on, and this morning I see some entries in the log that say:

PLEASE - - - PLEASE FIX MEEEEEEE

Anyone have any idea where I can start to troubleshoot my problem?

I am running 3.2.2 (Build: 5898EX).  I have configured a reserved IP address in my router so the Obi202 gets the same IP address each time it boots. 

I tried a static IP address, but maybe I didn't configure it right, because it changed back to DHCP (cause of Obitalk settings?).

Thanks in advance for any help.

drgeoff

#1
Quote from: dhoppy on January 15, 2019, 03:17:15 AM
I tried a static IP address, but maybe I didn't configure it right, because it changed back to DHCP (cause of Obitalk settings?).

Thanks in advance for any help.
1. Unless you have disabled Obitalk provisioning you should make changes to settings using the portal.  You can gain access to almost all the settings using the Expert mode.  There are two tick boxes at the right hand side of each settings line.  You need to click in those to make them both clear before the setting will become editable.  After making the change click on Submit at the bottom and wait for the OBi to automatically reboot.

2.  Don't the syslog "Fix me" messages give any nearby clues as to what should be fixed?

dhoppy

I will try to set a static IP address through the Obitalk expert interface, and see if that helps.

There don't appear to be any errors near the Please Fix Meeeee message.  I'll paste some of it here:

<142>1 2019-01-14T17:16:35.034131-08:00  PARAM - - - PARAM Cache Write Back(256 bytes)
<156>1 2019-01-14T17:17:10.481635-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<7>1 2019-01-14T17:22:40.694856-08:00  SNTP 0 - - SNTP[0]->pool.ntp.org

<156>1 2019-01-14T17:28:01.953080-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<156>1 2019-01-14T17:34:50.444645-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<156>1 2019-01-14T17:45:42.560521-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<156>1 2019-01-14T17:52:30.230918-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<7>1 2019-01-14T18:00:55.234825-08:00  CCTL - - - CCTL:NewCallOn Term 1[0] ->REDACT_ACCT,REDACT_ACCT
<6>1 2019-01-14T18:00:55.234825-08:00  fxst_ccapi_new_call - - - fxst_ccapi_new_call: REDACT_CALLID->REDACT_CALLID name REDACT_CALLID
<7>1 2019-01-14T18:00:55.235043-08:00   SLIC - - [SLIC] CID to deliver: 'REDACT_CALLID' REDACT_CALLID

And,

<7>1 2019-01-14T18:01:24.107151-08:00   DSP - - [DSP]: set FXS(0) DTMF detection level to (1)
<7>1 2019-01-14T18:01:24.107151-08:00   CPT - - [CPT] --- FXS h/w tone generator (dial)---
<7>1 2019-01-14T18:01:26.820352-08:00   SLIC - - [SLIC]:Slic#0 ONHOOK
<156>1 2019-01-14T18:02:02.280006-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<156>1 2019-01-14T18:08:50.508467-08:00  PLEASE - - - PLEASE FIX MEEEEEEE
<7>1 2019-01-14T18:22:40.648697-08:00  SNTP 0 - - SNTP[0]->pool.ntp.org
<7>1 2019-01-14T19:22:40.738576-08:00  SNTP 0 - - SNTP[0]->pool.ntp.org

user91988

#3
I'm also having to power cycle the Obi 200 that I have due to it no longer connecting to the network through the LAN port and therefore being a brick until this is done. This seems to happen for me every few weeks or so which makes it difficult to check the logs - though I suspect these two instances may have different problems but could be the same.

From what I understand from the OP is that the IP address isn't actually lost (as in not re-adding it), just no longer connected to network as in the light on the farthest right is no longer lit? And the device also needs a power cycle / reboot. So sounds like the same problem but the timing is completely different so the problem could be different.

I've had and am using the Obi 100 with SIP right now and it has not one single problem. Just keeps on working.

Either way, I developed a simple mobile app that automatically checks every hour and alerts me when either device is offline (I can be guaranteed of no nefarious stuff this way, this one will have no ads, etc) and will make it available at some point this year.

By the way, I use static method and this is the result. This should not be happening.

Update - looks like the network cable was slowly popping out at the router. Replaced with new cable and so far so good. So as I suspected, looks to be two different possible problems.