Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: andbra on July 13, 2009, 01:52:41 PM

Title: StatServer returns negative value for StatTimeInReadyState
Post by: andbra on July 13, 2009, 01:52:41 PM
Hello!

I have a problem with inbound call distribution.

We use the StatTimeinReady state by MAX for selecting targets. Suddenly one agent(recently started), can't get calls when there is no queue, so I checked the URS logs, and found out the statvalue returned was negative, followed by a [color=red](U)[/color](What does it mean?). Normally, and for all other agents, it is a positive number, followed by [color=red](S)[/color]. That means she won't get any calls unless there is a queue. When there is calls waiting in queue, a negative value is better than Not Ready State, and the calls get routed to this agent.  :)

Here is the modified log line:

[i]_M_I_019001b33042be0d [17:0b] VQ 00ee7360 Target "?:[color=red]SkillExpression here[/color]"(04dedf10) Component #77 [color=red]AgentID here[/color]: statvalue: 0, -10000001816.5(U) pass[/i]

Does anyone know what is causing this problem?

Regards,

Anders
Title: Re: StatServer returns negative value for StatTimeInReadyState
Post by: kubikle on July 13, 2009, 06:46:47 PM
As far as I remeber it's like that.

Letter in () is source of used statistic value - it can be (S)tatserver, (M)odeling, (U)nknown,
(N)one, may be something else.
(U)nkown used when strategy require to use statistic but for some resons URS fail to get it.
In my case it was when statserver send StatInvalid message to URS becaise of link disconnection message from tserver. Probably there are other scenarios.

For all agents URS fails to get statistic it uses big negative number - any agent with valid statistic will be preferable for URS. 

 
Title: Re: StatServer returns negative value for StatTimeInReadyState
Post by: andbra on July 14, 2009, 06:53:45 AM
Kubikle,

Thank you for your input. :)

As far as I can understand, this is a StatServer issue. I will try to restart it, and hopefully the agents statistic value will become normal.

Edit: Restarting the StatServer solved the problem. :)