Reconnecting Media...

[matush8]

Hello all,

we are experiencing "Reconnecting Media.." today. The WebMeeting was working fine in last two weeks and there was no configuration change on our 3CX installation during the weekend.

Do you have the same issue?

Best regards,
Matus

 

[Jim Spaargaren]

We are still having this problem. What can we do to fix this?

 

[JohnS_3CX]

What MCU are you currently connected to?

 

[Jim Spaargaren]

What MCU are you currently connected to?

It is set to automatic at the moment. Can I check it somewhere?

 

[JohnS_3CX]

@Jim Spaargaren
have you restarted your system service though? if yes and it still fails, send me a private message with your FQDN and Key.

If no, the restart it and try again

 

[Fernanda]

Same problem here, since yesterday

 

[LeonidasG_3CX]

Hi all, please report which MCU you were connected to when the issue occurred. You can see where you're connected to by opening the settings tab inside WebMeeting and going to the Info tab.

 

[LeonidasG_3CX]

We detected an issue with our MCU in Sao Paulo today which was the cause for the error you mentioned. The issue has been resolved and the Sao Paulo server can now be used again. If you experience the same issue on another server, please let us know.

 

[pigdog]

I too am experiencing this problem on my own instance and on my client's instances, we currently are trying to connect to South Africa MCU (centurion and cape town) but none are working the MCU's are af003-cnt.3cx.net and af004-cpt.3cx.net it always used to work in the past. For now my only workaround is to connect to London but the latencies are not so good.

 

[JohnS_3CX]

@pigdog
Can you confirm whether the system service has been restarted yet?

 

[Francois92]

Hi @JohnS_3CX,

We're experiencing the same in South Africa using the Automatic option and setting it to static.
South Africa (Centurion) 0003 (af003-cnt.3cx.net)

Thanks for your assistance.

 

[Francois92]

@pigdog
Can you confirm whether the system service has been restarted yet?

@JohnS_3CX

We have restarted the services and tried reloading one of our instances.

This is definitely server related.

 

[pigdog]

@pigdog Can you confirm whether the system service has been restarted yet?

I restarted all 3CX services and then decided to restart the whole server, it was only after restarting the server that the London MCU started working but still not the South African ones I have just for good measure restarted the services yet again

 

[JohnS_3CX]

Give that there is a major cable down now (scheduled to be repaired on 04/04/2020) you may have some trouble reaching the MCU.

Can you manually select another MCU (even if its far away) ?

 

[Francois92]

Hi John,

I was able to get it to work on the eu053-lon.3cx.net MCU earlier this afternoon.
Not the ideal but it will do for now.

Thanks.

Kind regards,
Francois

 

[IPMG]

We are still having the problem all week. using the following MCU: South Africa (Centurion) 0004

PBX MCU is set to automatic

 

[JohnS_3CX]

Check the latest status here for when https://status.3cx.net/

2020/04/02 | ZA degraded routing

Thursday April 02, 2020

2020/04/02 | Degraded routing has been observed with connections from ZA-ZA and ZA to EU and other zones. Connectivity issues to WebMeeting services may be observed by users in ZA.

 

[JLSeagull]

Hi all.

Same issue here in Brazil (Sao Paulo) when scheduling the meeting. In addition, I don't see option to set MCU on Quick Meeting.

 

[yetopen]

I don't see option to set MCU on Quick Meeting.

This is only in the admin panel, not in the user frontend

 

[JLSeagull]

This is only in the admin panel, not in the user frontend

OK. Thanks! I have updated the settings for MCU on 3CX Management Console.

 

[JLSeagull]

Hi!

I am in Brazil and I am facing the problem using MCU Brazil (Sao Paulo) 0100 (us100-sao.3cx.net. I have changed it for United States (Oregon) 0040 (us040-hil.3cx.net) and apparently solved.