Cisco Cisco MeetingTime Quick Setup Guide

As a system administrator, you can restrict Cisco Unified MeetingPlace from accepting certain meeting 
ID patterns that you consider unsecure. For example, you can restrict meeting ID patterns that repeat the 
same digit three times in a row, such as 111 or 222.

Keep the following points in mind when determining which meeting ID patterns to restrict:

Restricted meeting ID patterns affect both numerical and vanity meeting IDs. Therefore, if you 
select to restrict patterns that repeat the same digit three times, Cisco Unified MeetingPlace will 
disallow both the numerical meeting ID “333” and the vanity meeting ID “deepdive,” because 
“deepdive” translates to 3337383.

Keep the length of your minimum meeting ID requirement in mind. Repeating the same digit three 
times when the length of your minimum meeting ID is four digits long can be considered a security 
risk. However, repeating the same digit three times when the length of your minimum meeting ID 
is eight digits long may not.

There is always the chance of a meeting ID hitting the rule pattern and causing a problem. Judicious 
use of the rule is critical for the reduction of such incidents.

You cannot schedule a meeting with a supported meeting ID pattern through the phone or other 
scheduling endpoint, then attempt to modify it or reschedule it through the web. This rescheduling 
behavior is not supported.