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

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-20416:
------------------------------------

    Status: Open  (was: Triage)

> 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