I have just recently changed our General Dynamics Sectera vIPer devices from Firmware 4.2.1 to 5.2.1. I am running CUCM 11.5.1. According to General Dynamics Support staff, when I make the change from 4.2.1 to 5.2.1 with our CUCM version, I have to change the device Product Types from 'Cisco 7960' devices to 'Cisco 7961G-GE'.
When I do this in CUCM by deleting the phone and adding new, the device immediately comes up as Rejected. My thought is that somehow the 7960 config file is still getting shipped to the device and it's a model mismatch, causing the Rejected status? Is there a way I can delete the config file in the TFTP servers for one of my devices to test this out?
Can you fully reset the device (Hardware Reset) in order to attempt to download from "scratch" the new firmware from the CUCM? Additionally, can you reset any network settings on the phone device?
You can also go to RTMT>Tools>Syslog Viewer and Select the CUCM Node> Application Logs> Alternate Logs.
By doing that you should be able to identify the cause of registration failure.
Thank you for the quick post up. I will check on that. In the interim, I deleted the device in CUCM and let it reboot without a config. It came up as an autoregister device like it is supposed to on our system, and it identified as a 7960 device. I deleted that device and supercopied another vIPer, changed MAC Desc & DN, and it immediately came up.
I have an email out to GD support to verify if there is anything to set upon the endpoint to make the change from 7960 to 7961G-GE.
The Fix was quite simple actually, you have to go into the vIPer device itself through the Web Admin page and change the SCCP Settings "Cisco Phone Registration Type" from 7960 to 7961G-GE. Then let the phone reboot as you build the new phone in CUCM, it will come up fine.