[asterisk-bugs] [JIRA] (ASTERISK-30228) Lot of „Autodestruct on dialog with owner SIP/XXXX in place (Method: BYE). Rescheduling destruction for 10000 ms“, and finally „taskprocessor.c: The 'stasis/p:channel:all' task processor queue reached 500 scheduled tasks“

George Joseph (JIRA) noreply at issues.asterisk.org
Fri Sep 16 08:04:09 CDT 2022


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

George Joseph updated ASTERISK-30228:
-------------------------------------

    Status: Open  (was: Triage)

> Lot of „Autodestruct on dialog with owner SIP/XXXX in place (Method: BYE). Rescheduling destruction for 10000 ms“, and finally „taskprocessor.c: The 'stasis/p:channel:all' task processor queue reached 500 scheduled tasks“
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30228
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30228
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/CallCompletionSupplementaryServices
>    Affects Versions: 16.8.0
>         Environment: Ubuntu 20.04 LTS
>            Reporter: Vitalij Bogomolnikov
>            Severity: Critical
>
> We encountered with strange Asterisk hanging. We have a lot of Asterisk servers connected to a lot of providers, but this problem exists only with Asterisk servers connected to one provider. 
> Sometimes (randomly: one time per week or sometimes per day) Asterisk can't correctly Hangup incoming call. We see a lot of Warnings "Autodestruct on dialog with owner SIP/XXXX in place (Method: BYE). Rescheduling destruction for 10000 ms". Then we get Warning „taskprocessor.c: The 'stasis/p:channel:all' task processor queue reached 500 scheduled tasks“. 
> We don't find any way to destroy bad channel from CLI. Only one way help - Asterisk restart. We tried to change different SIP settings, but unsuccessfully. Please help us to resolve this problem.
> We made a some coredumps. How to send files to you?



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



More information about the asterisk-bugs mailing list