[asterisk-bugs] [Asterisk 0015924]: pulse and hardware dtmf digits not detected in chan_dahdi/trunk

[Asterisk Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15924 
====================================================================== 
Reported By:                tzafrir
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   15924
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 219719 
Request Review:              
====================================================================== 
Date Submitted:             2009-09-21 10:17 CDT
Last Modified:              2009-10-05 11:41 CDT
====================================================================== 
Summary:                    pulse and hardware dtmf digits not detected in
chan_dahdi/trunk
Description: 
sig_analog (in the chan_dahdi rewrite) fails to detect pulse digits events
as well as DTMF up events sent from DAHDI.

The events 'pulse digit N', 'dtmf digit N down', and 'dtmf digit N up' are
marked by (N | 1<<16) , (N | 1<<17) and (N | 1<<18), respectively. See
dahdi/include/user.h .

However in chan_dahdi.c:my_get_event() , the raw event number is filtered
through dahdievent_to_analogevent() . Which does not find those events and
thus returns ANALOG_EVENT_ERROR . This has the unlucky value of 13. Sadly,
though, computers are over-rational and don't consider 13 as an error
value. And generally this functionality is missing.

Generally implementing pulse dialing should be simple. Supporting DTMF
down/up events involves muting the line.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-05 11:41 jpeeler        Status                   acknowledged =>
assigned
2009-10-05 11:41 jpeeler        Assigned To               => jpeeler         
======================================================================