If the last point is the case, contact support, or myself via PM with the user's webmeeting FQDN or license to rectify this for him or the user can do this properly by releasing the FQDN from the ERP and restarting his 3CX System Service for a WebMeeting re-sync.
- This means his myphone port (5001) is not open to the outside world.
- Firewall/geolocation rules which may be blocking communication the main WebMeeting portal at webmeeting.3cx.net
- Installed license on a test PBX with FQDN A, he uninstalls the PBX and installs on another FQDN B without first releasing the previous FQDN A from the ERP. He should see an error in the management console event log regarding this if this is the case.
I had this problem last week on a fresh install. I had to do a complete backup, reinstall, restore to fix the issue.
The customer said that port 5001 was blocked, it is now enabled, but still MCU list is empty (after services restart).
They are checking now firewall settings (point 2).
Point 3 should not be the case.
Backup & restore helped (without preinstallation).
Thanks for support.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.