Cisco Cisco Unified MeetingPlace Audio Server メンテナンスマニュアル
Reservationless meetings 9-9
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
Identifying profile and meeting ID conflicts
When migrating from standard scheduled meetings to combined scheduled
and reservationless meetings, a utility is available to help you identify profile
ID and meeting ID conflicts.
and reservationless meetings, a utility is available to help you identify profile
ID and meeting ID conflicts.
The command for this utility is
mtgconflicts
. When a conflict is found,
you see a list of conflicting meetings. To resolve the conflict, either keep the
scheduled meetings or change the meeting IDs.
scheduled meetings or change the meeting IDs.
N
OTE
You can run the mtgconflicts utility only when the system is down.
The following table describes the meeting conflicts commands.
About Reservationless Single Number Access
The Reservationless Single Number Access (RSNA) feature allows multiple
MeetingPlace audio servers to appear as one server to the user community. All
users who host (as a profile user) or attend (as a profile user or a guest) a
reservationless meeting can access their meeting by dialing the same phone
number, regardless of which audio server is hosting the meeting.
MeetingPlace audio servers to appear as one server to the user community. All
users who host (as a profile user) or attend (as a profile user or a guest) a
reservationless meeting can access their meeting by dialing the same phone
number, regardless of which audio server is hosting the meeting.
In previous releases, remote users had to know and dial the number of the
local server, which can be different for each meeting. With RSNA, users
always dial the number of their home server, which then transfers the call to
the scheduler’s (or host’s) home server. Except for a short delay, end users are
not affected by this feature.
local server, which can be different for each meeting. With RSNA, users
always dial the number of their home server, which then transfers the call to
the scheduler’s (or host’s) home server. Except for a short delay, end users are
not affected by this feature.
I
MPORTANT
This feature works only with IP and SIP phones. For more
information, see the next section,
RSNA requirements
RSNA requires that all voice communication with the MeetingPlace server
must use VoIP and SIP. Any PSTN or H.323 end points must go through a SIP
gateway to communicate with MeetingPlace. This implementation depends
on the use of the SIP “REFER method” call transfer mechanism, as specified
in RFC 3515. All participating SIP end points, including the MeetingPlace
VoIP gateway, any SIP gateways that communicate with MeetingPlace, and
must use VoIP and SIP. Any PSTN or H.323 end points must go through a SIP
gateway to communicate with MeetingPlace. This implementation depends
on the use of the SIP “REFER method” call transfer mechanism, as specified
in RFC 3515. All participating SIP end points, including the MeetingPlace
VoIP gateway, any SIP gateways that communicate with MeetingPlace, and
Command
Description
mtgconflicts
Reports any conflicts found
mtgconflicts –f
Returns a list of user profiles where a meeting
ID matches the profile ID
ID matches the profile ID
mtgconflicts –s
Returns the entire list of user profile ID and
meeting ID conflicts in a short format
meeting ID conflicts in a short format
mtgconflicts –v
Returns the entire list of user profile ID and
meeting ID conflicts in a verbose (long) format
meeting ID conflicts in a verbose (long) format