Quickmeeting lasts under 60 seconds

[vintegrity]

Hi all,
I have a single user whose quick meeting keeps booting participants after between 30 and 60 seconds. He's able to use regular scheduled meetings without a problem so it seems to be related strictly to his personal webmeeting link. Other users who create meetings don't have the problem.

 

[LeonidasG_3CX]

Hi there,

Could you send me a PM with the shareable link for that meeting?

 

[vintegrity]

Sure, I sent it over. Thanks.

 

[vintegrity]

I found something interesting. With other quick meetings for other users you can't join unless they have entered the meeting no matter how they exit. With his, it's always active but boots people between 10-60 seconds. I tried pulling his email address out and then re-adding it in hopes it would reset something but it's still the same.

I also just completely disabled the extension and the webmeeting still works for the short time. Is it possible that a "session" of some sort is running on the 3cx company servers (I tried the resync option in the CP) as I see these don't run locally?

 

[vintegrity]

I found that in this process of of messing with the extension, the user was assigned a new url which works fine. This will solve the problem for us. Thanks for looking into it.

 

[LeonidasG_3CX]

Thanks, we'll take a look.

 

[LeonidasG_3CX]

I can verify there's indeed an issue and it's on our side, we're checking this further.
I'll let you know once we have something.

 

[LeonidasG_3CX]

Can you open your quick meeting and use the shareable link again please? It should work now.

The issue was that the link you provided above should have expired after a certain period of time but only partially expired for reasons we will be investigating. The link shouldn't have been accessible, period.

The 60 second disconnection timer seems to be something added by us to easily identify this issue if it ever occured. Please let us know if you experience it again.

 

[François Lepage]

Hi there,

Some of our employees are experiencing the same issue.

Gets kicked out after a very short period of time. Was the the Virginia 42 server.

Please let me know how to resolve the issue.

 

[François Lepage]

Update: I was Virginia 42 is not supposed to be open for new meeting but that employee keeps having sessions opened on there, although he had ended any previous meetings.

• Node United States (Virginia) 0042 temporarily not available for new meetings

That seems to be the issue.

Can you please advise on how to force a server change if these kind of situation happen in the future?

Thank you

 

[LeonidasG_3CX]

Yeah this is what we also saw. We intentionally made Virginia 42 unavailable in order to force the user to use another server and somehow these meetings were still able to connect there. We'll look into it and try to get it resolved as soon as possible.

 

[François Lepage]

Hi,

What I observed is that new sessions kept being opened on Virginia 42 for a specific user in my company. So it did not seems to be locked for him. Why is that?

Thank you.

 

[LeonidasG_3CX]

We're looking into this. In our upcoming update for WebMeeting, this issue does not occur, but that version will be out in a few weeks from now.

We're looking into the feasibility of backporting this into the current version of WebMeeting so we can resolve. It's not a simple task so we'll need some time to see how we're going to address this.

 

[LeonidasG_3CX]

Hi there, we've resolved the issue in one of our internal builds. We're going to be deploying the new version during the weekend. This should resolve any issues you're having Monday onwards.