Solved Unable to add participants to WebMeeting

[farmeunit]

This was working a few weeks ago, but have banned a LOT of IP ranges recently in our Fortinet and now it's not working. Originally, I had France allowed after having it blocked last time this didn't work.

Now I'm NOT geo-blocking France, but have issues with "An error occured while sending request to domain.com:5001"

I have 5 IPs allowed first in firewall.

3CX Allow 151.80.125.99
3CX Allow 158.69.11.10
3CX Allow 51.254.74.8
3CX Allow 69.197.144.178 (US Server)
3CX Allow Webmeeting 35.242.241.239

The ports are obviously correct, but I've blocked a range I don't know about. How can I track this down? What should I be looking at in the logs?

v15.5 lastest

 

[YiannisH_3CX]

Hello @farmeunit

Please note that you need to be able to access webmeeting.3cx.net and the MCU you are using for webmeeting. You should need any additional IPs for webmeeting to work

 

[farmeunit]

I can access those, it's the return/inbound response that I'm not getting. Using a Fortinet 600D. I have a group specifically set to geoblock by country, and a second group for IP blocks that drop traffic. I have had a lot of traffic allowed recently to legitimate services, but from illegitimate sources. So I started blocking IP ranges that I know don't need to access those services. In doing so, Webmeeting doesn't work. I found 3 IP ranges were in France, where in the past, I couldn't block. So I removed those from blocked group and it still didn't work.

If I move the block groups below the 3CX Blacklist I have, for machines that pass the filter, but are blacklisted by 3CX itself, then WebMeeting works. Once I move the block groups up again. WebMeeting doesn't work. Just not sure how to track down the IPs I need. Is there a log somewhere that shows what IP ranges it's connecting from in 3CX?

I can't find what I'm looking for in my Fortinet. I'm sure it's just my lack of familiarity with it.

 

[farmeunit]

I found the area in Fortinet to look, add that IP to the Allow list and moved that rule up and it's working now. Thanks for the information, it was helpful. I just wasn't sure how to find the information I needed.

 

[YiannisH_3CX]

Glad to see the issue has been resolved.