TANDBERG MOVI 4.0 - ADMINISTRATOR GUIDE 10-2010 Administrator's Manual - Running Movi
Running Movi
TANDBERG Movi Administrator guide
Page 17 of 23
Running Movi
Movi is designed to be straight forward and easy to use, but as a highly versatile tool it also has many hidden
configurations and features of use to the administrator. This section details these options so that you as an
administrator will know how to make the most of these features. It also provides an overview of Movi’s
communication with the servers, which should help you identify which part of the process to troubleshoot if
you are experiencing issues with your setup.
Signing in
Movi will attempt to sign in to a VCS according to its Advanced settings, whether pre-configured or provided
manually. The sign-in stages are described below.
Subscribing to the VCS
Movi first attempts to subscribe to the VCS indicated by the Internal VCS field in the Movi Advanced
settings. If this fails, for example because the user’s computer is connected to the public internet and the
VCS is behind a NAT, Movi will try to subscribe to the VCS indicated by the External VCS field in the Movi
Advanced settings.
However, if the Internal VCS is a DNS address that translates to more than one IP address, Movi will
attempt to connect to all these IP numbers before trying the External VCS. If the DNS server contains SRV
records, Movi will adhere to the priority and weight of the IP addresses, otherwise they will be tried in random
order.
Typically, the VCS or the TMS Agent will challenge the first subscription message. Movi will answer this
challenge by sending another SUBSCRIBE message with the authentication information. After the
subscription has been authenticated, the TMS Agent will send provisioning information to the Movi client.
Registering to the VCS
Movi will register to the VCS according to the provisioning configuration in TMS; SIP Server URI or Public
SIP Server URI. If this provisioning configuration is identical to the Advanced setting in the Movi client
(recommended), Movi will register to the same VCS it subscribed to.
After initial registration, Movi will continue to send registration messages to the VCS according to the
Registration expire delta setting under VCS configuration > Protocols > SIP > Configuration. Movi will
send the message after 75% of the specified time interval has elapsed.
When Movi is registered to the VCS
After Movi has signed in, a number of tasks are performed continuously.
Presence
The presence status service is provided by the VCS. Movi publishes its own presence to the VCS and
subscribes to presence statuses for any contacts stored in the My contacts list. Subscribing to the presence
status of a contact informs the VCS that the client should be notified when the contact’s presence status
changes.
In Applications > Presence there are two settings that determine timeouts for the Presence server:
Subscription expiration time
Publication expiration time
Movi will subscribe and publish when 75% of the specified time intervals have elapsed.