Asterisk People, I'm currently using Asterisk and with a SIP voip provider and I'm having problems where DTMF input in my IVR app is getting corrupted intermittently. For example, if someone enters 1025, it may come though correctly as 1025, or it may come trough as 10025, or 100255. DTMF digits will just double up. This doesn't happen all the time. Asterisk will just pick times to not be very friendly with DTMF, and other times it will just work flawlessly. I'm using RFC2833 on: Linux hostname 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006 i686 i686 i386 GNU/Linux with Asterisk 1.2.13. Also, I am not using a zaptel timer. Could this possibly be causing problems with DTMF?? Thanks! -- Justin Tunney
Justin Tunney wrote:> Asterisk People, > > I'm currently using Asterisk and with a SIP voip provider and I'm > having problems where DTMF input in my IVR app is getting corrupted > intermittently. > > For example, if someone enters 1025, it may come though correctly as > 1025, or it may come trough as 10025, or 100255. DTMF digits will > just double up. > > This doesn't happen all the time. Asterisk will just pick times to > not be very friendly with DTMF, and other times it will just work > flawlessly. > > I'm using RFC2833 on: > > Linux hostname 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006 > i686 i686 i386 GNU/Linux > > with Asterisk 1.2.13. > > Also, I am not using a zaptel timer. Could this possibly be causing > problems with DTMF?? > > Thanks! > > -- > Justin TunneyJustin, Have you tried 1.4 with vldtmf? -- Kristian Kielhofner
Hey, Justin: Justin Tunney wrote:> Asterisk People, > > I'm currently using Asterisk and with a SIP voip provider and I'm > having problems where DTMF input in my IVR app is getting corrupted > intermittently. > > For example, if someone enters 1025, it may come though correctly as > 1025, or it may come trough as 10025, or 100255. DTMF digits will > just double up. > > This doesn't happen all the time. Asterisk will just pick times to > not be very friendly with DTMF, and other times it will just work > flawlessly.I'm having virtually the same problem with Asterisk -- the SendDTMF() function. In my case, I hear the first digit, then none of the other digits -- or only some. It's been suggested that it's a channel issue, but I'm having the problem with an IAX channel, and if so, it would mean that there is DTMF issue in both the SIP and IAX channel drivers. That seems pretty unlikely. As in your case, it is highly inconsistent. Depending on when it is run, I'll hear different digits at different durations. Whatever the case, it's not usable. (DTMF grief seems to be painfully common with Asterisk.) It would help to get additional feedback from other users. I've posted a bug. The bug URL is: http://bugs.digium.com/view.php?id=8293 -Stephen-
> Also, I am not using a zaptel timer. Could this possibly be causing > problems with DTMF??I really don't know for certain but here's what I experienced: When calling out asterisk gives the option to allow called numbers to transfer by hitting the '#' by putting 'T' (or 't'?) as an option in th dial string. This would very seldom work. I could hit the '#' on the called phone it would say 'extension' but would always reply with 'not valid extension' I recently upgraded to 1.2.12 and noticed that there was no ztdummy running! I compiled my own zaptel installed it, loaded the modules on boot and now the transfer works perfectly. Also: my moh wasn't working for some reason. After I installed the ztdummy module it works too.. I'm not sure whether the transfer issue was fixed by using the ztdummy module or by the asterisk issue but my point is that you should always have the ztdummy module installed if possible. Just my .02. Hope it helps
UPDATE: I've installed ztdummy and have chan_zap.so loaded in to the system so Asterisk can use psuedo zap channels or whatever it does for timing. I also specified relaxdtmf=yes in sip.conf. DTMF is still completely awful. Digits are still getting doubled up and my IVR is still nearly impossible to use. I'd like to note that I'm using Bandwidth.Com (A Level3 reseller) for SIP VoIP service. I did not experience this problem before with my old VoIP provider Gafachi. Does anyone have some tips on trying to debug this further? Are there any commands I can put in to tethereal that will give me debug information on RFC2833 in the RTP stream? Thanks, Justin Tunney
Sup pigs, I think I found the solution to the problem! It's a one line of code fix to rtp.c that people have been going daffy about for almost a year! A patch was uploaded in August but for some reason it hasn't found its way in to 1.2. Here's the bug: http://bugs.digium.com/view.php?id=5970 Direct link to patch for the lazy: http://bugs.digium.com/file_download.php?file_id=11337&type=bug On 11/8/06, Justin Tunney <jtunney@gmail.com> wrote:> Asterisk People, > > I'm currently using Asterisk and with a SIP voip provider and I'm > having problems where DTMF input in my IVR app is getting corrupted > intermittently. > > For example, if someone enters 1025, it may come though correctly as > 1025, or it may come trough as 10025, or 100255. DTMF digits will > just double up. > > This doesn't happen all the time. Asterisk will just pick times to > not be very friendly with DTMF, and other times it will just work > flawlessly. > > I'm using RFC2833 on: > > Linux hostname 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006 > i686 i686 i386 GNU/Linux > > with Asterisk 1.2.13. > > Also, I am not using a zaptel timer. Could this possibly be causing > problems with DTMF?? > > Thanks! > > -- > Justin Tunney >