FQDN for exstensions presence

[kresimir.plasc]

I am useing Web client to register users exstensions on 3CX v20 server (OnPrem)
Users PCs do not have internet access but 3CX has. Problem is with Extensions presence. On 3CX server user status and Queues extensions are greyed. Status can be seen only if Internet access is permitted from PSs.

My question is what destinations IP addresses/FQDNs and ports I should allow on my firewall from PCs to get users presence status

Thanks in advance.

 

[N_G]

You should not have to open anything client side. Webclient uses webRTC 443

 

[kresimir.plasc]

I knew but in my case client should have internet connection for presence
+

 

[SteveITS]

But the server is local…Are you using split DNS or NAT reflection/hairpin?

 

[kampagnol]

Hi @kresimir.plasc

If your PCs are able to work by allowing outbound traffic, I assume your firewall/router is able to hairpin traffic back into your 3CX server.

However...

If your PCs and your 3CX server are in the local LAN, it may be simpler / safer to use internal DNS / split DNS to resolve this without having the traffic routing out and back in through the firewall.

You could check this out on one specific PC by adding an entry in the hosts file that maps the FQDN of the server to the INTERNAL ip address for the server.
---
K.

 

[SteveITS]

Also just to be clear, browser notifications are enabled in the web client? (The bell icon was clicked)

 

[kresimir.plasc]

sorry I did not mention that I am using split DNS and from inside LAN clients resolving internal/LAN 3CX's IP address. Outside is static nat and public IP is static
Also browser notifications are enabled from start

 

[Kevin Attard Compagno]

Hi

This seems to indicate that...

EITHER

Your clients are not able to reach the internal 3CX IP Address - possibly a LAN routing issue

OR

Your 3CX is refusing or dropping the incoming requests from your clients - so you need to check, on your 3CX server, minimally firewall rules and/or ip blacklists

===

Hint 1: just because the client can RESOLVE does NOT mean that it can ROUTE
Hint 2: traffic captures are your friend