VMPro and Condition Editor

[IPOUK]

I've setup a very simple Condition, as per the Voice Mail Pro example exercises! So setup a condition (Monday to Friday 08.00 to 18.00) then if that result returns true (if it is a Monday at 13.00), go through to whatever Hunt Group. If out of hours, goes simply to a generic message.

The exercise goes on to include public holidays, so that condition is then run against a calendar condition, so you can double click the day in the calendar to set that as a holiday - then it goes directly to the night message. That all works fine....however...when testing, I thought I would set the main condtion (a Monday) for the office to be in service between 9 and 12. The current time was after 12. So because of "And", and "Not" conditions, the actual result is coming back as true, so really, using the calendar condition is useless, as the actual call flow will ring as usual as soon as the normal day condtion goes into night service!

Unless I'm doing something wrong, Avaya haven't fully done their testing! Has anybody else used the VM Pro example exercises?

 

[Morrack]

I played around a bit with them a while back and found they weren't as predictable as I would like. What I tend to do now is create a seperate condition with my holiday calendar, then in my main condition I add a NOT <holiday condition>

This seems to work much better.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[IPOUK]

that's exactly what the exercises say as well - I've implemented it in a few sites but haven't actually tested it before when the HG should actually be in night service. I had to read the notes again and again to make sure I wasn't doing anything wrong!

If your HG is set to 9.00 to 11.00 for example, with a "not" condition set against a seperate calendar condition (select today as a holiday), try calling the HG after 12.00 (when it should go into night service) - from my testing, the group calls as usual! Between 9 and 12, it works as it should! Pulling my hair out over this one!

 

[IPGuru]

I usualy have 2 conditions
1 for working hours i for bank holidays & then check them 1 after the other:-

Check for working hour, if yes check for bank holiday.

This saves overcomplicatimg the condition deffinition.


K.I.S.S.

 

[IPOUK]

Ok that's a different way to look at it - and it seems a good idea really.

Mon-Fri it goes to 1 HG, but on a Sat it goes to another group, so that doubles the call flow (as the Sat has to have a different condition set) - but after a load of fiddling that seems a lot better!

Thanks for your input guys

 

[sizbut]

Haven't seen any mention of "Or".

For any week planner element, make sure it is fronted by an "OR" logical condition or else it will almost always be false.

Example: You set a "week planner" element for your office hours; 8am to 5pm, Monday to Friday. By default that element is fronted by an "ANDd". This means it will only be true for a mythical time travelling moment that is simultaneously between "8am to 5pm on Monday" AND also between "8am to 5pm on Tuesday" AND also "...".

Similar applies to any "Calendar" element.

Its really silly of Avaya to default these elements to ANDing.

 

[IPOUK]

Yeh I had the week planner set to "OR" - cause it is true between 9 and 5 on Mon OR Tue OR Wed etc..

The Calendar is set and that condition is "NOT" to the Week planner

check out the example exercices and see if it works for you (only when you put a bank holiday in) - set the time on the server as as if it was out of hours and see what result you get. Within normal hours it works fine. Probably a few NOTs and ORs cancelling eachother out as soon as it is out of hours.

Doing a large call flow is easier as IP Guru said, as you can just create a number of conditions and keep checkig it against a bank holiday and linking up the true and false connections to wherever you want!

 

[sizbut]

Sorry, had to check just in case.

IP Guru's method also makes it easier to understand the callflow when you come back to it a year from now.

 

[aeverson]

I agree with IPGuru,

Whenever I set my call flows up I use two separate tokens. I check to see if its a holiday first (Or condition) and then I check to see if its during business hours second (also OR condition). This works well when you have different groups that have different hours of operation. Also its alot less confusing.