Ocs Relay; Provisioning - TANDBERG D14049.04 Administrator's Manual

Tandberg video communications server administrator guide
Table of Contents

Advertisement

Grey Headline (continued)
Status
The OCS Relay status page lists all the FindMe IDs being handled by the OCS Relay application,
and shows the current status of each.
The OCS Relay application is required in deployments that use both Microsoft Office Communicator
(MOC) clients and FindMe, if they both use the same SIP domain. Its purpose is to:
enable the VCS to share FindMe presence information with MOC clients
enable the Microsoft Office Communications Server (OCS) to forward calls to FindMe IDs.
To view the OCS Relay status page:
Status > Applications > OCS Relay
The OCS Relay application is configured from the OCS Relay page (Applications > OCS
Relay).
The page displays the following information:
Alias
The FindMe ID being handled by the OCS Relay application.
Presence state
Shows the presence information currently being published for the FindMe ID.
Registration state
Indicates whether the FindMe ID has registered successfully with OCS. Doing
so allows OCS to forward calls to the FindMe ID.
Subscription state
Indicates whether the OCS Relay application has subscribed successfully to
the FindMe ID's presence information. Doing so allows MOC clients to view
the presence information of FindMe users.
Overview and
System
Introduction
status
configuration
D14049.07
March 2010

OCS Relay

VCS
Zones and
configuration
neighbors
The Provisioning status page shows the status of the VCS's provisioning server.
The provisioning server provides basic device provisioning for registered Movi users, without the
need for TMS.
To view the Provisioning status page:
Status > Applications > Provisioning
The provisioning server is only available if the Starter Pack option key is installed.
The page displays the following information:
Server status
The state of the provisioning server.
Subscription
A summary of the subscription requests received by the server since the VCS
counters
was last restarted. It shows counts of:
Clustering and
Call
Bandwidth
peers
processing
control
29
TANDBERG

Provisioning

the total number of subscription requests received
how many requests were sent a successful provisioning response
failed requests because the account requesting provisioning could not be
found
failed requests because the account requesting provisioning had no
provisioned devices associated with it
Firewall
Applications
traversal
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Maintenance
Appendices

Advertisement

Table of Contents
loading

Table of Contents