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

dkerr (JIRA) noreply at issues.asterisk.org
Thu Nov 15 19:28:45 CST 2012


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

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

    Attachment: asterisk-trunk-bugid20462v2.patch

After much testing I decided that sleeping for 1/10th second is a smart thing to do rather than have a tight loop.  So I have included it in this version of the patch.  I placed the sleep before checking for SLA Station hangup so that we don't go back through the loop if the originating channel is no longer active.
                
> 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, asterisk-trunk-bugid20462.patch, asterisk-trunk-bugid20462v2.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



More information about the asterisk-bugs mailing list