http://www.yeslab.com.hk/blog.php?

tid=14#

Workaround for Meetme Conference with

password


The Meetme Conference in CUCM is a built-in feature with limited function. Most of
the users expect to have password protection for Meetme Conference. However,
built-in Meetme Conference doesn't support password protection. You need to
purchase Meeting Place or WebEx to archive this function. Of course, Meeting Place
and WebEx provide more features instead of just password. However, it may not
worth to purchase those applications for just password protection requirement.
Below is a workaround method to have password protection for Meetme and its
limitation.
Requirement:
1 You need to have Unity Connection with additional mailbox license for each
Meetme DN. This workaround will make use of Unity Connection mailbox
authentication for achieving password protection.
2 You need to have ONE extra DN (DID number) for everyone to join any
Meetme DN. Once they call into it, it requests the caller to input the
Conference ID and password.
3 You need to have knowledge of Meetme, CSS, partition, Unity Connection
mailbox, greeting, transfer and system call handler. This document will
describe the procedures but not exactly steps by steps for dummy user.
Procedure:
1 Create separate partition and CSS for each Meetme DN(s).
2 Assign the CSS to specific phone(s)/DN(s) so only the specific phone/DN can
access the Meetme DN directly as the conference originator or host. Due to
the rest of phone/DN cannot access to the Meetme DN (without the specific
partition) so they cannot join the Meetme even there is a host inside the
Meetme.
3 Create a DN (DID number if require to allow external caller to join) with
common partition and call forward all to VM (As mentioned in requirement
point 2). We call this as conference bridge number for easy reference in
below steps.
4 Add all the specific Meetme partition(s) into the CSS which are using by
voicemail ports. Create a new CSS for voicemail port if required.
5 In Unity Connection, create a system call handler (may be call MEETME) with
the conference bridge number as the extension
6 Go to the Standard Greeting of MEETME. Change to My Personal Recording,
uncheck Play the "Record Your Message at the Tone" Prompt and After
Greeting, select Conversation: Sign-In. Then record a greeting like "Please

follow the voice prompt to input your conference bridge ID and press #,
input the password and press #"
7 Create a mailbox with Meetme DN(s), define the pin for the mailbox.
8 Go to the Standard Greeting of the mailbox, change to My Personal Recording,
uncheck Play the "Record Your Message at the Tone" Prompt and After
Greeting, select Call Action: Hang Up. Then record a greeting about "The
meeting host has not join the meeting. Please try again later.". This step to
prevent the caller who joins the Meetme before the meeting originator or
host.
9 Go to the Phone Menu of the mailbox; change the Touchtone Conversation to
Custom Keypad Mapping 1 or any Custom Keypad Mapping which you don't
use. Uncheck everything in After Sign-In, Play. Select User with Mailbox:
Meetme DN, Attempt Transfer. Remark: We send the caller to Sign-In from
MEETME system call handler so after Sign-In, we need to disable all the
phone menu prompt such as press 2 to send mail, etc.
10 Go to Transfer Rules of the mailbox, select Standard, Keep the Transfer Calls
To: the Meetme DN, change the Transfer Type to Supervise Transfer, uncheck
Play the "Wait While I Transfer Your Call" Prompt. You can check Ask for
Caller's Name so it will ask the caller to leave the name and the host or any
party in the conference can hear who is joining the conference. However, the
default prompt will ask caller to leave name but hasn't ask caller to press #.
Caller may confuse that why the call cannot join the meeting after said the
name.
11 Under Tools > Customer Keypad Mapping, select the Customer Keypad
Mapping 1 if you use it in step 9. Clear all the Key Assignment and uncheck all
in Option Voiced in Menu. This can disable the system to said anything after
Sign-In.
Limitation:
1 The concept is use a specific Meetme DN is special partition so not every can
call to the Meetme DN. However, you still need to assign each Meetme
partition to a phone or group of phone who can initiate the Meetme. For
example, you can create 10 Meetme DNs with 10 partitions and assign the
partition to 10 department's phones. Therefore, each department has their
own Meetme DN. Also, you can pass the Meetme mailbox to manage by
themselves so they can change the meeting password. In that case, all the
member in the same department can join the meetme without password.
Another way is everything controlled by yourself. Once user request to
Meetme, you change the CSS of user's phone/DN for calling the Meetme DN,
change and distribute the mailbox password to user. Once conference
completed, remove the CSS and change the mailbox password.
2 Of course the initiator of the Meetme don't need password to initiate the
conference.
3 There is no time duration to control the meeting.
The Meetme initiator must initiate the Meetme first otherwise the caller cannot join
into the Meetme. Refer to step 8, for leaving a greeting to inform the caller.