162
D14049.07
March 2010
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
Login accounts
The
User accounts
page lists all the user accounts held in the VCS's local database and lets you
add, edit and delete accounts.
If you are part of a large enterprise with, for example, TMS managing several VCS clusters,
the database may contain details of users and devices in other VCS clusters. Different
clusters are distinguished by their
Cluster name
. You cannot modify the details of accounts
that are not managed in your cluster.
To go to the
User accounts
page:
•
Maintenance > Login accounts > User accounts
.
Click on the account you want to configure (or click
New
to create a new account, or click
Delete
to
remove an account).
Creating user accounts
Account details are divided into three sections: general user details, FindMe details and provisioning
details (the provisioning section only appears if the
Starter Pack
option key is installed).
Username
The account name. It is used (along with a password) by the user to log in to the VCS and configure
their FindMe details. The username cannot be changed after the account has been created.
If remote authentication is enabled, the username defined in the VCS must match the
username set up in the remote directory service.
Display name
A free-form display name for the user (rather than the user's
Username
or
FindMe ID
). It is used in
phone books and as the caller display name in SIP calls.
Phone number
The numeric caller ID presented when making an outbound call through an ISDN gateway.
To allow call return, this number could be configured to route to the associated FindMe ID by
mapping incoming numbers to the FindMe ID using ENUM, search rules or CPL. See the
TANDBERG
Deployment Guide - FindMe [29]
for more information.
Password
The password to be used, along with the
Username
, when logging into this account. Enter the
Initial
password
and then enter it again in the
Confirm password
field. Users can change their password
after they have logged in.
Note that passwords are case sensitive, and that the password fields are not shown if
Remote
authentication is enabled.
FindMe ID
The FindMe alias — the dialable address — by which the user can be contacted.
The FindMe ID can be any string of up to 60 characters. However, not all endpoints are able to dial
aliases with spaces or other non-alphanumeric characters so it is recommended that these are not
used in your FindMe IDs.
Principal device address
The address or alias of the user's first principal device. An administrator (or users themselves) can
add more endpoint addresses after the account has been created.
Note that if the
Starter Pack
option key is installed, you can choose whether the address of the
user's principal device should be set to the default device URI (which follows the same format as
the
Provisioned device URI
) or whether to enter an alternative address.
FindMe type
Specifies if the account is for an individual person or a group of people, and affects how calls are
diverted when endpoints in the user's primary list are busy.
Individual
: calls immediately divert if any primary endpoint is busy.
Group of people
: calls immediately divert only if all primary endpoints are busy.
If the
Starter Pack
option key is installed all FindMe IDs are created as
Individual
accounts.
Provisioning
This section is used to enable or disable basic device provisioning for this user if the
Starter Pack
option key is installed. Currently, provisioning is limited to registered Movi users.
By default,
Provision this user
is set to
On
which enables provisioning for the shown device URI.
The format of the
Provisioned device URI
is <username>.<device type>@<FindMe ID domain> and
cannot be changed.
If
device authentication
using a local database is enabled, authentication credentials for the
provisioned devices must also be set up in the local authentication database. The credential
name must be the same as account username and the credential password must be the
same as the password configured on the provisioned device.
Maintaining user accounts
