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.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...