| Summary: | ASTERISK-00336: [patch] Added dtmf debug CLI command | ||
| Reporter: | jjhuff (jjhuff) | Labels: | |
| Date Opened: | 2003-09-30 00:07:51 | Date Closed: | 2011-06-07 14:05:17 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) debug_dtmf.diff | |
| Description: | dtmf debug enables the display of what DTMF digits * is getting from various channels. I'm not entirely sure that this is the best place for the code. Comments welcome... | ||
| Comments: | By: jjhuff (jjhuff) 2003-09-30 20:15:59 Updated patch.. By: Brian West (bkw918) 2003-11-22 16:09:48.000-0600 Can someone test this and post back results? By: screel (screel) 2004-01-06 16:55:19.000-0600 I applied the patch to CVS from 11/28/03 and had a small problem. I have a loop setup to read three digits, then SayDigits() back to me (trying to troubleshoot a dtmf recognition problem). If I dial slow, the dtmf debug messages are printed for all of the keypresses. If I dial quickly, the first digit is not reported (though the other two are). SayDigits confirms that the key was actually pressed. A small documentation typo - in the 'help' listing, the description for 'dtmf debug' has 'Enabled' instead of 'Enable' A very helpful patch... By: Brian West (bkw918) 2004-01-27 23:50:02.000-0600 Dont work :) | ||