So, apparently it is a bad thing to just directly pull the plug on a Cisco Unified Communications phone controller.
Apparently it is possible to corrupt CUE and to possibly have it go so far as to corrupting the flash memory and losing all stored phone messages and even the system configuration.
But I don't see a simple and easy way to use battery backup, with a controlled shutdown process, to safely power down a controller.
I am thinking something may be easily possible to tell a Cisco phone controller always do a safe shutdown when the UPS goes on battery, using one of the cheap microcontrollers that are now available, such as Rasberry Pi.
Most UPS have a serial port status monitoring capability that reports when the UPS is on battery. So write a tiny program for the microcontroller that looks something like this:
Sleep 1 second
Check serial port #1 for UPS state.
If UPS on battery then
add 1 to ShutdownDelay
set ShutdownDelay to zero.
If ShutdownDelay > 60 seconds then
Open serial port #2 to UC560 console port
Logon to router
If error, try to logon again.
Shut down cue: service-module integrated-Service-Engine 0/0 shutdown
Wait for successful command completion. If error, try again.
Write logging info to flash memory on Rasberry Pi.
Send command to UPS to turn off and go to into sleep mode until power is restored
Is there any such already existing thing? I'm not finding anything with my web searching.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...