Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
Cisco MeetingServer 5.1 System Manager’s Guide
202
Cisco Systems
March 2003
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 would only send out notifications for participants
that had been invited to join the meeting on that server. Even though 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 would only send out notifications for participants
that had been invited to join the meeting on that server. Even though 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, you need to remember
to attach the same document to each server involved in the meeting. For
example, if you attached a document to the London and New York City
servers but forgot to attach it to the Hong Kong server, the participants on
the Hong Kong server would not be able to access the attachment.
to attach the same document to each server involved in the meeting. For
example, if you attached a document to the London and New York City
servers but forgot to attach it to the Hong Kong server, the participants on
the Hong Kong server would not be able to access the attachment.
Using MeetingTime to Schedule Multiserver Meetings
When scheduling a multiserver meeting using MeetingTime, do not assign
more than one primary server to the meeting.
more than one primary server to the meeting.
Before beginning, make sure your user profile exists on all the MeetingPlace
servers that are involved in the multiserver meeting and that you have
multiserver scheduling privileges on each profile.
servers that are involved in the multiserver meeting and that you have
multiserver scheduling privileges on each profile.
Part 1: Schedule a meeting on the secondary MeetingPlace
server
server
1.
Launch MeetingTime, and log in to the secondary server (the one to
receive a call from the primary server).
receive a call from the primary server).
2.
Open the Register Book, and click the Schedule tab.
3.
Fill in the meeting details, and add any necessary attachments.
Note: Make note of the meeting ID because this same number
should be used when scheduling the other MeetingPlace servers.
should be used when scheduling the other MeetingPlace servers.
4.
In the # of Calling Sites parameter, make sure to include the primary
server in this number. For example, if three people from different
locations are going to call into this server, this number should be four.
server in this number. For example, if three people from different
locations are going to call into this server, this number should be four.
5.
If you do not want to invite participants to this meeting, click Schedule
Meeting and go on to step 10. If you do want to invite participants, click
the Participants option button.
Meeting and go on to step 10. If you do want to invite participants, click
the Participants option button.
6.
Select the participants who will connect to this secondary server, and
click Add after each selection. For example, if you schedule a New
York City to London meeting in which London is the secondary server,
add only the participants who will call into the London MeetingPlace
server. Do not add the participants who will call into the New York
City MeetingPlace server.
click Add after each selection. For example, if you schedule a New
York City to London meeting in which London is the secondary server,
add only the participants who will call into the London MeetingPlace
server. Do not add the participants who will call into the New York
City MeetingPlace server.