bridge.c: Obey BRIDGE_NOANSWER variable to skip answering channel.

If the BRIDGE_NOANSWER variable is set on a channel, it is not supposed
to answer when another channel bridges to it using Bridge(), and this is
checked when ast_bridge_call* is called. However, another path exists
(bridge_exec -> ast_bridge_add_channel) where this variable was not
checked and channels would be answered. We now check the variable there.

Resolves: #401
Resolves: #1364
This commit is contained in:
Naveen Albert
2025-08-14 08:50:31 -04:00
committed by github-actions[bot]
parent adde97bff3
commit d772f61231
2 changed files with 14 additions and 1 deletions

View File

@@ -172,6 +172,9 @@
<para>Additionally, to prevent a bridged channel (the target of the Bridge application)
from answering, the <literal>BRIDGE_NOANSWER</literal> variable can be set to inhibit
answering.</para>
<warning><para>Do not set the <literal>BRIDGE_NOANSWER</literal> variable globally,
as it will break normal bridging behavior in many cases. Only use this variable on
a per-channel basis when you really know what you are doing!</para></warning>
</option>
<option name="S(x)">
<para>Hang up the call after <replaceable>x</replaceable> seconds *after* the called party has answered the call.</para>