Routing Query/Possibility

[PFCCWA]

hello,

we are using Avaya for music on hold treatment (busy tab routing block, ivr treatment).
I have some routing blocks to extract value from transaction list, in addition to using statistics to perform a formula calculation.  All these are assigned to variables and using segments determine how call is routed.
Currently this check is performed once before call is queued at routing selection block.

I am wondering if I can perform the same checks within the additional threshold section of the general tab (in routing selection block)?
Ideally I want the checks to be performed on a regular interval without affecting callers.
At the moment they queue until answered or timeout is exceeded before routing to next block.

There are other possibilities such as exiting the routing block at a configured timeout, then performing the check again, repeating the initial cycle but want to avoid using multiple selection target entries or risk call looping etc.

thanks.

[Adam G]

Perhaps use a Peg/Count, incrementally?

[PFCCWA]

use peg/counters within the routing selection block?

[Adam G]

I think I understand your issue as needing a way to pass through a routing block a number of times, without looping and extract a Vlaue of some kind?

I'm suggesting using a Variable as a means to pass through a routing block and take a different path, based on the number of times passed through.  Check Expression Builder>Reporting>Peg Value - or add your own "PegValue" as a Variable.

Sorry if this isn't all that clear but I am still trying to work out what it is you need to do - hence my generic suggestion(s).

HTH?

[terry]

Additional threshold section of the general tab probably is not appropriate for such purposes - it is executed only at moments when some agent is checked is it Ok for some call (waiting in this target object) be route to him or not.
If during wauiting time no agents becomes available then URS will have no reason to execute threshold expression.

Basically there are few ways to periodicaly execute some extra logic "inside" strategy without necessity to code any loops in main strategy logic (some limitations applied like you can not route call from inside this extra logic).

What exactly targetting parameters your checks going to control/change while call is waiting in target selection block?