Threshold Condition

[Jonathan_Mc]

I'd like to build a threshold that shows when there has been a call completed who's MOS MINIMUM score is Fair and below(MOS = < 3.6)

What would be the syntax to write this and what table/field would I need to use?

[Anon]

Hi,

You can use the
- Prognosis record : AvayaCallLegFinishedQoS
- Fields : MOSFairPercent , MOSPoorPercent, MOSUnacceptablePercent

The following where clause matches calls that experienced Fair|Poor|Unacceptable MOS at least 10% of the entire call duration.
(MOSFA% + MOSPR% + MOSUA%) > 10

I suggest you to start with a display to test and fine tune the where clause in your environment.

Regards,
Alex

[Jonathan_Mc]

Thanks Alex-that's great.

[Christopher_Chi]

Hey Jonathan,

I'll second the idea of building a display first. Whenever I try to create any type of alert I always build a display first (table format usually) and then you can generally get the syntax from there. For example, we were alerting on 911 calls and some items changed and the alert stopped working. When looking deeper into it, we found that the threshold was alerting by searching for "911" and the CDR's being sent started to append and "E" onto it. We only found this by building out a display. We have since changed the alert from the original alert syntax of:

OUBDFLAG = 1 AND
(CurrentTime - CALLEND < 90000) AND
( DIALNUM = "911" OR DIALNUM = "112" OR DIALNUM = "000" OR DIALNUM = "111" OR DIALNUM = "999" )

It now reflects:

OUBDFLAG = 1 OR OUBDFLAG = 0 AND
(CurrentTime - CALLEND < 90000) AND
( DIALNUM = "911" OR DIALNUM = "911E" OR DIALNUM = "112" OR DIALNUM = "000" OR DIALNUM = "111" OR DIALNUM = "999" )

It seems simple enough in looking at it but without first building a display to see what Prognosis would return we never would have figured it out.

[Jonathan_Mc]

Thanks Christopher-really useful.

Aprreciate the response.

[Shoaib_Dilawar]

Hi Christopher,

Even though its a built-in threshold, but just an other useful way to re-write the condition would be to use 'IN' operator like:

DIALNUM IN {"911", "911E", "112", "000", "111", "999" }

[Christopher_Chi]

Thanks Shoaib! I've never been able to get the IN to work for me but I thinks it because I was using it incorrectly. I'm going to try your suggestion to see if I can get it to work. That said, if anyone has any thoughts on how to create a where clause to pick up on international calls, that's be helpful. On a most simple level I have something similar to the 911 where clause:

OUBDFLAG = 1 OR OUBDFLAG = 0 AND (CurrentTime - CALLEND < 90000) AND ( DIALNUM = "011 " )
OUBDFLAG = 1 OR OUBDFLAG = 0 AND (CurrentTime - CALLEND < 90000) AND ( DIALNUM = "011* " )
OUBDFLAG = 1 OR OUBDFLAG = 0 AND (CurrentTime - CALLEND < 90000) AND ( DIALNUM = "011*E " )

If I use a "Contains" it would pick up any call that has 011 in it which we don't want, and I've tried setting as shown above to "011*" as well as "011*E" which doesn't seem to work either. I'm fairly sure this is a simple solution but I can't get it to work currently. I'm testing by calling an Australian weather hotline: 011-613-966-94916
The CDR shows up for the Dialed Number accordingly: 01161396694916E

Any thoughts here would be much appreciated.

[Anon]

Hi Chris,

I think you can use regex if you know exactly where the 011 would be in the call string. Will this be something that may work for you?

Regards

Jitesh

[Christopher_Chi]

Thanks Jitesh! I'm not familiar with Regex so let me do some reading on this and how to use it and I'll see if I can get it to work! I'll post my findings here for sure.

[Anon]

I am testing this too. Let me run some tests...using https://regex101.com/