Meeting place event log interpretation

Gilberto Marcos — Sun, 17 Mar 2019 22:28:07 GMT

Hello Guys I am wondering if somebody could help me with the meaning of certain values that is shown in the meeting place event log.

I have the following:

08/13 12:31:17.72 P 8 RN MC s=009 mcpHangupNotification

08/13 12:31:17.72 P 8 SE CP m=020 HANGUPEVENT Resp 0

08/13 12:31:17.72 P 8 RQ SM m=01a C 0 REMOVEPORT

08/13 12:31:17.72 RQ CP m=020 CPGOINGTOCONF

08/13 12:31:17.72 P 8 SR SM m=01a C 0 REMOVEPORT Resp 0

08/13 12:31:17.72 SR CP m=020 CPGOINGTOCONF Resp 0

08/13 12:31:17.72 C 0 RQ CP m=020 CPPLAYFILELIST

08/13 12:31:17.72 C 0 Play prompt: lang=1, num=575

08/13 12:31:17.72 C 0 Play prompt: lang=1, num=399

08/13 12:31:17.72 C 0 Play guest name: confID=263 part=4661

08/13 12:31:17.72 C 0 SQ MC s=009 mcpPlayFileListRequest

08/13 12:31:17.72 P 8 RQ CP m=020 CPDISCONNECT

08/13 12:31:17.72 P 8 SQ MC s=009 mcpDisconnectCallRequest

08/13 12:31:17.72 C 0 RR MC s=009 mcpPlayFileListResponse Resp 0

08/13 12:31:17.72 P 8 RR MC s=009 mcpDisconnectCallResponse Resp 0

08/13 12:31:17.72 P 8 SR CP m=020 CPDISCONNECT Resp 0

I almost sure that P8 means port 8 but I do not know what RN, MC, SE, RQ, CP, mcp or C 0 means.

Is there a document that shows all?

Regards

Meeting place event log interpretation

anmarti2 — Mon, 19 Aug 2013 15:10:20 GMT

Hello,

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.

For example:

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

Leaving conference:

08/17 10:01:56.29  P 1       Action   : CONF_LEAVECONF

User disconnecting:
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.

Regards,

Andrew

Cisco TAC

topic Meeting place event log interpretation in Collaboration Applications

Meeting place event log interpretation

Meeting place event log interpretation