Skip to main content

Meeting is scheduled with "enable join before host" enabled. Host joins meeting, but attendees are unable to join. Attendees receive message "waiting for host", but host is already in the meeting. This issue does not happen with all meetings and there is no commonality to when it occurs.

Hi Beth!

There is currently an outage regarding this. RingCentral is already working towards a resolution with resolving the issue. To keep you updated, you may check https://status.ringcentral.com/ 

Thank you!
I believe this may be related to meetings created with "Enable join before host" selected. We have had several instances where the host left the meeting and chose "end meeting for everyone" and had another meeting scheduled after that. The participants get a message that host is in another meeting. Host is able to join second meeting but no one else can. You can also exit the meeting and try to Start the second one from RC Meetings app, and it gives message that you have another meeting running, with a button to end the first meeting. Button doesn't work (it closes the popup window and starts the new meetings but attendees still get message that host is in another meeting.

This is a problem, since we have no idea how long meetings hang around locking up the host's RC account.
These are known issues, all updates will be available on status.ringcentral.com

Ops has advised that they are rolling out new servers tonight to help resolve the issue where you can't join RC Meetings because it shows host is busy, on another meeting, or the meetings connector indicator spins.

Baring any unforeseen problems, hopefully this will be resolved tomorrow. 

I've experienced this twice, once in September and again today, our client kept getting " host is another meeting " They said the invite was showing the meeting was @ 2:00pm when the meeting had started @ 12:00 pm. one of the users forwarded them the link of meeting we were in and their link still said that the host was in another meeting.


@jessica is there an update on this?


Reply