A common use case is to have a conference node without date that can be open at will as a super chat function for people who are online within the authorization context of this node.
Sometimes (not sure how this happens yet), it impossible to restart a conference after it was closed, bbb telling that the conference information was mismatching.

At the beginning, I deleted the conference node and recreated it, but I noticed that after login and disconnecting several times and waiting a certain delay it becomes available again .

This might have some relation with http://drupal.org/node/876054 as the conference is left the hard way by leaving the conference node instead of login out within BBB.

Comments

sanduhrs’s picture

sanduhrs
he/him
Primary language German
Location 🇪🇺 Heidelberg, Germany, Europe
commented
Status: Active » Closed (works as designed)

No relations.
BBB (server) keeps all the conferences in memory for 60 minutes after all attendants left.