I'm having a heck of a time getting my IP Communicator to register over a VPN. It registers in the wink of an eye if I'm in the building, but if I go outside, not so much. I am using IP Communicator 220.127.116.11, the Cisco VPN client 4.0.1 and I'm connecting to a PIX 506. The connection occurs, but IP Comm. just won't register. The thing I'm wondering about is whether my topology might be part of the issue. My CallManager is in site 1. Site 1 is connected using a VPN to site 2 which is where the PIX my IP Comm. computer is connecting to is located. I can ping the TFTP server when the IP Comm. computer is in the building, I cannot ping the TFTP server when I'm connected using the VPN client.
I would presume. Inside the the settings for the IP Comm. I have the hardware NIC selected as the network card. Again, though, I think the real issue to troubleshoot first is the fact that I can't ping CallManager.
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 ...