Has anyone on here worked out how to use prognosis to manage/monitor B179 SIP phones on Prognosis?
They show up under the PHONES sub menu(type 9630) but how is this information being returned to the application? B179 SIP phones register to SM and NOT CM and it appears that the product is taking their status from CM(which is incorrect).
For example, we have a SIP B179 extension that has been created in SMGR(and built with a CM profile for features) and is not yet on the network, however, on Prognosis, under SIP phones it shows the status as UP which is misleading.
How can I use the product to monitor SIP conference phones of this type?
Starting with Session Manager 7.1.1, there is now an API available for this. From the Avaya DevConnect page for Session Manager:
Session Manager Element Manager Web Services API, new in release 7.1.1, is one of the Web Services comprising of the System Manager Web Service. The EM Web Service provides programmatic access to Session Manager Dashboard and User Registration status data.
I won't patronise you by asking if you have checked the Install/Admin Guide for this phone, but what I will say is that as I am not experienced with this type iof issue, my first port of call was to do that myself, as well as some general research. What strikes me as rather odd, as so far, although I can find documents confirming this model is supported by Avaya Aura, CS, CM etc. I have not been able to find the minimum versions for compatiility, phone firmware required etc. Is that not rather odd....? (for any PBX vendor, not jsut Avaya...)
It is difficult to comment on Prognosis showing the phone as 'up', when we rely (mainly) on information we get from CM etc. So I think the basic regisration/config problem is one for Avaya Support, before IR can comment on this. Also, I would point out the Prognosis does not (currently!) "manage" phones....
I'm apologise that this is not much help to you, but I suspect my colleagues with more experience with Avaya would likely make the same suggestion.
Actually Avaya SIP phones always register directly with Session Manager and it has all of the data on firmware versions, models, mac address, ip address etc. The original question is very valid. The CM only has H323 mode registration data not SIP phones. Prognosis needs to pull phone data from Session Manager as the original writer suggests. By the way a B179 is an Avaya phone built for Avaya systems. The guy who responded (Martin Smith) needs to restrain his responses when he obviously has no knowledge of the Avaya architecture at all. I agree with the original question and have the same issue with Prognosis not having much data about Avaya SIP phones in general (not just the B179).
Hi, You're right and I can confirm that Prognosis provides the status of SIP phones based on their "configured" state but not on a “registered” state because it is based on the Avaya SAT command output which always shows SIP phones with a value of 'in-service'. This is the product behaviour as described in Online Help here. Prognosis for Unified Communications > Avaya Aura Communication Manager > Monitoring Data > PBX Network Device > Phones
Therefore, when the Prognosis user sees the SIP phones under the Avaya Phones display as Up, this should not to be taken as being registered to the SM. HTH
This conversation is coming up more often these days. However, I haven't seen a nice way to collect phone registration and/or other status from SM directly i-e any API. Only way so far was to use SM's web portal screen scraping, but obviously that would be a bad choice and harder to maintain.
If my reply answered your question please click on the 'Accept as Solution' button to help others find the answer. Thanks, Shoaib
Why couldn't we use the detail in the OperationalEvent log? (/var/log/Avaya/sm)This log on the SM shows when a UA has unregistered and could be of use to get Prognosis to periodically check for any un-registrations-see example/excerpt from log file below.
Jul 27 16:20:14 : +01:00 2017 021 1 com.avaya.asm | 1 com.avaya.asm.core OP_CURE57003 User Aug 9 12:54:21 : +01:00 2017 153 1 com.avaya.asm | 1 com.avaya.asm.core OP_CURE57002 User sip:firstname.lastname@example.org:5060;transport=TCP;ob has un-registered.
I believe a similar integration of log file analysis is used for the CMS extended solution.