I'm running CCM 4.1(3), currently having a unique situation.
Just deployed 3 IP phones, a 7941, 7902 and ATA-186.
The 7941 works perfectly fine, however the 7902 and ATA were not, they seems to be not able to register with the CCM.
When I brought the 2 problem unit back to my office at level 2, they worked fine, again when I brought them back to level 5, the problem persisted.
All the IP phones are connecting to a CE500 PoE switch, all ports Voice and access vlan are verified. I've also swapped the ports with the working 7941, but to no avail, the CCM still shows the phone as not registerd and the IP address showing level 2 office vlan
I've removed the IP address lease from the level 2 VLAN DHCP service, but still it does not register.
What could be wrong? how to find out what went wrong. The 7941 is working fine, but not the rest at level 5 vlan
OK, found what what happened. Basically switching problems. Tried the above but still can't work.
I have a 3750 thats doing routing of a few vlans i have across the building. I have a few 3560s thats directly connected to this switch using the SFP port. During this new implementation, I've linked the CE500 to one of the 3560's SFP port. Thinking it will be able to trunk it all the way back to the 3750 to do the inter vlan routing. Somehow it is not working.
3750 - does the vlan routing
3560 - Vlan 300 - for level 3
CE500 - vlan 500 - for level 5
3750 -- connects to 3560 -- both link ports configured as mode trunk and 802.1q encapsulation
CE500 -- connects to -- 3560
CE500 using smartport config as switch role for uplink port
3560 configured as mode trunk and 802.1q encapsulation
somehow the Vlan 500 subnet is not able to be routed to Call manager subnet in vlan 200. Where the IP phone types 7902 and ATA186 do not have the ability to understand trunk, thus explains why 7911 and 7941 works only
If I want to use the uplink on the 3560 to be used for connecting to the CE500 thats in a different vlan, What should I do?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...