UnbridgeCalls will cause the two call legs specified to form a peer-to-peer relationship, in the process renegotiating their audio streams to receive and transmit to each other, bypassing the media engine.

Two calls in a Media Control API-driven conference both stream media to and from the media engine. Each in such a scenario has its own media engine connection. This is advantageous if there is reason to perfom Media Control API operations on the calls or the conference; however, if at some point during the call media control is no longer needed, then UnbridgeCalls is a means to cause both the rcemote endpoints of both calls to renegotiate their audio streams and begin streaming to and from each other. Using this action destroys the two existing media engine connections, minimizing the licensing impact of your application.

Using UnbridgeCalls is one way to create a peer-to-peer relationship between two calls. Another way is to use the PeerCallId action parameter of MakeCall, which is appropriate for certain scenarios. In either case, once a peer-to-peer relationship has been created between two call legs, those calls thereafter can only be in a peer-to-peer relationship with each other.

The Call Control API makes every effort to abstract the complexities of the underlying telephony protocol; however, one should consult the Call Control Feature Matrix to understand what Call Control actions and action parameters are valid for each of the four supported protocols. One can set installation and deployment guidelines based on the Call Control actions and action parameters that an application uses; the Call Control Feature Matrix makes developing such guidelines feasible.

No description.

No description.

No description.