Open GitYukari opened 8 years ago
I am experiencing the same issue.
I checked this issue and found the conference never unmuted until a moderator joins from his device. It might be updated from 1.2.10, where it searches for hasModerator flag and not allow just anyone to start a conference.
To avoid this bug moderator might need moderator to call from his device. Adding a openvbx number into device can work.
This has been an issue I've been struggling with for several days now. At first I thought it may have been a configuration error on my part, but everything seems to be set up properly.
Assume the following: I create a flow for a conference room, and I assign a user as a moderator to the conference room.
When a participant joins which is not a moderator, the conference room, by default, mutes the participant and plays hold music until a moderator joins.
Once the moderator joins, the music stops, but the participant who was in the room is not unmuted and is not able to speak. The participants are able to hear the moderator, but the moderator and other participants cannot hear each other.
However, if participants call in AFTER the moderator is in the conference, they are unmuted. So only participants who were muted before the moderator joined are never unmuted after the moderator joins.
I don't know why this is happening. I know that on May 26, Twilio updated the callback events for the conference API, but I'm not sure if it's relevant here. I don't know whether I am doing something wrong, or if this is a real issue with OpenVBX. If anyone could try the same scenario I've described, I would appreciate the confirmation.