- Joined
- Jul 10, 2020
- Messages
- 18
- Reaction score
- 1
We currently designed our system so that the 3CX server would have 3 NICs to segregate traffic for data/Internet, SIP provider and the phones. Most of the multi NIC posts here consist only of 2 subnets where they combine the phones and the SIP provider. In our case, the SIP provider supplies a router through which only voice traffic passes (like the SingTel set up). The reason for our 3rd NIC is to totally isolate phones into their own VLAN with no default gateway provided to the phones. I was just wondering whether that would work or not? Reading from the supported network configuration document, it seems that the phones would still need to have a default gateway assigned?
Is my understanding correct and there is no use to keep the phones on a separate VLAN?
For those wondering why we're doing it this way:
1. We want data-only traffic to flow from anywhere to the 3CX's NIC1 which has an IP address that is mapped/NAT'ed to the public IP
2. We don't want our VoIP provider getting access to any of our other network via their on-prem provided router (i.e. they can only see the 3CX's NIC2 and the server itself has no routing services enabled)
3. We want to isolate our phones so that they are accessible only via 3CX's NIC3 and again this is also non-routable
Are we over killing it and should we just stick to 2 NICs?
Is my understanding correct and there is no use to keep the phones on a separate VLAN?
For those wondering why we're doing it this way:
1. We want data-only traffic to flow from anywhere to the 3CX's NIC1 which has an IP address that is mapped/NAT'ed to the public IP
2. We don't want our VoIP provider getting access to any of our other network via their on-prem provided router (i.e. they can only see the 3CX's NIC2 and the server itself has no routing services enabled)
3. We want to isolate our phones so that they are accessible only via 3CX's NIC3 and again this is also non-routable
Are we over killing it and should we just stick to 2 NICs?