Got this update from one of the BU guys today :
Originally, the config files for SCCP devices contained very basic information about call processing servers and port number. So a restart would just close the TCP connection and reconnect. But now the config files contain a lot more config info, so the device will request the config file always before attempting to connect to UCM.
When you RESTART a phone, the endpoint will terminate its TCP connection to UCM, request and process it’s config file and reregister. This process is quick and a phone will normally reconnect to UCM in 5-15 seconds. In earlier versions (SCCP only), the restart process only took 1-2 seconds.
When you RESET a phone, the phone will terminate its TCP connection to UCM and then restart the network interface on the endpoint. This will force the device to reDHCP as if the device was just plugged in. After completing the network startup and DHCP request, the endpoint will request it’s configuration file, process it, then attempt to connect to UCM. The reset process will take 1-3 minutes to complete.
When you do a APPLY CONFIG to a device, that will cause the device to request its config file, process the contents, then decide if it should restart or not. So depending on what changed, the phone may or may not restart. Personally, almost every change I make to and endpoint’s config will cause the endpoint to restart, so expect this to work like the restart operation.
Manish
