I have a 7936 polycom that is displaying the error message "Cannot contact tftp server". I have reset to factory defaults, verified that it is not connected to a trunked switch port, and connected it to a known working power supply/switchport that another 7936 is working from. Only difference between two phones is firmware load versions.
Working 7936 app load = 7936.3-3-14-0 rev 16
Non-working 7936 app load = 7936.3-3-2-0 rev 14
- I can ping all tftp servers in UCCM cluster from this phone, but firmware upgrade does not work due to tftp contact failure
Is it necessary to manually upgrade firmware before tftp server(s) can be contacted? ..if so, is manual upgrade possible via bypass of the tftp service on an ip phone?
Any suggestions would be most helpful and I rate all posts!! :-)
Yes, the phone picks up an IP within the correct VLAN from DHCP successfully and references all the correct TFTP servers in the correct order as it tries to connect. Pings are successful in both directions to and from the phone/servers.
- No firewall ports blocking communication to the TFTP servers
- 7936 is in the same VLAN as the Call Managers
Remember, I plugged this 7936 phone into the same port as another known working 7936 and still received TFTP communication error. I can also ping all TFTP/Call Mgr servers from this phone.
I'm really thinking that it's got to be a hardware issue with the phone. All symptoms point to that, so I opened a TAC on it this afternoon and they stated that they will simply issue an RMA for replacement. Thanks for all posted replies on this matter.
Have you double checked that the phone is built in UCM with the correct MAC address? I've noticed in my environment that the 7936's will give that error rather than "registration rejected". Something simple but may save you an RMA.
Just wanted to follow-up on this and extend a thank you for all that responded to this thread...I was able to resolve my issue by deleting the 7936 from UCCM and manually creating the phone object. For some reason, the auto-registration would fail, but worked fine after manually recreating. I believe that this has something to do with the TFTP config files not being created on the subscribers during the auto-registration process which seems to have caused the registration reject. Also, I had to make sure that the "Build CNF Files" setting under Service Parameter Configuration | Clusterwide Parameters was set to "Build Selective".
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...