URS targeting is too long

[Vic]

Hi, we have thousands of agents on site with the same skill, so when we have a call arrive to URS, URS goes through the motion of listing every possioble target, which combined with a high volume of calls, not only puts a lot of load on the machine, but also fills logs in a matter of minutes.

Not only it lists the potential target,s but it also lists the same targets when call is routed to the agent.

Something like this:
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17022481 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17022399 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17021590 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17020970 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17023042 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17020926 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17020764 now
_M_I_00ba013bcd412865 [smUnMapTarget] call does not wait target 17020011 now

We are talking about thousands of them listed. This is a real night mare for me (URS 6.5.108).

One of the reasons why it is happenning is because I am using:

SkillInGroup function. <-I think this is why it is listing all the agents...
Is there a way to avoid having URS listing targets each time?

[ecki]

Hi Vic,

Did you try to slash down the trace level?
There is one option in default section "verbose". Have look on it.
And also is good to use buffering, but I recon you know this very well.

[Vic]

Hi, Ecki,

changing the log level is one of the ways probably, but then, we would also be losing all the other log data as well. I wish there was a way to turn targetting part of the data off: it is a drag when you have thousands of agents spewed at you!!!

Best regards,
Vic

[ecki]

Hi Vic

Actually this is not completely true. There is levelling from 5 –high(true) to 0false(none). If you combine this with verbose=all in Log section, you should still get some information about routing by value 0. Lets try each level and check it whether the log output is sufficient for you. This should be the only way as I assume you need to target so many agents. Otherwise you would split agents with same skill to several groups and for routing you would use call balancing between them. BTW you can also restrict the target group with option "clear target" in cases where is used gradationally routing like first step route to group A, second to B and so on. So if you do not need to accumulate the target objects, just use this option.

bye.