Creates a conference and places the specified connection into it as the 1st participant.

A conference can not be created with zero connections; there must be one connection in the conference to start.

A conference is uniquely identified by the ConferenceId result data parameter returned by CreateConference.

In most cases, Hairpin should be set to true (the default) to use the minimum amount of audio resources for a 2-party conference. Specifically, a hairpinned conference does not use any conference resources. However, a hairpin conference will be 'promoted', or converted to a true media conference, if a 3rd participant is added to the conference or if a voice operation is performed on the conference itself. In either case, this will cause each participant and conferenced voice operation to use one conference resource. True conferences also have a slightly increased latency over a hairpinned conference.

All connections in the conference must be fully connected (Tx and Rx conditions both established on the connection; CreateConnection and certain actions in the Call Control API are used to accomplish this. For convenience, a ConnectionId returned from a ReserveConnection can be specified along with the MediaTxIP, MediaTxPort and MediaTxCodec parameters, in which case a CreateConnection does not have to be performed explicitly by the develeoper, since the media engine will automatically fully establish the Tx RTP properties the ConnectionId as the connection is joined to conference.

Mute and Monitor have a similar effect to one another; the participant specified by ConnectionId can only hear audio and is unable to send audio to the conference. The difference is that each Mute participant is truly in the conference, and so uses a conference resource; at anytime this participant can be allowed to send audio seamlessly via the use of the SetConfereeAttribute Mute parameter. Monitor participants are not truly in the conference from an internal logic standpoint, and can only transmit audio into the conference by removing their connection from conference, and placing back in with Monitor set to false. One also saves resources by using Monitor over Mute for many participants. Each Monitor participant shares one conference resource, but Mute participants each need a conference resource.

AnswerCall and MakeCall both automatically invoke CreateConference or JoinConference if the AnswerCall Conference action parameter or MakeCall Conference action parameter is set to true.

Each connection in a conference uses one conference resource. Because this action places one connection into the conference, one conference resource is utilized once this action has succeeded.

No description.

No description.

No description.