Source: Packetspoon

ShoreTel Phone showing “No Service”? Check your SG switch capacity…

A ShoreTel phone showing “No Service” can be a cause of frustration, as sometimes the reason is not clear.

I’m currently rolling out some additional IP115 handsets, and all of a sudden I noticed “No Service” on the screen of a newly attached phone. I have seen this just a few times, and often resetting the configuration and rebooting fixed it. Not this time though.

The phone had been through the DHCP process, getting an IP address on the Voice VLAN, contacting the FTP server, downloading the image, etc. After the usual reboot, the phone displayed “No Service”

First thing I did was check the switch port config, which was OK. So I tried another port on the switch, same story.

I turned to Google, where other people had queried the same issue. Some of the advice was to check the capacity on the ShoreGear switch, to see if it can take any more phones.

Lo and behold, it was full. Remember, using an Analog port reduces the IP phone capacity by 5 for each non-IP phone port configured. If you are using BRI Trunks, SIP Trunks or a SIP Proxy, this takes up ports too.

So with the Standard config of an SG90, it can support 90 handsets. If you configure 4 analog ports, then this drops to 70, and so on and so forth.

Avoid pulling your hair out (or at least, delay the process) by checking the capacity first. To do this, log in to ShoreWear Director and go to Administration > Switches > Primary. From here you can see a high level view of all switches. The two columns of particular interest are “IP Phones in Use” and “IP Phones Capacity”…if the two are the same, then there’s your problem! I was able to carry on by changing some analog ports which were not required back to “5 IP Phones”.

As an aside…you would think that ShoreTel would give a little less vague message in this case? “No Capacity”, for instance, especially when “No Service” can mean there are other problems.

Liquid Layer Networks | Performance Cloud Hosting
http://www.LiquidLayer.net