Cisco Cisco Unified MeetingPlace Audio Server メンテナンスマニュアル
Multiserver meetings 8-13
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
MeetingPlace server is the primary server, the connections look like the
following illustration.
following illustration.
Before scheduling a multiserver meeting, it is recommended that you write
down which servers are involved in the meeting and which server you want as
the primary server.
down which servers are involved in the meeting and which server you want as
the primary server.
Inviting participants and attaching documents
Because you schedule more than one MeetingPlace server, special
considerations need to be made when inviting participants and attaching
documents.
considerations need to be made when inviting participants and attaching
documents.
When inviting participants to a multiserver meeting, each server is
responsible for sending out its own notifications. In the previous example, the
New York City server sends out notifications for participants that were invited
to join the meeting on that server. Although the New York City server is the
primary server, it is not responsible for sending out notifications for the Hong
Kong and London servers.
responsible for sending out its own notifications. In the previous example, the
New York City server sends out notifications for participants that were invited
to join the meeting on that server. Although the New York City server is the
primary server, it is not responsible for sending out notifications for the Hong
Kong and London servers.
When attaching documents to a multiserver meeting, remember to attach the
same document to each server involved in the meeting. For example, if you
attach a document to the London and New York City servers but forget to
attach it to the Hong Kong server, the participants on the Hong Kong server
cannot access the attachment.
same document to each server involved in the meeting. For example, if you
attach a document to the London and New York City servers but forget to
attach it to the Hong Kong server, the participants on the Hong Kong server
cannot access the attachment.
Supported setup for a multiserver meeting