Actually, I have already done this. We have the TFTP server up and pushing the config binary file to the ATA, but it seems to be having problems when we set a static address on the ATA 186. We get all the proper provisioning... UID's Gatekeeper Address, etc, but we want the ATA to keep its statically assigned address (the one we entered via the handset or web access). So, we leave out the IP address, Subnet, and Router address from the binary assuming that the ATA will keep the IP address we statically assigned it. However, when the ATA gets its config from the TFTP server, the ATA puts 0.0.0.0 into all three fields.... essentially wiping out access to the box.
These seems like a horrible way to provision a multitude of ATA's. It seems like the only way to set them up using TFTP is if you know the IP address or the unit is set to DHCP.
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 ...