[asterisk-bugs] [DAHDI-linux 0015352]: [patch] Click heard 6 seconds after answer on FXS ports.

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 5 11:13:06 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15352 
====================================================================== 
Reported By:                alecdavis
Assigned To:                dbailey
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15352
Category:                   wctdm
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-06-18 04:12 CDT
Last Modified:              2009-08-05 11:13 CDT
====================================================================== 
Summary:                    [patch] Click heard 6 seconds after answer on FXS
ports.
Description: 
Continuation of https://issues.asterisk.org/view.php?id=15311 which is
specifically related AsteriskNOW 1.5

This is for SVN trunk.

If a call to a FXS port on a TDM400P is picked up while ringing (not
silent period), after 6 seconds of the pickup a click is heard, and it's
reported that sometimes this causes a hangup.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0015311 [patch] Call to a FXS DAHDI channel wit...
====================================================================== 

---------------------------------------------------------------------- 
 (0108659) dbailey (administrator) - 2009-08-05 11:13
 https://issues.asterisk.org/view.php?id=15352#c108659 
---------------------------------------------------------------------- 
Alec, 

I was able to reproduce the following on the wctdm and wctdm24xxp
drivers.

Here is my scenario

My fxo line is configured so that it waits 4 seconds, answers, then loops
through a playback.
I have two FXS lines in which FXS2 is looped back the FXO line.

I have fxs1 (dahdi/9) call fxs2 (dahdi/10) which connects to the fxo
(dahdi/1).
Before the call is answered by the fxo (i.e. it is executing wait), I
hangup fxs1 which hangs up both fxs1 and fxs2
The fxo diaplan continues to execute with a simple switch thread started
on fxs2

    -- Starting simple switch on 'DAHDI/9-1'
    -- Executing [7770 at default:1] NoOp("DAHDI/9-1", ""Call dahdi10"") in
new stack
    -- Executing [7770 at default:2] Dial("DAHDI/9-1", "dahdi/10") in new
stack
    -- Called 10
    -- DAHDI/10-1 is ringing
    -- DAHDI/10-1 is ringing
    -- Starting simple switch on 'DAHDI/1-1'
    -- Executing [s at dougfxo:1] NoOp("DAHDI/1-1", ""Doug's test context"")
in new stack
    -- Executing [s at dougfxo:2] Wait("DAHDI/1-1", "4") in new stack
    -- Hanging up on 'DAHDI/10-1'
    -- Hungup 'DAHDI/10-1'
  == Spawn extension (default, 7770, 2) exited non-zero on 'DAHDI/9-1'
    -- Hanging up on 'DAHDI/9-1'
    -- Hungup 'DAHDI/9-1'
    -- Starting simple switch on 'DAHDI/9-1'
    -- Executing [s at dougfxo:3] Answer("DAHDI/1-1", "") in new stack
    -- Executing [s at dougfxo:4] Playback("DAHDI/1-1", "tt-weasels") in new
stack
    -- <DAHDI/1-1> Playing 'tt-weasels.gsm' (language 'en')
    -- Starting simple switch on 'DAHDI/10-1'
    -- Hanging up on 'DAHDI/9-1'
    -- Hungup 'DAHDI/9-1'
    -- Executing [s at dougfxo:5] Wait("DAHDI/1-1", "10") in new stack
    -- Executing [s at dougfxo:6] Goto("DAHDI/1-1", "looper") in new stack
    -- Goto (dougfxo,s,4)

Is this the scenario you are talking about? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-05 11:13 dbailey        Note Added: 0108659                          
======================================================================




More information about the asterisk-bugs mailing list