This particular eventlog is for the CPMCP module within the Application Server which only talks to other internal components within the Application Server, so it's not exactly the best eventlog to start out with and is typically only reviewed for complex internal issues which are typically bugs. Since this getting involved with the internal workings of MeetingPlace, there is no external documentation for interpreting this.
If you are going through the logs or an Information Capture of a particular incident, I would suggest first going through the VUI eventlog. Here you can ignore any lines with "State" or "Substate" since those are internal messagings, but this will give you a good idea of when a user calls in, which port they are on, the meeting they joined, and when they disconnected.
New call into MeetingPlace:
08/17 09:54:55.83 P 1 In Call : DID/DNIS 2085, ANI 3062 ============= (2)
Outdial from MeetingPlace
08/17 09:48:00.14 P 4095 Outdial : UserID 3 RetCode 3107
Dest +13076R Trans Dest
Meeting ID that was entered in:
08/17 09:55:11.36 P 1 ConfStr : 640603980
08/17 10:01:56.29 P 1 Action : CONF_LEAVECONF
08/17 10:01:56.27 P 1 Input : Far end disconnect
Also if you are familiar with SIP, you can review the SIP messages for specific calls in either the "CCA Sip Log" or "SIP B2BUA log" depending on your deployment. These logs tend to overwrite fairly quickly, so you should gather an Information Capture as soon as an issue occurs.
The Information Capture is the main set of logs for Cisco Technical Support to review. To collect the Information Capture, login to the web page of the Application Server and go to Services, Logs, and System Information Capture. Select the appropriate start and end times to capture the issue. This will create a zip file for you to save on your computer. This can be unzipped and you can click on the "index.html" file to see the list of log files.
If you need any further help with these or want further steps on troubleshooting a particular issue, open a TAC case and we will be able to these logs with you.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...