Our network currently has 2 CME's and because ip phones on different CME's are connected to the same switch we have had to set up each port on our switch's for switchport mode access and encap dot1q so that they can connect to both VLANS, The problem is that the phones often try to register with the wrong CME resulting in error: Registration failed: no config. When this happens we have to change the option 150 on the router the phone is trying to register to to point to the other CME, then when the phone registers we have to change it back.
Is there a way to set up a secondary option 150 so that when the phone fails to register with the CME it looks for its config on its secondary TFTP which would be the other CME.
the only other option i can think of is to go round to every switch in the network and find out which phones are on which VLANS and change the port to that VLAN which is a long process and then people would not be able to just pick up and move their phone to a different desk.
Iv tried to get people to change their numbers but execs are stubborn and wont let me change it.
From what I understand, you have phones for both CMEs in same VLAN. Generally people would configure two voice VLANs and have the phones for each CME in seperate VLAN and have a DHCP server in the concerned VLAN wih each DHCP server providing option 150 to the phones.
But as you seem to have both the phones in same VLAN (so it seems from your description of the problem) you can configure a secondary TFTP server using option 150 in dhcp pool.
Use the following command to keep A.B.C.D as primary TFTP server and W.X.Y.Z as secondary:
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...