Solved WebMeeting Server Error

[58voip]

Hello, 3CX teams,

The customer encountered a temporary error of the WebMeeting on this Monday very often. Then it worked. Is it the problem of the MCU that the customer selected? Just want to know the reason for the issue. So we can avoid it and make suggestions to the customer in the future.

 

[JohnS_3CX]

Hi,

The MCU the customer selected is preferential.

This means we will take into account the fact that you prefer that server IF it is available and not too far or too busy. It does not mean you will end up on that server. In fact, if the server is unavailable you get redirected elsewhere so the meetings are not interrupted.

Even though I cannot say for certain, this looks like a network accessibility issue.

 

[giwm]

Hmm... so what if you get that error and are set to automatic and have been using 3CX webmeeting successfully for a while? Oh, and changing the MCU does nothing?

 

[dalton1]

Hmm... so what if you get that error and are set to automatic and have been using 3CX webmeeting successfully for a while? Oh, and changing the MCU does nothing?

I'm getting the same error. looks like a network issue at 3cx?

 

[FridayIT]

We have the same issue on our side. Tried changing MCU and restarting system services without luck. This is a 3CX side issue.

 

[dalton1]

Error has changed a Google page with 404 that's an error. the requested URL was not found on this server, that's all we know.

 

[FridayIT]

Confirmed - same here. I've updated our support case with the details

 

[immarbethelportales]

I have the same problem

 

[dalton1]

Just have to wait for them I guess, the status page says all okay. I hope they remembered to pay the bill!!

 

[LeonidasG_3CX]

Hi everyone,

Yesterday from 20:45 - 22:00 GMT+2 we experienced unexpected downtime when our WebMeeting Director proxy services which authenticate WebMeeting customers before directing them to their respective WebMeeting Zone Portal & MCUs.

The Director service running on GAE detected a health issue and tried to automatically fix itself but due to very unexpected circumstances was unable to do so. After manual intervention by our team/s the issue was resolved.

The fault cause was identified and has been temporarily addressed. A full review of the cause is pending once our teams reconvene soon.

We apologize for the inconvenience during this downtime. We do our best to try to provide the best user experience with WebMeeting and keep everyone happy but failed in this instance. As with all mistakes, we've learned from this one and will ensure not to repeat it.