Bug #5312

Problemas com BBB plugin on Chamilo 1.9 Stable.

Added by Ricel Leite almost 8 years ago. Updated almost 8 years ago.

Bug resolved
Target version:
Start date:
Due date:
% Done:


Estimated time:
SCRUM pts - complexity:



Chamilo upgraded to 1.9 stable. Video Conference set up the plugin, however, when using the Video Conference, first it opens a new window with the message 'Unable to fetch & checksum url = e445a427d0544f23a03971349e3a6f2ff93f0a70'. Close this window and update the previous window and the room appears in "Record List". When trying to access the room I am directed to another page with the message:

<message>The meeting ID that you supplied did not match any existing meetings</message>

What to do to fix this problem?

Thank you and congratulations for the beautiful work.

Related issues

Related to Chamilo LMS - Bug #4840: BigBlueButton bug in 1.9 nightly 2012-06-04Bug resolved05/06/2012




Updated by Yannick Warnier almost 8 years ago

  • Priority changed from High to Low
  • Target version set to 1.9.2

Thanks for reporting. This is part of the "plugins" section of Chamilo. As such, it is low priority (even if your own needs tend to set it to high priority :-p).
If you want it quickly fixed, please consider hiring an official provider or developer to fix it.


Updated by Ricel Leite almost 8 years ago

Olá Yannick.

Thanks for the quick response!
I'd like to know how to update the Chamilo to 1.9 without updating the plugin BBB.
How can I do this?

Thank you.


Updated by Julio Montoya almost 8 years ago

I think that's not possible, the plugin system changed a lot for chamilo 1.9, so the old bbb plugin will not work


Updated by Julio Montoya almost 8 years ago

  • Status changed from New to Needs more info

Updated by Ricel Leite almost 8 years ago


The problem is solved. Reinstalled the plugin and everything went ok, however sometimes it creates an indefinitely entry in the table plugin_bbb_meeting, making each time a user clicks to enter the videoconferencing opens a new room. The problem ends when we remove the entry from the table.

Thank you.


Updated by Julio Montoya almost 8 years ago

  • Status changed from Needs more info to Bug resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF