Understanding Statvalues / Bug in StatServer?

[astrakid]

Hi,
1. when urs targets a vq, we get the following information for the best target:

_M_I_<connid> [17:0b] VQ <id_of_vq> Target "?:<Skill>"(<skillID>) Component #6 <AGENT>: statvalues: 0, 0 1220276586 22811(S) the best

Can someone explain these statvalues?
I think, that 1220276586 is the timestamp.

2. We had the problem, that after restart of statserver used for routing an agent, which was absolutely sure not logged in, was in status available. Has someone encountered the same or similar problem? we are using statserver 7.6.000.18.

[Fra]

Hi,

1. the 22811(S) is the value of the stat being used, checked some lines above where it says "SELECT XXX by statistic Statsomething"

2. with "avalaible" do you mean "ready"? StatServer gets the agent state from TServer on startup, so you should check its log when it registered the DN the agent was registered against.

[astrakid]

Yes, I meant ready. I will check t-server-logs tomorrow.

thanks for the hint.

regards,
andre

[aakarach]

yes I have seen this before, there is an issue with leaving the max value in the Target block routing blank (to be default) in URS 7.6, ie it has to be either set to statagentready if you want your longest available agent to take the call, but if you choose statagentloading that is considered a better option and will give you the same result as the latter ( to tell you the truth I did not find statagentloading to be that useful). the "best" is generated by a statserver random number ie it is trying to make sure that all agents take approximately the same amount of calls not necessarily the longest available agent . I hope this helps,

PS , i have only seen this in URS 7.6 

[astrakid]

we are using statserver 7.6, but urs 7.5 (because of another bug in urs 7.6 -> transition_time is ignored).
Later on I will check startup-logfiles of tserver.

regards,
andre