We have multiple CUCM clusters in our environment. About a week ago, 3 of those clusters will not longer authorize with Cisco. When I try to manually authorize it, it comes up with a Communications Timeout. TAC requested i unregister, and re-register one of the clusters, that cluster will not re-register, same error, communications timeout.
Has anyone else seen this? I'm sure we have blocked this somehow on our network side, but Cisco kind of side steps around those questions when asking exactly how CUCM registers and authorizes.
Smart Account: XXXXXXXXXXXXXXXXXXXX
Virtual Account: XXXXXXXXXXXX
Export-Controlled Functionality: Allowed
Initial Registration: SUCCEEDED on Dec 19 07:26:32 2019 EST
Last Renewal Attempt: SUCCEEDED on Jun 16 12:28:37 2021 EDT
Next Renewal Attempt: Dec 13 11:28:37 2021 EST
Registration Expires: Jun 16 12:23:36 2022 EDT
Status: AUTHORIZED on Sep 22 12:41:02 2021 EDT
Last Communication Attempt: FAILED on Sep 22 12:41:02 2021 EDT
Failure Reason: Communication send error.
Next Communication Attempt: Jun 25 06:36:53 2021 EDT
Communication Deadline: DEADLINE EXCEEDED
Solved! Go to Solution.
TAC requested i unregister, and re-register one of the clusters, that cluster will not re-register, same error, communications timeout.
We do not use a local server
Can you do below and ensure that you are connecting to 220.127.116.11 and using 443?
I had this issue and I was using an internal DNS, so I had to make sure that I was pointing to the correct IP address.
utils network host tools.cisco.com
> Check whether you are resolving to 18.104.22.168
utils network connectivity tools.cisco.com 443
> Wait until it says "Service accessible" or "Service not accessible"