There are logs with more detail on the CUCM server. Please post those.
There are various things that could cause a TFTP error:
1. An incorrectly specified IP address (static or DHCP) for the TFTP server
2. A misconfigured station in CUCM (check device name for instance)
3. TFTP service has lost its subscription to the dblnotify service. You can
test this with a TFTP client. Try to pull down the phone config XML to
your client. If you have multiple TFTP servers, see if one works and the
other does not.
4. The two messages you provided in combination could occur when the TFTP
server has an issue servicing the configuration file AND the IP address the
phone is using for TFTP is a server that does not have the call manager
service running. When a phone can't download its configuration, it will
attempt to register to the TFTP server.
#4 implies that you should figure out the TFTP issue as a precursor to
determining the registration issue as there is a likely connection.
Oh, and do ensure you check model types still.
HTH.
Regards,
Bill
Please remember to rate helpful posts.
