Only the initiator/controller can add participants into the conference. Have a look;
Using Conference Softkey for Ad Hoc Conference
The conference controller controls ad hoc conferences. When you initiate an ad hoc conference, Cisco CallManager 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 Cisco CallManager Administration, Cisco CallManager Service Parameters Configuration by using the Maximum Ad Hoc Conference service parameter setting.) Cisco CallManager supports multiple, concurrent ad hoc conferences on each line appearance of a device.
When the conference controller initiates a conference call, Cisco CallManager places the current call on hold, flashes the conference lamp (if applicable), and provides dial tone to the user. At the dial tone, the conference controller dials the next conference participant and, when the user answers, presses Conference softkey again to complete the conference. Cisco CallManager then connects the conference controller, the first participant, and the new conference participant to a conference bridge. Each participant Cisco IP Phone display reflects the connection to the conference.
The conference controller can drop the last conference participant from the conference by pressing the RmLstC softkey on the Cisco IP Phone model 7960 or 7940. If a conference participant transfers the conference to another party, the transferred party becomes the last conference participant in the conference. If a conference participant parks the conference, the participant becomes the last party in the conference when the participant picks up the conference. When only two participants remain in the conference, Cisco CallManager terminates the conference, and the two remaining participants reconnect directly as a point-to-point call.
Participants can leave a conference by simply hanging up. A conference continues even if the conference controller hangs up, although the remaining conference participants cannot add new participants to the conference.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...