We are running CallManager 3.0(8) in an eleven story building with approx 1200 phones. Each floor has a 6500 for an access switch which converge at dual 6500s (w/MSFC) at the core. We thought it would be a best practice to give each floor a separate data and auxillary VLAN. We have users who are switching floors and taking their 7940/7960s with them. This will place their phone on a different voice VLAN. Just plugging the phone into the new switch does not work. Also, reseting the phone (**#**) does nothing. We have to go to the Network Configuration on the 7940/7960 and release the DHCP address and re-initialize the phone.
Is this how it is supposed to work or do we have the 6500s misconfigured? I/we were under the impression that we could move the phones anywhere on the LAN with out any re-configurations.
We also think that it should work, but it doesn't. The 6500s are setup almost exactly from a cookbook. What kind of information gathering do you think we need to do? I would think that CDP would have cleared this during the port to phone setup.
When you go to the network configuration after you have moved a phone, does it show in option number 19 that the Operational VLAN Id has changed to the correct value for that particular floor? Just curious. Also, do you have portfast enabled on the switchports the phones are connected to?
I also wonder if you move a PC (e.g. notebook) to a different floor, would it work correctly without doing anything special?
In any case, what I would suggest is to make sure Forwarding Delay is set to NO on the phone configuration, plug a PC running sniffer software into the PC port, plug the phone into the wall and start the capture. We should be able to figure something out from the sniffer trace.
Hmmmmmm. It appears that DHCP is returning the old IP address. Funny that it only happens if we don't release the IP address from the phone. We are now looking into IP Helper and DHCP on the CallManagers. Any ideas?
Try restricting the vlans allowed on the trunk from the core switch.
You say you have a different Vlan for each floor (I assume a different Aux VLAN also) are you running all vlans on the trunks to all switches? It could be the switch is seeing the phone attempt to connect to a Vlan the switch knows about so allows it through (something to do with the way the phone sets up trunking).
However if the switch doesn't know about the Vlan then it should force the phone to request a new one and subsequently a new IP address.
We had the same problem with phones and laptops set to dhcp. Turned out it was a known bug with Win 2000
server. Dhcp scopes configured under a superscope will not release the original dhcp address. When you move to a different vlan you still get the original address. We reconfigured individual dhcp scopes with out the use of superscope, and this solved the problem. This was approximately three months ago.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...