![]() ![]() Collecting CUCM logs is mostly the same in most CUCM version however there are some variations depending on which CUCM version you are using. Please refer to the link below to see what you need to ensure your CUCM servers are correctly configured. There are certain settings that may be needed on the CUCM itself before you can collect meaningful traces. RTMT is the tool we use in downloading logs from CUCM. RTMT is the easiest and most efficient so I thats the one we will focus on. CUCM logs can be collected either via RTMT or the OS CLI. As simple as it sounds, knowing how to collect CUCM logs and which servers in your cluster to collect the logs from could save you lots of time in troubleshooting. ![]() The first place to start is obviously collecting CUCM logs, hence we need to know how to collect them. My aim here is to look at a call end to end and dealing with each protocol that are involved in the call flow 2.1 Collecting CUCM logs I will post links to some of these excellent documents later on There are several protocol specific documentations that have been written and you should refer to them. This document is not protocol specific although we will be looking at a sip centric call flow. In this document I will be sharing a few tips that have really helped me to understand this product a little better. These logs can be daunting if you don’t know what to look for or how to interpret what you are looking for. CUCM is a very complex call control system and sometimes it is hard to troubleshoot issues without looking at logs. In this document, I will attempt to share one or two things about understanding how to read and interpret CUCM traces. 3.1.5 Task 2: Open Up The Traces In notepad++. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |