Cisco TELEPRESENCE MOVI 4.1 - ADMINISTRATOR GUIDE... Service manual

Cisco TelePresence Movi
4.1
Administrator Guide
D14410.08
January 2011
Software version 4.1.1.9724

Cisco TelePresence Movi Administrator Guide (4.1) Page 2 of 29
Table of contents
Introduction 5
Prerequisites 6
Infrastructure requirements 6
PC requirements 6
Mac requirements 6
Multimedia device requirements 6
Microphone 6
Camera 7
Deploying and upgrading the client 8
Obtaining the setup files 8
Configuring the client 8
Advanced settings 8
Using DNS 9
Windows client pre-configuration 9
Mac OSX client pre-configuration 10
Distributing and installing the setup file 11
New deployment 11
Upgrading 11
Upgrading to Cisco TelePresence Movi 4.1 11
Default file locations 12
Provisioning the client 12
Uploading additional provisioning options to Cisco TMS 12
Provisioning options 13
Launching Movi calls from other applications 17
Testing the protocol handler 17
Use cases 17
How communication works 18
SIP communication 18
Media communication 18

Cisco TelePresence Movi Administrator Guide (4.1) Page 3 of 29
Port ranges 18
Duo video–Binary Floor Control Protocol (BFCP) 19
Traversal calls 19
Media routing 19
Media routing without ICE 19
Media routing with ICE 19
Enabling ICE 19
Configuring Movi's TURN port 20
Running the client 21
Signing in 21
Subscribing to the Cisco VCS 21
Registering to the Cisco VCS 21
Movi is registered to the Cisco VCS 21
Presence 21
SIP keep alive 22
Losing connection 22
Searching for a contact 22
Call setup 22
Encryption 23
Sent and received bandwidth 23
Resolution 24
Video and audio standards 24
Far-end camera control and ICE negotiation 24
During a call 25
Multiway initiation 25
Muting media streams 25
Automatic bandwidth adaptation 25
Automatic CPU adaptation 25
Conference information 25
Checking for updates and getting help 27

Cisco TelePresence Movi Administrator Guide (4.1) Page 4 of 29
References and related documents 28

Introduction
Cisco TelePresence Movi Administrator Guide (4.1) Page 5 of 29
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.
Cisco TelePresence Movi for Windows is a certified Windows 7 application.

Prerequisites
Cisco TelePresence Movi Administrator Guide (4.1) Page 6 of 29
Prerequisites
Infrastructure requirements
Movi requires the Provisioning option on the Cisco VCS and in Cisco TMS to be enabled.
Product Version
Cisco TelePresence Management Suite (Cisco TMS) 12.6 or later recommended
Cisco Video Communication Server (Cisco VCS) X5.2 or later recommended
PC requirements
Processor A processor supporting SSE3 (such as Pentium 4 Prescott) or better. For business-quality HD
video, Cisco recommends using the Cisco PrecisionHD™ USB camera and a 2 GHz Core 2
Duo processor or better.
Memory 512MB RAM or more.
Operating
system
nWindows XP SP2 or later
nWindows Vista SP1 or later
nWindows 7
Connection IP network connection (broadband, LAN, wireless). At least 24 kbps is required for an audio
connection. For a video connection, the recommended minimum is 128 kbps.
Graphics
card
OpenGL version 1.2 or higher. Hardware support for DirectX 8 or higher.
Sound card Any standard sound card (full-duplex, 16-bit or better) should work with Movi.
Mac requirements
Processor All Intel processors. For business-quality HD video, Cisco recommends using the Cisco
PrecisionHD™ USB camera and a 2 GHz Core 2 Duo processor or better.
Operating
system
Mac OSX 10.6 or later is recommended. Make sure to have the latest security updates installed.
Connection IP network connection (broadband, LAN, wireless). At least 24 kbps is required for an audio
connection. For a video connection, the recommended minimum is 128 kbps.
Multimedia device requirements
Microphone
All microphones work well with Movi. Note that some cameras have built-in microphones.

Prerequisites
Cisco TelePresence Movi Administrator Guide (4.1) Page 7 of 29
Camera
Movi works with most common web cameras. See the Cisco Knowledge Base for updated information
on Movi and cameras.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 8 of 29
Deploying and upgrading the client
This section describes the process of deploying and upgrading the Movi client and details the pre-
configuration options that are available and the settings required for Movi to operate.
Note: Before provisioning, Cisco TMS and Cisco VCS must be configured appropriately. See the
Provisioning Deployment Guide available on our website for detailed information.
Obtaining the setup files
When a new version of Movi is available, you will get a Cisco TMS ticket if:
1. Automatic update checking is enabled. To do this:
a. In Cisco TMS, go to Administrative Tools > Configuration > Network Settings.
b. Under Automatic Software Update, set Automatically Check for Updates to Yes.
2. Cisco TMS Agents are enabled. To do this:
a. In Cisco TMS, go to Administrative Tools > Configuration > General Settings.
b. Set Enable TMS Agents to Yes.
The description field of the Cisco TMS ticket includes a link to a .zip archive containing the files
described below.
File name Description
Movi<version>.msi For organizations creating their own Movi installer for Windows
MoviSetup<version>.exe Ready-made installer for Windows containing the .msi file
MoviSetup<version>.dmg Application bundle for Mac OSX
MoviProvisioningConfigTemplate<version>.xml Adds Movi provisining configurations to Cisco TMS. See the
Provisioning the client section for more information.
Cisco_TelePresence_Movi_Release_Notes_
<version>.pdf
Software release notes describing the changes from the last to
the current version of Cisco TelePresence Movi.
Configuring the client
This section describes and recommends configuration settings. Cisco recommends that you create an
installation file that will install Movi with the Advanced settings pre-configured, as described in the
sections Windows client pre-configuration and Mac OS X pre-configuration below.
Advanced settings
Network communication settings are also available by clicking Advanced in Movi's sign-in window.
Setting Description
SIP
Domain
Identical to the SIP domain configured on the Cisco VCS, in VCS configuration >
Protocols > SIP > Domains.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 9 of 29
Setting Description
Internal
VCS
The DNS address of the Cisco VCS Control cluster you want to connect to. Movi will
always look for this address first when connecting. It is possible to specify which port
on the Cisco VCS Movi should connect to. For example
InternalVCS.example.com:5063.
External
VCS
The DNS address of the Cisco VCS Expressway cluster you want Movi to connect to.
If Movi fails to connect to the Internal VCS, it will try this address. It is possible to
specify which port on the Cisco VCS Movi should connect to. For example
ExternalVCS.example.com:5063.
Transport Determines the transport layer used when connecting to the Cisco VCS. The options
available are Auto,TLS, and TCP. See the section on Call setup for more
information.
Using DNS
Movi can use IP or DNS addresses to locate the Cisco VCSs.
Using DNS addresses offers advantages such as:
nRedundancy: if you have more than one Cisco VCS, using a DNS that translates to the IP address of
all Cisco VCSs will enable Movi to "fail over" to other Cisco VCSs in case of a fault in one Cisco VCS.
nLocation awareness: for global companies, it is possible to configure the DNS servers so that Movi will
be directed to the "local" Cisco VCS wherever it may be.
nFlexibility: using DNS makes it possible to change the IP address of your Cisco VCS later on.
Movi also supports DNS SRV records, which allow for even greater redundancy and flexibility because
they contain information such as "Priority" and "Weight".
Windows client pre-configuration
Registry settings
Movi registry keys can be used to preconfigure the client. They are located at:
nHKEY_LOCAL_MACHINE\Software\Cisco\Movi\2.0 – default settings for all users
nHKEY_CURRENT_USER\Software\Cisco\Movi\2.0 – settings for a specific user
Note: The Movi 2.x registry keys are valid for all later releases. This means that upgrading does not
require setting the registry keys again.
The following is an example of how to set the registry keys:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Software\Cisco\Movi\2.0]
"InternalVcs"="internal.provserver.com"
"ExternalVcs"="external.provserver.com"
"Domain"="example.com"

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 10 of 29
Running the installer with special arguments
Any installer needs to run MsiExec.exe in order to install the Movi client. In addition to the arguments
that are innate in MsiExec.exe, there are also special arguments that can be given to MsiExec.exe and
pre-set the client.
Argument Description
DOMAIN Corresponds to SIP Domain in the Advanced settings.
EXTERNALVCS Corresponds to External VCS in the Advanced settings.
INTERNALVCS Corresponds to Internal VCS in the Advanced settings.
ENCRYPTIONPOLICY Corresponds to Transport in the Advanced settings.
HIDEADVANCEDLOGIN A value of 1hides the Advanced settings link in the Movi client sign-in screen.
Cisco recommends using this setting so that end users will not be able to make
changes to the Advanced settings.
USEWINDOWSUSERNAME A value of 1has the following effects:
nMovi uses the current Windows user's logon name as username
nThe Username and Password fields are disabled.
nThe Remember my Username/Password check boxes in the login window
are selected and disabled.
nThe Forget me link is disabled.
For information on how to disable authentication on the Cisco VCS and Cisco
TMS Agent, contact your support representative.
The MoviSetup.exe file supplied by Cisco is a basic InstallShield-generated installer.
MoviSetup.exe can be run with standard InstallShield switches, such as
n/s for a silent install
n/x for performing an uninstall
MoviSetup.exe can also be run with arguments on the format /v"<arguments>". MoviSetup.exe will
then run MsiExec.exe with these arguments.
A /v option argument on the form UPPERCASE=value will set the "UPPERCASE" property to that
value.
For example, from the command line or script, run:
MoviSetup.exe /s /v"/qn DOMAIN=example.com
HIDEADVANCEDLOGIN=1"
n/s is a basic InstallShield switch that hides the initialization dialog.
n/v"arguments" passes the arguments to the MsiExec.exe that is actually performing the install.
n/qn is a basic MsiExec.exe switch, an instruction to install silently.
nDOMAIN=example.com sets the SIP Domain field in the Advanced settings of the Movi client to
example.com.
nHIDEADVANCEDLOGIN=1 hides the Advanced settings link in the Movi client sign-in screen.
Mac OSX client pre-configuration
The Movi client for Mac OS X can be preset by installing Movi and setting the Preferences file.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 11 of 29
This file is stored at ~/Library/Preferences/com.Cisco.Movi.plist
Preferences may be configured by using the defaults tool. A configuration command will have this
format:
defaults write/delete com.tandberg.Movi <Preference> <value>
The ‘write’ command will set the <Preference> to the <value>, where the value can be either a string or a
number. The number ‘0’ means ”false” while the number 1 means “true”.
For example, set your Advanced settings by starting Terminal and typing:
defaults write com.tandberg.Movi InternalVcs internal.provserver.com
defaults write com.tandberg.Movi ExternalVcs external.provserver.com
defaults write com.tandberg.Movi Domain example.com
Distributing and installing the setup file
Please note that installing Movi requires administrative rights on the computer.
New deployment
For new deployments, Cisco recommends that you use your own deployment tools.
To distribute to end users, you can send a customized email message from TMS:
1. Go to Systems > Provisioning > Directory.
2. In the Workspace pane, click Send Account Info.
3. In the dialog that opens, click Configure email settings.
4. Verify that SMTP host, username, and password have been added correctly, or add them yourself.
5. Choose a suitable subject for the email notification.
6. By default, this email message will contain login credentials for Movi and Cisco TelePresence System
E20. If you want users to download and install Movi themselves, you can add the download link to the
same message.
Upgrading
The process of upgrading Movi is controlled by the IT administrator through two Provisioning options in
Cisco TelePresence Management Suite: Software URL and Software Version.
When these two options are correctly configured, users can upgrade their own Movi client by clicking a
link in the application, which downloads the setup file for the new version.
This method presents users with a choice to upgrade their Movi client. If you want to make absolutely
sure that all clients are upgraded, you can instead opt to use your deployment tool(s) to force the
upgrade.
Upgrading to Cisco TelePresence Movi 4.1
Due to the changes in product name and brand, the Movi 4.1 installer will make some changes to
previous installations. The installer will uninstall whichever previous version of Movi is present on the
system, and the program file and icons are completely removed. However, all profile folders and files are
kept intact on uninstall.
Movi will then install itself to the program file paths described under File locations.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 12 of 29
When Movi is launched:
nWindows: Existing profile folders and registry settings are renamed from ~\TANDBERG\~ to
~\Cisco\~.
nMac OS X: The com.tandberg.Movi.plist file is renamed to com.cisco.Movi.plist
Note: Movi 4.1 will also install itself as the operating system's default SIP protocol handler, see the
section Launching Movi from other applications.
Default file locations
Files Windows location Mac OSX location
Program file nWindows Vista and 7 (64 bit): %Program Files
(x86)%\Cisco\
nWindows Vista and 7 (32 bit) : %Program Files%\Cisco\
nWindows XP: ~\Program Files\Cisco\
\Applications\Cisco
TelePresence Movi
Contacts and recent
calls
%APPDATA%\Cisco\Movi\2.0 \Library\Application
Support\Movi
Log files for
debugging
purposes
<CSIDL_LOCAL_APPDATA>\Cisco\Movi\2.0\Logs\.
The <CSIDL_LOCAL_APPDATA> directory is hidden by
default and can be found at
nWindows XP: %USERPROFILE%\Local
Settings\Application Data\
nWindows Vista and Windows 7: %LOCALAPPDATA%
(typically %USERPROFILE%\AppData)
\Library\Logs\Movi
For each user signing in, Movi creates a new folder and files; therefore several people can use the client
on the same computer without having access to each others’ contact list and recent calls information.
Provisioning the client
Upon subscribing to the Cisco VCS, the Movi client will receive provisioning information from the Cisco
TMS Agent and act on it. Provisioning is a powerful tool for the administrator to control the Movi clients.
The following table details the provisioning options available, including tips on how they can be used and
in which situations.
To access the Cisco TMS provisioning configurations, go to Systems > Provisioning > Directory and
the Configurations pane.
Uploading additional provisioning options to Cisco TMS
In Cisco TMS version 12.6 and later, the link Manage Configuration Templates is available below the
Configurations pane. To add Provisioning options for Movi 4.0 and later to TMS:
1. Go to Systems > Provisioning > Directory.
2. Click Manage Configuration Templates.
3. In the dialog box that opens, click the button Upload New.
4. Locate the MoviProvisioningConfigTemplate.xml file on your computer (see the Obtaining the
setup files section).
5. Click Open, and the template will be uploaded to Cisco TMS.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 13 of 29
Note: For more on managing provisioning templates, see the Provisioning deployment guide.
Provisioning options
The "Default" column in the table below describes how Movi behaves if no specific provisioning
information is configured.
Note: Some settings are only available in TMS 12.6 or later, after uploading the
MoviProvisioningConfigTemplate.xml file, as described above. See the “Description” column.
Field Default Description
ClearPath Off ClearPath is a Cisco TelePresence solution that minimizes
the negative effects of packet loss in a non-optimal network.
Among the mechanisms used are H.264-specific error
recovery techniques, feedback from decoders and forward
error correction (FEC).
Both call participants must support ClearPath for it to take
effect.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
Default Mediatype
Candidate
Host The address to use before ICE has completed, if ICE fails or
if the remote side does not understand ICE. The available
options are:
nHost
nRflx
nRelay
Relay is the recommended setting if changing the default.
This is typically needed when Movi is deployed in
environments where most other endpoints do not
understand ICE. See the Enabling ICE section.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
Enable Far End
Camera Control
On This setting lets Movi control far end cameras, when allowed
by the far end.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
Enable ICE Off Interactive Connectivity Establishment (ICE) dynamically
discovers the best possible path for media to travel between
call participants.
See the Enabling ICE section for more information on what
is required to enable this setting.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 14 of 29
Field Default Description
Enable MNS Mode Off Enabling this option forces relayed media to be relayed via
private HD links with guaranteed capacity to ensure quality
of video.
This setting relies on ICE being enabled. Private dedicated
links are provided by companies such as Media Network
Services.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
Encryption Depends on the
Transport configuration
in the Advanced settings
of the Movi client, which
is Auto by default.
Determines the encryption policy for the account. This
configuration affects both the SIP communication (Transport
TLS or TCP) and the media communication (SRTP or no
SRTP).
See the Call setup section for more information.
Maximum In
Bandwidth
512 kbps (adjustable to
up to 2014 kbps from
within the client)
Determines the maximum bandwidth that can be
received/sent by the account. The Movi client will be set to
send the provisioned value. With no provisioning, the default
starting level is lower than the maximum that can be set by
the user.
High bandwidth is directly related to good video quality, but
bandwidth control can be useful to prevent a client from
trying to receive/send beyond its capacity, as this may result
in packet loss, jitter and general low video quality.
Maximum Out
Bandwidth
384 (adjustable to up to
2014 kbps from within
the client)
Media Port Range
End
21900 The upper/lower bound of the port numbers that that are used
in the video and audio communication.
These can be configured to control security/firewall issues. A
range of minimum 10 ports must be provisioned, or Movi will
revert to default.
Media Port Range
Start
21000
Multiway
Participant URI
When Multiway is initiated, participants are directed to this
Uniform Resource Identifier (URI). See the Multiway
Initiation section for more information.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
Phone Book Uri If no value is set, the
Movi client will not be
able to search for
contacts.
Enables the account to search for other accounts in the
Cisco TMS Agent database.
This configuration should be a URI on the form:
phonebook@<sip_domain>.com

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 15 of 29
Field Default Description
Presence Server
Uri
If no value is set, the
Movi client will not be
able to publish presence
and appear offline.
Enables the account to send presence status.
This configuration should be a URI on the form:
presence@<sip_domain>.com
Public Default
Mediatype
Candidate
Host The address to use before ICE has completed, if ICE fails or
if the remote side does not understand ICE. The available
options are:
nHost
nRflx
nRelay
Relay is the recommended setting if changing the default.
Public Maximum In
Bandwidth
Uses the value set for the
Maximum In Bandwidth
configuration (changes
dynamically).
Determines the maximum bandwidth that can be
received/sent by the account after connecting to the external
Cisco VCS configured in Movi's Advanced settings.
The settings may be useful for controlling the bandwidth of
users that connect from outside of the company’s network.
These users may have slow network connections, or the
company may want to limit their bandwidth usage.
Public Maximum
Out Bandwidth
Uses value set for the
Maximum Out Bandwidth
configuration (changes
dynamically).
Public Phone Book
Uri
Uses value set for Phone
Book Uri (changes
dynamically).
Enables the account to search for other accounts in the
Cisco TMS Agent database after connecting to the external
Cisco VCS configured in Movi's Advanced settings.
It is sufficient to set the Phone Book Uri configuration.
Public Presence
Server Uri
Uses value set for
Presence Server Uri
(changes dynamically).
Enables the account to send presence status after
connecting to the external Cisco VCS configured in Movi's
Advanced settings.
It is sufficient to set the Presence Book Uri configuration.
Public SIP Server
Address
Uses value set for SIP
Server Address
(changes dynamically).
Address of the server to which the user should send a
register request after connecting to the external Cisco VCS
configured in Movi's Advanced settings.
Generally, this configuration should be the same as
External VCS in the Movi Advanced settings.
Resolution
Preferences
High The highest possible value of the video resolution setting in
the Movi client.
Clients using old computers may need to lower the
resolution to ensure the Movi client runs smoothly.
SIP Keep Alive
Interval
24 seconds The interval at which SIP Keep Alive messages are sent.
For more information, see the Movi is registered to the Cisco
VCS section.

Deploying and upgrading the client
Cisco TelePresence Movi Administrator Guide (4.1) Page 16 of 29
Field Default Description
SIP Server Address The SIP server (Cisco
VCS) that the client
subscribed to.
Address of the server the user should send a register
request to.
Should be the same as the Internal VCS configuration in the
Movi Advanced settings.
Software URL URL linking to the setup file for the new version of the Movi
client.
The combination of this and the Software Version setting
allows the administrator to inform Movi users that a new
version is available, and provide a clickable link from within
the client to the setup file.
Software Version Indicates the version number of the new Movi client (the
version that the users will have once they have upgraded),
including software build number. The build number is
indicated both in the release notes and in the About box in
Movi's settings.
TurnAuthPassword TURN server settings that are required for enabling ICE. See
the Enabling ICE section for more information.
This setting is only available in TMS 12.6 or later after
uploading the MoviProvisioningConfigTemplate.xml file.
TurnAuthUsername
TurnServer

Launching Movi calls from other applications
Cisco TelePresence Movi Administrator Guide (4.1) Page 17 of 29
Launching Movi calls from other applications
Movi will install itself as the default SIP protocol handler on the operating system. As long as Movi
remains the default SIP client, activating any SIP URI link will launch a call from Movi.
It is also possible to use "movi:" as the protocol rather than "sip:". This will ensure that Movi is always
used even if another SIP client is the system default.
Testing the protocol handler
1. Have the latest version of Cisco TelePresence Movi installed
2. Open a web browser (or a keyboard launch application such as Quicksilver or Launchy).
3. 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
nAdd SIP URIs to default employee email signatures and vcards.
nEmbed SIP URI links in intranet employee profiles, helpdesk contact pages, and similar.
nIntegrate with any application that can send a protocol request to the operating system.

How communication works
Cisco TelePresence Movi Administrator Guide (4.1) Page 18 of 29
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
n5060 (unencrypted)
n5061 (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:
nAudio
nPrimary video
nSecondary video (presentation sharing)
nBFCP(management of presentation sharing/duo video, see below)
nFar 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.
2. 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.
The default port range used on the Cisco VCS is 50,000-52,399. To configure:

How communication works
Cisco TelePresence Movi Administrator Guide (4.1) Page 19 of 29
1. Go to VCS Configuration > Local zone > Traversal subzone.
2. Set the Traversal media port start and Traversal media port end.
Note that in both cases, the port numbers used will be consecutive, but chosen randomly within the
specified range.
Duo video–Binary Floor Control Protocol (BFCP)
Movi supports BFCP for handling the control of duo video. BFCP communication can be sent over a
UDP or a TCP link. Movi uses the same ports as for audio and video for this communication.
On the Cisco VCS, a port will be chosen at random from the same range that has been assigned to the
media links.
Traversal calls
Media links can be established directly between the two endpoints in non-traversal calls, or between
Movi and the Cisco VCS in traversal calls. As a general rule, non-traversal calls are defined as calls
between two participants that are on the same network and do not require interworking.
Note that SIP to H.323 calls require interworking and are therefore traversal calls irrespective of whether
the endpoints are on the same network. For detailed information, see the latest Cisco VCS Administrator
guide.
Media routing
Cisco TelePresence Movi supports Interactive Connectivity Establishment (ICE) for better media
routing. ICE will be used if enabled both in Movi and the far end.
Media routing without ICE
When the ICE protocol is used in a call, media links are established directly between the two endpoints
in non-traversal calls, or between Movi and the VCS in traversal calls. As a general rule, non-traversal
calls are defined as calls between two participants that are on the same network and that don’t require
interworking.
Note that SIP to H.323 calls require interworking and are therefore traversal calls irrespective of whether
the endpoints are on the same network. For detailed information, see the latest VCS Administrator
Guide.
Media routing with ICE
ICE dynamically discovers the best possible path for media to travel between call participants.
It is possible to further improve the routing of media and force it through dedicated links by using the
Enable MNS Mode Provisioning configuration.
Enabling ICE
Media routing using ICE requires a TURN server. VCS Expressway running version X5.2 or later can
function as a TURN server if it has TURN Relay licenses. Having the TURN server option key is
required.

How communication works
Cisco TelePresence Movi Administrator Guide (4.1) Page 20 of 29
To start setting up the Cisco VCS Expressway, go to VCS configuration > Expressway > TURN and
configure the fields as described below.
Setting Change to
TURN services On
Port 3478
Media port range start 60000
Media port range end 61399
To finish setup on the Cisco VCS Expressway:
1. Go to VCS configuration > Authentication > Devices > Configuration and set the Database type
to LocalDatabase.
2. Go to VCS configuration > Authentication > Devices > Local database and create a username
and password. The username and password are necessary to allow for use of TURN Relay licenses.
The Movi client is provisioned with the username and password as described below.
To enable ICE on the Movi client, go to Systems > Provisioning > Directory and the Configurations
pane for Movi, then update the fields as described below.
Setting Change to
Enable ICE On
TurnAuthPassword Password created when setting up the Cisco VCSExpressway
TurnAuthUsername Username created when setting up the Cisco VCSExpressway
TurnServer The address of the server media is relayed through in an “ICE call”, typically the
address of the Cisco VCS Expressway
Note: The ICE Provisioning configurations are not available by default. See the Provisioning section for
more information.
Configuring Movi's TURN port
TURN port configuration should be controlled through DNS. Movi will do an SRV lookup for the TURN ip,
pri, weight, and port. As TURN runs over UDP, the lookup will be for _turn._udp.<domain>. If no
SRV record for TURN is found, Movi will perform an A record lookup (IPv4) or an AAAA lookup (IPv6),
but will default to port 3478.
If the port needs to be provisioned, you can append it to the IPaddress in the TurnServer field, for
example 192.0.2.0:3478.