"DHCP addressing for daisy-chained PCs--A PC or workstation that is connected to the IP Phone
obtains its IP address from the same address pool (subnet) as the phone if DHCP is used for
With this I understand that if I have PC's connected to the phone switch I can't use DHCP servers. Anybody knows some workaround?, or at least can I have my PCs with static adressisng and the phones with dinamic of other subnet?
You can use DHCP for both Phone and PC, even if the PC is connected to the switch port on the phone. If both are in the same VLAN then you only need to configure one scope. If you want PC's and Phones in separate VLAN's, on your switch you need to configure AUX VLAN for the PC and Native VLAN for the Phone. Then setup one scope for each VLAN. Do not use superscopes though as there are known bugs when using AUX VLAN's and Superscopes on Win2k DHCP servers.
We Currently have PC's daisy chained off of our 7960 phones. The PC's get their IP from one DHCP server while the phones get their IP from a different DHCP server. The trick is you need a switch that supports auxillary VLANs. I know the 6500's do and I believe the 4000's do also, although not sure.
If you set Auxiliary VLANs on the switch the phone and switch will set this VLAN as the voice VLAN (VVID) and send 802.1q tagged frames to the switch for voice. PCs attached to the phone will send untagged Ethernet frames (unless you have a very unusual PC). The 802.1q frame will specify the Aux VLAN for the voice frames and the switch will assume that untagged frames from the PC are on the normal port-VLAN.
when you have a PC connected to an IP Phone you can have different IP subnets for PCs and IP Phones. You configure the port to the switch to which you connect the IP Phone as a trunk, which will have as native VLAN the VLAN of the PCs and as voice VLAN the VLAN of the IP Phones. So you can have static IP addressing for your PCs and your IP Phones obtaining their IP address from a DHCP server.
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...