T-server agent-no-answer-action

[OXE_4400]

According to T-server parameter agent-no-answer-action with value notready, agent should be moved to notready state after not answered call during agent-no-answer-timeout, but actually agent goes to After Callworks  state for some 20 sec and goes back to ready state.
How to push agent to endless notready state?

[cavagnaro]

Do it on URS instead

[fnunezsa]

Are you sure the call is not abandoned before the timeout? If this is the case, then agent-no-answer-action is ignored.

[OXE_4400]

[quote author=fnunezsa link=topic=6789.msg29544#msg29544 date=1320963765]
Are you sure the call is not abandoned before the timeout? If this is the case, then agent-no-answer-action is ignored.
[/quote]
Yes, I am sure. I am making tests in lab not on customer site with a lot of calls.

[cavagnaro]

I have it working and checked and we have to work with 3 values:

agent-no-answer-action = notready
agent-no-answer-overflow = recall
agent-no-answer-timeout = 15

These are my values.

So if the agent doesn't answer after 15 seconds (obviously OXE timer must be greater that 15 secs) then the call will return to the RP and then the agent will became NotReady. Never happened to me that they go to ACW.

**My bad about URS.

[OXE_4400]

It looks that OXE timer on RP level was the same like in URS and happened not exactly what I have expected.

Thanks for everybody