Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Report of Registered stations not matching Administered stations

Status
Not open for further replies.

KEDinFL

Technical User
Sep 21, 2022
1
US
Older H.323 Stations are being converted to SIP stations. There is also a movement to replace all the older stations. Meanwhile, we have stations that are registering extensions that don't match the station type. IE: Administered as J139, but they are registering a new J179 phone agains the extension. or Administered as 9611, but placing a J159 on the desk and registering it. As you are aware, this is causing chaos with button layouts. I can see the Administered station and the registered station types via status station, but with 15,000 stations, it is not practical. Is there a way to get a report that will show administered set type and registered set type for each station? MAC addresses are available, but doesn't seem to be an easy way to correlate MAC adddresses with Specific station models. (yes I have run this against Avaya device PM). If I recall, the ASA application could possibly extract this, but not sure anymore.
 
list registered should show you administered vs connected type for H323.

For SIP, you see firmware version in SMGR, but all 96x1 (except 9601) report that they're running 96x1-version-XYZ.bin, so you can't find the real model there.
SNMP is the way to go for that.
SIP J phones do report the right model in SMGR.

I wrote a script to flip H323 phones to SIP where you start with list regsitered - so, extension and IP, and then I SNMP get the MAC from each, and then write mac.txt that says "ext=1234, password=1234".

It'd be too easy if Avaya gave you one place to see all registered phones, administered models and connected models whether they were H323 or SIP.

Inemsoft has a great product that's a file server on steroids that manages a lot of this stuff and does Avaya endpoint management. You're the perfect customer for them and they're they only thing I've ever seen that addresses that problem.

If you've got a big migration underway, I can't recommend their product highly enough.
 
As you move to SIP, remember that up to 10 devices - of any type - can register to the same extension. So having an extension configured as a specific device is almost irrelevant.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top