Polycom RealPresence 1500 Administrator's Manual page 52

● End-to-end latency on a local network (same site), is around 200msec to ensure AV sync (also known
as Lip-sync).
● Dial-out is not available in SVC Only conference.
● Dial-in is available as follows:
 AVC endpoints (participants) can only connect to an AVC conference or Mixed CP and SVC
conference. When dialing into SVC Only conferences they will be disconnected and the calls fail.
 SVC endpoints support both AVC and SVC video protocols:
When dialing into SVC Only conferences, they connect as SVC endpoints.
When dialing into AVC Only conferences, they connect as AVC endpoints. They cannot connect
to an AVC conference using the SVC capabilities.
● SVC endpoints can connect to conferences via Entry Queues, however:
 The Entry Queue and Conference Modes must match - both SVC Only or both Mixed.
 Both the Entry Queue and the Conference must have the same line rate.
● SVC endpoints cannot be moved between conferences.
● Content is supported in H.264 (AVC).
 Only the H.264 Cascade and SVC Optimized option is supported.
 LPR and DBA are not supported for SVC content sharing.
● In SVC Only conferences and Mixed CP and SVC conferences, Auto Layout is the default and the
layout display for SVC endpoints is controlled from the endpoint application.
● Site names display on SVC endpoints is controlled from the SVC endpoints.
● When a RealPresence DMA system is part of the solution:
 The DMA is used as the SIP proxy and the SVC endpoint subscribes to the RealPresence DMA
system for call control. If a RealPresence DMA system is not part of the solution, the SVC
endpoint dial directly to the Collaboration Server using IP addresses is the SIP dialing strings.
 It is recommended that all calls, both dial-in and dial-out, should originate from the DMA. This is
especially important in Mixed Mode where SVC endpoints receive a participant count from the
DMA in order to decide on layout and how many media streams they wish to receive. If
participants are dialed out from the conference, the call flow is not routed through the DMA
resulting in the participant count and layout information not being received.
● When Hot backup is enabled, all the conferences are created on the Slave MCU.
● When Hot Backup is activated and the Slave MCU becomes the Master MCU:
 All AVC endpoints will be reconnected to the AVC (CP and VSW) conferences. SVC endpoints
connected to AVC conferences using their AVC capabilities will be reconnected to their AVC
conferences.
 SVC endpoints cannot be reconnected to their SVC Only conferences as dial-out is not supported
for SVC endpoints. These endpoints will have to manually reconnect to their SVC conferences.
● Cascading between SVC Only conferences or between AVC and SVC Only conferences is not
supported.
● Gateway sessions are not supported for SVC calls.
● Reservations cannot be scheduled for SVC Only conferences.
● The following functionality and features are not supported during SVC Only conferences:
 FECC
Polycom®, Inc.
Conferencing Modes Overview
22