- Joined
- Jan 16, 2019
- Messages
- 1
- Reaction score
- 0
Hi mates,
- I am going to deploy an Full Licensed On-Premise 3CX system (Windows Server Based) for my company with 2 NICs on 3CX Server as below:
+ 1st NIC ("in-bound" direction) connected to Local system (Core Switch => Core Router with VLAN Routing) for 3CX Clients connect to this 3CX Server: no default gateway for this NIC, just Local IP Address and add Routes to local subnets/VLAN & ping OK
+ 2nd NIC ("out-bound direction) with default gateway connected to Cisco Router acts as Voice SBC (with 2GE interface: 1 GE0/0 to 3CX Server & GE0/1 to Fiber Internet Router, and VIC2-4FXO module for PTSN CO lines calling in/out)
3CX Server ipconfig /all
Host Name . . . . . . . . . . . . : 3CXSERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter VLAN 19:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Gigabit Ethernet (NDIS VBD Client) #34
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::31ce:xxxx:xxxx:xxxx%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.19.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.19.1
DHCPv6 IAID . . . . . . . . . . . : 129773659
DHCPv6 Client DUID. . . . . . . . : xx-xx-xx-xx-xx-xx-xx-xx-xx-xx
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VLAN 1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Gigabit Ethernet (NDIS VBD Client) #33
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
3CX Server route print
Interface List
7...xx xx xx xx xx xx ......Gigabit Ethernet (NDIS VBD Client) #34
2...xx xx xx xx xx xx ......Gigabit Ethernet (NDIS VBD Client) #33
1...........................Software Loopback Interface 1
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.19.1 Default
192.168.2.0 255.255.255.0 192.168.1.1 1
192.168.3.0 255.255.255.0 192.168.1.1 1
192.168.4.0 255.255.255.0 192.168.1.1 1
192.168.5.0 255.255.255.0 192.168.1.1 1
192.168.6.0 255.255.255.0 192.168.1.1 1
192.168.7.0 255.255.255.0 192.168.1.1 1
SO, IS IT POSSIBLE TO DEPLOY 3CX SYSTEM LIKE THIS? OR ANY RISKY ISSUE, BETTER SOLUTION FOR MY DEPLOYMENT, MATES.
WILL 3CX GLOBAL SUPPORT TEAM HELP ME ON THIS CASE FOR PURCHASED LICENSE WITH THIS DEPLOYMENT?
SINCERELY!!!
- I am going to deploy an Full Licensed On-Premise 3CX system (Windows Server Based) for my company with 2 NICs on 3CX Server as below:
+ 1st NIC ("in-bound" direction) connected to Local system (Core Switch => Core Router with VLAN Routing) for 3CX Clients connect to this 3CX Server: no default gateway for this NIC, just Local IP Address and add Routes to local subnets/VLAN & ping OK
+ 2nd NIC ("out-bound direction) with default gateway connected to Cisco Router acts as Voice SBC (with 2GE interface: 1 GE0/0 to 3CX Server & GE0/1 to Fiber Internet Router, and VIC2-4FXO module for PTSN CO lines calling in/out)
3CX Server ipconfig /all
Host Name . . . . . . . . . . . . : 3CXSERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter VLAN 19:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Gigabit Ethernet (NDIS VBD Client) #34
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::31ce:xxxx:xxxx:xxxx%7(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.19.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.19.1
DHCPv6 IAID . . . . . . . . . . . : 129773659
DHCPv6 Client DUID. . . . . . . . : xx-xx-xx-xx-xx-xx-xx-xx-xx-xx
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VLAN 1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Gigabit Ethernet (NDIS VBD Client) #33
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
3CX Server route print
Interface List
7...xx xx xx xx xx xx ......Gigabit Ethernet (NDIS VBD Client) #34
2...xx xx xx xx xx xx ......Gigabit Ethernet (NDIS VBD Client) #33
1...........................Software Loopback Interface 1
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.19.1 Default
192.168.2.0 255.255.255.0 192.168.1.1 1
192.168.3.0 255.255.255.0 192.168.1.1 1
192.168.4.0 255.255.255.0 192.168.1.1 1
192.168.5.0 255.255.255.0 192.168.1.1 1
192.168.6.0 255.255.255.0 192.168.1.1 1
192.168.7.0 255.255.255.0 192.168.1.1 1
SO, IS IT POSSIBLE TO DEPLOY 3CX SYSTEM LIKE THIS? OR ANY RISKY ISSUE, BETTER SOLUTION FOR MY DEPLOYMENT, MATES.
WILL 3CX GLOBAL SUPPORT TEAM HELP ME ON THIS CASE FOR PURCHASED LICENSE WITH THIS DEPLOYMENT?
SINCERELY!!!