[asterisk-bugs] [JIRA] (DAHLIN-100) Hangups are ignored if the channel has not been answered

[Keith Morgan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHLIN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Morgan closed DAHLIN-100.
-------------------------------

    Resolution: Won't Fix

> Hangups are ignored if the channel has not been answered
> --------------------------------------------------------
>
>                 Key: DAHLIN-100
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-100
>             Project: DAHDI-Linux
>          Issue Type: Bug
>          Components: dahdi (the module)
>    Affects Versions: 2.1.0.4
>            Reporter: Daniel Hazelbaker
>            Severity: Minor
>
> 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.
> ****** ADDITIONAL INFORMATION ******
> I am technically using zaptel still with 1.4, but from looking at the code it is the same in both.



--
This message was sent by Atlassian JIRA
(v6.2#6252)