Summary:ASTERISK-19354: ConfBridge does not close channel when using local channels
Reporter:Marcello Ceschia (marcelloceschia)Labels:
Date Opened:2012-02-14 07:56:55.000-0600Date Closed:2014-01-09 20:40:49.000-0600
Versions: Frequency of
Environment:linux 64bitAttachments:
Description:I'm unsing local channels to push participants into conference.
But sometimes the channels will not be cloed after all participants left the conference.

using gdb I get (no active conferences at this moment):

Thread 16 (Thread 0x7fc12e56e700 (LWP 20595)):
#0  0x00007fc157105913 in poll () from /lib/libc.so.6
#1  0x00000000004714c6 in ast_waitfor_nandfds (c=0x7fc12e569170, n=1, fds=0x7fc12e568fb0, nfds=0, exception=0x0, outfd=0x7fc12e568fac, ms=0x7fc12e568fa8) at channel.c:3203
#2  0x000000000044e6f4 in bridge_channel_join_multithreaded (bridge_channel=0x7fc12e569100) at bridging.c:724
#3  0x000000000044f729 in bridge_channel_join (bridge_channel=0x7fc12e569100) at bridging.c:929
#4  0x000000000044ffa9 in ast_bridge_join (bridge=0xc02b6f8, chan=0x7fc1319d1a58, swap=0x0, features=0x7fc12e569290) at bridging.c:1003
#5  0x00007fc144dd9903 in confbridge_exec (chan=0x7fc1319d1a58, data=0x7fc12e56b540 "12,cM(confSound1)") at app_confbridge.c:791
#6  0x00000000005035e7 in pbx_exec (c=0x7fc1319d1a58, app=0xbf02b70, data=0x7fc12e56b540 "12,cM(confSound1)") at pbx.c:1431
#7  0x000000000050d505 in pbx_extension_helper (c=0x7fc1319d1a58, con=0x0, context=0x7fc1319d1fb0 "konferenz", exten=0x7fc1319d2000 "12", priority=20, label=0x0, callerid=0x7fc131476690 "12", action=E_SPAWN, found=0x7fc12e56dc30, combined_find_spawn=1)
   at pbx.c:4250
#8  0x000000000050f142 in ast_spawn_extension (c=0x7fc1319d1a58, context=0x7fc1319d1fb0 "konferenz", exten=0x7fc1319d2000 "12", priority=20, callerid=0x7fc131476690 "12", found=0x7fc12e56dc30, combined_find_spawn=1) at pbx.c:4890
#9  0x000000000050fbd5 in __ast_pbx_run (c=0x7fc1319d1a58, args=0x0) at pbx.c:4990
#10 0x00000000005118dd in pbx_thread (data=0x7fc1319d1a58) at pbx.c:5330
#11 0x0000000000567f74 in dummy_start (data=0x7fc13171b0d0) at utils.c:1004
#12 0x00007fc1596878ca in start_thread () from /lib/libpthread.so.0
#13 0x00007fc15711086d in clone () from /lib/libc.so.6
#14 0x0000000000000000 in ?? ()
Comments:By: Matt Jordan (mjordan) 2012-02-14 08:38:19.822-0600

ConfBridge in Asterisk 1.8 is extended support, which means that development support for it primarily comes from the Asterisk community.  In particular, ConfBridge prior to Asterisk 10 was primarily a proof of concept for a new way of performing conferences, as opposed to MeetMe.  In Asterisk 10, ConfBridge was taken beyond the proof of concept stage.  In general, prior to Asterisk 10, it is recommended that you use MeetMe for your conferencing needs; in Asterisk 10 and later, ConfBridge is the preferred mechanism.

I've acknowledged this issue, but I'd recommend that you either use MeetMe in Asterisk 1.8, or move to Asterisk 10 if you prefer to use ConfBridge.

By: Marcello Ceschia (marcelloceschia) 2012-02-14 09:51:39.013-0600

Thank you Matt for this answer.
But why isnt it mentioned in the application description? I think, nobody outside the asterisk development team know this state of ConfBridge in 1.8.

We use the way ConfBridge handles conferences in chan-sccp, for now we know that ConfBridge is still alpha - with a remark that this os only a proof of concept, life would be much easier.

I think we can close this issue, but it would be nice to see a notice for this application, precisely because 1.8 is a LTS version.
Thank you Matt

By: Matt Jordan (mjordan) 2014-01-09 20:40:41.963-0600

Unfortunately, there isn't really a place to document that, since {{app_confbridge}} doesn't have a config file in Asterisk 1.8. While we could spit out a NOTICE message on module load, those are typically ignored or not seen due to the quantity of messages that get dumped out on startup. It was documented to an extent on the Asterisk wiki on the [ConfBridge 10 page|https://wiki.asterisk.org/wiki/display/AST/ConfBridge+10].

ConfBridge is marked as "extended" support in Asterisk 1.8 (which can be viewed in menuselect). In general, this is an indication that this module has limited support, or the support of a smaller segment of the Asterisk developer community. In general, we recommend people use "core" supported modules when possible, unless they need the functionality provided by an extended support module.

Since this is no longer an issue in later versions of Asterisk, I'm going to close this out as Won't Fix.