Cisco TelePresence Administrator's Manual page 255

Enhanced status reporting
in the VCS when it is operating in Provisioning Extension mode. Only limited status reporting is available
when the VCS is in legacy mode.
TMS Agent legacy mode
See TMS Agent (legacy)
TMS Provisioning Extension mode
Provisioning licenses
There is a limit to the number of devices that can be provisioned concurrently by the Provisioning Server.
VCS and TMS manage the number of available provisioning licenses by exchanging information through the
TMS Provisioning Extension Devices service. If the Devices service is not active, the VCS's Provisioning
Server will not be able to provision any devices.
The VCS is provided with the current number of free licenses available across the range of VCS clusters
being managed by TMS, and the VCS updates TMS with the status of provisioning licenses being used by
this VCS (or VCS cluster). License limits can be managed at a per device type basis.
Go to Status > Applications > TMS Provisioning Extension services > Device requests
n
summary status of the provisioning licenses that are available within your system.
Go to Status > Applications > TMS Provisioning Extension services > Provisioned device status
n
see a list of all of the devices that have submitted provisioning requests to the VCS's Provisioning Server.
Note that some devices, including Movi 4.x, do not inform the VCS when they sign out (unsubscribe) from
being provisioned. The VCS manages these devices by applying a 1 hour timeout interval before releasing
the license.
Provisioning and device authentication
The VCS's Provisioning Server requires that any provisioning or phone book requests it receives have
already been authenticated (the Provisioning Server does not do its own authentication challenge):
You must ensure that the Default Zone and any traversal client zone's Authentication policy is set to
n
either Check credentials or Treat as authenticated, otherwise provisioning requests will fail.
The authentication of phone book requests is controlled by the authentication policy setting on the Default
n
Subzone (or relevant alternative subzone) if the endpoint is registered (which is the usual case), or by the
authentication policy setting on the Default Zone if the endpoint is not registered. The relevant
Authentication policy must be set to either Check credentials or Treat as authenticated, otherwise phone
book requests will fail.
If the Authentication policy is set to Check credentials, then you must configure how the VCS checks the
credentials presented by an endpoint when it sends a provisioning request and when it registers. Device
credentials can be authenticated against the VCS's local authentication database, an LDAP directory if
remote authentication is selected, or via a direct connection to an Active Directory Service. See the
authentication section for more information about authentication policy settings.
Cisco VCS Administrator Guide (X7.1)
(Status > Applications > TMS Provisioning Extension
for information about provisioning via the legacy TMS Agent mode.
Applications
services) is available
to see a
to
device
Page 255 of 479