Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide

If meeting participants are consistently dropped after a certain period of time (for example, 

12 hours) after meetings begin, then you may need to change the Maximum Call Duration Timer service 
parameter in Cisco Unified Communications Manager. 

Use the CLI to troubleshoot:

Log into the CLI. 

Enter one of the following commands, specifying a start time (-b) shortly before the call was dropped 
and a stop time (-e) shortly after the call was dropped:

For a call on the current day: eventlog -G -b hhmm -e hhmm 

For hhmm, enter the two-digit hour (in 24-hour format) and two-digit minute, according to the local 
server time of the Application Server.

For a call on a previous day: eventlog -G -b [YY]MMDDhhmm -e [YY]MMDDhhmm 

For MMDD, enter the two-digit month and two-digit day. Specify the two-digit year YY if you are 
troubleshooting issues around the start of a new calendar year.

The following sample log output shows a normal dial-in call that was intentionally disconnected by the 
caller:

[mpxadmin@example-server ~]$ eventlog -G -b 1030 -e 1040 

07/15 10:36:43.14  P 0    RN MC s=013 mcpIncomingCallNotification

07/15 10:36:43.14  P 0    SE CP m=018 NEWCALLEVENT Resp 0

07/15 10:36:43.14  P 0    Leg=134217732 Dialed=9007@172.27.106.63: ANI=1881@172.27.99.180 

GCID=96E8CEEA529411DD97F60018FE735D02

07/15 10:36:43.14  P 0    RQ CP m=018 CPANSWERCALL

07/15 10:36:43.14  P 0    SQ MC s=013 mcpAnswerCallRequest

07/15 10:36:43.62  P 0    RR MC s=013 mcpAnswerCallResponse Resp 0

07/15 10:36:43.62  P 0    SR CP m=018 CPANSWERCALL Resp 0

07/15 10:36:43.65  P 0    RN MC       mcpMediaActiveNotification (audio:HC, video:off)

07/15 10:36:43.65  P 0    SE CP m=018 UPDATEMEDIAEVENT Resp 0

07/15 10:36:44.63  P 0    RQ CP m=018 CPPLAYFILELIST

07/15 10:36:44.63  P 0    SQ MC s=013 mcpPlayFileListRequest

07/15 10:36:44.63  P 0    RR MC s=013 mcpPlayFileListResponse Resp 0

07/15 10:36:49.25  P 0    RC MC s=013 mcpPlayFileListCompletion Resp 0

07/15 10:36:49.25  P 0    SR CP m=018 CPPLAYFILELIST Resp 0

07/15 10:36:49.26  P 0    RQ CP m=018 CPPLAYFILELIST

07/15 10:36:49.26  P 0    SQ MC s=013 mcpPlayFileListRequest

07/15 10:36:49.26  P 0    RR MC s=013 mcpPlayFileListResponse Resp 0

07/15 10:36:55.50  P 0    RC MC s=013 mcpPlayFileListCompletion Resp 22

07/15 10:36:55.50  P 0    SR CP m=018 CPPLAYFILELIST Resp 0

07/15 10:36:55.51  P 0    RN MC s=013 mcpHangupNotification

07/15 10:36:55.51  P 0    SE CP m=018 HANGUPEVENT Resp 0

07/15 10:36:55.51  P 0    RQ CP m=018 CPDISCONNECT

07/15 10:36:55.51  P 0    SQ MC s=013 mcpDisconnectCallRequest

07/15 10:36:55.51  P 0    RR MC s=013 mcpDisconnectCallResponse Resp 0

07/15 10:36:55.51  P 0    SR CP m=018 CPDISCONNECT Resp 0

If the log includes a far-end disconnect event, then the disconnect was probably initiated outside of 
Cisco Unified MeetingPlace. 

Check for errors on the devices between the phone and Cisco Unified MeetingPlace. In a Cisco Unified 
Communications Manager environment, contact the Cisco Unified Communications Manager 
administrator to get a call session trace, which may indicate if and why Cisco Unified 
Communications Manager initiated the disconnect.