[asterisk-bugs] [DAHDI-linux 0015018]: Hangups are ignored if the channel has not been answered
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 7 11:49:44 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=15018
======================================================================
Reported By: cabal95
Assigned To:
======================================================================
Project: DAHDI-linux
Issue ID: 15018
Category: dahdi (the module)
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
JIRA:
Reviewboard Link:
======================================================================
Date Submitted: 2009-05-02 13:32 CDT
Last Modified: 2010-10-07 11:49 CDT
======================================================================
Summary: Hangups are ignored if the channel has not been
answered
Description:
When a call comes in, if it has not been Answer()'d yet by Asterisk and the
call is hung up (i.e., I changed my mind, or I called wrong number, etc.),
Dahdi does not pass the hookswitch state to Asterisk to signal a hangup.
In my dialplan I have a Wait(2) before I Answer() the call. If the calling
party hangs up during this Wait(2) call before Answer() then the hangup is
never detected and eventually goes to voicemail as a re-order tone.
At or near line 6321 is this bit of code:
case DAHDI_SIG_FXSKS: /* FXS Kewlstart */
/* ignore a bit error if loop not closed and stable */
if (chan->txstate != DAHDI_TXSTATE_OFFHOOK) break;
Is there any reason for this? I commented this out and everything seems
to be fine and it actually detects those early hangups now. It would seem
like this was put in to fix one bug and caused another.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-10-07 11:49 mspiceland Description Updated
======================================================================
More information about the asterisk-bugs
mailing list