IVR not reading dtmf correctly on a few calls
we have 2 numbers for calling in 2557, and 2559. I setup 2559 to be a blind IVR with an announcement saying, please enter the ext you wish to speak with.
People are saying they get a extension not found or they get transferred to the wrong ext. Works correctly for 95% of the calls, unfortunately customers are sometimes part of the 5% that wont route correctly. It doesn't happen enough to troubleshoot it, we are doing between 6000-7000 calls per day, so its pretty hard to filter.
is there some sort of inbound, inband, relaxed dtfm setting I can use in the zapata-auto file?
sangoma card is a A102 w/ HW echo
thanks!
Robert
Hi Robert,
First thing you can do is simply add "relaxdtmf=yes" to "/etc/asterisk/zapata.conf" and see if this resolves the issue. After you add this you must stop and start asterisk for this to take effect. If this does not work then you try adjusting your "rxgain" in your "/etc/asterisk/zapata.conf" and see if this works, you will also have to stop and start asterisk for this to take effect as well. If this does not work then please send the following information to techdesk@sangoma.com. Also please insure you include a brief description of the issue or just simply reference your post.
-the output from "wanrouter version"
-the output from "wanrouter restart" (asterisk needs to be turned off for this so it may need to be done after hours)
-the file /var/log/messages (the entire file containing a wanrouter restart)
-the output from "wanrouter hwprobe verbose"
-the output from “wanrouter status”
-the file(s) /etc/wanpipe/wanpipeX.conf (where X is the wanpipe number)
-the file /etc/zaptel.conf (if you have made any changes)
-the file(s) /etc/asterisk/zapata*.conf (if you have made any changes)
-the output from "ifconfig", (re run a couple of times with a second or so delay in between each run)
Marc
Sangoma Technologies


Member Since:
2007-11-19