When I initially built the server, it was configured with a hostname of "mpx" and a domain name of "company.corp"
When I mapped an external IP to the server and pointed to it from an external host, the web browser is redirected to "mpx.company.corp" and that returns an error because an external host can not resolve that address.
So created a DNS record, and pointed meetings.company.com to the external IP Address of the server. Also, internally, I changed the DNS record meetings.company.com to the internal IP Address of the MPX server.
So the next step was to change the domain and the hostname of the server, so I used the "net" configurator to make such changes. I saved the configuration and rebooted the server. Ever since then the server has not been accesible via HTTP. I can access it via SSH with no issues, and since I built it, I have access to root if needed.
I think HTTP is broken because something in Tomcat needs to be reconfigured to reflect the changes.
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: email@example.com 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 ...