pls replycan u provide a confirmation that can i use 3cx hosted in UAE region and can i provide it to customers?
?if it have a CGNAT issue can i use additional router or firewall to overcome this is
Just no! Please stop doing any crazy stuff and listen to the people they trying to help you.To set up a VPN tunnel between your on-premise 3CX and a cloud instance to bypass firewall issues, here is a step-by-step guide using OpenVPN on a cloud provider, like Oracle Cloud or digital ocean. This setup provides a secure, single port tunnel, minimizing firewall configuration needs.
Prerequisites
- A cloud account on Oracle Cloud (Free Tier), DigitalOcean, or another provider.
- Access to your on-premise 3CX server and your firewall/router settings.
Step 1: Set Up a Cloud Instance
- Sign in to your cloud provider (Oracle or DigitalOcean).
- Create a Virtual Machine (VM):
- Choose a small instance type, like Oracle’s Free Tier VM or a DigitalOcean droplet.
- Select Ubuntu or Debian as the operating system (works well with OpenVPN).
- Configure Networking:
- Assign a static IP to the VM (some providers include this for free).
- Open port 1194 (UDP) in your cloud provider’s firewall settings for OpenVPN (or choose TCP if required).
Step 2: Install OpenVPN on the Cloud Server
ssh user@your-cloud-ip
- Connect to your Cloud VM:
- Use SSH to connect to your instance:
sudo apt update
- Install OpenVPN:
- Update the package list:
sudo apt install openvpn easy-rsa
- Install OpenVPN and Easy-RSA:
make-cadir ~/easy-rsa
- Configure Easy-RSA for Certificate Generation:
- Make the Easy-RSA directory:
cd ~/easy-rsa
- Initialize PKI and create certificates for the server and client.
- Configure OpenVPN:
- Create and edit the OpenVPN server configuration file (/etc/openvpn/server.conf) with basic VPN settings.
- Make sure port 1194 and proto udp are set (adjust to TCP if needed).
- Start OpenVPN:
- Enable and start OpenVPN:
sudo systemctl start openvpn@server
sudo systemctl enable openvpn@server
Step 3: Configure OpenVPN on the On-Premise 3CX Server
- Install OpenVPN Client on your 3CX server if it’s a Linux machine, or download the client on Windows.
- Import the VPN Configuration:
- Transfer the VPN configuration file generated from the cloud instance to the 3CX server.
- Start the OpenVPN client on the 3CX server and connect using this configuration.
Step 4: Adjust Firewall Settings
- Firewall Adjustment on 3CX Location:
- Open only port 1194 (UDP) (or the port you configured) for outgoing VPN traffic.
- No additional SIP or media ports need to be configured for NAT, as all 3CX traffic will route over the VPN.
- Test the VPN Connection:
- Once the VPN is active, ensure your on-premise 3CX can communicate through the VPN tunnel to the cloud instance.
Step 5: Configure 3CX to Use the VPN Connection
is this method is possible in real life scenario ?Can u please suggest how can i search for it?
- Set 3CX Server to Use VPN IP:
- In your 3CX management console, configure it to communicate through the VPN IP addresses.
- Test Calls and Connections:
- Test internal and external calls to confirm that the VPN tunnel is handling the traffic properly.
That has nothinh to do with your firewall your starting here. please stay at one thing and dont start many new things. You are not capable to fix the first thing, why are you trying alot more complicated stuff before you are able to fix the easy stuff.Not like that sir, this is a doubt raised by my team lead to ask in community i need answer only when anyone knows about this or aware with this in here
Did you see the part where he's on CGNAT? Aint no BT hub in UAEWas the original port mapping issue ever resolved?
If not it looked remarkably like the issue I had getting 3CX to work behind a "Business Smart Hub 2" router.
The problem was due to how ports were forwarded, forwarding only happens for INBOUND connections, OUTBOUND connections used the default NAT function which remaps ports.
The partial solution was to use the router's DMZ function instead of port forwarding. There's an important caveat though, this makes ALL ports reachable including port 22 (SSH) so to be safe I added a rule to forward port 22 to nowhere because I don't want to expose it.
Other than that putting 3CX in DMZ just works.
Regarding using 3CX cloud with a SBC, I haven't configured one but as I understand it the SBC is responsible for connecting to the cloud instance and the SBC creates a secure tunnel by itself it doesn't need a VPN
Oh and for multiple customers on the same host that would be multi-tennant. Alternatinvely you'd need multiple virtual machines each with its own IP address, good luck with that...
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.