Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide
Troubleshooting Telephone Issues for Cisco Unified MeetingPlace
How to Resolve Problems with Call Connections
11
Step 4
If the log does not include a far-end disconnect event, then the disconnect was probably initiated by
Cisco Unified MeetingPlace.
Cisco Unified MeetingPlace.
•
If the log messages identify a reason for disconnecting the call, then investigate and resolve those
issues.
issues.
•
Check the
or the
to for issues that may have caused the system to drop
calls.
Related Topics
•
in the
module
•
module
•
Direct Inward Dial (DID) Call Does Not Connect to Meeting
Problem
DID calls do not connect to the designated meeting.
Solution
Verify the configuration:
Step 1
Verify that the
field on the
is set
to Yes.
Step 2
Verify that Cisco Unified Communications Manager is configured with a valid route pattern:
•
The Route Pattern field contains the meeting ID.
•
The Gateway/Route List field specifies the SIP trunk to Cisco Unified MeetingPlace.
Step 3
Schedule a test meeting using these parameters:
•
Meeting ID: Use one that already has a matching route pattern in Cisco Unified
Communications Manager.
Communications Manager.
•
Time: Now.
Step 4
Place a test call to the meeting ID.
Solution
Use the CLI to check which DID phone number was received by Cisco Unified MeetingPlace:
Step 1
Place a test call to the meeting ID.
Step 2
Log into the CLI.
Step 3
Enter the following command:
eventlog | grep DID/DNIS | head
Step 4
Read the log output to see which DID phone number was received by the system.
For example, in the following output, the phone (with extension number 7178) dialed the DID phone
number 1717.
number 1717.
08/11 13:51:54.14 P 0 In Call : DID/DNIS 1717, ANI 7178 ============= (1)