Cisco Cisco Unified MeetingPlace Audio Server メンテナンスマニュアル
9-10 Reservationless meetings
Cisco MeetingPlace Audio Server System Manager’s Guide
February 27, 2004
any phones or other terminals that may communicate directly with
MeetingPlace using SIP.
MeetingPlace using SIP.
A SIP phone that does not support the REFER method will not transfer
correctly and will not be able to attend meetings that require a transfer. In this
situation, users are asked to dial the phone number of the hosting server, as if
they entered an unrecognized meeting ID.
correctly and will not be able to attend meetings that require a transfer. In this
situation, users are asked to dial the phone number of the hosting server, as if
they entered an unrecognized meeting ID.
I
MPORTANT
•
As a system manager, you must ensure that all participating MeetingPlace
servers have synchronized user databases and that all user profiles for
active users are present on all systems. Use MeetingPlace Directory
Services to synchronize user databases across multiple 8112 or 8106
systems. The following fields in each user profile on all servers must be set
identically:
servers have synchronized user databases and that all user profiles for
active users are present on all systems. Use MeetingPlace Directory
Services to synchronize user databases across multiple 8112 or 8106
systems. The following fields in each user profile on all servers must be set
identically:
•
User ID
•
Scheduling Home Server
This assumes that profile numbers are assigned across the system (for
example, profile ID 1234 on servers A and B both refer to the same
person). This also assumes that either server can authenticate the user for
both servers.
example, profile ID 1234 on servers A and B both refer to the same
person). This also assumes that either server can authenticate the user for
both servers.
•
Passwords should be synchronized. If the password is not the same across
the system, the user will be provisionally authenticated (and must reenter
the password for access as a profile user after exiting the meeting). Also, if
users want to rerecord their name on a remote server, they will need to
know their password on that server. (For more information about
rerecording user names, see the next section,
the system, the user will be provisionally authenticated (and must reenter
the password for access as a profile user after exiting the meeting). Also, if
users want to rerecord their name on a remote server, they will need to
know their password on that server. (For more information about
rerecording user names, see the next section,
Enabling RSNA
To enable single number access, you must perform the following general
steps. (Details are described in the sections that follow.)
steps. (Details are described in the sections that follow.)
1.
Create an Other MeetingPlace Servers record for each remote server that
will participate in RSNA. (See
will participate in RSNA. (See
)
2.
Enable the system for RSNA, to turn on the RSNA transfer mechanism in
the voice user interface. (See
the voice user interface. (See
3.
Assign users or groups to servers who will use RSNA. (See