[asterisk-bugs] [JIRA] (ASTERISK-20462) Trunk not hungup if SLA Station hangs up before answer

[dkerr (JIRA)]

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

dkerr updated ASTERISK-20462:
-----------------------------

    Attachment: asterisk-1.8-bugid20462.patch

Attached patch file fixes this issue inside app_meetme.c.  The problem was that after triggering an asynchronous dial for a Trunk, the code loops waiting for that trunk/channel to do something (answer, hangup, whatever). But the code does not watch for status changes at the originating channel/device. So if it hangs up the SLA code never knows.

I added code into this loop to test for the originating channel/device going to NOT_INUSE status and if detected break out of the loop with NULL trunk channel.  Existing code acts on that to shut down the trunk, et al.

See also bug 20440 for another critical fix to SLA, and 20675 for a desirable added feature to SLATrunk().

Thanks !
                
> Trunk not hungup if SLA Station hangs up before answer
> ------------------------------------------------------
>
>                 Key: ASTERISK-20462
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20462
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme, Applications/SLA
>    Affects Versions: 1.8.15.0
>         Environment: Astlinux
>            Reporter: dkerr
>         Attachments: asterisk-1.8-bugid20462.patch, extensions.conf, Hangup before answer.txt, sip.conf, sla.conf
>
>
> If an SLA station hangs up before the called party answers, then the channel to the sla station is terminated, but the channel to the called party remains open and continues to ring until timeout. Or if the party answers then they get unobtainable tone and asterisk fails all over trying to connect to a meetme conference that does not exist.
> See attached log file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira