/mcpError Message %UC_CALLMANAGER-3-PublishFailedOverQuota: %[DID=String][Server=String][Current quota=UInt] [Maximum target quota=UInt][AppID=String][ClusterID=String][NodeID=String]: Publish Failed - over Quota. Explanation Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, even though you should be under quota, due to an extremely unlikely statistical anomaly, the IME distributed cache rejected your publication, believing you were over quota. You should only see this alarm if you are near, but below, your quota. This error is likely to be persistent, so that the corresponding E.164 number from the alarm will not be published into the IME distributed cache. This means that you will not receive VoIP calls towards that number - they will remain over the PSTN. Recommended Action The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server on the same IME distributed cache. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem. Error Message %UC_CALLMANAGER-4-PublishFailed: %[DID=String][AppID=String][ClusterID=String] [NodeID=String]: Publish Failed. Explanation Unified CM attempted to store a number into the IME distributed cache, but the attempt failed. This is typically due to a transient problem in the IME distributed cache. The problem will self- repair under normal conditions. However, you should be aware that, as a consequence of this failure, the E.164 DID listed as part of the alarm will not be present in the IME distributed cache for a brief interval. Consequently, this may delay the amount of time until which you will receive VoIP calls made to that number - they may continue over the PSTN for some callers. It is useful to be aware of this, in case you are trying to understand why a call is not being made over VoIP. Recommended Action If you notice single small numbers of this alarm in isolation, no action is required on your part. However, a large number of them indicates a problem in the IME distributed cache, most likely due to problems with Internet connectivity. Check your Internet connectivity. Error Message %UC_CALLMANAGER-3-IMEDistributedCacheInactive: %[AppID=String][ClusterID=String] [NodeID=String]: Inactive IME distributed cache . Explanation This alarm is generated when Unified CM attempts to connect to the IME server, however, the IME distributed cache is not currently active Recommended Action Check to make sure that the IME certificate is provisioned on the IME server. Check to make sure that the IME distributed cache has been activated via the CLI on the IME server. Error Message %UC_CALLMANAGER-4-RejectedRoutes: %[Domain=String][DN=String][AppID=String] [ClusterID=String][NodeID=String]: Rejected route due to Untrusted status. Explanation This alarm is generated when Unified CM learned a route from the IME server. However, due to the configured Trusted/Untrusted list, the route was rejected. Recommended Action This condition is not an error. However, it indicates to you that one of your users called a number which was reachable over IME, however, due to your configured 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 286/343