[asterisk-dev] [Code Review] 3009: Add channel variable that describes why a channel left a ConfBridge()

Mark Michelson reviewboard at asterisk.org
Fri Nov 15 14:04:05 CST 2013

This is an automatically generated e-mail. To reply, visit:

(Updated Nov. 15, 2013, 8:04 p.m.)

Review request for Asterisk Developers.


Updated XML documentation and CHANGES file.

Repository: Asterisk


This introduces a channel variable called CONFBRIDGE_RESULT that can be read after an invocation of ConfBridge in order to determine why the channel left. The possible values are:

* ERROR: The channel never joined the confbridge either due to bad input to the ConfBridge, an invalid PIN, or some internal error such as a memory allocation failure.
* HANGUP: The channel left the confbridge due to a soft or hard hangup.
* DTMF: The channel left due to the participant pressing a DTMF sequence to leave the ConfBridge.
* KICKED: The channel was removed from the conference either by an admin, or some outside command to kick the user from the conference.
* ENDMARKED: The channel was removed from the conference because it had the "endmarked" option enabled and the final marked user left the conference.

If there are ideas for other useful values, please let me know.

Diffs (updated)

  /trunk/apps/confbridge/conf_state_multi_marked.c 402777 
  /trunk/apps/app_confbridge.c 402777 
  /trunk/CHANGES 402777 

Diff: https://reviewboard.asterisk.org/r/3009/diff/


See review 3015


Mark Michelson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20131115/b8193a40/attachment.html>

More information about the asterisk-dev mailing list