News:

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

Main Menu

Connect after DSL Off

Started by Clacey, June 10, 2018, 08:11:22 AM

Previous topic - Next topic

Clacey

I have my Internet equipment on a timer that shuts it down for several hours every night. That does NOT remove power from my Obi200. That used to work fine, but lately the Obi200 does not reconnect. I now have to unplug the Obi200 from power, then when I plug it back it has the red light and goes ahead with the reconnect.

Any idea how to fix this problem?

drgeoff

Patient: "Doctor, it hurts when I do this."

Doctor: "Don't do that."

Clacey

Now there is a tremendously helpful post. Thanks a lot for the trolling.

Mango

If possible, I would rather see you fix the problem that is creating the need for powercycling your equipment every night.

However, your OBi should automatically reconnect once the internet connection is restored.  I'd be curious to know if this is an issue with corrupted NAT tables.  To see if I am correct, try to change Service Providers >> ITSP Profile X >> SIP >> RegisterRetryInterval to a high number like 300 or even 600.  If you used OBiTALK to configure your device, you will need to use OBi Expert Configuration to make the change.

Next time your internet is restored, wait 300 seconds (5 minutes) and see if the device recovers on its own.  Let us know if that works.

If it doesn't work, then we need to know the make and model of your router, and the VoIP service provider you use.

I would also be curious to know if your ATA reconnects with a reboot instead of pulling the power plug.

Clacey

Thanks for your input. I shut all my electric entertainment equipment down at night. Mostly for power saving, but also to allow modem, routers etc to do a cold boot. This has worked fine for me for years. My computer and peripherals are on a 1500 watt UPS. I have a Zyxel Q1000z modem/router on Centurylink 20 meg DSL. This problem is only very recent, no more than a week old. In that time nothing about my setup has been changed.

Before trying your advice I am going to put the Obi200 on the timed power strip with the other peripherals and see if that solves the problem. I don't really know why I left the Obi on 24/7. I guess I thought it might be better for it. But now I see that power cycling causes it to connect. I want to try that first. If that fails, I will attempt your suggestion.

Thanks

Lavarock7

Pros and cons.

Many decades ago I worked in a large computer room with everything from PC sized servers to giant mainframes. The room was the size of a football field with many hundreds of systems.

We used to have very random system failures and hangs. Then we implemented a large-scale UPS system. This system used electricity to charge batteries. Then those batteries ran an inverter to create power for the building. In this system we were always using clean power. If the electric company all of a sudden shut down, we were still running until our batteries were depleted. (This is not unlike how a vehicles power system works - you are using battery power all the time and the alternator charges the battery). Your UPS probably works the same way, always supplying power even if you pull the plug. Some cheap UPSs use a relay and don't supply power until the main service disappears, then they switch to the batty and inverter. This type of system causes spikes in the output and thankfully are not that common.

What we found was that many or most of our unexplained reboots and failures stopped. It was a dramatic change.

Electronic devices and software can develop issues where they need to be rebooted. Certainly Windows operating systems fell into that category.

With electronics, there is often a power button which allows a proper shutdown. Oftentimes it does not just cut the power, but rather starts a graceful procedure to store current configurations, stop processes and power down. Of course, not all equip met does that.

My feeling is that by forcing power shutdowns just because you can, is not the best idea. Electronic chips don't like stress and continued stress can cause more chance of failures.

If your equipment was meant to be recycled and cold booted, the manufacturer would have put software or hardware times inside.

Just because you CAN reboot nightly does not mean you should.

My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info<br />A simplified Voip explanation: http://voip.planet-aloha.com

SteveInWA

+1 to DrGeoff and Lavarock.

There is no good reason to power off your equipment every night.  All small electronic devices with plug-in AC/DC power supplies, manufactured within the past decade, have power supplies that meet stringent power efficiency standards (the small IV, V or VI in a circle on the power adapter signify compliance, with the increasing Roman numerals indicating compliance to a higher/newer standard).  They use an insignificant amount of power, especially when the devices are idle.  You can do the math yourself, if you have a "KillAWatt" power meter, and you know the cost of your electric power (typically around 10 to 12 cents per KWH).

