How to reserve a target after SelectDN target method

[Gef Buneri]

Hi all, I must reach a goal, but doing something wrong.

In a IRD appliation, after a SelectDN funtion with the sintax ----- SelectDN[VQ001,GetPriority[],'',StatSelectAny,AGENTGROUP001,'','','','','','','','',''] ----- I must play a message. The point is that to play a message, the only method I have in my configuration is to use a studio application recalling GVP and using a play and exit/play and continue application. I'm using a subroutine that sends the call back to main IRD application after the message play; the problem is that when the interaction go back to main app, URS gives an error... "target is no more valid"... so I can't mantain the SelectDN choosen target.


Any tip ? URS 7.5, IRD 7.5



Regards,

Gef.

[kubikle]

Any more info available?
When this message about not valid target appears? From RouteCall function?
What exactly problem it results (RouteCall function still make routing as far as I Know)?
May be there is URS log covering the processing of some call?

[smile]

is it virtual hold? use their standard starategy and don't care about select dn and other functions.

[deadmeat]

I could be wrong, but I think BlockDN function with a large time interval can help you.

[fnunezsa]

SIPServer? TServer? What the final purpose? Is it to play a greeting to the customer?

[Gef Buneri]

@kubikle The error appears when the interaction returns from the subroutine to the main IRD application. It results in an "endless vq wait" on a backup VQ used to manage corrupted interactions. The RouteCall function fails to get the SelectDN target even if I store it in a durable variable.

@smile I must use this method to route calls, cause is an already existing application.

@DeadMeat The BlockDN function prevent the interaction to go ahead, so I can't call the subroutine, using that function.

@fnunezsa TServer, no SIP Server. H.323 VoIP. The final purpose is to choose a target to route the call (Person), play the AgentLogin information ant then route the interaction to the already selected target.


Regards,


Gef.

[kubikle]

Might be (but not sure) the following:
If after SelectDN function you move call to some other DN (for example as result of applying TreatmentIVR) then originally selected "destination" can be erased and following RouteCall can complain about not valid target.
I think it could be "fixed" by reselecting the previously selected agent again (apply SelectDN again with the same VQ, priority, and as target use just this agent ID with .A postfix (as it is already available to you). RouteCall need to be applied to result of this last selection.

BlockDN function still might be very helpfull if used after first SelectDN to keep the slected target locked after the current call for time longer then transiton_time option. I'm not sure what exactly means "preventing the interaction to go ahead" - as far as i know this function just marks target as bound to current interaction (so URS will not allocate it to some other call).

[Gef Buneri]

Thank you a lot, kubikle. I'll try using the selected "AgentID.A" as a target after the treatment, and let you know. I'll study more about theBlockDN function.

Regards.

[fnunezsa]

So the final purpose for this is that the Customer hears the targeted AgentID? I certainly cannot see a valid use of such functionality, but anyways... have you thought of loading a strategy on agent's DN to accomplish your goal?

[Gef Buneri]

@fnunezsa Here in Italy laws about Call Center activities impose to the Agent to comunicate his AgentID to the Customers. Happens many time that the Agent doesn't does so, for this reason we want to automatize the AgentID comunication to the customer. Can you deepen the "loading a strategy on agent's DN" ?