Cisco MeetingPlace Video Integration Administrator's Manual page 74

Problems Joining a Video Conference
If the participant is attempting to join on an ad-hoc basis, video resources cannot be guaranteed and
•
may not be available.
It is possible, though highly unlikely, that video ports may be unavailable, even if video ports have
•
been scheduled in advance. If this problem occurs frequently, consider reducing the number of
overbook ports you have specified. To set an optimal number of overbook ports, see
Configuring the Number of Overbook Ports, page
Verify that all connectivity is set correctly, all calls are routed to their intended destinations, and the
•
intended endpoint is reachable.
Check the eventlog.
•
See also other problem/solution sets in this section related to outdialing and dialing in.
•
Problem
Solution
Any of the items in the previous problem/solution set.
•
The problem may be temporary. Try again.
•
It is not possible to create an ad-hoc conference simply by dialing in to the Cisco IPVC MCU from
•
a video endpoint. The meeting must first be either in progress or scheduled in Cisco MeetingPlace.
To start an ad-hoc conference in Cisco MeetingPlace, see
Conferences, page
conference.
If the meeting requires a password, or is restricted to profiled or invited users, users must join the
•
meeting by outdialing from Cisco MeetingPlace Web Conferencing or from a
Cisco MeetingPlace for Outlook notification.
• The call may not have successfully reached its intended destination. Check your routing patterns.
For example, make sure the service prefix for Cisco MeetingPlace meetings is unique in the
Cisco IPVC MCU, and that the gatekeeper and Cisco CallManager have no initial strings that are
identical to or begin with this code. For example, if your service prefix is 87, make sure the
gatekeeper and Cisco CallManager do not have a routing instruction that routes all calls beginning
with 8* to an unintended destination.
Some endpoints may have a maximum dial string length that is shorter than the dial-in number.
•
Problem
Solution
Problem
message appears.
Solution
• The video endpoint must be running before the user attempts to join the video conference.
Cisco MeetingPlace Video Integration may be configured with the wrong E.164 number.
•
There may be no more ports available on the system.
•
The line to be outdialed to may be already in use (busy), not connected, nonexistent, entered
•
incorrectly, or configured incorrectly.
See also the items in the problem/solution set related to initiating or joining conferences.
•
Administrator's Guide for Cisco MeetingPlace Video Integration Release 5.3
6-6
Cannot dial in to meeting from the video endpoint.
Possible causes include the following:
5-6. After the Cisco MeetingPlace conference is in session, then initiate the video
Unable to outdial successfully to SCCP endpoints.
Make sure the technology prefix is correctly set in Cisco CallManager.
A user attempts to outdial to join the video conference but nothing happens, or an outdial failure
Chapter 6
4-8.
About Attending Ad-Hoc Video
Troubleshooting
(Optional)
OL-6280-01