Page 1 of 1

DTMF issues

PostPosted: Thu Mar 31, 2011 9:07 am
by crisfurtado
Goautodial install from ISO
VERSION: 2.2.1-237
BUILD: 100510-2015

single server setup
Hardware IBM quad core processor, 8 GB RAM
1 Sangoma A101DE card with echo cancellation
no additional software installed


Agents need to keep the customer in conference and dial into a 3rd party IVR (payment gateway). The IVR promtps the customer to inputs information related to the purchase amount, product number and their credit card information.

We initially had only an inbound campaign and this was working fine. We later launched an outbound campaign and faced issues with the IVR only with OB conf calls. Every digit entered got doubled. Eg 1234 became 11223344.

I figured it had something to do with the sangoma card doing the DTMF and changed parameter TDMV_HW_DTMF= YES to =NO in wanpipe1.conf.
On restarting wanrouter the issues with the OB calls got resolved BUT the inbound campaign got affected with the same issue. There is another angle to this - If the agents collect the information from customers and enter it into the IVR using the input DTMF on agent screen it works fine. The digit doubling issue is only on inbound calls where the customer is inputing the digits.

I have checked and the Sangoma hw echo cancellation is enabled.

PostPosted: Thu Mar 31, 2011 12:43 pm
by williamconley
can you upgrade to the latest SVN and/or show agi debug output from this?

Resolved

PostPosted: Fri Apr 01, 2011 7:42 am
by crisfurtado
Got a few hints from debugging the PRI and made changes in the wanpipe.conf file. Set both the parameters below to yes ie enabling hw dtmf and removing DTMF on incoming media. restarted wanrouter and asterisk, made a few test inbound and outbound calls and everything's fine now.

TDMV_HW_DTMF = YES # YES: receive dtmf events from hw
HWEC_DTMF_REMOVAL = YES #YES: remove dtmf out of incoming media (must have hwdtmf enabled).

Btw..if I do upgrade to the latest SVN would I still be able to use the fancy goautodial agent interface /agc.new/vicidial.php or will i then be required to use the earlier /agc/vicidial.php? Am i correct in assuming that admin.php remains the same?

Thanks

PostPosted: Fri Apr 01, 2011 8:16 am
by williamconley
sorry, pretty agent interface is not compatible past 2.2.1

admin interface is the same

good postback!