I just want to verify that I am understanding the VLAN settings for an IP phone correctly, with a few examples:
I understand that the use of a voice VLAN together with CDP or LLDP is the recommended way of working for assigning VLAN's automatically.
But I want to understand the other option's better.
1) I have a basic SOHO switch with only VLAN's so no CDP or LLDP. All interfaces are assigned to 'default' VLAN 1 untagged, a DHCP server is also connected to a port in VLAN 13.
My phone is a 7945 for example, brand new out of the box.
If I connect the phone, he will just come up on this untagged VLAN and get an IP address from the DHCP server, just similar as a regular PC would?
2) same situation as in 1), but now I also connect a PC to the phone's internal switch, will the phone's switch just pass the traffic to the PC by default as would be the case with a regular switch. So in this case I will end up with the PC, phone, and other devices connected to the switch on 1 VLAN (VLAN 1 in this case)
3) I create a 2nd VLAN on the switch (VLAN 2) which will be used for voice. On the port connected to the phone I create a 802.1Q trunk with VLAN 1 as the native VLAN (untagged) and VLAN 2 as tagged. Still my switch does not support CDP or LLDP.
- The phone boots and will get a IP address in VLAN 1 again as was the case before the creation of the trunk?
- I need to manually configure the Admin VLAN ID to VLAN 2?
- The PC VLAN option stays empty since it is untagged?
- After a reboot the phone comes back up and receives a IP in VLAN 2, and the untagged traffic is forwarded to the PC connected to the Phone's internal switch?
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...