Automated scheduled reboot of IP Office 500 fails

[jks728]

I've tried INTRIGRANT's suggestion below to reboot IP Office via Task Scheduler in Windows 7. If I run this line manually from a command prompt it works and the system reboots. However, it will not work when executed in a .bat or .cmd file and thus fails in Task Scheduler. This is the output and error I receive when executing from a batch file.
------------------------------------------------------------------
C:\>tftp -i 10.103.10.230 get "nasystem/reboot/00e0070c7f07/$t$'~ q//"

WinAgents TFTP Client version 2.0b Copyright (c) 2004-2011 by Tandem Systems, Ltd.

http://www.winagents.com

- Software for network administrators

Transfering file nasystem/reboot/00e0070c7f07/$t$'~ q/" from server in octet mode...
Transferring data from 10.103.10.230...
Error occurred during the file transfer (Error code = 1):
NotFound

C:\>pause
Press any key to continue . . .
-----------------------------------------------------------------
I'm stumped! I've tried "Run As Administrator", tried running with my Domain Admin account, and many other things. If I could get this to run in a batch file I'm pretty certain it would the run as a scheduled task. Like I said, this line does work when run manually from a command prompt. I've tried to run it in a batch file from several different computers.

Anybody have any ideas?
Thanks!
John


~~~~~~~~~~~~~~~~~~~~~~~~~~
INTRIGRANT's original post -
Schedule this in MS scheduler:

reboot.bat
tftp -i 192.168.42.1 get "nasystem/reboot/00e007004e65/$t%$'~ q//"

the ip address is the ip address of the ipo, 00e007004e65 is the MAC address of the ipo, $t%$'~ q/ is the password of the ipoffice ( in this case "password")

If you have changed the systems password then connect a deltaserver to the ipo and search the registry of the pc for deltaserver entries, there you can find the new coded password.

~~~~~~~~~~~~~~~~~~~~~~

 

[IPOLackey]

What version are you running on your IPO? Is TFTP read/write enabled? Can you link the original thread?

 

[IPGuru]

why not simply schedule a timed reboot using manager as deigned?


Do things on the cheap & it will cost you dear

 

[jks728]

IPGuru:

I need it to reboot early every morning not just a one time event. We are very rural hospital and we have one analog line which frequently does not release the call due to an issue between IP Office and our local Frontier CO.

Thanks,
John

 

[joe2938]

now that just crazy, why not fix the problem instead of putting a band aid on it

 

[amriddle01]

John, the line provider needs to setup disconnect clear/disconnect supervision, you then set the IP Office for 150ms less than the time they set it at. That and also setup busy tone detect, that should clear the call down. If the provider can't do this then find a provider that's up to 80s technology at least

Fix the cause not the symptoms

 

[IPGuru]

I am with Joe & Andy

Get the line issue fixed,

you are trying to amputate an arm to cure exma.

a less aggressive TEMPORARY work arround would be to limit the duration of inbound calls

send the ICR to a short code instrad of a group/destination

SC <whatever>
TN:<destination>T(60)
feature Dial Extn

should restrict inbound calls to a maximum of 60 minutes (adjust as appropriate)

Do things on the cheap & it will cost you dear

 

[jks728]

RE:
amriddle01
John, the line provider needs to setup disconnect clear/disconnect supervision, you then set the IP Office for 150ms less than the time they set it at. That and also setup busy tone detect, that should clear the call down. If the provider can't do this then find a provider that's up to 80s technology at least

Fix the cause not the symptoms

We are located in a very small rural town with one provider - Frontier. The last time I spoke with the guy at the CO he wasn't even sure how to set up disconnect supervision on the line. However, I've implemented your suggestion and changed Disconnect Clear from 500ms to 350ms and enabled Busy Tone Detection with the default System Frequency. I'll monitor to see if this solves the problem. I ran into this same issue at our other clinic site of couple of years ago. What seemed to fix it was adding a 16-port external analog module (#700449473) which has Ground Start capability. I configured all their lines to ground start and was able to get the local CO to do the same.

Thanks for your help!
John

 

[jks728]

RE: IPGuru
I am with Joe & Andy

Get the line issue fixed,

you are trying to amputate an arm to cure exma.

a less aggressive TEMPORARY work arround would be to limit the duration of inbound calls

send the ICR to a short code instrad of a group/destination

SC <whatever>
TN:<destination>T(60)
feature Dial Extn

should restrict inbound calls to a maximum of 60 minutes (adjust as appropriate)

Do things on the cheap & it will cost you dear

I admit the daily reboot is a Band-Aid and not the preferred approach. However, we only have one Telco in our very rural area and working with them is a challenge due to outdated equipment, expertise, etc. If amriddle01's suggestion doesn't fix this I'll implement yours!

Thanks!
John

 

[intrigrant]

Your software is expecting some kind of response from IP Office after the TFTP command which will not be send by IP Office but I agree on the replies of others : fix the problem.
One thing you can do is to buy a digital switching clock and disconnect the line for a minute every morning or if you persists, power down IP Office...

 

[mojoputter]

We are located in a very small rural town with one provider - Frontier. The last time I spoke with the guy at the CO he wasn't even sure how to set up disconnect supervision on the line.

Ok wait a minute, I've worked with some very small CO's in the past here in Minnesota, actually one was in the back room of a Radio Shack,
but you would think if that guy works for a large comm company like Frontier you would think he would have a tech services group he could talk to about your issue.