Polycom RealPresence 2000, Руководство администратора

Страница: 387 / 1130

Chapter 12-Polycom Conferencing for Microsoft Outlook®
Polycom, Inc.
12-7
• The RMX must be configured as a Static Route .
For more information see " Modifying the Default IP Network Service in the RealPresence
Collaboration Server 800s” on page 1-8 .
• The RMX’s Default Entry Queue must be configured as an Ad Hoc Entry Queue and must
be designated as the Transit Entry Queue .
For more information see the " Entry Queues” on page 7-1 .
• The meeting organizer can enable recording and/or streaming of the meeting.
• If meeting is to be recorded, the Ad Hoc Entry Queue must have recording enabled in its
Profile .
For more information see " Defining New Profiles” on page 2-27 .
• Meetings can be single instance or have multiple occurrences.
• Attendees that do not have video devices may be invited to the meeting.
• Attendees using e-mail applications that use the iCalendar format may be invited to
meetings via the Calendaring Service .
• Meeting invitations sent by Polycom Conferencing for Microsoft Outlook can be in a
different language to the RMX Web Client. The following languages are supported:
— English
— French
— German
— International Spanish
— Korean
— Japanese
— Simplified Chinese
• RMX resource management is the responsibility of the system administrator:
—
Conferences initiated by Polycom Conferencing for Microsoft Outlook are ad hoc
and therefore resources are not reserved in advance.
—
Polycom Conferencing for Microsoft Outlook Add-in assumes that sufficient
resources are available and does not check resource availability. Sufficient
resources are therefore not guaranteed.
—
A meeting invitation that is automatically accepted by the RMX is not guaranteed
availability of resources.
—
If the RMX runs out of resources, attendees will not be able to connect to their
conferences.
• By using DMA to load-balance resources between several RMXs, resource capacity can
be increased, alleviating resource availability problems.