Filter
Top Products
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing
Polycom, Inc. 3-29
The following table describes the number of allocated video resources for each video
resolution when using the RTV protocol.
Threshold HD Flag Settings using the RTV Video Protocol
The system flag MAX_ALLOWED_RTV_HD_FRAME_RATE defines the threshold Frame
Rate (fps) in which RTV Video Protocol initiates HD resolutions.
Flag values are as follows:
•Default: 0 (fps) - Implements any Frame Rate based on Lync RTV Client capabilities
•Range: 0-30 (fps)
For example, when the flag is set to 15 and the Lync RTV Client declares HD 720P at 10fps,
because the endpoint’s frame rate (fps) of 10 is less than flag setting of 15, then the
endpoint’s video will open VGA and not HD.
In another example, when the flag is set to a frame rate of 10 and the Lync RTV Client
declares HD 720P at 13fps, because the endpoint’s frame rate (fps) of 13 is greater than flag
setting of 10, then the endpoint’s video will open HD and not VGA.
Table 3-7 Allocated video resolutions per video resolution
Selected Video Resolution Number of Allocated Video Resources
HD720p 3
VGA 1.5
CIF 1
QCIF 1
If the MAX_RTV_RESOLUTION flag is set to AUTO dual core systems always view VGA. For more
information on Lync RTV Client capabilities, see , "Controlling Resource Allocations for Lync Clients
Using RTV Video Protocol” on page 3-27 for more information.
• Single core PC’s cannot view HD and always connect in VGA.
• Dual Core Processor - The threshold for flag settings on Dual Core systems is 13 (fps) and less
for viewing HD. When system flag is set to 14 (fps) or higher, the RTV Video Protocol shall
connect in VGA.
• Quad Core PC systems always view HD, even when flag settings are set anywhere from to 0-30.
• The number of resources used by the system to connect a Lync client with RTV is determined
according to the conference line rate and the maximum video resolution set in the Conference
Profile. For more information, see "Microsoft RTV Video Protocol Support in CP Conferences”
on page 3-24.