Mar 11

IP Phone may have power, but it doesn’t mean it’s connected to the network.

Last week I had one of the phone techs come to my desk and ask me to check the configuration on a switch port. He was setting up an IP Phone for a user at a new desk and the phone powered on but would not register with Call Manager. I checked the switch port, the configuration was correct, but the port was down. To double check the port, I went to the closet with the tech to make sure we were looking at the correct port. After confirming we were looking at the correct port, we headed to the desk.

When I arrived at the desk, the IP Phone had lights illuminated with an error of “Network Not Available”. I suggested that the tech replace the CAT5 jumper at the desk to see if that would resolve the issue, it did. With a new patch cable, the IP Phone powered up and registered with Call Manager.


So why did a new CAT5 patch cable fix the problem?

CAT5 has 4 pair of wires inside of it. 10/100 Ethernet uses pins 1,2,3,6 Ethernet (Data). Power Over Ethernet (PoE) uses pins 4,5,7,8 to power the end device.

In this case, the IP Phone used 100BASE-T, so one or more of pins 1,2,3 or 6 were damaged while 4,5,7 and 8 worked fine.

The troubleshooting steps that the tech went through were correct.
– Phone powered up, but wouldn’t register.
– Switch port was enabled, but didn’t look configured
– Switch port was configured correctly.
– Had to be a cable issue, or a phone issue

By understanding how the basics of PoE worked, I was able to easily identify the best action to troubleshoot the issue. After confirming the configuration was correct, I was able to easily troubleshoot the issue.

Understanding the basic foundations of the technology that you use can really reduce the time it takes to troubleshoot. There are many resources on how PoE works, here is the resource I used to identify what pins are used in the CAT5 cable for PoE. There is a nice chart towards the bottom of the page.

Have you run into this PoE issue on a PoE device?
Do you have any good stories to share about a co-worker not understanding the basics of a technology they are using?

An account is NOT needed to reply, simply click Reply (Replies) or add you comments below and hit submit.

Jan 07

Cisco Call Manager Uptime

What is your record for Call Manager uptime? Mine is 970 days! This is actually bad. TAC recommends multiple reboots per year to keep from virtual memory utilization running too high.

From the publisher, which is a 7835H2 appliance running 7.1.3:

Uptime:
14:39:44 up 970 days, 17:55, 2 users, load average: 0.99, 0.76, 0.70

Rebooting in a few days due to this. It would be cool to hit 1000 days though. 🙂

To find uptime:


SSH into your publisher and login

Issue the “show status” command

You will get a bunch of good info, including uptime.