Failover breaks webmeetings

[giwm]

Like many people, we've experienced meetings suddenly going to the troubleshooting page. It was easy to blame it on user error, but today it happened to me for the first time. We BELIEVE that in this instance, it was due to a failover event. After switching our backup 3CX back to passive, we restarted the 3CX System Service on our primary 3CX instance. This seemed to fix the couple meetings we were able to test with.

Is anyone able to test and confirm this is an issue and not isolated to my install?

 

[LeonidasG_3CX]

Hi,

Both PBX's databases will need to be synced in order for WebMeeting to work as you'd expect.

Here's how things can go wrong if this is not the case:

• Meetings are created and stored on your primary PBX A because that's what you use daily.
• You create meetings on PBX A on day 1.
• On the say day, PBX A stops working and your failover PBX B starts up.
• The PBX B grabs the latest configuration backup of PBX A and restores it to PBX B.
• PBX B services start up and meetings synchronize the PBX B meetings with our WebMeeting servers.

If the backup restored (or if not backup was restored) on PBX B is older than 1 day and does not contain those new meetings then when opening a meeting link that previously worked correctly now stops working.

It would be best to verify you've followed this part of the failover guide correctly as the 2 PBX's being synced is critical if you want your failover to have the most updated DB data in case of failover.

 

[giwm]

To clarify, the failover process doesn't always happen between backup/restore processes. I'll have to review the latest failover documentation, as we may need to tweak it, but what actually happened was the internet connection between them dropped, so the heartbeat pings dropped. This caused the failover to assume it was up to bat and become active. When the internet came back up, we manually switched it back to passive. The primary never flinched so those services never restarted. So until we manually restarted the Server service on the Primary, our web meetings didn't work.