reboot ALL phones

[avayaguy23]

Looking for potential solutions to reboot all types of avaya phones (9611g, 9608g, 9620, 9630) even if they are not logged in.

Option 1:
Obviously you can reset the network region but it only reboots the logged in phones. Theoretically it could be years before all the phones get truly rebooted.

Option 2:
Work with the network team to do a shut/no shut on the ports. This is a bit of a pain, but it at least reboots ALL phones.

Option 3:Avaya diagnostic server but we haven't deployed this tool to the entire organization. (Again for this feature to work the phones have to be rebooted). This tool also only lets me reboot one phone at a time.


Is there a subnet scanner where I can scan the phones and select reboot? You would think after nearly 20 years in the IP industry Avaya would have an easy tool.

 

[kyle555]

Have you tried by IP address and explicitly tried one that isn`t logged in?

Maybe there's something about H323 TTI stuff where they can be on-switch - like TDM phones on unprogrammed ports and that'd let you get up to rebooting them from CM with reset ip-phones.

 

[avayaguy23]

Unfortunately Avaya only allows the phone to be rebooted if the extension is logged in. CM was built on TDM technology and not IP. It doens't know anything about the device until it is logged in.

 

[joe2938]

reset system 4 will do a complete reboot of cm

 

[avayaguy23]

okay? but rebooting CM won't reboot the already unregistered phones. I have 5 different CM pbxs in my dhcp scope options. The reset system 4 would never work.

 

[joe2938]

Then you would have to power cycle the data switches as mentioned

 

[avayaguy23]

Another poor design on Avaya's part *shocked face*

 

[joe2938]

Not really, do not know of any phone system that can reboot all logged out ip phones, but it is what it is.

 

[avayaguy23]

A polycom for instance has a web interface that I can log into and reboot a phone that way. Avaya just started providing a web interface on the SIP J series phones. Most IP devices on the network at the very least has a management interface. Then again Avaya always tries to go against the grain. Look how horrible of a product system platform was until they finally realized they should use vmware. Sometimes I think Avaya Engineers should take a basic networking class.

 

[ZeroZeroOne]

Reset ip-stations can be used to reset all ip-phones, registered or unauthenticated. I've used this with h.323 sets but I don't think it will work with SIP.

 

[avayaguy23]

What model and firmware for the unauthenticated? I tried with 3.2 9630 h323

 

[Wanebo]

Our network guys wrote an expect script that found all the Avaya mac addresses via the switch arp tables and then shut no shut all the ports they were connected to. It was pretty effective and we could apply it by switch name or enterprise wide. I don't think we ever applied it enterprise wide (yeah, we were chickens) but we did break the whole network down to chunks and reboot all the phones connected in the space of one night a few times.

 

[kyle555]

Got me playing in my lab...

Bottom line, who cares? If you can reboot the registered ones, they'll pickup what you want them to pickup. The rest should pick them up whenever they reboot, but they're not in service now anyway.

You can use unnamed registration to get the phones on CM with a basic line - like TTI for TDM. Then you can reset ip-stations of type tti.

Condition for that to come up as a TTI station without touching the phone is that the phone comes up after the feature is enabled on CM and that the phone doesn't have an extension programmed already.

The only way reset ip-station unauthenticated worked for me was if I gracefully logged out a station from the phone itself, not by changing the security code in CM. Once that occurred, upon reboot it did do an unnamed registration I could later bounce with reset ip-stations tti.

I've got a bunch of notes and was trying to do each procedure a few times and either I wasn't paying attention, or did something different, or the behaviour is inconsistent, but I was trying to find ways to "reboot any phone regardless of bad/old login info"

I did it on CM8 with a 96x1 6.6.1

If you have the subnets in the network map, maybe with ELE just to be sure, and you have TTI enabled, and you have PSA enabled in a COS, and those features have FACs defined (just to be safe) and you never changed the default value of UNNAMEDSTAT (enabled if unspecified in 46xx), then the phone will try to perform an unnamed registration after a minute.

I can try the same stuff with 96x0s later when I have some down time.

 

[dialtonebone]

Kyle555 summarized it... you need TTI/Unnamed Reg for IP telephones working to get those un-registered telephones (since they are technically registered, just featureless).

 

[kyle555]

I was still hoping phones with invalid credentials (and not just phones with no credentials) would still drop to unnamed registration - like phones removed from CM but still remembering their old extension.

From my packet captures, it appears that once a phone boots and says HI for the first time, if it doesn't get in with the extension it remembered, it doesn't send out any more packets.

Reset 4 or disabling/enabling procr doesn't seem to have CM establish a TCP socket outward to IPs in the network region if CM didn't have a valid registration from that IP previously.

And it seems nothing makes a phone forget it's old extension unless you log it out gracefully/from the desk set.

So, 100s of phones on desks that got removed from CM over the years and CM went through a few reboots too means that short of touching the phone, CM has decided it doesn't want to talk to them anymore.

I'm still on the "who cares" bandwagon. If you can reboot H323 sets that ARE on your PBX, you can change them as needed. If it's stuff like a firmware upgrade, then LLDP can provide device type (phone) and vendor (avaya) and model (9608) and firmware (6.6.x) and you can still hunt them down if you really wanted to. Or, have people reboot them before using them again. Or, if they won't do that and just login to the thing, you can still list reg and find who's got old firmware or whatever and if you reboot quarterly or whatever, they'll eventually clear up in batches as you go along.

 

[avayaguy23]

I would assume the unnamed registration feature is disabled for most people's environments. Also, I don't want to get the networking team involved. I don't have access to the switches which is part of the problem. In addition, we are upgrading to Aura 8 so it involves pushing new configuration/firmware to the phones so you have to pretty much touch every phone. I'm not sure why Avaya doesn't just make the phones try to periodically reach out and check for settings, firmware, certificates, etc and reboot if necessary.