Meeting not found

[edfosho]

Every so often I'm getting 'Meeting not found" (screenshot attached). I've been following it as an issue on one of my systems, and seems a restart of the 3CX services fixes it. It's a system where the WebMeeting feature may be used once every few days, or once a week even.

Almost like it needs a refresh (to re-register itself against the WebMeeting service hosted by 3CX).

Is it a DNS time out? If so, how often should I be running meetings so it always works? Said system uses a 3cx.co.uk FQDN, with a auto generated 3cx.net FQDN for the WebMeeting profile.

 

[JohnS_3CX]

Hi,

Due to upgrades and migrations while expanding our webmeeting servers, it's quite possible you may have come across times where servers where being moved (including UK-based FQDNs).

In those cases, the system will eventually re-sync itself to webmeeting servers, but restarting the system service will force it to happen immediately.

 

[edfosho]

Hi,

Due to upgrades and migrations while expanding our webmeeting servers, it's quite possible you may have come across times where servers where being moved (including UK-based FQDNs).

In those cases, the system will eventually re-sync itself to webmeeting servers, but restarting the system service will force it to happen immediately.

Thanks John - do you know how often it re-syncs itself (daily, weekly), and is this something I can script on Debian?

 

[JohnS_3CX]

It can take up to 8 hours, I would not recommend scripting it as you have no control over the process that resyncs.

This would mean you have to script a forceful services restart and we do not recommend doing that unnecessarily. You should restart services only if needed, and only during troubleshooting.

The reason you noticed it in the first place is because we were expanding the network of MCU servers, and you probably needed to create a meeting before the PBX had the chance to resync.

 

[edfosho]

Thanks for the explanation!