Always-on MeetMe with password protection

In this post I will show you how to configure multiple password protected MeetMe conference bridges that are always on/open and does not require the user to initiate it from his/her IP Phone.

I’m assuming you know your way around UCM, CME and UCCX, and how to route calls in/out, class of service etc. This information is just the specifics for this topic.

Here’s what you need:

– UCM and or CME running at least 8.0 with DSP resources.


Starting with CME version 8.0 (IOS 15.1(1)T) there is a new features called MeetMe Unlocked. This allows you to configure a conference bridge that’s always on/open. This feature is not available on the UCM. There you still need to start the MeetMe bridge from an IP Phone.

While it’s possible to mix the conference bridge in software, it only supports G711 and 3 participants. I’m using a hardware conference bridge that supports 16 participants in each bridge with different codecs.

Note: The MeetMe numbers in the config below are just  dummy numbers that the UCCX transfers users to. You should ensure that users cannot dial these numbers directly.

Users will hear a beep when participants are joining or leaving the bridge. This is configured with the conference custom-cptone.

voice-card 0
dsp services dspfarm
voice class custom-cptone conf-join
dualtone conference
frequency 400 400
cadence 150 50 50
voice class custom-cptone conf-leave
dualtone conference
frequency 300 300
cadence 150 50 50
sccp local GigabitEthernet0/0
sccp ccm identifier 1 version 7.0
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register MEETME_CFB
dspfarm profile 1 conference
codec g711alaw
codec g711ulaw
maximum conference-participants 16
maximum sessions 5
conference-join custom-cptone conf-join
conference-leave custom-cptone conf-leave
associate application SCCP
sdspfarm units 1
sdspfarm tag 1 MEETME_CFB
conference hardware
max-ephones 10
max-dn 10
ip source-address port 2000
transfer-system full-consult
ephone-dn  1  octo-line
number 1111
conference meetme unlocked
ephone-dn  2  octo-line
number 1111
conference meetme unlocked
ephone-dn  3  octo-line
number 2222
conference meetme unlocked
ephone-dn  4  octo-line
number 3333
conference meetme unlocked

Ephone-dn 1 and 2 are configured with the same number to allow 16 participants in one bridge.
Ephone 3 and 4 are configured for 8 participants in each bridge.

Router#show ephone-dn conference
type         active inactive  numbers
Meetme          2       14      1111
DN tags: 1, 2
All DN tags unlocked.

type         active inactive  numbers
Meetme          0       8      2222
DN tags: 3
All DN tags unlocked.


I made a UCCX script that prompts the user for Meeting ID and password. If authentication is successful the call is transferred to the MeetMe bridge running on the CME router.

Each Meeting ID and password is a variable that’s set as a parameter. So you set/change each Meeting ID and password from the Application webpage.

You need to record your own prompts for this script. I have defined each prompt and if you just record each prompt as I have named it you should be able understand all messages.

Download the script below, rename it to MeetMe.aef


1. User calls the conference DID number from the PSTN.
2. The UCM has the number configured as a CTI Route Point that points to the UCCX trigger number.
2. The UCCX MeetMe script starts and prompts the user for Meeting ID and password.
3. Authentication is successful, the UCCX makes a call redirects to the dummy MeetMe number on the CME.
4. User is placed in the conference bridge and a join tone is played.
5. User leaves the bridge and a leave tone is played.


Handle meeting ID and password in an XML file. However it’s easier for users to manage id/pwd from the application page.

Add meeting administrator code that opens and closes the bridge by writing to an XML file. If the bridge is closed put users on hold until it’s open.

I have no idea how to automatically close the bridge however, also it would be nice to allow the users to record their name and play it to the bridge, but the supervised transfer does not allow you to play prompts.


Cisco Jabber for Windows custom EDI config file

Here’s a sample config file if you want to use custom parameters in EDI mode in Jabber for Windows.

First we specify EDI as Directory Server Type.
Connection type is set to 1 = Connect to a Domain Controller server.
Primary AD server IP is
Server port is 389.
Use Windows Credentials is disabled by setting it to 0.
Username and Password is specified to be used when connecting to the AD.
SSL is disabled by setting it to 0.
Secure Connection is enabled to encrypt all data including authentication and query data. It seems backwards but according to Cisco 0 enables it.
Search Base is specified for specific container and DC lookup.
Business Phone is set to ipphone instead of the default telephoneNumber.
Contact photos are grabbed from a web server and sAMAccountName is used to substitute the filename.

All other LDAP attributes that you don’t configure are set to their default values as specified here: 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">