Phone Out of Service after upgrade

[westsounder]

Hi all, great site!

I have updated my system from 6.1 11.14.2402 to 6.1 11.15.4400 and now I have no phones! ACK! I *think* I rebooted everything in order HQ Server>DVM>Switches then Phones.

I am seeing all phones reporting Out of Service, Operational. Calls in from the outside get voicemail or the Auto Attendant. I can dial from Personal Call manager (no sound though).
I have tried adding FTP Tagging and VLAN id to the phones. No luck. I have also tried changing the switch that the phones get the update from.
We use INFOBLOX for DHCP on the network side and I have option 156 enabled on HQ box with the full statement FTP Tagging1,VLAN=105 ect.

I cant access my Infobloxs right now, so is there anything besides the network side DHCP that I can check to get this up and running before Monday morning???
Thanks in Advance
Dino

[Forum]

What is displaying on the phones itself???

[westsounder]

phone display

The phones are circling the DHCP loop. They get an LAN address and then a Local address, then count up to 300 and start again.

[luckycharms]

What is managing the VLAN? Can you statically address a phone to see what happens without a VLAN tag?

Are the phones ever getting their second address for the VLAN?

[nbendel]

Is DHCP running on the same server as Shoretel? Verify that the DHCP service is running. Try putting a pc on that vlan to see if it gets an IP.

[westsounder]

Resloved

Is DHCP running on the same server as Shoretel? Verify that the DHCP service is running. Try putting a pc on that vlan to see if it gets an IP.

So it was a rookie type mistake. When I rebooted the HQ server, I did not check the services. The previous admin had set the HQ DHCP server to Manual instead of DISABLED. So after the reboot, the dchp server come back to life. Two DHCP servers handing out addresses for a single Vlan is trouble.

We did not have the ftpservers= %FTPSERVERIP%, 2layertagging=1, vlanid=105 defined for Option 156 on the real server either.

We still needed to do a physical reboot of each phone.

So lessons learned here, check your documentation, note the services running and have somebody at a remote site or be able to remotely down a POE port before doing an upgrade!

[dhelfond]

We still needed to do a physical reboot of each phone.

So lessons learned here, check your documentation, note the services running and have somebody at a remote site or be able to remotely down a POE port before doing an upgrade!

A managed switch or managed PDU is a great solution for this, giving you the ability to power-cycle items remotely.

[westsounder]

A managed switch or managed PDU is a great solution for this, giving you the ability to power-cycle items remotely.

Right
We have mostly Cisco POE switches, but some of the remote locations have PIG phones...
What we need is a telent command that does a hard reset of a phone via MAC address.

[cburgy]

Right
We have mostly Cisco POE switches, but some of the remote locations have PIG phones...
What we need is a telent command that does a hard reset of a phone via MAC address.

You can actually telnet to the phones (assuming they have an IP) and issue a reboot command. Use phontctl.exe -telneton IP_ADDRESS on the server under the Shoreware Server directory.

[ctmega]

Resetting phones the easy way with cisco PoE switches...

If you are using Cisco switches with PoE you can issue the following command from the config menu:

(Example - 24 port 10/100 PoE switch mass reset of phones)

*******************
config t
int range fa0/1-24
power inline never
power inline auto
*******************
That's it. They will all reset.