Configure Meeting Connector Controller 1:1 NAT with end-to-end encryption Follow

The following is an example of configuring your Meeting Connector (MC) Controller using 1:1 NAT with end-to-end encryption support.

End-to-end encryption requires that each MC Controller has two IP addresses, which will be configured as an IP alias on the Network Interface Controller (NIC) once the configuration below has been saved and the VM has been rebooted. Please make sure that the second IP address has been reserved for this VM.

One Meeting Connector Controller (350 participants)

Your network information:

External IP address (for MC): 173.228.57.201
Internal IP address (assigned to MC): 10.251.10.123
Second External IP address (for MC alias): 173.228.57.202
Second Internal IP address (for MC alias): 10.251.10.124
Subnet mask: 255.255.255.0

Firewall Setup:

Set up 1:1 NAT 173.228.57.201 > 10.251.10.123
Set up 1:1 NAT 173.228.57.202 > 10.251.10.124

Controller Configuration:

 

Two Meeting Connector Controllers (700 participants)

Your network information:

External IP address (for to MC-1): 173.228.57.201
Internal IP address (assigned to MC-1): 10.251.10.123
Second  External IP address (for MC-1 alias): 173.228.57.202
Second Internal IP address (for MC-1 alias): 10.251.10.124
External IP address (for to MC-2): 173.228.57.203
Internal IP address (assigned to MC-2): 10.251.10.125
Second External IP address (for MC-2 alias): 173.228.57.204
Second Internal IP address (for MC-2 alias): 10.251.10.126
Subnet mask: 255.255.255.0

Firewall Setup:

Set up 1:1 NAT 173.228.57.201 > 10.251.10.123
Set up 1:1 NAT 173.228.57.202 > 10.251.10.124
Set up 1:1 NAT 173.228.57.203 > 10.251.10.125
Set up 1:1 NAT 173.228.57.204 > 10.251.10.126

Contoller 1 Configuration:

Controller 2 Configuration:

Was this article helpful?
Have more questions? Submit a request
Powered by Zendesk