Have a question regarding some issues when running Avaya 9600 phones on my 3560 switches. Under normal circumstances, our IP phones work properly when we manually tell the Avaya phone what vlan it should be in. We use these commands on the ports that have the 9600 phones:
description IP Phone
switchport access vlan 16
switchport mode access
switchport voice vlan 204
The problem is when I completely erase all the phone settings, or add a new phone out of the box to one of these switchports, the phone will not properly boot up until I manually add the vlan information into the phone. We had a power outage recently where when the power came back on, many of the ip phones lost their vlan information, and we had to manually walk to each desk to put in the vlan information so they could boot up. Wanted to know if there was some work around to this that anybody has experience who has a similar environment.
Yes, we are using dhcp, and we are using option 242 with the information that you mentioned. Upon further troubleshooting, I discovered that I needed to put that string in option 242 in both the voice vlan, as well as the corresponding data vlan.
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...