cancel
Showing results for 
Search instead for 
Did you mean: 

Remove Trunk/s in Trunk Group Down alert

tppr1
05 Base Camper

Remove Trunk/s in Trunk Group Down alert

We have an active alert and want to remove a trunk from being alerted.

Can this be done in Threshold Conditions, WHERE Clause is AVAICURR = "DO"?

1 ACCEPTED SOLUTION

Accepted Solutions
SCOTT_BALDWIN
Expert

Re: Remove Trunk/s in Trunk Group Down alert

Hello @tppr1,

 

You are correct, there are 2 ways to filter out the unwanted trunk-groups:

  1. The current method using a "white list" in the Where Clause so all the trunks expected to alert is part of the list.
    The updated syntax below is very similar to the current Where Clause posted, the term "IN" was added:
    AVAICURR = "DO" AND TGRPNUMB IN {X,Y,Z}
  2. Alternately, a "black list" of the unwanted trunks can be used in the Where Clause.
    Where Clause syntax of this method can be:
    AVAICURR = "DO" AND TGRPNUMB <> X AND TGRPNUMB <> Y   
    -- Then continue to add "AND TGRPNUMB <> " and the trunk number as needed.
    Or this syntax can be used:
    AVAICURR = "DO" AND NOT IN TGRPNUMB {X,Y,Z}

NOTE: The Avaya_Alert Threshold included with Prognosis has multiple alert Conditions assoiciated with trunks. This means multiple Conditions' Where Clauses may need to be updated to prevent the unwatned alerts.

 

Here is a list of the included Conditions in the Avaya_Alert Threshold I suspect might need to be changed:

  • Trunk Group Degraded
  • Trunk Group Down
  • Trunk Group Down
  • Trunk Group Up (DO)

 

Thank you,
Scott Baldwin

 

View solution in original post

5 REPLIES 5
SCOTT_BALDWIN
Expert

Re: Remove Trunk/s in Trunk Group Down alert

Hello @tppr1,

 

The Threshold Condition with WHERE Clause AVAICURR = "DO" is the correct place to adjust the alert.

A field showing the trunk (or other identifier) value will need to be added to the Where Clause so the specific trunk is NOT alerted on.

 

The Where Clause would look something like this:
AVAICURR = "DO" AND TGRPNUMB <> 123

 

Thank you,
Scott Baldwin

 

tppr1
05 Base Camper

Re: Remove Trunk/s in Trunk Group Down alert

Thank you, Scott.

Currently what we have, AVAICURR = "DO" AND TGRPNUMB {X,Y,Z} 

where we included the active trunks.

 

Below suggestion is another option, AVAICURR = "DO" AND TGRPNUMB <> X 

and adding another trunk will be an additional AND TGRPNUMB <> Y?

SCOTT_BALDWIN
Expert

Re: Remove Trunk/s in Trunk Group Down alert

Hello @tppr1,

 

You are correct, there are 2 ways to filter out the unwanted trunk-groups:

  1. The current method using a "white list" in the Where Clause so all the trunks expected to alert is part of the list.
    The updated syntax below is very similar to the current Where Clause posted, the term "IN" was added:
    AVAICURR = "DO" AND TGRPNUMB IN {X,Y,Z}
  2. Alternately, a "black list" of the unwanted trunks can be used in the Where Clause.
    Where Clause syntax of this method can be:
    AVAICURR = "DO" AND TGRPNUMB <> X AND TGRPNUMB <> Y   
    -- Then continue to add "AND TGRPNUMB <> " and the trunk number as needed.
    Or this syntax can be used:
    AVAICURR = "DO" AND NOT IN TGRPNUMB {X,Y,Z}

NOTE: The Avaya_Alert Threshold included with Prognosis has multiple alert Conditions assoiciated with trunks. This means multiple Conditions' Where Clauses may need to be updated to prevent the unwatned alerts.

 

Here is a list of the included Conditions in the Avaya_Alert Threshold I suspect might need to be changed:

  • Trunk Group Degraded
  • Trunk Group Down
  • Trunk Group Down
  • Trunk Group Up (DO)

 

Thank you,
Scott Baldwin

 

tppr1
05 Base Camper

Re: Remove Trunk/s in Trunk Group Down alert

Hi Scott,

Top Man. Appreciate the detailed solution.

Forgot to add filters in other conditions, ill ty to do that now.

Cheers!

SCOTT_BALDWIN
Expert

Re: Remove Trunk/s in Trunk Group Down alert

Hello @tppr1,

 

You are very welcome. Please let us know if additional issues are seen.

 

Thank you,
Scott Baldwin

 

Webinar: Keep the modern workforce connected

Unified Communications has always been an important part of companies' digital transformation efforts due to its ability to enable rich virtual collaboration and communication. But with COVID-19, we've reached a break-through point.

Join Bill Haskins, Sr. Analyst & Partner, Unified Communications at Wainhouse Research, and John Ruthven, CEO at IR discuss UC challenges companies are experiencing due to the COVOID-19 crisis.

Join webinar
Top Liked Members