Avaya Phone Status - Idea/Suggestion

[Jonathan_Mc]

How feasible would it be to add a field in the dashboard 'IP phones with status down' to also show a timer which tracks how long they have been down for. This would be a great compliment to managing capacity for your customer - I'd imagine something like this would be quite resource intensive but would be interested to hear if this may be possible?

Thanks

[SCOTT_BALDWIN]

Hello Johnathan,

The AvayaPhone (AVPHONE) record has a field that shows when the status changed. The Avaya Phones Display included with Prognosis uses a different record called AvayaStatus (AVSTATUS), but this record doesn't contain the status change time field.

A Custom Display based on the AvayaPhone (AVPHONE) record could provide the desired information.

Thank you,

Scott Baldwin

[Jonathan_Mc]

Thanks Scott

What actually would this look like if it were added to a custom display? By status change, is this looking at registsred/un registered or another type of state?

Thanks

[SCOTT_BALDWIN]

Hello Johnathan,

The AvayaPhone (AVPHONE) record includes fields:
• CurrentStatus: shows Up or Down. I believe for IP Phones this indicates registered or not.

• TimeChanged: shows when the status changed.

A Display/Dashboard could be created to only show down extensions and their status change time.

The Professional Services Organization might already have some customizations showing this and other desired data, but I don't know.

Thank you,

Scott Baldwin

[GeraldC1 · Accepted solution]

Hi Jon,

Another thing, because the last change time stamp field in AvayaPhones record gets reset and lost when Prognosis restarts or irAvaya_PBX.exe restarts, then the Prognosis Availability can be used to track the down time better as it is not affected by restarts (time stamps get written to persistent files on disk so that they are not lost by restarts).

Here is a short video (3.5 minutes) on how to use Prognosis Availability to more accurately monitor for phones that have been down for a long time / went down before Prognosis restarts.

Steps in the Video (and additional suggestions):

On the Monitoring node in the Prognosis Client

1. create a display of
AvayaPhone:
Record: AvayaPhone (AVPHONE)
Fields: NodeName, Extension, CurrentStatus, TimeChanged
Where clause: ALL
Refresh: 1 minute
Nodes: EntireNetwork
Sort by: CurrentStatus, Node, Extension

Availability:
Record: MpAvailability (AVMON)
Fields: StateCurrent, StateChangeTimeLast, SubIDPrimary, SubIDSecondary
Where clause: THLDNAME= "AvPhoneAV"
Refresh: 1 minute
Nodes: (no change required - default node)
Sort: StateCurrent, ID

2. create an availability threshold:

Give it the name AvPhoneAV to match the where clause in the display above.

- AvayaPhone-DN condition:
WhereClause: AvayaPhone CURRSTAT<>"UP"
Name: AvayaPhone-DN
Timing: 5 minutes
Message Defaults: AvayaPhone-DN, no Off Event
Message Destinations: no Off Event
Availability message destination:

Entity Name: ^SRCNODE@ @AVPHONE.EXTNSION@
Primary Sub ID: ^SRCNODE@
Secondary Sub ID: @AVPHONE.EXTNSION@

'Configure new entity'
Nodes to Monitor: EntireNetwork

- AvayaPhone-UP condition:
WhereClause: AvayaPhone CURRSTAT="UP"
Name: AvayaPhone-UP
Timing: 5 minutes
Message Defaults: AvayaPhone-UP, no Off Event
Message Destinations: no Off Event

Availability message destination: 

Entity Name: ^SRCNODE@ @AVPHONE.EXTNSION@
Primary Sub ID: ^SRCNODE@
Secondary Sub ID: @AVPHONE.EXTNSION@

'Configure new entity'

Condition Pair: AvayaPhone-DN
Nodes to Monitor: EntireNetwork

Additional Steps:
3. Set larger memory limit:
Rule of thumb: 100MB per 10,000 rows.
for under 30,000 phones, 300MB

In PROGNOSIS config:
SET MEM-SIZE ( IRavcol.EXE, 300 )
Start

4. If need to start again (and OK to lose down times of all entities in Availability):
Stop Threshold
Stop Prognosis
Move avpers\* out
Start Prognosis
Then start the adjusted threshold should put back fresh rows reflecting the latest changes.

[Jonathan_Mc]

Hi Gerald - this is great.

I'll try this later and see how i get on.

Regards jon

[Jonathan_Mc]

Hi Gerald

Thank you again for compiling this- so far so good but I am up to building the threshold but your video seems to run in double time. Are you able to slow it down as I am missing some bits to get this working.

Thanks in advance

Regards Jon

[GeraldC1]

Hi Jon

Sure. Please see below short video of the part on creating the  availability threshold slowed back down to a more normal speed.

Please let me know if anything is unclear.

[Jonathan_Mc]

Thanks Gerald !

[Jonathan_Mc]

Hi Gerald,

Thank you again for taking the time to amend the video speed for me - thats really appreciated.

I have built the threshold now and I have 2 panes - one showing  a list of discovered phones, node, and status and time chnaged. In my other window, I dont yet see any data, and it has headers last chg/cut stat/sub id1 and 2.

I guess the reason I dont yet have data is because I need to wait for 5 minutes for the colllection to run?

What I don't also get is how I would use these views to determine how long a device has been down?

Are you able to explain further pls?

Thanks again

Jon