Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
We did a thorough analysis of this for a client a few months ago. With Asterisk 11/13 there were underlying changes in how the base functions of Asterisk interacted with AMD and cause it to not work properly. These issues were fixed in Asterisk 13.29.2-vici, but the fix also caused AMD to be able to classify some calls that it previously would not be able to, resulting in those calls being able to be sent to agents, and giving the appearance that AMD was not working as well as it had been. This is the reason we added the Campaign feature "AMD Agent Route Options":
"If enabled and you are using Asterisk AMD, this setting will allow you to define the AMD statuses and responses for calls going through AMD that will be sent to agents, overriding the default which sends all HUMAN and NOTSURE status calls to agents. To see the AMD statuses and responses for the calls that have been logged on your system, go to the AMD Log Report on the Admin Utilities page. The PENDING option for this setting will allow you to click on this option to go to the Modify Settings Container page to edit the settings without making them active yet. Default is DISABLED. The Settings Container for these options allow for multiple lines of settings, with each line containing one AMD status-response pair each separated by a comma. For example:
HUMAN,HUMAN
NOTSURE,TOOLONG"
This option allows AMD to work the way it did in much older versions, but it would not allow those TOOLONG calls to just sit there running up your telco bill as happened in those older versions.
Users browsing this forum: No registered users and 86 guests