Webmeeting - Meeting not found

[firenet]

Hi all,

We have encountered a strange issue where some extensions suddenly cannot create webmeetings, this is affecting about 25 instances of 3cx. I have tried the fixes in this thread with no change - https://www.3cx.com/community/threads/select-users-on-pbx-are-getting-web-meeting-not-found.55381/ . I tried restarting services, rebooting VMs, changing conferencing servers to Singapore and others, tried loading from different ISPs, tried 3cx instances with different SSL certs, creating new extensions is hit or miss.

For example on our test instance we have 2 identical extensions:

https://testing-firenet-net-au.3cx.net/webrtc/join/testing -- (extension 100) not working.

https://testing-firenet-net-au.3cx.net/webrtc/join/firenettesting -- (extension 110) works fine.

Systems are: linux debian 8 and 9, windows 2016 all on vmware.

based in sydney so we use the syd conferencing server - as003-syd.3cx.net 43.245.161.34



For reference: I have logged a support case as i am a 3cx gold partner but have not had any response for 4 days (#232220 if any 3cx rep is looking). Tried the support number assigned to us but plays a message saying all agents are busy and then hangs up, tried our sales rep but was told to call.

I decided to try the forums to see if anyone else can suggest things to try. It must be something on our end otherwise i'm sure there would be a lot more posts about it.

 

[LeonidasG_3CX]

-Could you please try giving your 3CX System Service a restart? This won't cause any downtime on your PBX.

-Ports 443 or 5001 are open to inbound/outbound traffic?

-Are you on a self signed PBX certificate?

-Is webmeeting.3cx.net blacklisted in your PBX by any chance?

 

[firenet]

-Could you please try giving your 3CX System Service a restart? This won't cause any downtime on your PBX.

-Ports 443 or 5001 are open to inbound/outbound traffic?

-Are you on a self signed PBX certificate?

-Is webmeeting.3cx.net blacklisted in your PBX by any chance?

I had already restarted all services and also rebooted the server BUT just restarting the system server service fixed the issue, re-reading the thread I linked it did say restart just that service but I misread it as restarting all services. I did not try this in my testing. Thankyou Leonidas.

I'm just a bit confused why only restarting that service did it instead of the all services restart or reboot.