Kicked-out of Webmeeting after 30s to 1min

[François Lepage]

Hi,

One of my employee reported not being able to stay connected to the webmeeting session this morning. The issue is persisting.

The user is using Chrome, but same behaviour happens with the new Edge and Firefox. After 30s to 1 min, he gets kicked out and returns to the device selection screen.

We have tried celaring cache and hard reload.

I attached a sceenshot. The screenshot clearly shows the WebSocket being shutdown.

The DOMException seems to be related to a Chrome extension which is not installed on the other browsers we have tried, yet the result is the same. I beleive this error message is not relevant.

Server used at that point was Oregon 0018.

You input would be appreciated.

Thank you

François

 

[François Lepage]

Hi again,

The user just sent me another screengarb from firefox.

This time, 403 from a 3CX CDN.

Thank you

 

[StefanW]

Any AV software on the PC which my interrupts the stream?

 

[François Lepage]

Hi,

The user has AVG installed.

He just reported that the issue disapeared on its own.

It's the 2nd time I mention that to you guys, but it does make me unconfortable when things get resolved with no apparent resolution. Is there anything to report on your end?

Thank you

François

 

[Evolute IT]

Hi,

The user has AVG installed.

He just reported that the issue disapeared on its own.

It's the 2nd time I mention that to you guys, but it does make me unconfortable when things get resolved with no apparent resolution. Is there anything to report on your end?

Thank you

François

What's the firewall on-site? I've seen Meraki and few others cause issues when different protections are enabled.

 

[François Lepage]

Hi,

It's a mix of Mikrotik and Cisco. But the issue disapeared on it's own from the same site and I'm not aware of any configuration changes network wise.

 

[Evolute IT]

Hi,

It's a mix of Mikrotik and Cisco. But the issue disapeared on it's own from the same site and I'm not aware of any configuration changes network wise.

Could be instability at the ISP level. Do you use any network monitoring?

 

[François Lepage]

Looking at the browser console of the above screenshot, the error seemmed to be related to the 3CX CDN with a 403 Forbidden on https://wm-cdn.3cx.net. I have no reason to suspect that packets were not routed properly @ ISP.

It's difficult to assess, and the following is only an hypothesis, but if there was any changes on 3CX's side, and the CDN network and / or browser is caching an older verison of the code, it might be that an outdated ressource was requested by the web app, or that this request was made in an un-authorized way and got secured in a newer iteration of the code base. With 3CX Webmeeting rapid expansion over the last few months, I wouldn't be surprised that there are still some things to iron out in terms of delivery optimization.

 

[MarcelloV]

The 403 error on Firefox does not affect Webmeeting client. It's an extra request sent by Firefox only. Transient issues are usually related to routing/network issues. We had no alerts on Oregon servers, so it should be temporary routing issue between customer provider and Oregon server.