[Home]

Summary:ASTERISK-12964: dahdi doesn't send correct dtmf on dialing
Reporter:Sean Darcy (seandarcy)Labels:
Date Opened:2008-10-25 12:30:25Date Closed:2011-06-07 14:02:42
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
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 ~7-10 secs ) after dialing, one ring and the telco message:

   -- Starting simple switch on 'DAHDI/2-1'
   -- Executing [6258013@internal:1] Answer("DAHDI/2-1", "") in new stack
   -- Executing [6258013@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@internal:1] Answer("DAHDI/2-1", "") in new stack
   -- Executing [6258013@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
Comments:By: Russell Bryant (russell) 2008-10-25 12:38:26

This is likely just a configuration issue.  Try putting some w's in your dial string to introduce a short wait before dialing.  This usually fixes these problems on an FXO.

Dial(DAHDI/1/ww${THENUMBER})