cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1066
Views
3
Helpful
11
Replies

How to avoid the Termination Reason AGENT_ENDS

In Webex Contact Center we occasionally have out dial calls that end abruptly with a termination reason AGENT_ENDS.  The documentation states that this is related to RONA timeout.  I have a couple of questions:  Since this is an out dial why does RONA timer get initiated?  What configuration or process changes can be made so that we can avoid these in the future?

1 Accepted Solution

Accepted Solutions

Also, are you using any type of outdial flow/scripting, or simply the agent is making the call? If you remove that scripting/flow, does it still happen?

View solution in original post

11 Replies 11

What type of endpoints are receiving the calls (i.e. physical PSTN phone vs cell phone vs UCM phone with external DID vs. etc)? And what WebexCC configuration do you have as far as the routing?

We are 100% cloud Webex Calling.  PSTN DNs are hosted by a Cisco 3rd party (cloud based).  Agents use WxCC which transfers to their Webex client app for Webex Calling.  We have custom WxCC configuration.  What specifics are you wanting to know about the routing?  Thank you for your reply.

Well, there are a couple of outdial defects that not sure are what you're seeing. You're not seeing this on inbound, only agent created outbound calls for instance?
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy89534
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa77267

Thank you for the bug reports; I will review them.  These calls are all out dial.

In reviewing these reports, I do not believe this is my issue.

Also, are you using any type of outdial flow/scripting, or simply the agent is making the call? If you remove that scripting/flow, does it still happen?

We were pointing to our standard Business Hours flow. I have removed that from the Outdial entry point configuration. I have no Flow selected.

I will monitor the 'Surge Protection Statistics' particularly abandoned outdial calls with a code of 'Agent Ends' to see if this was the fix.  Thank you Bill King for that insight.

Thanks for sharing the potential fix/next steps. Please let us know how it goes.

Bill,

While we still get a few "Agent_Ends" these have been greatly reduced and are low enough that they may be legitimate.  I am going to 'Accept as Solution' above.

Glad to hear it and thank you for sharing that was the fix/resolution.
I also saw this, may not be applicable for you now, but figured it might be worth keeping in mind.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwf96314