[asterisk-users] ConfBridge - Failed to find a bridge technology to satisfy capabilities

Michael L. Young myoung at acsacc.com
Fri May 20 09:48:10 CDT 2011


----- Original Message -----
> From: "Chris Maciejewski" <chris at wima.co.uk>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
> Sent: Thursday, May 19, 2011 9:39:57 AM
> Subject: [asterisk-users] ConfBridge - Failed to find a bridge technology to	satisfy capabilities
> 
> Hi,
> 
> I am trying to use ConfBridge application, but it throws "Failed to
> find a bridge technology to satisfy capabilities 0x4 (ulaw)" error.
> Please see console output below.
> 
>     -- Executing [501 at services:9] ConfBridge("SIP/OpenSER-00000005",
> "1001") in new stack
> [May 19 13:36:05] DEBUG[7452]: app_confbridge.c:404
> join_conference_bridge: Trying to find conference bridge '1001'
> [May 19 13:36:05] DEBUG[7452]: bridging.c:475 ast_bridge_new: Failed
> to find a bridge technology to satisfy capabilities 0x4 (ulaw)
> [May 19 13:36:05] DEBUG[7452]: app_confbridge.c:368
> destroy_conference_bridge: Destroying conference bridge '1001'
> [May 19 13:36:05] ERROR[7452]: app_confbridge.c:435
> join_conference_bridge: Conference bridge '1001' could not be
> created.
> 

I wonder if this recent commit to the 1.8 branch would help fix this issue at least with 1.8.

  Author: twilson
  Date: Thu May 19 18:28:13 2011
  New Revision: 319920

  URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=319920
  Log:
  Revert part of a change to the bridging API code

  The capabilities used in the bridging API are very different than the
  ones used for formats. When the conversion was made expanding the bit
  width of codecs, the bridging code was accidentally accosted in ways
  that it didn't deserve.

  Modified:
      branches/1.8/include/asterisk/bridging.h
      branches/1.8/include/asterisk/bridging_technology.h
      branches/1.8/main/bridging.c

As far as why svn trunk is stating that it cannot create the bridge, the debug message is not very informative as to why it couldn't create the conference bridge from what I could see briefly looking at the debug logs you posted in another message.

Michael
(elguero)



More information about the asterisk-users mailing list