Chapter 2-Conference Profiles
Polycom, Inc. 2-15
—Polycom SVC-enabled endpoints (Polycom® RealPresence® Desktop, Polycom®
RealPresence® Mobile)
—Ad Hoc conferencing via Meeting Rooms and ongoing conferences
• SVC Only conferences can run on the same MCU as AVC Only conferences.
• All the endpoints participating in a single SVC Only conference must be connected to
the same media card and cannot be handled by different media cards as the SVC media
streams cannot be shared between them.
• 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 CO
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 cannot connect to SVC Only conferences via Entry Queues.
• 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 DMA is part of the solution, the DMA is used as the SIP proxy and the SVC
endpoint subscribes to DMA for call control. If a DMA is not part of the solution, the
SVC endpoint dial directly to the Collaboration Server using IP addresses is the SIP
dialing strings.
• 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