Webmeeting: "[MISSING]: Your name"

[HH60]

Hi All,

i have the same problem as described in this Thread from May 15th 2018:
https://www.3cx.com/community/threads/planned-webmeeting-missing-your-name.56464/

In our case a restart of the services fixes the problem only temporarily but after a day the same error occurs again. The Firewall Checker walks through without any Problems (including our https-Port, 443 tcp). Our SSL-Certificate and FQDN are custom, but the Certificate is a valid Let's Encrypt Certificate. External DNS resolution is also sucessfully tested.

My next idea was that maybe our firewalls blocked some of the 3CX-Webmeeting Server IP Adresses, is there a list of all needed 3CX Server IPs available anywhere? So i could check if any of these IPs are blocked by our systems...

Any further ideas are welcome

Thanks & regards

 

[YiannisH_3CX]

Hello @HH60

Please note that the firewall checker does not check the https used by your system so make sure that it is correctly configured on your firewall.
If you navigate to Dashboard / Blacklisted IPs tab you will see 3 whitelisted IPs there that are the 3CX webmeeting servers.

 

[HH60]

Hi @YiannisH_3CX ,

thanks for your post!

Sorry, i didn't notice that the firewall test doesn't check the https port. But this should not be the problem because https-Access from LAN and Internet is possible and used on a daily basis. I also checked our logging system if one of our security systems caused this crash but it seems that not. Also i temporarlily whitelisted the IPs for the last days in our security systems while testing again (multiple times), but the same problem continues to occur. (See picture attached...)



The only way so far to get webmeeting back to work for me, is to log in to the admin console and restart the media server service (incl. dependent services). After a few hours it stops working again then...
Another thing to mention is that we (have to) use a web application proxy (MS ADFS Proxy) for our https traffic, but in earlier versions of 3CX (also earlier 15.5 SPs) this never seemed to be a problem with webmeeting... (while it still is a problem with the 3CX WebClient because the proxy has no web sockets support) Is it conceivable that our reverse proxy is the reason for this problem?

regards

 

[YiannisH_3CX]

Another thing to mention is that we (have to) use a web application proxy (MS ADFS Proxy) for our https traffic, but in earlier versions of 3CX (also earlier 15.5 SPs) this never seemed to be a problem with webmeeting... (while it still is a problem with the 3CX WebClient because the proxy has no web sockets support) Is it conceivable that our reverse proxy is the reason for this problem?

Thant is a useful information to have, and we have seen cases were the proxy was the issue. I would recommend trying without the proxy and see if that resolves your issue.