CUCM 14 Status Rejected Initialization Error

[ziqex]

I have multiple phones in various location that have status rejected.

Initialization Error. Factory reset does not resolve the issue.

one publisher and two subscriber setup

Setup was fully working, yesterday one of the subs went down due to connection issue and the devices did not registered back even after restart.

Cluster Replication State: BROADCAST SYNC ended at: 2022-09-15-20-59
     Sync Result: SYNC COMPLETED on 749 tables out of 749
     Sync Status: All Tables are in sync

System version: 14.0.1.12900-161

CUCM group 

Any suggestions highly appreciated. Thanks

[Leonardo Santana]

Hi,

All sites have this issue?

These IP Phones are registered to a particular CUCM node?

The CUCMs are located at the same site?

All services are up and running at your CUCM nodes?

Do you have any network issue between the IP Phones and CUCM nodes?

Could you check the health of you servers via cli using the command utils diagnose test

[ziqex]

No only some sites.

E.g. one site has 5 phones with rejected status whereas one phone is registered

All same model 7841, all connected to same switch, same DHCP server etc.

In the packet capture I could see message HTTP/1.1 404 Not Found between subscriber and desk phone

[ziqex]

Please see the utils diagnose test result below:

admin:utils diagnose test

Log file: platform/log/diag1.log

Starting diagnostic test(s)
===========================
test - disk_space : Passed (available: 5677 MB, used: 13452 MB)
skip - disk_files : This module must be run directly and off hours
test - service_manager : Passed
test - tomcat : Passed
test - tomcat_deadlocks : Passed
test - tomcat_keystore : Passed
test - tomcat_connectors : Passed
test - tomcat_threads : Passed
test - tomcat_memory : Passed
test - tomcat_sessions : Passed
skip - tomcat_heapdump : This module must be run directly and off hours
test - validate_network : Passed
test - raid : Passed
test - system_info : Passed (Collected system information in diagnostic log)
test - ntp_reachability : Passed
test - ntp_clock_drift : Passed
test - ntp_stratum : Passed
skip - sdl_fragmentation : This module must be run directly and off hours
skip - sdi_fragmentation : This module must be run directly and off hours

Diagnostics Completed

The final output will be in Log file: platform/log/diag1.log

Please use 'file view activelog platform/log/diag1.log' command to see the output

Inside ssosp_container container
==============================================

Log file: platform/log/ssosp_container1.log

test - tomcat : Passed
test - tomcat_deadlocks : Passed
test - tomcat_connectors : Passed
skip - tomcat_heapdump : This module must be run directly and off hours

Diagnostics Completed

The final output will be in Log file: platform/log/ssosp_container1.log

Please use 'file view activelog platform/log/ssosp_container1.log' command to see the output

Inside axl_container container
==============================================

Log file: platform/log/axl_container1.log

test - tomcat : Passed
test - tomcat_deadlocks : Passed
test - tomcat_connectors : Passed
skip - tomcat_heapdump : This module must be run directly and off hours

Diagnostics Completed

The final output will be in Log file: platform/log/axl_container1.log

Please use 'file view activelog platform/log/axl_container1.log' command to see the output

Inside uds_container container
==============================================

Log file: platform/log/uds_container1.log

test - tomcat : Passed
test - tomcat_deadlocks : Passed
test - tomcat_connectors : Passed
skip - tomcat_heapdump : This module must be run directly and off hours

Diagnostics Completed

The final output will be in Log file: platform/log/uds_container1.log

Please use 'file view activelog platform/log/uds_container1.log' command to see the output

admin:

[Leonardo Santana]

Hi,

There was any changes at your network enviroment?

Check on RTMT Voice/Video > Device > Device Search > Open Device Search > Phone 

Filter the field any status putting any cucm try to find these ip phones with this issue to see the reason that they are registering.

PS: You need to download the RTMT from CUCM and install in your computer.

[ziqex]

There was a connection drop at DC where voice server is located (one of the subscribers, second one and publisher remained active) . The connection was restored but some phones did not register back. In the RTMT I can see Initialization Error (node - our subscriber). 

[ziqex · Accepted solution]

The issue was resolved.

Cisco TFTP service was restarted on both subscribers.

According to TAC, TFTP services were stuck due to heavy load.