I recently ran into a problem while deploying 30 new 7940 and 7 new 7960 phones. These phones were connected to three different 3550 switches. The port configurations on these switches is:
description user port
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2,1002-1005
switchport mode trunk
switchport voice vlan 2
no ip address
Even though the phones were supposed to be running on VLAN 2, they were getting DHCP addresses from VLAN 1. The "Network Configuration" menu on the phones showed an "Operational VLAN ID" of 2 but they would not communicate. The only way we could get these phones to come up was to set the switch ports to access mode and make them members of VLAN 1.
Once the phones upgraded their software from the factory P0030301MFG2 to P00303030200, I could re-configure the switch ports to their original dot1q trunk configuration and everything worked fine.
It seems to me that there is a problem between the original firmware and the 3550 switch. Has anybody else experienced this problem?
In 3.3 by default ip phones cnf files are not written into the tftpath so it might well be that you have the old file there and that the new one is stored in memory. So it looks like the 7940 and 7960 bunch that you recieved still had factory settings from Cisco.
The problem, as I saw it was that the phone never even got to the point of requesting its config becuase CDP and/or IP was not working correctly. The phone showed that it should be on VLAN 2 but was getting and IP address off of VLAN 1. The phone was never even getting to the point of trying to get its config from CallManager becuase it wasn't communicating with the network properly.
Here's an interesting tid-bit. I have had a similar situation w/ wireless clients. Currently I have four VLAN's per site...1 for management, 1 for data, 1 for voice and 1 for wireless. The wireless clients would end up pulling addresses from various IP subnets.
After a few days of working w/ TAC, turns out that because I had Superscopes (1 for each site) and then had the four individual scopes within it...the Wireless clients would pull from the first available scope.
Take the superscopes away....works like a champ.
Again...it's a long shot that you're doing this...but hope it helps!
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 ...