Your setting is wrong.You have to set no_answer_timeout to any value,no_answer_action has following options:
1.None
2.Not-ready
3.Logout
and no_answer_overflow to the:
1.None
2.Recall
3.Release
So,if you set for example timeout=10,action=not-ready,overflow=recall callflow will be as follow:
1.Extension is ringing
2.Call is not picked up to the 10s(no_answer_timeout)
3.Call is returned to the last point(ie.queue)
4.Originated agent is in not-ready state
5.Call is routed again
That works fine. Your option âwalkawayâ is rubbish, where did you figure it out?
For next time you should first read the documentation properly.It is a basic and simple thing/setting.
I got it from T-server Avaya CM, Now I can able to do make agent not ready and call is not rining on extension, but if all agents are busy then it should play Music but call is idle.
and one more issue, if other agent ready it is routing but that time he also not answering the call then RONA action is not working.
RONA is working correctly - you have bad configuration,if RONA not working. No_answer_overflow option has one more value : destination number. So, you can set any DN(extension,routing point,..) and if agent not answered call in configured timeout,the call will be rerouted to the destination point.
Kubig,
You might want to tone the language down a little and read through some documentation.
walkaway is a very valid option for no-answer-action for some of the TServers and is documented. In fact I use it in production systems right now.
agent-no-answer-action
Default Value: none
Valid Values: none, notready, walkaway
Changes Take Effect: Immediately
Related Feature: âSupport for Agent No Answer Supervisionâ on page 160
Specifies the agent state to which T-Server is set after the time period for the
agent-no-answer-timeout option has expired. If the value of this configuration
option is set to none, the agent will remain in its current state.
agent-no-answer-overflow
Default Value: none
Valid Values:
Changes Take Effect: Immediately
Related Feature: âSupport for Agent No Answer Supervisionâ on page 160
Redirects the ringing call to the destination described by this option after the
time period for the agent-no-answer-timeout option has expired, T-Server.
Notes: ⢠The walkaway value is identical to the NotReady value unless a
non-ACD (soft agents) setup is utilized.
⢠The walkaway value is a special NotReady work mode that is
applicable for soft agents only. Otherwise the NotReady work mode
will be AuxWork.
I think no, you can return the call back to the last distribution point (is in attribute ThisQueue), release or overflow to another destination - in case when you look at the documentation ( I know that you think âwhy read the doc?â) - you will find out how to achieve your need and how to configure it. Little hint - you can configure it in strategy via AttributeExtension in TRouteCall function
One more question on this subject. Is it possible to count calls on VQ come from RONA ?
RONA is countable on agent (By callforward stats), but I couldnât find one for VQ ?
Call distributed to 4 targets ACTO user choice. Each has its own VQ. If overflows with RONA, call goes to the top of the strategy and user makes new choice
If new choice is different than previous one, the stats on the previous VQ becomes anormal. (ie 150 entered, 140 answered, 7 abandoned, 0 cleared, - What about the 3 calls ??? â RONA is in action )