123it / bigbluebutton Goto Github PK

When a new user arrives to a conference room few minutes late, the system generate a new room. This issue was supposed fixed before the release.

The issue was discovered using api calls by the Moodle-BBB moodle, after a waiting period of time of the student.

This issue is indirectly related to the Issue #4

The voice phone applet doesn't works neither openning the client in demo nor api mode.

The getMeetingInfo method for the api returns wrong information. Specifically the running parameter is false when a moderator is logged in. That should be true.

XML returned by a 0.72 server

SUCCESS
b995590d60751173
eb88b6f13d5f71e8a41207ded86289cbb0d6832f
7e9d5bb964f88fa9a974a2e8d3c3ad1263ce7bf4
false
false
null
null
0
0






demo

XML returned by a 0.71 Server

SUCCESS
b995590d60751173
eb88b6f13d5f71e8a41207ded86289cbb0d6832f
7e9d5bb964f88fa9a974a2e8d3c3ad1263ce7bf4
true
false
Tue May 10 16:03:19 EDT 2011
null
1
1


3
Jesus Federico
MODERATOR

The conference session in ConferenceDynamics are not persistent. Seems like the last 3 methods used by the spring framework are never called.

This issue seems to be related with all the others.

The module command is not working, apparently the call is not executed in the server

When starting conference from an external application, after closing the session the api doesn't return to the page that made the call.

Apparently is an issue related to Chrome extension, but need to be tested in Wordpress and moodle

The problem is that the client is always receiving the api mode