[Home]

Summary:ASTERISK-04713: [patch] Allow DTMF to be logged
Reporter:Tilghman Lesher (tilghman)Labels:
Date Opened:2005-07-27 17:15:58Date Closed:2008-01-15 15:44:48.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/Configuration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 20050727__log_dtmf.diff.txt
Description:Just another feature for debugging purposes... a new log type of LOG_DTMF, which allows us to track what DTMF is coming through on non-natively bridged channels.  I'm sure we could do this for native channel bridging as well; it just hasn't been done here.
Comments:By: Olle Johansson (oej) 2005-07-28 02:09:34

Must be a spelling error in logger C when you're adding another LOG_DEBUG instead of LOG_DTMF - or do I misunderstand something again? (Just read the patch, did not try).
By: Tilghman Lesher (tilghman) 2005-07-28 13:10:30

No, that's for syslog.  There is no DTMF syslog level, so we have to map it to a level which exists.
By: Kevin P. Fleming (kpfleming) 2005-08-22 17:18:10

Committed to CVS HEAD, thanks! (This is a cool feature <G>)
By: Digium Subversion (svnbot) 2008-01-15 15:44:48.000-0600

Repository: asterisk
Revision: 6358

U   trunk/channel.c
U   trunk/configs/logger.conf.sample
U   trunk/include/asterisk/logger.h
U   trunk/logger.c

------------------------------------------------------------------------
r6358 | kpfleming | 2008-01-15 15:44:47 -0600 (Tue, 15 Jan 2008) | 2 lines

add a LOG_DTMF logging channel and send all bridged DTMF events out that channel (issue ASTERISK-4713)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=6358