Why can't I connect to a conference on a Telepresence Server using a Cisco CTS endpoint?
If a call does not connect successfully:
- Ensure that the Telepresence Server is registered with a SIP registrar (such as a Cisco VCS Control), with an appropriate domain specified. See the online help topic, System settings, for details.
- Ensure that Register numeric ID with SIP registrar is selected for the conference that you are trying to connect to.
- If you are using a Cisco VCS Control as a SIP registrar (as recommended), check that your CUCM and Cisco VCS deployments follow the guidelines in the document, VCS Deployment Guide - Cisco Unified Communications Manager (6.1 7 and 8) and Cisco VCS (X6).
- Ensure that the default bandwidth on the Telepresence Server is set to at least 1.25 Mbit/s. Cisco CTS calls disconnect at lower bandwidths.
If a call connects with audio but you do not receive video:
- Check that the call received by the Telepresence Server is a SIP call. If your configuration results in an H.323 call to the Telepresence Server (interworked from SIP by the Cisco VCS), then there will be no video. Check that your CUCM and Cisco VCS deployments follow the guidelines in the document: VCS Deployment Guide - Cisco Unified Communications Manager (6.1 7 and 8) and Cisco VCS (X6)
- Ensure that you have added a Cisco endpoint configuration on the Telepresence Server for your CTS endpoint with appropriate call-in matching parameters.
This article applies to the following products:
- Cisco Video Communication Server
- Cisco Telepresence Servers
|June 22nd, 2011||TAA_KB_658|