Hi,
When using the RouteCall function in IRD, you need to specify a Varible instead of routing the call directly to DN@Switch.
An example of this would be to first create a SelectDN function and assign it to a Varible...For instance, v_routecall. The selectDN function you would use is v_routecall=SelectDN['','','',StatSelectMax,'
IA@Stat_Server.A'], where IA=the AgentID. Then in your next block you would use the RouteCall function and the expression would be RouteCall[v_routecall].
RouteCall
Parameter: Destination: STRING (target) or variable (representing a string
for the destination)
Return value type: STRING (target)
This function attempts to definitively route the current interaction to a target
specified in low-level format. Its operation is very similar to that of the
function DeliverCall with Type parameter equal to 1 (DeliverToAgent) or 2
(DeliverToIVR). The returned value also obeys the rules listed there.
This function differs from DeliverCall in the following ways:
1. The function RouteCall waits for EventRouteUsed from T-Server in order to
conclude that the interaction has been sent to the destination successfully.
Thus, it is not concerned with the actual arrival of the interaction at the
destination DN.
2. After the current interaction has been routed successfully, URS no longer
controls it. After the definitive routing of the interaction, URS proceeds to
execute the postrouting actions, specified in the sequence of objects.
Note: Usually the input for this function is the output from the SelectDN,
SuspendForDN, or Translate function. You also can manually construct
the target string, but in this case URS performs routing in force mode.
That is, no statistics calculated by URS are updated.Best Regards,
Steve.