Краткое Руководство По Установке для Cisco Cisco Unified MeetingPlace for Microsoft Office Communicator
Troubleshooting Telephone Issues for Cisco Unified MeetingPlace
How to Resolve Problems with Call Connections
4
•
•
•
•
•
Dial-In Calls Fail
Problem
Users who call Cisco Unified MeetingPlace hear dead air or a busy signal.
Solution
See
Possible Cause
Some third-party terminals are incompatible with and cannot establish connections
with Cisco Unified MeetingPlace.
Solution
Make sure that your endpoints are supported for use with Cisco Unified MeetingPlace.
.
Possible Cause
Assuming that the phone number was dialed correctly, and that call routing is set up
correctly:
–
Dead air generally implies that call setup is failing for some reason, or that some device (such
as Cisco Unified MeetingPlace or Cisco Unified Communications Manager) is completely
unresponsive.
as Cisco Unified MeetingPlace or Cisco Unified Communications Manager) is completely
unresponsive.
–
A busy signal means that some device knew that the call could not be answered and responded
with a busy indication. This could mean that a device is down or that all resources (such as ports
on Cisco Unified MeetingPlace or bandwidth on a link) are in use.
with a busy indication. This could mean that a device is down or that all resources (such as ports
on Cisco Unified MeetingPlace or bandwidth on a link) are in use.
Solution
Step 1
Log into the CLI.
Step 2
To troubleshoot a previous call that occurred at a known time, enter one of the following commands,
specifying a start time (-b) shortly before the failed call attempt and a stop time (-e) shortly after the
failed call attempt:
specifying a start time (-b) shortly before the failed call attempt and a stop time (-e) shortly after the
failed call attempt:
•
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.
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.
troubleshooting issues around the start of a new calendar year.
Step 3
To troubleshoot a call in real time, complete these steps:
a.
Enter the following command:
eventlog -G -t
b.
Place a test call to the system.
Step 4
Read the log output to see how the system responds to the incoming call.
The following sample log output shows a successfully completed dial-in call:
[mpxadmin@example-server ~]$ eventlog -G -b 1030 -e 1040
07/15 10:36:43.14 P 0 RN MC s=013 mcpIncomingCallNotification