From: Mark Michelson <mmichelson@digium.com>
Date: Fri, 18 Oct 2013 15:28:16 +0000 (+0000)
Subject: Clarify in ast_bridge_destroy() about how departable channels must be handled.
X-Git-Tag: 12.0.0-beta2~123
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=edc734c694df95e04af5fca19116e22795ed9580;p=thirdparty%2Fasterisk.git

Clarify in ast_bridge_destroy() about how departable channels must be handled.



git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@401212 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---

diff --git a/include/asterisk/bridge.h b/include/asterisk/bridge.h
index 610e0f944c..7d21aa76f4 100644
--- a/include/asterisk/bridge.h
+++ b/include/asterisk/bridge.h
@@ -409,6 +409,12 @@ static inline void _ast_bridge_unlock(struct ast_bridge *bridge, const char *fil
  * \endcode
  *
  * This destroys a bridge that was previously created.
+ *
+ * \note
+ * While this function will kick all channels out of the bridge, channels that
+ * were added to the bridge using ast_bridge_impart() with the flag
+ * AST_BRIDGE_IMPART_CHAN_DEPARTABLE set must have ast_bridge_depart() called
+ * on them before calling ast_bridge_destroy().
  */
 int ast_bridge_destroy(struct ast_bridge *bridge, int cause);