| 01:24.19 | *** join/#asterisk-bugs darkbasic (~quassel@niko.linuxsystems.it) |
| 08:04.51 | *** join/#asterisk-bugs Qwell (~north@pdpc/sponsor/digium/Qwell) |
| 08:04.51 | *** mode/#asterisk-bugs [+o Qwell] by ChanServ |
| 08:57.54 | *** join/#asterisk-bugs tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 11:10.06 | *** join/#asterisk-bugs darkbasic (~quassel@niko.linuxsystems.it) |
| 11:10.13 | *** join/#asterisk-bugs italorossi (~italoross@187.60.66.11) |
| 11:14.32 | *** join/#asterisk-bugs darkbasic_ (~quassel@niko.linuxsystems.it) |
| 13:07.33 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:07.33 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 13:11.41 | *** join/#asterisk-bugs mjordan (~mjordan@nat/digium/x-ktryiwknpmiaufot) |
| 13:11.41 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 14:01.00 | *** join/#asterisk-bugs Juggie (~Juggie@unaffiliated/juggie) |
| 14:01.00 | *** mode/#asterisk-bugs [+o Juggie] by ChanServ |
| 14:12.05 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:12.05 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 15:39.53 | *** join/#asterisk-bugs darkbasic (~quassel@niko.linuxsystems.it) |
| 16:59.05 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 16:59.05 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 17:14.05 | *** join/#asterisk-bugs tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 17:56.05 | *** join/#asterisk-bugs ibercom (5121944c@gateway/web/freenode/ip.81.33.148.76) |
| 18:43.21 | ibercom | I have a Digium Wildcard TE410P (4th Gen) with hardware echo canceller. With DAHDI Version 2.6.x DTMF detection is bad, With DAHDI Version 2.7.x something better. |
| 18:47.34 | ibercom | DAHDI Version 2.4.0 is good. Where do I report the bug ? Digium or issues.asterisk.org |
| 19:17.11 | newtonr | Digium technical support |
| 19:17.17 | newtonr | one second I'll grab the link |
| 19:17.42 | newtonr | ibercom, http://www.digium.com/en/support/contact |
| 19:19.43 | newtonr | ibercom, they'll probably want to see some debug or get on your system to identify the issue, so in preparation ahead of time you can look https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information and collect logs with debug,verbose,dtmf message types. Probably want to collect logs with the working versions and the ones that fail |
| 19:20.17 | newtonr | They may also want recordings with the dahdi_monitor application to correspond to those logs |
| 19:20.30 | newtonr | http://docs.tzafrir.org.il/dahdi-tools/man/dahdi_monitor.8.html |
| 19:22.30 | newtonr | you'll only need recordings if the DTMF is inband of course |
| 19:23.31 | newtonr | ibercom, If the issue does end up being with Asterisk's DTMF detection, then they'll file the issue for you on the tracker. But it is best to work with them |
| 22:17.20 | *** part/#asterisk-bugs mjordan (~mjordan@nat/digium/x-ktryiwknpmiaufot) |
| 23:52.00 | *** join/#asterisk-bugs newtonr (~newtonr@nat/digium/x-ujqmbfulhdtpcmua) |
| 23:52.00 | *** mode/#asterisk-bugs [+o newtonr] by ChanServ |