| 00:03.06 | *** join/#asterisk-doc DarkFlib (~DarkFlib@cpc3-nfds13-2-0-cust424.8-2.cable.virginmedia.com) |
| 00:04.30 | *** join/#asterisk-doc snuff-home2 (~snuffy@203-219-29-182.tpgi.com.au) |
| 00:19.24 | *** join/#asterisk-doc corretico (~laguilar@201.201.46.106) |
| 02:45.31 | *** join/#asterisk-doc DarkFlib (~DarkFlib@cpc3-nfds13-2-0-cust424.8-2.cable.virginmedia.com) |
| 05:29.05 | *** join/#asterisk-doc codefreeze-lap1 (~murf@mail.parsetree.com) |
| 05:35.23 | *** join/#asterisk-doc corretico_ (~laguilar@201.201.46.106) |
| 05:37.05 | *** join/#asterisk-doc codefreeze-lap (~murf@mail.parsetree.com) |
| 06:50.35 | *** join/#asterisk-doc codefreeze-lap1 (~murf@mail.parsetree.com) |
| 08:27.53 | *** join/#asterisk-doc snuff-home (~snuffy@203-219-29-182.tpgi.com.au) |
| 09:30.51 | *** join/#asterisk-doc snuff-home2 (~snuffy@203-219-29-182.tpgi.com.au) |
| 11:23.28 | *** join/#asterisk-doc leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 11:23.28 | *** mode/#asterisk-doc [+o leifmadsen] by ChanServ |
| 12:13.15 | *** join/#asterisk-doc codefreeze-lap (~murf@mail.parsetree.com) |
| 13:22.51 | *** join/#asterisk-doc eliel (~eliels@201.234.94.226) |
| 17:45.25 | jsmith-brazil | ~buy seanbright sugary snack |
| 17:45.26 | infobot | ACTION goes to S-Mart and gets a dozen sugary snacks for seanbright |
| 17:46.50 | seanbright | thanks |
| 18:02.55 | leifmadsen | I'm getting a bit stumped here.... any pointers would be appreciated |
| 18:02.56 | leifmadsen | <leifmadsen> ok this is the first time I've really had an issue like this, so I'm curious if I should be trying something like "relaxdtmf" or the like. Problem is that I have a PRI on a Digium TE220p card. For some reason sometimes I get either duplicate DTMF on the first digit (sometimes) or it misses the first digit entirely. This seems to most often happen with '2' (oddly enough). It's not consistent, and I don't b |
| 18:02.56 | leifmadsen | elieve the card h |
| 18:02.56 | leifmadsen | <leifmadsen> as an echo cancel board on it (not 100% sure, researching that now). Configuration information here: http://pastebin.com/p1m2mcp |
| 18:03.13 | leifmadsen | (btw: confirmed no echo cancel daughter board was purchased) |
| 18:04.38 | jsmith-brazil | Just the number two, eh? |
| 18:06.25 | leifmadsen | that seems to be it... but not sure if it's just a fluke. And only when it is the first character. More often than not someone dialing 2013 for example will just get 013 on the asterisk system |
| 18:06.34 | leifmadsen | sometimes it's duplicated |
| 18:06.39 | leifmadsen | but ONLY when it's the first character |
| 18:06.48 | leifmadsen | something like 9287 seems to be fine several times in a row |
| 18:06.52 | leifmadsen | sometimes 2999 will be 999 |
| 18:06.57 | leifmadsen | other times I've seen 22013 |
| 18:07.13 | leifmadsen | dtmf is out of band as I see it come in with a duration of 0ms |
| 18:25.17 | jsmith-brazil | Don't know what to tell you, other than to try to get a recording w/ dahdi_monitor and file a bug report |
| 18:25.52 | jsmith-brazil | You might find some "DTMF torture" audio files on the internet, and try passing those through Asterisk and see if anything breaks too |
| 18:28.28 | leifmadsen | hmmm good call. I'll have to try some of that. |
| 18:29.24 | leifmadsen | it is definitely an odd issue. Latest DAHDI and Asterisk 1.6.2.7 as well... |
| 18:29.42 | leifmadsen | 1.6.2.7 has been tested for RFC2833, but not sure what other DTMF testing goes on (like for PRI etc...) |
| 18:50.10 | seanbright | i'm having interesting dtmf issues with latest 1.4 and lumenvox |
| 18:50.24 | seanbright | 2s also seem problematic |
| 18:50.34 | seanbright | but it's not a pri |
| 18:50.46 | leifmadsen | odd |
| 18:50.48 | leifmadsen | and I'm not on 1.4 :) |
| 18:50.52 | seanbright | i know this |
| 18:51.02 | seanbright | 1.4 -> 1.6.2 was not a complete rewrite |
| 18:51.05 | seanbright | :-) |
| 18:52.10 | leifmadsen | maybe it was |
| 18:52.12 | leifmadsen | :D |
| 18:52.53 | seanbright | it wasn't though |
| 18:52.59 | leifmadsen | oic |
| 18:53.01 | seanbright | there's a public record |
| 18:53.05 | seanbright | it's called svn |
| 18:53.06 | seanbright | heh |
| 18:53.14 | leifmadsen | that's what "the man" wants you to believe |
| 18:53.22 | seanbright | ah |
| 18:53.25 | seanbright | understood |
| 18:53.36 | leifmadsen | it seems quite odd that a '2' in particular would be an issue |
| 18:53.52 | seanbright | i agree with you |
| 18:58.11 | jsmith-brazil | It's not the first time I've heard of problems with the number 2 |
| 18:58.25 | jsmith-brazil | But I've never been able to reproduce the problem |
| 18:58.47 | jsmith-brazil | If we can get to where we can reproduce it reliably (and capture recordings), we'll be a lot further ahead of where we are now |
| 19:00.27 | leifmadsen | agreed |
| 19:00.38 | seanbright | mine is using rfc2833 too, so it's not dsp related |
| 19:00.38 | leifmadsen | perhaps I can capture a recording of the incoming calls with dahdi_monitor? |
| 19:00.54 | seanbright | i need to try with the latest 1.4 |
| 19:09.51 | *** join/#asterisk-doc Alric (~nbowyer@anvault.com) |
| 19:57.21 | ctooley | seanbright, which DTMF issue are you having with 1.4? We've been having an interesting one as well. |
| 20:00.12 | seanbright | ctooley: well it's hard to nail down exactly. i'm working on reproducing. |
| 20:00.47 | seanbright | what was happening earlier (consistently) was pressing '6572' and asterisk getting '67572' |
| 20:03.02 | seanbright | though i want to get a packet capture and take a look in wireshark |
| 20:03.24 | seanbright | this is using SpeechBackground, which may be part of the problem |
| 20:04.56 | file | it's not. |
| 20:58.39 | seanbright | file: k, thanks. |
| 20:59.01 | seanbright | does that mean you know what the problem is or just that it's not related to SpeechBackground? |
| 21:09.58 | file | I know it's not related to speechbackground |
| 21:42.31 | *** join/#asterisk-doc codefreeze-lap (~murf@mail.parsetree.com) |
| 21:52.19 | ctooley | file is biased. |
| 21:58.21 | *** join/#asterisk-doc codefreeze-lap (~murf@mail.parsetree.com) |
| 22:07.18 | file | ctooley, that is true! |