Cisco Cisco MeetingTime Quick Setup Guide

Page of 766
 
Troubleshooting Telephone Issues for Cisco Unified MeetingPlace
How to Resolve Problems That Occur During Calls
13
 
How to Resolve Problems That Occur During Calls
  •
  •
System Does Not Detect Key Presses
Problem   
The system does not detect user input through the telephone user interface (TUI).
Solution   
Step 1
Log into the CLI. 
Step 2
Troubleshoot a call in real time by completing these steps:
a.
Enter the following command:
eventlog -G -t 
b.
Place a test call to the system.
c.
Press phone keys in response to the voice prompts.
Step 3
In the log, look for DTMFEVENT and mcpLegNotification messages, each pair of which would indicate 
that Cisco Unified MeetingPlace received the user input of a single digit.
The following sample log output shows that at 10:42:04, a caller on port 0 pressed the “1” key on the 
phone:
08/28 10:42:04.95  P 0    RN MC       mcpLegNotification (1)
08/28 10:42:04.95  P 0    SE CP m=017 DTMFEVENT Resp 0
Step 4
If you do not see DTMFEVENT and mcpLegNotification messages in the log, make sure that your 
call-control devices are set up to transport DTMF digits:
  •
In Cisco Unified Communications Manager SIP trunks to Cisco Unified MeetingPlace, make sure 
that th
 is set to No Preference. 
  •
If the call passes through a voice gateway, then you may need to configure that gateway to use 
DTMF relay to transport DTMF digits. 
  •
On the 
, try setting the 
 field to Yes. 
  •
Make sure that the Media Server is correctly configured. See the Installation, Upgrade, and 
Migration Guide for Cisco Unified MeetingPlace
 at 
Step 5
If you do see DTMFEVENT and mcpLegNotification messages in the log, check the 
TUI-related issues, and resolve them.  
Related Topics
  •
 module