[Home]

Summary:ASTERISK-15909: Dial 'm' option produces a lot of warnings on DAHDI channel
Reporter:leff (leff)Labels:
Date Opened:2010-04-02 12:17:54Date Closed:2011-06-07 14:05:16
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_dial
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) app_fax
( 1) chan_dahdi.conf
( 2) connectedline
( 3) sip.conf
( 4) system.conf
Description:Dial command with 'm' option produces the huge amount of messages on DAHDI channel while playing music, like this:

WARNING[13939]: chan_sip.c:3890 sip_write: Asked to transmit frame type 8, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
Comments:By: Alec Davis (alecdavis) 2010-04-02 20:41:59

Not much to go on here.
You may need a Progress() or Answer() statement before the outgoing dial to the dahdi channel.

Are you able to provide console output with verbose setting of at least 3.
By: leff (leff) 2010-04-03 00:31:05

I used Answer(), have tried Progress() with the same result:

-- Accepting call from '...' to '...' on channel 0/1, span 1
   -- Executing [...:1] Set("DAHDI/1-1", "CALLERID(all)="..." <...>") in new stack
   -- Executing [...:2] Goto("DAHDI/1-1", "ivr|s|1") in new stack
   -- Goto (ivr,s,1)
   -- Executing [s@ivr:1] Set("DAHDI/1-1", "TIMEOUT(absolute)=18000") in new stack
   -- Channel will hangup at 2010-04-03 10:22:19 UTC.
   -- Executing [s@ivr:2] Set("DAHDI/1-1", "TIMEOUT(digit)=5") in new stack
   -- Digit timeout set to 5
   -- Executing [s@ivr:3] Set("DAHDI/1-1", "TIMEOUT(response)=5") in new stack
   -- Response timeout set to 5
; It was Answer() here:
   -- Executing [s@ivr:4] Progress("DAHDI/1-1", "") in new stack
   -- Executing [s@ivr:5] Wait("DAHDI/1-1", "2") in new stack
   -- Executing [s@ivr:6] BackGround("DAHDI/1-1", "ivr/hello") in new stack
   -- <DAHDI/1-1> Playing 'ivr/hello' (language 'en')
   -- Executing [s@ivr:7] WaitExten("DAHDI/1-1", "4") in new stack
   -- Timeout on DAHDI/1-1, going to 't'
   -- Executing [t@ivr:1] Macro("DAHDI/1-1", "operator") in new stack
   -- Executing [s@macro-operator:1] GotoIfTime("DAHDI/1-1", "9:00-17:30|*|*|*?operator|1") in new stack
   -- Goto (macro-operator,operator,1)
; If we move the 'm' option out from Dial() here, there will be no warning, but no music too:
   -- Executing [operator@macro-operator:1] Dial("DAHDI/1-1", "SIP/XXXX|120|mt") in new stack
   -- Called XXXX
   -- Started music on hold, class 'default', on DAHDI/1-1
[Apr  3 09:22:40] WARNING[14478]: chan_sip.c:3890 sip_write: Asked to transmit frame type 8, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
...and so on until I disconnect (music is ok) or operator answers...
By: Alec Davis (alecdavis) 2010-04-03 17:44:33

I've been unable to reproduce this issue, using a fresh download of the 1.4.30 tag release, using the following dialplan, from a EuroISDN E1 source to a TE122<pre>
[macro-operator]
exten => s,1,Dial(SIP/cisco4,120,mt)

[ivr2-bdt-main]
 exten => s,1,Verbose(0,'${CALLERID(num)}' IVR Main called '${CALLERID(dnid)}')
 exten => s,n,Progress()
 exten => s,n,Wait(2)
 exten => s,n,Goto(ivr2-bdt-day,s,1)

[ivr2-bdt-day]
 exten => s,1,Verbose(0,'${CALLERID(num)}' IVR MAIN-DAY)
 exten => s,n,Set(TIMEOUT(absolute)=18000)
 exten => s,n,Set(TIMEOUT(digit)=5)
 exten => s,n,Set(TIMEOUT(response)=5)

 exten => s,n,Background(silence/1)
 exten => s,n,Background(bdt/mainbdt-day)
 exten => s,n,WaitExten(4)

 exten => t,1,Macro(operator)</pre>

Could you describe your setup and upload the following taking care to remove sensitive data
/etc/dahdi/system.conf
/etc/asterisk/chan_dahdi.conf
/etc/asterisk/sip.conf
By: leff (leff) 2010-04-04 02:57:23

Hello.

Software: Debian Lenny, Asterisk 1.4.30 + app_fax patch + connectedline patch (last is not used now because of the bug https://issues.asterisk.org/view.php?id=17134).

Hardware: Digium TE220B (that with echocompensation module on card).

# cat /etc/modprobe.d/dahdi
install wct4xxp /sbin/modprobe --ignore-install wct4xxp t1e1override=0x03 debug=1 && /usr/sbin/dahdi_cfg

Files are attached.

Thank you and best regards.
Leff.


By: Alec Davis (alecdavis) 2010-04-04 03:04:39

Forgot to ask - dahdi and libpri version?
By: leff (leff) 2010-04-04 03:12:55

dahdi-linux-complete-2.2.1.1+2.2.1.1
libpri-1.4.10.2
By: Alec Davis (alecdavis) 2010-04-04 04:05:29

Please point me to the patches for app_fax_patch and connectedline patch?
By: leff (leff) 2010-04-04 04:23:47

Both patches are attached.
app_fax patch has been taken from some maillists (the only one that started to work with 1.4.30 for me).
Connectedline patch has been taken from here:
https://issues.asterisk.org/file_download.php?file_id=25318&type=bug
Thank you.
By: Alec Davis (alecdavis) 2010-04-04 04:53:24

reproducible after connected_line patch.

[Apr  4 21:37:11] WARNING[23203]: chan_sip.c:3890 sip_write: Asked to transmit frame type 8, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
By: leff (leff) 2010-04-04 05:04:04

Thank you.
That CONNECTEDLINE function is needed in our corporate environment. Hope, it will be fixed, because of it crashes Asterisk when it is used by dialplan and consultative transfer.
I have updated the information here:
https://issues.asterisk.org/view.php?id=17134
By: Leif Madsen (lmadsen) 2010-04-06 10:02:08

Closed due to this being an issue with an out-of-band patch. Thanks alecdavis!