Hi,
In scenarios where you are unable to configure a 4500 series MCU with the firewall option key to achieve communication privately and publically, would the following be a viable alternative:
- Deploy the Cisco MCU in a DMZ
- Allocate a private DMZ IP address (Routable over the internal network)
- Configure a NAT rule for external communication
- Configure identical DNS A records both internally and externally which resolves the MCU's FQDN to the respective IP address i.e. external A record resolving against the NAT'ed public IP address and the internal A record resolving against the private DMZ address.
Upon creating a ConferenceMe enabled conference, the URL provided will have the MCU's FQDN embedded which should be resolvable externally or internally - Obviously port forwarding would need to be configured appropriately also.
Has anyone achieved this?
Thanks, Simon