Aside from no meaningful cost savings from powering off, as Lavarock mentioned, the repeated power-cycling can eventually result in component failure.

Clacey

#7
I appreciate the inputs. We all have our experiences. I am an electronics technician since 1961 when I joined the USAF and took two years of schooling in Cryptographic equipment. In addition I have taken other electronics schooling as well as working in the field for 40 years when I took retirement at 59 due to health. We had the newest and best of binary crypto equipment. That said, I have never seen a reason to leave solid state equipment running when not in use. When it was tubes, yes, it was hard on them and constant on/off cycles was a bad idea. Having owned my own computers since 1994 I have always shut down all my systems at night. It has caused me no failure with any of my computers or peripherals. My timer is after the UPS and in no way affects it. I would suggest reading government reports on the billions of KWH wasted just running computers when they are not needed.

https://blogs.scientificamerican.com/news-blog/leaving-pcs-on-overnight-wastes-bil-2009-03-30/

I am a security nut and run numerous programs to protect my computers. And while I do what I can to protect them, having them off when not in use makes it much less likely I will become part of a botnet.

Thanks, I find all the opinions interesting, but will continue to use a timer to save energy as well as having less time exposed to the hackers and slimeballs out there that want nothing more than to find unattended idle computers.

ProfTech

#8
To Clacey: Just a couple of points. I've been in the business since before 1971 and I shutdown my Windows computer for some of the same reasons. Years ago when I worked in a corporate office I powered down my PC when I left at 5 PM so the IT department could not load so-called "patches" and updates on my machine at night. As a result my PC ran very well for years while many of my co-workers were forever having theirs crashing, Blue Screen and so on.  Fast forward to 2008 and I became self employed working out of my home. I opted to go with VOIP for long distance because ATT wanted $200 to install a second line and $60 a month for service. Immediately it was apparent that in order to keep my phone service working at night it was necessary to keep the modem/router on at all times. I still shutdown my PC. Sometimes during the day I disable the ethernet port on my PC but leave it on if I'm going to be away for a few hours. Takes 2 mouse clicks. This time to keep the viruses, crooks and scammers out. No better security than to turn it off.

Now the info: If you have an early model Obi 110 and an attached POTS line there can be a very good reason for you to power down the Obi at the same time you power down the router. The early 110's had a relay that would connect the POTS line directly to your phone(s) if powered down, and keep your phone service [at least the POTS line] available to you. If you have a newer 110 or the 200 series and you power either the Obi or the router [or both] off your phones go dead.

If you power the router off and leave the Obi on, when you power the router up in the morning the Obi automatically reboots. It is designed to do that. If it reboots before the router is ready, there could be a timing issue that might cause the Obi to lock up.

Clacey

I will give it a few days. But yesterday I plugged the Obi into the timed power strip. I have it set to turn on before I get up. This morning the Obi was connected and the phones were ready to go. As far as the phones being off at night. That is part of my scheme. Robocalls etc are not able to bother us at night. We have cell phones that all our friends and family can reach us on 24/7.

Clacey

It has been a week now. And the Obi200 has connected fine every morning after having been shut down for 6 hours each night. Apparently that solved the failure to connect explained in my original post.

Thanks for all posts.

Rukbat

Quote from: Lavarock7 on June 11, 2018, 11:01:07 AMElectronic devices and software can develop issues where they need to be rebooted. Certainly Windows operating systems fell into that category.
Really.  Windows 95 certainly did in most cases.  But this desktop, running Windows 10, doesn't even reboot weekly (I refuse updates for long periods).  This year, the only problem I've had has been - this forum, and that's because my bookmark had https in the URL.  Rebooting Windows?  Es no my yob, man, not in years.  (My first OS?  Isis.  Never needed a reboot.  Neither did CP/M.  Microsoft invented "reboot daily".  46 years of this stuff, and we're finally back to where we were in the 70s - dumb terminals, an OS that doesn't need a reboot, and everything on a server, nothing local [so why are we running dual 10TB drives?].)