Solved Cant Access **.3cx.co.uk webmeeting URLs

[alex22alex]

Hello,

We can access webmeeting urls when on the same lan as the 3cx machine with an ip based url like https://192.168.2.124:5001/webclient/#/login

However our non local url http://companyname.3cx.co.uk:5001/webclient/#/people doesnt load. Anyone got any suggestions to guide in the the right direction ?

I guess potential some sort of firewall issue here ?

Thanks everyone

 

[3cx31]

Hello,

it depends on your network. If you can create an internal DNS record in your DNS Server from
companyname.3cx.co.uk --> A Record --> 192.168.2.124
this would be the simplest solution for all users in your network.

Another alternative would be to write this in your Windows PC host file.

And the last option would be to check the firewall to allow reverse NAT.
When you call companyname.3cx.co.uk it will resolve to your WAN IP address.
Commonly do firewalls not allow to send data out and back in. You might can "NAT" the request back to your PBX. It is a bit of a hack though...

 

[alex22alex]

Thanks for the reply i understand about hosts internally thanks for that.

What i didnt understand then is that 'companyname.3cx.co.uk' isnt anything to do with 3cx or so it sounds. I assumed it was some sort routed link to our internal server for people externally trying to access it ? Kind of like a dyns forwarder which it sounds like it is not ?

Thanks. Alex

 

[JohnS_3CX]

Hi Alex,

When accessing your (locally installed) PBX via the FQDN http://companyname.3cx.co.uk:5001/webclient/ you need to ensure the ports are forwarded (otherwise the PBX is not accessible from outside ie. form your home).

However, if you want to access the FQDN from within the company, and your firewall does not allow hairpin traffic, you will have to point your local DNS server to resolve it at 192.168.2.124

These are two separate problems, I hope my explanations was helpful

 

[alex22alex]

They are perfect i fully get it now!

 

[JohnS_3CX]

Glad to hear