[asterisk-bugs] [Asterisk 0015129]: Incoming DTMF causes "Cannot handle frames in 2 format" error, call dies

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15129 
====================================================================== 
Reported By:                bmh
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15129
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-16 08:18 CDT
Last Modified:              2009-05-18 08:25 CDT
====================================================================== 
Summary:                    Incoming DTMF causes "Cannot handle frames in 2
format" error, call dies
Description: 
All incoming DTMF tones over my DAHDI interface (a PRI) cause the following
error:

[May 16 08:38:27] WARNING[2387]: chan_dahdi.c:5624 dahdi_write: Cannot
handle frames in 2 format
[May 16 08:38:27] WARNING[2387]: file.c:723 ast_readaudio_callback: Failed
to write frame
    -- Hungup 'DAHDI/1-1'

The call is dropped and this error appears on the Asterisk console as soon
as any DTMF is received over the DAHDI interface. Calls otherwise function
normally until any digit on a phone's keypad is pressed while calling in.

====================================================================== 

---------------------------------------------------------------------- 
 (0104915) file (administrator) - 2009-05-18 08:25
 https://issues.asterisk.org/view.php?id=15129#c104915 
---------------------------------------------------------------------- 
Can you please upload a *complete* console output log with debug set to go
to console in logger.conf and "core set debug 2" executed in the CLI? The
message is actually coming up because a GSM audio frame is getting to
chan_dahdi when it shouldn't be. So the real question is - what is causing
that to happen? Hopefully the console log will show exactly what is up. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-18 08:25 file           Note Added: 0104915                          
2009-05-18 08:25 file           Status                   new => feedback     
======================================================================