Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

7940 & 7960 Errors CCM

Hi,

I have a CCM 3.3(4) and for the most part it works perfectly, however I've had a couple of issues with the 7940/7960 phones. On several occasions I end up with the error on the Universal Application Loader Screen "Protocol Application Invalid" on the display. These phones worked fine under CME 3.1 in a remote site, however after I configured the CCM and environment to register this remote site 4 of these types of phones showed this error, and the rest of the phones 7910s, 7912s, 7905s and including some 7940/7960s registered fine. I searched everywhere for an answer but with no luck. Any ideas?

Djassi

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Red

Re: 7940 & 7960 Errors CCM

Hi Djassi,

Here is an excerpt from a Cisco document that seems to address this problem:

Problem

The 7960 IP phone fails to perform the boot process correctly. As the phone boots, this error message displays in the phone LCD:

Protocol Application Invalid

Solution

When you examine the sniffer trace between the DHCP server and the phone, you can identify that the phone accepts a DHCP offer from the data VLAN (the native VLAN) instead of the voice VLAN. The phone tries to communicate with the voice VLAN with the IP address that belongs to the data VLAN.

This problem can happen under these conditions:

With an IP Phone 7940/7960 with firmware version 7.2(2) and earlier

When a DHCP server sends a response packet in an untagged format

With a DHCP server switch port that is configured with voice VLAN or with a trunk that contains that voice VLAN

When option 150 is not set for the native VLAN on the DHCP server

When Cisco Discovery Protocol (CDP) on the switch and the phone do not converge in a timely fashion

----------------------------------------------------------------------------------------------------------------

The workaround for this problem is to complete these steps:

Configure option 150 in the native VLAN scope on the DHCP server.

Complete these steps:

Choose Start > Programs > Administrative Tools > DHCP.

Right-click the DHCP server and choose Set Predefined Options in the pop-up window.

Click Add.

Enter TFTP Server IP Address in the Name field.

Choose IP Address from the Data type menu.

Enter 150 in the Code field

Click OK.

Choose 150 TFTP Server IP Address from the Option name menu.

Enter the IP address of the TFTP server in the IP Address field, which is in the Value area.

Click OK.

-----------------------------------------------------------------------------------------------------------------

Remove the voice VLAN command from the phone switch port and leave the switch port as an access port on the native VLAN.

For example, if the phone is connected to a Catalyst 3550 multilayer switch, remove this line:

switchport voice vlan 205

Reboot the 7940/7960 IP phone.

The phone upgrades its load with the use of an IP address on the native VLAN.

Add the voice vlan command back to the switch port.

Reboot the 7940/7960 IP phone.

The phone now comes up with an IP address on the voice VLAN.

Here is a link to the actual doc:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008055c1fe.shtml

Hope this helps!

Rob

1 REPLY
Hall of Fame Super Red

Re: 7940 & 7960 Errors CCM

Hi Djassi,

Here is an excerpt from a Cisco document that seems to address this problem:

Problem

The 7960 IP phone fails to perform the boot process correctly. As the phone boots, this error message displays in the phone LCD:

Protocol Application Invalid

Solution

When you examine the sniffer trace between the DHCP server and the phone, you can identify that the phone accepts a DHCP offer from the data VLAN (the native VLAN) instead of the voice VLAN. The phone tries to communicate with the voice VLAN with the IP address that belongs to the data VLAN.

This problem can happen under these conditions:

With an IP Phone 7940/7960 with firmware version 7.2(2) and earlier

When a DHCP server sends a response packet in an untagged format

With a DHCP server switch port that is configured with voice VLAN or with a trunk that contains that voice VLAN

When option 150 is not set for the native VLAN on the DHCP server

When Cisco Discovery Protocol (CDP) on the switch and the phone do not converge in a timely fashion

----------------------------------------------------------------------------------------------------------------

The workaround for this problem is to complete these steps:

Configure option 150 in the native VLAN scope on the DHCP server.

Complete these steps:

Choose Start > Programs > Administrative Tools > DHCP.

Right-click the DHCP server and choose Set Predefined Options in the pop-up window.

Click Add.

Enter TFTP Server IP Address in the Name field.

Choose IP Address from the Data type menu.

Enter 150 in the Code field

Click OK.

Choose 150 TFTP Server IP Address from the Option name menu.

Enter the IP address of the TFTP server in the IP Address field, which is in the Value area.

Click OK.

-----------------------------------------------------------------------------------------------------------------

Remove the voice VLAN command from the phone switch port and leave the switch port as an access port on the native VLAN.

For example, if the phone is connected to a Catalyst 3550 multilayer switch, remove this line:

switchport voice vlan 205

Reboot the 7940/7960 IP phone.

The phone upgrades its load with the use of an IP address on the native VLAN.

Add the voice vlan command back to the switch port.

Reboot the 7940/7960 IP phone.

The phone now comes up with an IP address on the voice VLAN.

Here is a link to the actual doc:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008055c1fe.shtml

Hope this helps!

Rob

180
Views
0
Helpful
1
Replies
CreatePlease to create content