Cisco switch Config - Phone

Hi,
you'd better add thise lines:

 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape  10  0  0  0
 mls qos trust device cisco-phone
 mls qos trust cos
 auto qos voip cisco-phone

as in your working switch, as it gives yiu the right QoS as well.

Besides note that the working switch is 10/100 Mb while the latter is Gb.
Your phone might have problem to get tftp server and/or IP from DHCP from Voip server.

You should connect with a console cable to the switch (to see if you have duplex mismatch) or see logs in voip server

hope this helps
max

Can you let us know what make and model of phone you're trying to plug in? Voice VLAN configuration is pretty straightforward with Cisco and Polycom phones, but if you're using something else, it can be more involved.

I would add to the global switch config:

Lldp run
Cdp run

Non-Cisco phone's use lldp protocol to communicate with switch that they are a phone, and then they can get the voice vlan, etc.

Hi Experts,

The phone were using is a Cisco 8845. Also not to proficient in switches, i want to be careful with what I am entering, I would like if I can get a command for single port to try out first. Thanks Much.

Some phones will use LLDP while other phones rely on the untagged network's DHCP options to figure out their voice VLANs. It all depends on make and model.

Hi Jody,

Thanks, I checked the phone and dhcp is set to on. Do I have to look at the phone and Cisco Call Manager or is it at the switch level

If you're using a Cisco phone, all of the suggestions above from other experts should be followed. It won't be a DHCP options problem. Have you verified that you have general connectivity to the call manager on the voice VLAN?

Add...

Switchport mode access

It could be DHCP options actually. Cisco phones use them to learn the CCM address and TFTP server.

Doing some troubleshooting, plugging in an old cisco phone and checking some dhcp options clearing it to see the results. Will update the question shortly

Is this the first phone on this switch? If so, it may be worth checking the basics. Is the voice VLAN actually defined on the switch? Have you tried setting up an access port configured for the voice VLAN and just connecting a PC to it in order to verify the connectivity?

(@craigbeck, good point on the DHCP options. I was thinking purely in terms of the voice VLAN assignments.)

Hi Jody,

I thought with the port having switchport voice vlan20, that would enable the voice portion.

That's only part of it. The phone needs to know how to reach CCM. It does that via DHCP options.  If your DHCP server isn't offering the correct options the phone won't work.

The voice VLAN still needs to be functional and have end to end connectivity with the rest of the voice network. If it isn't defined in the switch, or there's a disconnect between your switch and the upstream switch, that will lead to trouble.

Try setting a port to access mode on VLAN 20, plug a PC into that, and see if you can ping the call manager from there.

Hi Jody,

I plugged the laptop in a port that is set to vlan 20 and I do get a ping to the call manager. I compared the switches we use for voice and I see that vlan 20 is configured with an IP where the switch stack having the issues with is not. Would that cause any issues?

Compared the settings on a switch port to which a working phone is connected, and configure this port in the same manner.

It would be simpler as others attempted to point to different things to consider.
Main point depending on whether the Cisco switch in use has the dynamic vlan assignment based on the MAC address or the type of data being passed, I.e. Voice type sip/h.323 data would be tagged and passed within voice vlan.
Versus seemingly you are trying to assign the port to a specific vlan and experience some issue.

The setting of the switch as level2 or level 3 switch...(level 3 can do routing within the switch, ...

So model of switch, config replace rputer name if identifies your organization.
There is little need to mask 192.168.10 10.1.10. Or similar private ip space.

......
10.0.0.0-10.255.255.255
172.16.0.0-172.31.255.256
192.168.0.0-192.168.255.255

These are private spaces free to be used and do not identify or distinct to that masking is needed.