Summary:ASTERISK-07520: DTMF not read correctly on Zap channels if busydetect=yes
Reporter:inspired (inspired)Labels:
Date Opened:2006-08-11 03:33:39Date Closed:2011-06-07 14:03:25
Versions:Frequency of
Description:I recently upgraded from version 1.0.7 to 1.2.10 and noticed that DTMF is no longer working like it should on incoming Zap channels (E1 PRI). I have a few apps that read entered DTMF, among them is a dial-in app that reads destination number and calls it. If I call this number only 4-5 digits are detected before the channel is hung up when using 1.2.10, and on 1.0.7 the whole digit sequence is detected. I have also tried other apps like Read to see if my app is the problem, but the output is the same no matter what app I use.

See below. If you look at dst it shows 0047xt, while I actually entered 004721651012.

app_mcc2.c:639 mcc2_acct_stop: User ID: 2, src: 99355151, dst: 4646xt, hangup: NO ANSWER, time: 0, rate: 0, price: 0.000000

On SIP channels DTMF works OK - the whole DTMF sequence is captured, but for Zap channels it doesn't work.
Comments:By: Serge Vecher (serge-v) 2006-08-11 09:23:41

if you have a Digium card, I think the best route here is to contact Digium Technical Support. Be prepared to use stock Asterisk build though.

By: inspired (inspired) 2006-08-11 09:26:28

I have a Sangoma card in this machine. I don't think the problem has anything to do with the card, since it worked before and drivers etc are exactly the same. The only things I have updated are libri, zaptel and asterisk.

By: Russell Bryant (russell) 2006-08-13 21:37:32

Well, you're also using a module that is not in Asterisk (app_mcc2), so we can't help you.

By: inspired (inspired) 2006-08-14 02:12:39

Ok. As I stated earlier I have tried with other apps as well, including removing app_mcc2.c from the modules dir and using a clean unpatched asterisk 1.2.10 version, and the problem still persists. It has nothing to do with the module.

By: Russell Bryant (russell) 2006-08-14 09:04:15

Still, given that we have absolutely no other reports of problems related to DTMF detection on zap channels, I am going to have to say this is a problem with your hardware.  Please pursue the issue through your vendor.

By: inspired (inspired) 2006-11-10 06:42:57.000-0600

Sorry for reopening this, but I want to say that
busydetect=no fixes this. Just wanted to give anyone else who might have this problem the cure to resolve it. If busydetect=yes Asterisk will mistake the DTMF for a BUSY signal and then hang up the call.

By: Russell Bryant (russell) 2006-11-10 15:42:40.000-0600

Thanks for the update.  busydetect is known not to work very well ...