CUCM Conference Ad Hoc Conference
Unlike the Meet-Me conference, the ad hoc conference is started by an initiator and only the initiator of the conference can add people into the conference.
There are two methods to use in order to initiate ad hoc conferences:
- Put a call on hold, dial another participant, and conference additional participants.
- Join established calls by using the Select and Join softkeys Use the Conference Softkey for Ad Hoc Conference
The conference controller controls ad hoc conferences. When you initiate an ad hoc conference, CUCM considers you the conference controller. In an ad hoc conference, only a conference controller can add participants to a conference. If sufficient streams are available on the conference device, the conference controller can add up to the maximum number of participants that is specified for ad hoc conferences to the conference.
Configure the maximum number of participants for an ad hoc conference in CUCM Administration under CUCM Service Parameters Configuration by using the Maximum Ad Hoc Conference service parameter setting.
The default value for this Clusterwide Service Parameter is 4. If you have more than 4 participants in the conference, you need to change the default value for this service parameter to allow all the participants to join the conference. CUCM supports multiple, concurrent ad hoc conferences on each line appearance of a device. For example, phone 2001 dials 2002. The phones want to add 2003 into their conversation. 2001 presses the conference button and dials 2003. When 2003 answers, the confrn button is pressed again in order to add 2002 and 2003 into the conference.
Conference by Using Join Softkey: The user initiates an ad hoc conference by using the Select and Join softkeys. During an established call, the user chooses conference participants by pressing the Select softkey and then the Join softkey. This makes it an ad hoc conference. Up to 15 established calls can be added to the ad hoc conference, for a total of 16 participants. CUCM treats the ad hoc conference the same way as one that is established by using the Conference softkey method.
Note: You cannot be the only person in an ad hoc conference.
Note: There must be either hardware or software conference resources available before you can use any conference features. By default, the CUCM has a software conference bridge configured that can be used. In order to configure a hardware conference bridge, refer to Configuring and Using a Hardware Conference Bridge with Cisco Call Manager and a Catalyst 6000 WS-X6608 Port.
The Cisco Hardware Conference Bridge supports the Cisco Catalyst 4000 and 6000 Voice Gateway Modules and these conference sessions:
On the Cisco Catalyst 6000—In a G.711 conference, there are 32 available streams. Up to 10 conference sessions with three participants in each conference or one conference session with 32 participants.
On the Cisco Catalyst 4000—In a G.711 conference, only 24 conference participants are allowed. A maximum of four conferences with six participants each.
For the Cisco Software Conference Bridge—The maximum number of audio streams is 128. With 128 streams, a software conference media resource can handle 128 users in a single conference, or the software conference media resource can handle up to 42 conferencing resources with three users per conference.
Note: Although a single software conference bridge can run on the same server as the CUCM service, Cisco strongly recommends against this configuration. If you run a conference bridge on the same server as CUCM Ad Hoc Conference Settings CUCM Administration provides the Clusterwide Service Parameter, Drop Ad Hoc Conference, to allow the prevention of toll fraud (where an internal conference controller disconnects from the conference while outside callers remain connected). The service parameter settings specify conditions under which an ad hoc conference gets dropped.
Perform these steps to configure the Drop Ad Hoc Conference parameter:
From CUCM Administration, choose Service > Service Parameters. Choose the server from the server drop-down list box, and choose CUCM from the service drop-down list box.
1. From the Drop Ad Hoc Conference drop-down list box, which is listed in the Clusterwide Parameters (Features – General) area of the window, choose one of these options:
2. Never: The conference is not dropped. (This is the default option.) When No OnNet Parties Remain in the Conference: The system drops the active conference when the last on-network party in the conference hangs up or drops out of the conference. CUCM releases all resources that are assigned to the conference. When Conference Controller Leaves: The active conference terminates when the primary controller (conference creator) hangs up. CUCM releases all resources that are assigned to the conference.
3. Click Update. Note: CUCM does not support multiple options; that is, all conferences support the same functionality dependent upon the option that you choose.