Information About Resetting and Restarting Phones
Differences between Resetting and Restarting IP Phones
Cisco Unified IP phones must be rebooted after configuration changes in order for the changes to be effective. Configurations for phones in Cisco Unified CME are downloaded when a phone is rebooted or reset. You can reboot a single phone or you can reboot all phones in a Cisco Unified CME system. The differences between reboot types are summarized in Table 1.
Note |
When rebooting multiple IP phones, it is possible for a conflict to occur if too many phones attempt to access changed Cisco Unified CME configuration information via TFTP simultaneously. |
reset Command |
restart Command |
|||||
---|---|---|---|---|---|---|
Type of Reboot |
Similar to power-off, power-on reboot. |
Quick restart. |
||||
Phone Configurations |
Downloads configurations for IP phones. |
Downloads configurations for IP phones. |
||||
DHCP and TFTP |
Contacts DHCP and TFTP servers for updated configuration information.
|
Phones contact the TFTP server for updated configuration information and reregister without contacting the DHCP server.
|
||||
Processing Time |
Takes longer to process when updating multiple phones. |
Faster processing for multiple phones. |
||||
When Required |
Can be used when updating the following:
|
|
Cisco Unified CME TAPI Enhancement
Before Cisco Unified CME 7.0(1), the only method to clear a session between a Microsoft Windows Workstation and an SCCP phone that was out-of-sync was to reboot the router. In Cisco Unified CME 7.0(1) and later versions, you can clear a Telephony Application Programming Interface (TAPI) session that is in a frozen state or out of synchronization by using a Cisco IOS software command. For configuration information, see Reset a Session Between a TAPI Application and an SCCP Phone.
This enhancement also automatically handles ephone-TAPI registration error conditions. No additional configuration is required for this new feature.