Hi everyone. We have 3CX installed on AWS using the PBX Express which gave it an internal IP of 172.31.17.202 on the default VPC since it never let me pick a VPC, and then an elastic IP 35.x.x.x.
We then have a VPN bonding system that also runs on AWS, completely different VPC but it has an internal IP of 172.31.16.100. Without getting too in depth, we have 2 fibre connections here and LTE, and the VPN bonds them and load balances, sending all traffic out through AWS so if one WAN goes down the others take over and calls aren't dropped.
When we are in the office, if I set it to send all 3CX traffic over the VPN, our 3CX clients register and show their IP as 172.31.16.100, as expected. The problem is that I guess the client seems to think that 3CX's internal IP of 172.31.17.202 should be accessible internally or something, so there's no audio on calls and they never work. If I go into the account settings in the 3CX client and manually change the "In office" to match our out of office company.3cx FQDN then it works fine, all traffic goes over the VPN and works as expected.
So long story short, how do I set in office and out of office both to only connect via the FQDN and not the internal IP since the internal IP for 3CX would never be accessible? Manually changing it on the 3CX client works but I'm not sure how long that sticks for, and is kind of confusing to request all my users manually change it.
Thanks!
We then have a VPN bonding system that also runs on AWS, completely different VPC but it has an internal IP of 172.31.16.100. Without getting too in depth, we have 2 fibre connections here and LTE, and the VPN bonds them and load balances, sending all traffic out through AWS so if one WAN goes down the others take over and calls aren't dropped.
When we are in the office, if I set it to send all 3CX traffic over the VPN, our 3CX clients register and show their IP as 172.31.16.100, as expected. The problem is that I guess the client seems to think that 3CX's internal IP of 172.31.17.202 should be accessible internally or something, so there's no audio on calls and they never work. If I go into the account settings in the 3CX client and manually change the "In office" to match our out of office company.3cx FQDN then it works fine, all traffic goes over the VPN and works as expected.
So long story short, how do I set in office and out of office both to only connect via the FQDN and not the internal IP since the internal IP for 3CX would never be accessible? Manually changing it on the 3CX client works but I'm not sure how long that sticks for, and is kind of confusing to request all my users manually change it.
Thanks!
