10-05-2016 12:13 PM - edited 03-19-2019 11:39 AM
I am struggling with trying to determine which logs to gather to determine what is happening with a couple of phones.
I have a couple of phones that were registered and now they are not registered.
While most of the phones we have are SCCP, the 2 I am looking to discover the issue are SIP phones . (not sure if that makes a difference in choosing the RTMT log ).
Seems like there is a log that shows the phones and activity and can see if a phone is trying to connect and why it can not and I thought it would show the reason it became unregistered.
Any other information needed from me to help point me to the right log in RTMT ?
Really appreciate the assistance.
Solved! Go to Solution.
10-05-2016 01:21 PM
Hi,
You need the below logs from CUCM server.
CUCM traces get overwritten very frequently depending on your call volume, but other 2 are a dump so you should be able to find information in those.
With CUCM 10.4 you would only see SDL file, as tracing from CUCM 9.X onward in interleaving.
JB
10-05-2016 12:14 PM
I did choose " Cisco CallManager" and it produced SDL and Call logs .... the SDL ones did not help.
I looked at both the PUB & SUB of that SDL log ,and did not find anything
10-05-2016 01:21 PM
Hi,
You need the below logs from CUCM server.
CUCM traces get overwritten very frequently depending on your call volume, but other 2 are a dump so you should be able to find information in those.
With CUCM 10.4 you would only see SDL file, as tracing from CUCM 9.X onward in interleaving.
JB
10-05-2016 01:42 PM
Thanks for letting me know. I marked this as "correct" as I wanted to know which logs to click in the tool.
The logs are proving to not be helpful , only shows the phone unregistered (reason=13) which I think it means 'timeout'.
thanks for your time
10-05-2016 01:46 PM
Reason code 13 = KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
Check the link below for details
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/10_x/ccmalarms1001.html
Happy to help
JB
10-05-2016 02:19 PM
thanks for the additional information, I will go through the items and see what I can find !
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide