See all registered ip Stations with Java avaya.jtapi ?

[avc852340203484]

Hello everyone,

it is very easy to see and list all registered ip Stations when I use the "Integrated Management - Site Administration" tool.


Is there something similar for the avaya.jtapi ?

Getting a list of all registered (logged in) ip Stations? 👀

[jtb1]

From my understanding Avaya Site Administrator will only show you H.323 device registrations since it is leveraging the SAT's 'list registered ip-stations' command.

Tf you have a TSAPI/JTAPI/DMCC Call control monitor on a station you can get registered and unregistered events for it. Unfortunately there is not a bulk query through AE Services that is available.
While you can use AES system management services to do a "list registered ip-stations" query, the results are limited to H.323 but if you are happy with ASA this may be sufficient.
You need to use System Manager's Web Services to get registered SIP stations.

[avc852340203484]

From my understanding Avaya Site Administrator will only show you H.323 device registrations since it is leveraging the SAT's 'list registered ip-stations' command.

Tf you have a TSAPI/JTAPI/DMCC Call control monitor on a station you can get registered and unregistered events for it. Unfortunately there is not a bulk query through AE Services that is available.
While you can use AES system management services to do a "list registered ip-stations" query, the results are limited to H.323 but if you are happy with ASA this may be sufficient.
You need to use System Manager's Web Services to get registered SIP stations.

so do I understand this correctly?


If want to know in Java (avaya.jtapi) if a Station is registered/logged in, I need to monitor all stations that are there.

Lets assume the client has 1000 phones, so in Java I need to monitor all 1000 phones all the time and then manually keep track of each register and unregister event and logging them in a table?

Where can I configure/find this "Call control monitor on a station". I feel a bit lost here.

[jtb1]

"I feel a bit lost here." You are... and I am not surprised - This appears to all be new to you. JTAPI does not register stations. It can be used to monitor stations for call releated events and do third party call control on calls. Conceptually an application can control one station at a time (but it may control many stations, through many messages).

Through JTAPI you can create a monitor on a station extension - that provides the application with events occurring at the station.

JTAPI can put monitors on both SIP and H.323 stations and get station registered and unregistered events.(So can DMCC and TSAPI). Unless you are already a JTAPI programmer (and it appears you are not), I would recommend using DMCC (at least the Java implementation of it).

If you want to use JTAPI to get registered status, yes you would need to establish 1000 monitors and hold the information in your own table; or you could use the other APIs I mentioned System Manager's Web Services (I believe event monitor has that capability), and AES's System Management Service where you can do block queries (up to 100 stations at a time as an example) - but you would need to poll periodically to keep this information up to date. As a super advanced topic, for H.323 device registrations you can enable certain SAT command tracing and it will show you H.323 device registrations and unregistrations and monitor list history for changes (but you need to also watch for system restarts where the log can be overwhelmed).

[avc852340203484]

OK I see.



How about this alternative approach.


In Avaya System Manager I would schedule a Report Generation of list registered-ip-stations for every minute or every 5 minutes.

Then a separate tiny cronjob and a tool would update every minute this exported .csv generated ip-stations and write it into a table.


I think this should be working. My only question is can the Avaya System Manager handle this report generation reliably. I think every 5-10 minutes should not be a big deal, right?
When I ran the script, it took less than 1-2 seconds to finish. I think this could work.

[jtb1]

It may be well behaved for a small set of stations, but I would not recommend it for thousands.Reports in general are not efficient operations since they comb the database for information.

If you want to make use of SMGR directly to get at this information I believe it can be provided through the System Manager Element Management Web Service see: https://www.avaya.com/en/partners/devconnect/sdks/#6