[asterisk-bugs] [JIRA] Commented: (ASTERISK-20416) Autodestruct warnings spamming CLI and extension to extension calls not possible after problem forces maximum calls limit reached at 500 calls

[aragon (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197839#comment-197839 ] 

aragon commented on ASTERISK-20416:
-----------------------------------

In regards to the other reporters comment=
3. If you hang up the remaining channel (put phone back on-hook) BEFORE 30 seconds are up, Asterisk really doesn't like this. A few seconds after you do this, you will see a "WARNING: chan_sip.c: __sip_autodestruct: Autodestruct on dialog '[...]' with owner in place (Method: BYE)" show on the console, and the BYE dialog will remain "stuck" in 'sip show channels' until you restart Asterisk. After a while, these really begin to accumulate.'

Inadvertently we have reproduced the reporters steps to reproduce.
In step 16 our all-hangup agi script forces a hangup on the channel waiting for the BYE which causes the channel to hang until we restart Asterisk.  I presume the hangup() cancels Asterisk ever sending the BYE... so I am left pondering why Asterisk waits so long to send a BYE in the first place.

> Autodestruct warnings spamming CLI and extension to extension calls not possible after problem forces maximum calls limit reached at 500 calls
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20416
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20416
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: SVN
>         Environment: Centos 5.8 x64 quadcore 8 GB RAM
>            Reporter: aragon
>            Assignee: aragon
>            Severity: Critical
>         Attachments: asterisk.stack.txt, autodestructverbosecli2.txt, autodestructverbosecli.txt, cli_debug_autodestruct.rar, cli_debug_autodestruct.rar, log.rar
>
>
> Every single day Asterisk cannot complete transfers or local extensions cannot call.
> While incoming and outgoing calls are working...
> Autodestruct warnings spam the CLI with hundreds of WARNINGS per minute.
> Local calls become possible only after the Autodestruct messages go away or Asterisk is restarted.
> It is speculated that Autodestructs frequently occur during dynamic ACD logins or outgoing calls requiring PINs so this could be related to some ast_waitfordigit issue discovered at ASTERISK-20375.
> All incoming calls terminate to ACD queue.
> All outgoing calls require a PIN to complete.
> No IVR's in use.
> No DTMF *2 transfers being done by users.
> Opening a new ticket since I am not 100% sure they are related issues.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira