Cisco 8851 SRP Register Failed.

[rakunkest77]

I am honestly clueless. I installed CUCM in my homelab for fun mind you ive installed 100ish CUCMs in the past and have never had this problem when it came to cucm. My phones are giving me an SRP error and it feels like no one on the internet know how to help. If anyone on here does know I would be forever grateful.

The logs boil down to this:

Configuring IP

ITL Installed

File not found SEP(ciscophone).cnf.xml.sgn

XMLDefault.cnf.xml.sgn (HTTP) - I am assuming it taking a default template of some sort.

The SRP Register failed.

I have tried fixing my DNS bc it was yelling at me about my dns but that did nothing. I tried setting the DNS Records too for example my cucm is "PREMNetworksCUCM01.PremNetworks.org" (that's not on the public internet don't worry just a homelab dns

i tried adding that URL into my DNS and it didn't work. I feel so lost so if someone could help it would make my day.

[vishalbhandari]

The SRP error you're encountering with CUCM can be challenging, especially when it appears to stem from configuration files not being found. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Verify TFTP Configuration:

• Ensure that the TFTP service is running on your CUCM. The TFTP service is responsible for serving the configuration files to the phones.
• Verify that the correct TFTP server is specified in the DHCP scope or manually configured on the phones. This is where the phones will look for the .cnf.xml.sgn files.

2. Check ITL and CTL Files:

• Since the phones are indicating that the ITL (Identity Trust List) is installed, there might be an issue with the trust relationship between the phones and CUCM.
• Try resetting the ITL file on one of the phones. This can be done by navigating to Settings > Security Configuration > Trust List > ITL File on the phone and choosing to erase it.
• After erasing the ITL file, reboot the phone to see if it can then download the necessary configuration files.

3. Check and Regenerate Configuration Files:

• Go to Cisco Unified Serviceability > Tools > Control Center - Feature Services and select the CUCM server. Restart the TFTP service.
• Regenerate the phone configuration files by navigating to Cisco Unified CM Administration > Device > Phone and performing a Reset or Restart for the affected phones.

4. Inspect and Manually Create Configuration Files:

• Verify if the phone configuration files exist on the TFTP server. You can do this by accessing the CUCM CLI and navigating to the TFTP directory:
  php

  file list tftp /SEP<MAC_ADDRESS>.cnf.xml.sgn
• If the files are missing, try creating a basic configuration file manually or ensure that the phone has been properly added to CUCM with the correct device name.

5. DNS Resolution and CUCM Hostname:

• Since you've mentioned DNS issues, ensure that your DNS is correctly resolving the CUCM hostname to the correct IP address.
• Verify that the DNS configuration on both the CUCM server and the phones is accurate. Sometimes, even if DNS records are correct, incorrect DNS settings on the phones themselves can cause issues.

6. SRTP Configuration:

• The error might also relate to Secure Real-time Transport Protocol (SRTP) settings if the phones are trying to register securely but are unable to.
• Ensure that the SRTP settings on both CUCM and the phones match. You can disable secure communications temporarily to see if that resolves the registration issue.

7. Logs and Detailed Debugging:

• Enable detailed logs for the TFTP and phone registration processes on CUCM and analyze the logs to see where exactly the process is failing.
• Use RTMT (Real-Time Monitoring Tool) to monitor the registration attempts and gather more information on the error.

These steps should help narrow down the issue and get your phones to register successfully. If the problem persists, you might need to perform a deeper dive into the specific configuration settings or even re-examine the CUCM installation itself.

[Leo Laohoo]

Look at your DHCP server in your Unify switch.  What is the configuration of the DHCP Option 150?

[Maren Mahoney]

If your Status messages don't show a DHCP timeout nor a TFTP timeout, then you can assume they are reaching a CUCM server that has the TFTP service is active. If you have "File Not Found" then for some reason CUCM is not recognizing them as phones that already exist in the CUCM database. Are the phones built on CUCM? Are they built with the correct model (and protocol - if they are old enough to still allow SCCP)? What happens if you turn on Auto-Registration, do they register?

I've been working with Cisco phones for a couple of decades and don't recognize "SRP" as a phone-related 'thing'. Can you confirm that error? Or did you mean to type "The SIP Register failed."?

Maren

[Nithin Eluvathingal]

The “File not found SEP(ciscophone).cnf.xml.sgn” error clearly indicates that the configuration file for your MAC address is not found on the CUCM. It’s trying to use the default profile, which will never register like SCCP phones.

Please check if you have configured the phone on CUCM with the correct MAC address.

On the Cisco phone, verify that it has the correct TFTP address, which should be your Call Manager server IP address.

As @Maren Mahoney highlighted, even I can’t recognize SRP.