search

shettima / bigbluebutton

Automatically exported from code.google.com/p/bigbluebutton
0 stars 0 forks source link

Please add API warnings about voice conference requirements #614

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I believe API users would greatly benefit from a warning (both on the 
documentation wiki and as an error message from the API) when the parameters 
that they have specified to "create" will not work with Asterisk for voice 
conferencing.

Having encountered this problem myself, I finally came across a thread 
http://groups.google.com/group/bigbluebutton-setup/browse_thread/thread/14fab37e
0f85081 which explained that the default BBB Asterisk configuration only 
supports 5-digit extension names.  Reading the API source, it appears that the 
meetingID is used as the Asterisk extension when voiceBridge is not specified.  
This was not obvious (to me) and not easy to track down for Asterisk-novices.

If the API could provide an error when the messageID/voiceBridge parameter 
combination will not work with Asterisk (or use an alternative method for 
setting voiceBridge when it is not specified) and the wiki could provide a 
warning about valid values for messageID when voiceBridge is not specified, I'm 
sure it would save future users some time tracking down this error.

Original issue reported on code.google.com by kevin...@gmail.com on 29 Aug 2010 at 8:49

GoogleCodeExporter commented 9 years ago 
There is already a note in the documentation wiki about this.  It says 
specifically that the voiceBridge is used for the Asterisk meeting pin, and 
tells you what to change if you want something different.

The API can't return a warning because you can configure Asterisk 1,000,000 
different ways and it has no way to know that.  In my systems, the voiceBridge 
is a random six-char alpha-numeric string, and this works fine, because 
Asterisk uses AGI scripts to look up numeric pins and find the string that is 
the conference "room".

Original comment by jeremyth...@gmail.com on 9 Sep 2010 at 11:56

GoogleCodeExporter commented 9 years ago 
True, it does say that voiceBridge is used for the meeting pin.  It doesn't say 
that meetingID is used as the voice pin when voiceBridge is not specified and 
that therefore if you don't specify voiceBridge your meetingID must be a valid 
voiceBridge identifier.

Original comment by kevin...@gmail.com on 10 Sep 2010 at 2:00

GoogleCodeExporter commented 9 years ago 
Good point.  I've edited the API documentation.

Original comment by jeremyth...@gmail.com on 10 Sep 2010 at 6:07

GoogleCodeExporter commented 9 years ago 
Great.  Thanks!

Original comment by kevin...@gmail.com on 10 Sep 2010 at 7:10