Audio not working with Freeswitch

Same problem here, using 0.71 with FreeSWITCH, and the latest BBB dev module. The odd thing is I did manage to get it working (with FreeSWITCH) intermittently, but haven't been able to identify how to fix this.

Changing the server to use Asterisk, as described here in the troubleshooting section, solves this:
http://code.google.com/p/bigbluebutton/wiki/InstallationUbuntu#2._Instal...

Unfortunately the audio latency when using Asterisk is pretty high.
.

Thanks for the information. I'm having the same problem.

Here is also the switching commands from FreeSwitch to asterisk.

Switching between Asterisk and FreeSWITCH

The BigBlueButton packages let you switch back and forth between using Asterisk and FreeSWITCH.

To switch from FreeSWITCH to asterisk, do

sudo apt-get purge bbb-freeswitch-config
sudo apt-get purge freeswitch
sudo apt-get install bbb-voice-conference
sudo bbb-conf --clean

Hopefully this issue is resolved soon.

I have also the same issue. Audio does not work in bbb 0.71. If I start a meeting directly within bbb, audio is working fine.

subscribe

same issues,
Audio works by default on Big blue though it fails when via drupal.

V0.71

Are you using asterisk or freeswitch?

Regards, Stéphane

Does anyone have a solution, how to enable FreeSwitch with this module?

I'm currently using Asterisk, but the voice delays can be up to 5 seconds while Skype is ok with the same people.

Currently it's virtually impossible to use bbb with voice.

To switch from Asterisk to FreeSWTICH, do

sudo apt-get purge bbb-voice-conference
sudo apt-get purge asterisk
sudo apt-get install bbb-freeswitch-config
sudo bbb-conf --clean

-- Chipie

Chipie, thanks for the information.

I was wondering why the audio does not work when using this module with FreeSwitch?

BBB without using Drupal module both asterisk and freeswitch voices are ok
BBB using Drupal only asterisk works.

Asterisk had huge voice delays which forced us to switch from BBB back to skype on a conf call.

Try to configure FreeSWITCH to accept any 5-digit conference number. Change /opt/freeswitch/conf/dialplan/public.xml

    <extension name="bbb_conferences">
      <condition field="destination_number" expression="^(7\d{4})$">
          <action application="answer"/>
          <action application="conference" data="$1@wideband"/>
          <!-- <action application="conference" data="$1@wideband"/> -->
      </condition>
    </extension>

to

    <extension name="bbb_conferences">
      <condition field="destination_number" expression="^(\d{5})$">
          <action application="answer"/>
          <action application="conference" data="$1@wideband"/>
          <!-- <action application="conference" data="$1@wideband"/> -->
      </condition>
    </extension>

and then restart FreeSWITCH.

sudo /etc/init.d/freeswitch restart

-- Chipie

I had the same problem with FreeSWITCH and bbb conferencing with drupal. The conference number this drupal extension uses is the node id of the meeting node. So the regexp exrepssion should really be "^\d{1,10}" in order for it to work correctly in all scenarios.

Also the earlier dialplan "public_extensions" should be removed or moved after this bbb_conferencing dialplan.

I guess better fix would be to append some number to these drupal meetings so that they could be identified using an regexp expression

As far as I can follow this conversation, the conference number you're referring to is probably the voiceBridge parameter?

This parameter is generated like so: 'voiceBridge' => rand(10000, 99999),.
So it should always be a five digit code, just as documented:

Voice conference number that participants enter to join the voice conference. Note that if you don't specify a voiceBridge parameter, the meetingID parameter is used. The default pattern for this is a 5-digit number, because in the default Asterisk configuration, this is the PIN that a dial-in user must enter to join the conference. If you want to change this pattern, you have to edit /etc/asterisk/bbb_extensions.conf

see: http://code.google.com/p/bigbluebutton/wiki/API

If that is different for the default configuration of freeswitch in bbb this is upstream and should be reported in the issue queue on http://code.google.com/p/bigbluebutton/issues/list

There is already an issue:
http://code.google.com/p/bigbluebutton/issues/detail?id=749

and a wiki entry:

In BigBlueButton 0.7, Asterisk was configured to use any 5-digit conference number. However, for BigBlueButton 0.71, FreeSWITCH is configured to use any 5-digit number that begins with 7 (i.e. 7XXXX).

see: http://code.google.com/p/bigbluebutton/wiki/FAQ#Why_did_my_voice_confere...

Alright, so the only difference is, that freeswitch accepts 5-digit numbers starting with 7 and asterisk accepts any 5-digit number.
Patch is attached, anyone available for testing?

Sorry for the noice. I was running the stable version of the plugin. The latest development version uses the voiceBridge parameter correctly. I still needs the patch though to work out of the box with freeswitch

I got the conference number from FREEswitch log. This is the number that drupal bbb module uses when connecting to FREEswitch. I don't know what is the name of the parameter in the module itself. But at least for me it matches the node id

Here is the FREEswitch log for unsuccessful attempt :
(the node id was 156 and regexp fails for all dialplans)

2011-01-12 09:44:29.930379 [INFO] mod_dialplan_xml.c:331 Processing WikiSysop <156>->156 in context public
Dialplan: sofia/external/156@188.165.136.54 parsing [public->unloop] continue=false
Dialplan: sofia/external/156@188.165.136.54 Regex (PASS) [unloop] ${unroll_loops}(true) =~ /^true$/ break=on-false
Dialplan: sofia/external/156@188.165.136.54 Regex (FAIL) [unloop] ${sip_looped_call}() =~ /^true$/ break=on-false
Dialplan: sofia/external/156@188.165.136.54 parsing [public->outside_call] continue=true
Dialplan: sofia/external/156@188.165.136.54 Absolute Condition [outside_call]
Dialplan: sofia/external/156@188.165.136.54 Action set(outside_call=true)
Dialplan: sofia/external/156@188.165.136.54 parsing [public->call_debug] continue=true
Dialplan: sofia/external/156@188.165.136.54 Regex (FAIL) [call_debug] ${call_debug}(false) =~ /^true$/ break=never
Dialplan: sofia/external/156@188.165.136.54 parsing [public->public_extensions] continue=false
Dialplan: sofia/external/156@188.165.136.54 Regex (FAIL) [public_extensions] destination_number(156) =~ /^(10[01][0-9])$/ break=on-false
Dialplan: sofia/external/156@188.165.136.54 parsing [public->bbb_conferences] continue=false
Dialplan: sofia/external/156@188.165.136.54 Regex (FAIL) [bbb_conferences] destination_number(156) =~ /^(7\d{7})$/ break=on-false
Dialplan: sofia/external/156@188.165.136.54 parsing [public->public_did] continue=false
Dialplan: sofia/external/156@188.165.136.54 Regex (FAIL) [public_did] destination_number(156) =~ /^(5551212)$/ break=on-false

After I changed to regexp in FREEswitch to \d{1,10} it works.

It seems that the modules uses nodeid as the voicebridge parameter. I can try to debug further.

Can the patch in #16 be committed in dev?
Wouldn't be time to release a stable version of this great module?

Thanks

You might issue another post for the "Fullscreen" issue if appropriate.
This issue is now well defined - and gracefully solved.

#11 + #15 make it work indeed. Thanks to you both.

Fullscreen button has been removed by BBB. So it is not an issue handled by the module.

Your patch works here.

-- Chipie

I can confirm that #11 (configure freeswitch to use any 5 digit conference number) fixes the problem. Thanks very much to those who figured this out and posted here.

Thanks chipie this solution you have posted in #11 has worked for me!