Release Notes

New features introduced in 4.0(1.57)
Cisco TelePresence Server Software Release Notes (4.0(2.8)) Page 11 of 36
Cisco TelePresence Conductor allocates screen licenses to calls based on the TelePresence Server's
reports of what the endpoints require.
The reports are affected by several factors:
n The Participant quality setting of the Conductor's conference template, provides an upper limit to the
number of screen licenses that can be allocated to a participant for video and audio
n The Content quality setting of the Conductor's conference template, which provides an upper limit to the
number of screen licenses that can be allocated to a participant for content (also known as 'extended
video'). TelePresence Server honors this limit when calculating the screen license requirement, so that
content quality does not suffer if the call is optimized down.
n The endpoint's advertized maximum resolution (behavior in previous releases; TelePresence Server's
response to this factor is not configurable)
n The endpoint's advertized receive bandwidth (new in this release; TelePresence Server's response to this
factor is now configurable via API)
You can define the participant quality and content quality settings in the conference template. When an
endpoint is joining the conference, the TelePresence Server negotiates with endpoints to calculate how many
screen licenses are required to fulfil the endpoint's request, within the limits provided by Conductor. The
TelePresence Conductor then grants those resources to the call.
Prior to this release, the TelePresence Server only considered the maximum resolution advertized by the
endpoints when doing this calculation. In this release, TelePresence Server calculates the resources
required for a particular call based on two aspects of the endpoint's advertized capabilities; the maximum
resolution (as previously) and the receive bandwidth. The TelePresence Server then chooses the lower of the
two resulting screen license requirements to report to Cisco TelePresence Conductor.
The benefit is more concurrent calls for the same number of screen licenses. The management
system can reclaim resources if a call does not have enough bandwidth to support the requested resolution.
In addition to limiting the Participant quality and Content quality, you can now choose how aggressively the
TelePresence Server pursues resource efficiency when considering the receive bandwidth, by setting the
optimizationProfile.
There are five settings for optimizationProfile; one that disables the feature, causing the TelePresence
Server to behave as it did in previous releases, and then four levels that control the balance between quality
of experience and efficiency of resources. The optimizationProfile parameter, which is passed to the
API during conference creation, takes one of the following values:
optimizationProfile
value
Description
maximizeEfficiency
Screen licenses are conserved aggressively. This value gives the most calls for the
available resources.
favorEfficiency
This is a balance of efficiency and experience that favors conserving screen licenses
over attempting to grant the requested resolution.
favorExperience
Default. This is a balance of efficiency and experience that favors granting the
requested resolution over conserving screen licenses.
Table 5: Optimization profiles enumerated type