It is possible to reboot IP phones remotely. I have 40 phones and i make some changes in configuration file and phones must reboot to accept new changes.
Well IPURI wont reboot the telephone in many cases, it will force the telephone to read the config file.
Surf to the telephone, log on and go to network.
Push apply all settings.
"Well IPURI wont reboot the telephone in many cases"
Can you explain this please? IPURI - FORCE reboots a registered phone, and when it comes up it reads config file. If the phone is not registered it does not receive the IPURI command so does not reboot and read the config file. Can you explain how a phone will read the config file on IIS without rebooting the phone which is what you say?
To give another option to smurf, restart the network switch(es) the phones are connected to if they are PoE, this will reboot all the phones.
I've write shell script (using curl command) which remotly login to IP phones and "virtual" press "Apply all settings"
I've only provide list of IP addresses of ip phones...
script has only few lines... I don't have access to it at this moment - but if you need I can retrive it from site... - just let me know.
can someone explain what is the reason of using this method to reboot a logged on phone when you can already do forced IPURI on extension from the TSW/TSE? I can only see you create more work this way?
Hello.
sometime not every IP phone is registered on the switch. In my situation this was the reason why I've used this method instead of IPURI ( which is working find - but IP phone must be registered).
IPURI only unregister telephones and don't reboot them."
In my experience IPURI FORCE reboots the phone and it looks to the IIS server for the new config file and updates the phone if anything changed, I have updated entire networks this way remotely. Can someone clarify if something has changed with this and when?
I've tested at this moment IPURI on ip extension ( both types SIP and H.323) and IPURI doesn't couse restart of IP phone but in fact the config is reloaded from web server...
in test i've used TSE 3.2 SP3 and phone DBC 4422 with latest firmware R7B
IPURI is very inconsistent. We've had people use it to upgrade whole sites and wraths of phones are left on old firmware due to it.
The sure fire way to ensure a phone cold boots is to power cycle it.
If via PoE switch, this is of course easy by bouncing the individual port, or the entire switch.
Of course any PC using the IP phone as a switch will temporarily lose service.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.