Percentage Rule Routing (IRD)

[PFCCWA]

Hello,

I am trying to use the Percentage Routing Rule in IRD Strategy and wonder if I can do the following:

[list]
[li]Route x% the call to an external target using a switch destination ie 500976482 (500 being an aar code in Avaya and 976482 being a vector vdn which dials an external ngn)[/li]
[li]for the other x% let the call carry on within the same strategy[/li]
[/list]

As I have to select a object type, I thought for the first route I need to use destination label but if I enter the 500976482 URS logs advise it cannot find the object in the configuration.

    [i]_M_I_ [17:06] VQ 104807f80 TRG 10214fdf0 added: name=500976482, location=StatServer, type=DL, state=##true, activity=unknown
    _C_W_ [10:05] SO(0 0 0) ten=Resources name=500976482@StatServer.DL: there is no config object
    _M_E_ [10:06] SO(0 0 0) ten=Resources name=500976482@StatServer.DL: stat <##true> failed
    _M_E_ [17:02] can not find SO 500976482[##true] for stat server StatServer..[/i]

For the other x% I just used a 'space' so the call will go down the red port and carry on the strategy.
I have seen archived attempts to use routing points, which may work for the first % ie create independent strategy and use TRoute function to route to 500976482 but how would I set up second route where I want the call to carry on within existing strategy.

Is there a way to do what I need to achieve using this functionality in IRD?
If not I can try another method ie use a database stored procedure to extract the values from an external source or use 'RAND' after taking the values from a transaction list option value.

We use Genesys v81, T-Servers (premise and site) with Avaya CM (no SIP).

thanks,

[cavagnaro]

Can you post your strategy conf?

[terry]

Using Destination Label (DL) type of targets assume such must exist in configuration and URS will check it.
Plain Destonation Numbers (DN) probably more convenient (no need to define them in configuration).

In any case percentage routing rule not look ideal for choosing between routing to some DN and just continuing strategy  - it probably will require extra "fake" RP etc.

Probably easier to implement such logic directly in strategy.
For example imitating how URS does it:
Create 2 FLOAT SCRIPT variable v1 and v2.
If you like 30% of calls to be routed to some dn and 70% to be processed by strategy then at the beginning check what is less v1 or v2. If v1 then increcent v1 by 1.0/30.0 and route call to DN, if v2 then increment v2 by 1.0/70.0 and proceed with strategy.