[asterisk-bugs] [Asterisk 0013782]: dahdi doesn't send correct dtmf on dialing

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13782 
====================================================================== 
Reported By:                seandarcy
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13782
Category:                   Channels/chan_dahdi
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-25 12:30 CDT
Last Modified:              2008-10-25 12:38 CDT
====================================================================== 
Summary:                    dahdi doesn't send correct dtmf on dialing
Description: 
1.4.22 on dahdi-2.0.0, a pstn line on a tdm400p.

When I dial a valid local ( 7 digit ) number, most of the time I'll get
the telco recording - "number you have dialed is incomplete". Redialing
once, sometimes twice it goes through.

Here's an example of the line just waiting ( silence for
http://bugs.digium.com/view.php?id=11#c7-10 secs )
after dialing, one ring and the telco message:

    -- Starting simple switch on 'DAHDI/2-1'
    -- Executing [6258013 at internal:1] Answer("DAHDI/2-1", "") in new
stack
    -- Executing [6258013 at internal:2] Dial("DAHDI/2-1", "DAHDI/4/6258013")
in new stack
    -- Called 4/6258013
    -- DAHDI/4-1 is ringing
    -- DAHDI/4-1 answered DAHDI/2-1
    -- Native bridging DAHDI/2-1 and DAHDI/4-1
    -- Hungup 'DAHDI/4-1'
  == Spawn extension (internal, 6258013, 2) exited non-zero on
'DAHDI/2-1'
    -- Hungup 'DAHDI/2-1'

Two minutes later it works:
 
    -- Starting simple switch on 'DAHDI/2-1'
    -- Executing [6258013 at internal:1] Answer("DAHDI/2-1", "") in new
stack
    -- Executing [6258013 at internal:2] Dial("DAHDI/2-1", "DAHDI/4/6258013")
in new stack
    -- Called 4/6258013
    -- DAHDI/4-1 is ringing
    -- DAHDI/4-1 is ringing
    -- DAHDI/4-1 is ringing
    -- DAHDI/4-1 is ringing
    -- DAHDI/4-1 answered DAHDI/2-1
    -- Native bridging DAHDI/2-1 and DAHDI/4-1
    -- Hungup 'DAHDI/4-1'
  == Spawn extension (internal, 6258013, 2) exited non-zero on
'DAHDI/2-1'
    -- Hungup 'DAHDI/2-1'


I use iax for long distance, so I only see it on local calls.

 dahdi show channels
   Chan Extension  Context         Language   MOH Interpret       
 pseudo            incoming-pstn-l            default             
      1            internal                   default             
      2            internal                   default             
      4            incoming-pstn-l            default

 cat chan_dahdi.conf
[trunkgroups]

[channels]
usecallerid=yes
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=yes
group=1
callgroup=1
pickupgroup=1
callprogress=yes
progzone=us
tonezone =0 ; 0 is US
jbenable = yes              ; Enables the use of a jitterbuffer on the
receiving side of a
                              ; DAHDI channel. Defaults to "no".

;;[home-phones]
context=internal      ; Uses the [internal] context in extensions.conf
signalling=fxo_ks     ; fxo_ks. auto doesn't work. Use FXO signalling for
an FXS channel - as set in system.conf
channel => 1          ; Telephone attached to port 1
channel => 2          ; Telephone attached to port 2
;;dahdichan => 1,2

;;[pstn]
context=incoming-pstn-line  ; Incoming calls go to [incoming-pstn-line] in
extensions.conf
signalling=fxs_ks     ; fxs_ks. auto no longer works. Use FXS signalling
for an FXO channel - use as set in system.conf
faxdetect=incoming
busydetect=yes
channel => 4
;;dahdichan => 4          ; PSTN attached to port 4

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-25 12:38 russell        Status                   new => resolved     
2008-10-25 12:38 russell        Resolution               open => no change
required
2008-10-25 12:38 russell        Assigned To               => russell         
======================================================================