From the Cisco docs that I can find that explains the procedure for setting up the Outlook integration with Presence, all of them describe setting up a certificate authority and creating a cert to be installed onto the presence server. This cert is then also installed into the exchange server so both the presence server and exchange server talk SSL.
The problem I think we have here is that our exchange servers already have external SSL certs installed. The certs are called webmail.<domain>.com to match the external DNS name that people use for OWA. The Cisco docs describe installing the cert into the Default Website of IIS on the exchange server, but this is where the other cert is, and you can't have two.
The only workaround I can think of is to set up an internal DNS record pointing webmail.<domain>.com at the internal IP address of the exchange server. Although this is not ideal, we'll do it if that's what needs to be done. I'm just wondering if that's the Cisco way??
the cert is a 3rd party cert, the name of it matches the external name of the server - webmail..com.
My CUPS server is on the inside of the network, if I point the CUPS at the internal name of the server, the cert name is not going to match. If I point teh CUPS at the external name of the server, it will resolve to the public IP, therefore sending it out to the internet in order to come back in.
So do I just create an internal dns record to point the external name to the internal ip address?? Doesn't seem right to me??
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 ...