This topic describes the endpoint registration options for the Cisco TelePresence Video Communication Server (VCS).
Required Cisco VCS Control configuration:
- Initial configuration is completed.
- H.323 or SIP protocol is activated.
Required endpoint configuration:
- IP address of Cisco VCS Control
- SIP URI for SIP
- H.323 ID for H.323
To register an endpoint with Cisco VCS, the following configuration is required:
- Initial configuration (system name, DNS, time, and so on) of Cisco VCS has been performed.
- H.323 or SIP or both are activated.
At the endpoints, you must configure the following:
- IP address of Cisco VCS (Registrar Server)
- The SIP URI of the endpoint when using SIP to register the endpoint with Cisco VCS
- The H.323 ID of the endpoint when using H.323 to register the endpoint with Cisco VCS
Some endpoints, such as Cisco Jabber Video for TelePresence, must be provisioned by Cisco TMS:
- Cisco VCS must be managed by Cisco TMS server.
- Cisco TMS Provisioning Extension must be installed on Cisco TMS.
Some endpoints, such as the Cisco Jabber Video for TelePresence (formerly known as Movi) software-based endpoint, require the Cisco TelePresence Management Suite (TMS) to register with Cisco VCS. They are not supported by Cisco VCS without Cisco TMS.
To support Cisco Jabber Video for TelePresence, Cisco VCS must be managed by Cisco TMS. Cisco TMS must control Cisco VCS to perform provisioning tasks on Cisco VCS. Cisco VCS must include a provisioning license.
On Cisco TMS, the Cisco TMS Provisioning Extension must be installed. The Cisco TMS Provisioning Extension is a Java-based application that runs on the Cisco TMS server. This application offers user and software-based device provisioning for Cisco VCS.