Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Page of 348
Multiserver meetings  8-7
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
5.
Click 
Save Changes
.
6.
Using MeetingTime, log on to the remote MeetingPlace server that you 
just created a profile for.
7.
Repeat steps 2 through 6 to create a Server Information record of your 
local MeetingPlace server on this remote server. Repeat this procedure 
until every server contains a Server Information record for every other 
MeetingPlace system.
Naming MeetingPlace servers
As a system manager, you can provide descriptive names to the MeetingPlace 
servers, which helps users identify which systems to schedule for a 
multiserver meeting. 
As you name servers, keep the following points in mind:
Make sure to:
Name each server with an easily identifiable name
Name all servers consistently across all MeetingPlace systems
(Optional) VoIP 
gateway IP address 2
IP address of a second remote server’s VoIP gateway, 
if there is one. (For more information, see 
Will accept SNA 
transfers?
Whether this server accepts single number access 
transfers. (For more information, see 
Ethernet address
12-digit (with leading zeros) hex string that represents 
the Ethernet address of a MeetingPlace server. A 
MeetingPlace server’s Ethernet address identifies 
itself to other MeetingPlace servers. This Ethernet 
address must match the Ethernet address that appears 
in the Server Configuration record (Configure tab) on 
the server this entry refers to.
Web Publisher 
location
IP address or the URL of MeetingPlace Web.  For 
MeetingPlace Web to function correctly, this field 
must contain the correct URL.
Data conference 
active?
If the server has the MeetingPlace Web Conferencing 
Option installed and MeetingPlace Web is operational, 
set this field to Yes. If the server does not have this 
option installed, set the field to No.
Server number
As a standalone server, the MeetingPlace conference 
server number is 0.
Field
Description