Cisco Cisco Unified MeetingPlace Audio Server 관리 매뉴얼
Cisco MeetingServer 5.1 System Manager’s Guide
193
Cisco Systems
March 2003
Creating Server Information Records for MeetingPlace Servers
Before two MeetingPlace servers can connect, each server must have
information about the other server entered into its database. Just as profiles
identify MeetingPlace users, each server must have a Server Information
record to identify it to the other servers.
information about the other server entered into its database. Just as profiles
identify MeetingPlace users, each server must have a Server Information
record to identify it to the other servers.
For example, in a New York City to London multiserver meeting, the New
York City MeetingPlace server must have in its database a Server
Information record for the London MeetingPlace server, and vice versa.
York City MeetingPlace server must have in its database a Server
Information record for the London MeetingPlace server, and vice versa.
Note: You must contact the system managers of the remote
MeetingPlace servers to obtain the correct information about
their server. This information is explained in Table 8-4.
MeetingPlace servers to obtain the correct information about
their server. This information is explained in Table 8-4.
To create a Server Information record on your local server for a remote
MeetingPlace server:
MeetingPlace server:
1.
Using MeetingTime, log in to your local MeetingPlace server.
2.
Open the Register Book, and click the Configure tab.
3.
Under the System Configuration heading, select the Other MeetingPlace
Servers topic (Figure 8-3).
Servers topic (Figure 8-3).
Figure 8-3 Creating a Server Information Record
4.
Click New.
5.
Enter the information for the remote server in the fields provided. These
fields are explained in Table 8-4.
fields are explained in Table 8-4.