Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Page of 314
Cisco MeetingServer 5.1 System Manager’s Guide   
 
                  60 
 
Cisco Systems 
 
March 2003 
Securing Meetings In Session 
During a meeting, a user can access the in-session meeting features and use 
the admittance options to control who can come into the meeting. The 
options are as follows: 
#21 
Takes a roll call of current participants 
#41 
Locks the meeting to prevent additional parties from joining the 
meeting without permission 
#42 
Admits an announced participant to the meeting 
#43 
Drops the last participant that enters the meeting 
Restricting Access to Meeting Recordings 
You can restrict a user’s ability to record meetings from the User Profile and 
User Groups topics in the Configure tab. When scheduling meetings you can 
determine whether access to recordings of certain meetings will be restricted 
to specific users or require a password. 
Restricting Vanity Meeting IDs  
When users schedule meetings, by default they may assign vanity (custom or 
common) meeting IDs, such as 1234. Although vanity meeting IDs are easier 
for meeting participants to remember and identify, you may want to restrict 
their use. Doing so adds a level of security and prevents unauthorized users 
or hackers from easily guessing the ID and gaining access to the meeting.  
To restrict vanity IDs:  
1.
 
In the Configure tab, select System Parameters.  
2.
 
For the Allow Vanity Mtg IDs field, choose No.  
MeetingPlace assigns a unique, randomly generated ID (which users can’t 
change) to every meeting scheduled from then on. 
When users are allowed to assign vanity IDs, you can add a level of security 
by restricting groups or individual users from assigning vanity IDs to 
meetings that are scheduled by phone. To do so:  
1.
 
In the Configure tab, select User Groups or User Profiles.  
2.
 
For the Can Chg Mtg ID via Phone field, choose No.  
User profiles inherit the group setting, but system managers can change 
the setting for individual users. 
 
Note: To protect meeting IDs that can be hacked easily (such as 
1234 or ABCD), create zero-port continuous meetings and 
assign those meeting IDs. Limit those meetings to invitees only, 
and don’t invite other people.