User manual TANDBERG TELEPRESENCE MOVI 4.1 ADMINISTRATOR GUIDE V4.1.1.9724

[. . . ] Cisco TelePresence Movi 4. 1 Administrator Guide D14410. 08 January 2011 Software version 4. 1. 1. 9724 Table of contents Introduction Prerequisites Infrastructure requirements PC requirements Mac requirements Multimedia device requirements Microphone Camera Deploying and upgrading the client Obtaining the setup files Configuring the client Advanced settings Using DNS Windows client pre-configuration Mac OS X client pre-configuration Distributing and installing the setup file New deployment Upgrading Upgrading to Cisco TelePresence Movi 4. 1 Default file locations Provisioning the client Uploading additional provisioning options to Cisco TMS Provisioning options Launching Movi calls from other applications Testing the protocol handler Use cases How communication works SIP communication Media communication 5 6 6 6 6 6 6 7 8 8 8 8 9 9 10 11 11 11 11 12 12 12 13 17 17 17 18 18 18 Cisco TelePresence Movi Administrator Guide (4. 1) Page 2 of 29 Port ranges Duo video­Binary Floor Control Protocol (BFCP) Traversal calls Media routing Media routing without ICE Media routing with ICE Enabling ICE Configuring Movi's TURN port Running the client Signing in Subscribing to the Cisco VCS Registering to the Cisco VCS Movi is registered to the Cisco VCS Presence SIP keep alive Losing connection Searching for a contact Call setup Encryption Sent and received bandwidth Resolution Video and audio standards Far-end camera control and ICE negotiation During a call Multiway initiation Muting media streams Automatic bandwidth adaptation Automatic CPU adaptation Conference information Checking for updates and getting help 18 19 19 19 19 19 19 20 21 21 21 21 21 21 22 22 22 22 23 23 24 24 24 25 25 25 25 25 25 27 Cisco TelePresence Movi Administrator Guide (4. 1) Page 3 of 29 References and related documents 28 Cisco TelePresence Movi Administrator Guide (4. 1) Page 4 of 29 Introduction Introduction This guide provides comprehensive information on Cisco TelePresence Movi, its capabilities and functions. Movi works in conjunction with other Cisco videoconferencing infrastructure products, primarily the Cisco TelePresence Video Communication Server (Cisco VCS), the Cisco TelePresence Management Suite (Cisco TMS) and provisioning. Some knowledge of these products is assumed in this document. The References and related documents section contains a list of documents referred to in this guide. [. . . ] Have the latest version of Cisco TelePresence Movi installed 2. Open a web browser (or a keyboard launch application such as Quicksilver or Launchy). In the input (URL) field, type a SIP URI, then hit Enter. Movi will now open and launch a call to the URI provided. Note: Adding "//" after the "movi:" and "sip:" protocols is not supported by the Movi protocol handler. Use cases n n n Add SIP URIs to default employee email signatures and vcards. Embed SIP URI links in intranet employee profiles, helpdesk contact pages, and similar. Integrate with any application that can send a protocol request to the operating system. Cisco TelePresence Movi Administrator Guide (4. 1) Page 17 of 29 How communication works How communication works This section includes general information on Movi's main types of communication and is essential for the subsequent section, which describes specific messages. SIP communication Movi communicates with the Cisco VCS using the Session Initiation Protocol (SIP). Subscribing, registering, presence querying, call invites--all communication except video and audio, is done in SIP. SIP messages are sent using TCP, with or without TLS encryption depending on the Transport configuration in the Advanced settings. The default SIP listening ports used on the Cisco VCS are n n 5060 (unencrypted) 5061 (encrypted) These are both configurable. Go to VCS Configurations > Protocols > SIP > Configuration to change the listening ports. Note: If you change the SIP listening port number on the Cisco VCS, you must also configure the Movi clients to contact the Cisco VCS on this port. See Advanced settings for more information. Movi itself will use ephemeral TCP ports for this communication. These ports are handed over to the Movi client by the TCP stack and are not configurable. To enable communication with endpoints and other devices that rely on H. 323 and do not support SIP, interworking on the Cisco VCS can be used. Media communication Media data is transferred through up to nine UDP links (ports). There are at most five media streams: n n n n n Audio Primary video Secondary video (presentation sharing) BFCP (management of presentation sharing/duo video, see below) Far end camera control (FECC) With the exception of BFCP, each of these streams requires two links: one link for RTP packets and one link for RTCP packets. The SRTP protocol is used if encryption is enabled. Port ranges The default port range for Movi to receive media is 21, 000-21, 900. This range is configurable in Cisco TMS: 1. Go to Systems > Provisioning > Directory. Add (or select) the configuration's Media Port Range Start and Media Port Range End. Note: A minimum range of 10 ports must be configured, or Movi will revert to default. [. . . ] New feature and maintenance releases are published regularly, and we recommend that your software is always kept up to date. If you experience any problems when configuring or using the product, consult the documentation at http://www. tandberg. com/support/video-conferencing-documentation. jsp for an explanation of how its individual features and settings work. You can also check the support site at http://www. tandberg. com/support/ to make sure you are running the latest software version. You or your reseller can also get help from our support team by raising a case at http://www. tandberg. com/support/. [. . . ]