Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

In a multiserver environment, the primary MeetingPlace server hosts the web 
conference. Users on a secondary MeetingPlace server are redirected to the 
web conferencing server for the primary MeetingPlace server. MeetingPlace 
automatically accommodates all web conference participants in the entire 
multiserver meeting.

For example, if a multiserver meeting is being conducted between New York 
City and London and a participant on the New York City server initiates a web 
conference, everyone on the London server who wants to participate in the 
web conference has their IP connection directed to the New York City server. 
These users still use their user licenses on the London server for the voice 
conference, but use user licenses on the New York City server for the web 
conference.

This section answers common questions that users may ask when setting up 
and attending multiserver meetings.

When I am scheduling a multiserver meeting 
using MeetingPlace Web, what if I receive an 
error message that MeetingPlace Web cannot 
read the user profile?

This happens because the user probably does not have a 
user profile on the server they are trying to schedule. To 
solve this problem, create or import their user profile 
onto the server they are trying to schedule.

What if I want to schedule a meeting with 
MeetingPlace Web, but I do not see the 
Schedule Multiserver link?

This happens because of either of these: 

• The user does not have multiserver scheduling 

privileges. To solve this problem, set the Can Schedule 
Other Servers? parameter in their user profile to Yes.

• The user’s web browser is not supported. For browser 

requirements, see the scheduling requirements table in 

What if I am trying to schedule a meeting but 
I am unable to use the same meeting ID on 
each MeetingPlace server?

This happens if the user is trying to schedule a meeting 
between two or more networked MeetingPlace servers, 
or there is already another meeting scheduled at the same 
time on the same server with the same meeting ID. To 
solve this problem, have the user assign a different 
meeting ID to the meeting.

What if I am trying to schedule a meeting 
using MeetingPlace Web, but when I select a 
primary or secondary server I receive an 
error message that the server could not be 
accessed?

Check that the MeetingPlace conference server they are 
trying to access is connected to a MeetingPlace Web 
server. If it is not connected, users cannot schedule a 
meeting through their web browser.

What if I am in a multiserver meeting and the 
participants on another server can access an 
attachment that I cannot?

This happens because the person who added the 
attachment to the other server did not add the attachment 
to the server the user is connected to.