blacklist due to local ip definition

[cturk]

Hello,
We purchased from your 3cx dealer to run on local servers in our company. Setup with the technical team that will lead our company performs 3cx ip range are being used in the black list have indicated they are looking for does not alter the rope if we can not use the system.
The ip range we want to use for ip phones and 3cx PBX is planned between 192.20.30.1 - 192.20.30.254 for ip phones and 3cx PBX. However, the technical team that made the installation; It states that we cannot use this range, citing that it has blacklisted the internal network ip range 3cx starting with 192.20.x.x. We access the Internet by using a fortigate security device at the exit of the local network. Naturally, why doesn't it accept the ip range that I have given or wanted to define to 3cx in my internal network? Is the technical team giving wrong or incomplete information? Please help me.

 

[SteveITS]

Not sure what a "rope interval" is...typo?

192.20.30.x is a public IP address range, belongs to AT&T. I suggest not putting your phones directly on the Internet. Were they intending to use a private subnet like 192.168.30.x?

 

[Saqqara]

192. 20.30.0/24 is not part of the rfc 1918 address range which is reserved for private use. Tech team are giving correct info

you will have issues if the 3cx is not on a rfc 1918 network, as the system only listens on rfc1918 networks addresses

More info here https://netbeez.net/blog/rfc1918/

 

[cturk]

192. 20.30.0/24 is not part of the rfc 1918 address range which is reserved for private use. Tech team are giving correct info

you will have issues if the 3cx is not on a rfc 1918 network, as the system only listens on rfc1918 networks addresses

More info here https://netbeez.net/blog/rfc1918/

Wouldn't nat be a solution? As a result, the 3cx goes to the Internet via a gateway.

 

[SteveITS]

Normally when using NAT one uses private IPs on the LAN/internal networks and NAT translates those to one public IP to get to the Internet.

3CX can use public IPs. That's how we set it up when we host 3CX. But then there aren't any local connections since everything is connecting over the Internet.

The problem as described here is that anything on the Internet that tries to connect to your server by its 192.20.30.0/24 IP address will end up connecting to whatever is actually using that public IP.

Or are we misunderstanding and you have actually been assigned that entire subnet by AT&T?

 

[cturk]

Normally when using NAT one uses private IPs on the LAN/internal networks and NAT translates those to one public IP to get to the Internet.

3CX can use public IPs. That's how we set it up when we host 3CX. But then there aren't any local connections since everything is connecting over the Internet.

The problem as described here is that anything on the Internet that tries to connect to your server by its 192.20.30.0/24 IP address will end up connecting to whatever is actually using that public IP.

Or are we misunderstanding and you have actually been assigned that entire subnet by AT&T?

Thank you for the information you provided. normally we tried to create a structure by dividing it into vlans within the company. In this structure, we planned the rope as 192.company.device.xxx/24.
192.20.10.xxx/24 A Location servers,
192.10.10.xxx/24 B Location servers,
192.20.20.xxx/23 A Location Clients,
192.10.20.xxx/23 B Lovation Clinets,
192.20.30.xxx/ 24 A Location 3cx Network,
192.10.30.xxx/24 B Location 3cx Network. We thought that, but we chose the wrong segment. 3cx is also blacklisted.

 

[JohnS_3CX]

Wouldn't nat be a solution? As a result, the 3cx goes to the Internet via a gateway.

No, it would not be a solution. Convert all your subnets to RFC1918 or you will have the joy of discovering all the problems this will cause in the future.

https://www.3cx.com/docs/manual/pho....e. 172.16.0.0 /10.0.0.0/192.168.0.0 IP range.