- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Alert a Moderator
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
About the error message "<ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg".
About the error message "<ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg".
On the controller we are continuously receiving the following messages:
Aug 4 11:19:03 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:20:06 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:21:08 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:22:11 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:23:13 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:24:16 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:25:19 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed Aug 4 11:26:21 ucm[4621]: <347001> <ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 878, ucm-record lookup failed
1. What is the reason for this error message?
2. Is there something wrong with the config or the setup that needs to be corrected?
A:
We will usually see this message on a controller with voice clients.
This message appears when if UCM doesn’t have the entry for the client MAC for which statistics needs to be updated. UCM keeps only last 6000 latest CDRs (max limit for Aruba 7240). If a client has not made any call for a few days then it’s complete record could have been deleted by UCM after max CDR limit is hit.
After it’s entry is deleted in UCM, we will see “record not found error” for such clients. The error message will go off after the client re-registers again.
There are two possible error messages we will se in the logs:
A. We will see the below message when periodic quality statistics need to be updated however the record wasn't found:
<ERRS> |ucm| Unexpected UCC runtime error at ucm_call_setup_message, 279, No record found
B. We will see the below message when the controller tried to update the stats for a client due to different call events but client MAC wasn't available.
<ERRS> |ucm| Unexpected UCC runtime error at ucm_call_statistics_msg, 880, ucm-record lookup failed
These messages will go away when the voice client registers again on the controller. Thus there is nothing wrong in controller configuration which needs to be corrected.
UCM=Unified Communication Manager
CDR=Call Detail Record
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Email to a Friend
- Alert a Moderator
What happens when a client never reconnects, does the error continuously occur until the controller is restarted? We have some controllers where this error is occuring every minute for several weeks.
Why would the stats need to be updated for a client that has not made a call for some time?