[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=197762#comment-197762 ] 

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

We have narrowed it down to some interaction with all-hangup agi script.
which does:
sip*CLI> dialplan show all-hangup
[ Context 'all-hangup' created by 'pbx_config' ]
  's' =>            1. Set(CDR(hangupside)=${HANGUPSIDE})         [pbx_config]
                    2. Set(CDR(hangupcause)=${HANGUPCAUSE})       [pbx_config]
                    3. Set(CDR(codec1)=${CHANNEL(audioreadformat)}) [pbx_config]
                    4. Set(CDR(codec2)=${CHANNEL(audiowriteformat)}) [pbx_config]
                    5. Set(CDR(recvip)=${CHANNEL(recvip)})        [pbx_config]
                    6. Set(CDR(fromchan)=${CHANNEL(from)})        [pbx_config]
                    7. Set(CDR(uri)=${CHANNEL(uri)})              [pbx_config]
                    8. Set(CDR(useragent)=${CHANNEL(useragent)})  [pbx_config]
                    9. Set(CDR(llp)=${CHANNEL(rtpqos,audio,local_maxrxploss)}) [pbx_config]
                    10. Set(CDR(rlp)=${CHANNEL(rtpqos,audio,remote_maxrxploss)}) [pbx_config]
                    11. Set(CDR(ljitt)=${CHANNEL(rtpqos,audio,local_maxjitter)}) [pbx_config]
                    12. Set(CDR(rjitt)=${CHANNEL(rtpqos,audio,remote_maxjitter)}) [pbx_config]
                    13. GotoIf($["${FAXID}xxx" != "xxx"]?all-faxnotify,s,1:$[${PRIORITY} + 1]) [pbx_config]
                    14. ResetCDR(w)                               [pbx_config]
                    15. NoCDR()                                   [pbx_config]
                    16. Hangup()                                  [pbx_config]

The only relevant lines here are 14-16
Where I think we try to write CDR and Hangup on a leg that is already disappeared and that causes failed to write frame and Autodestructs.  I have no idea why.

Unfortunately I think we are weeks away from being able to run asterisk in ref count debugging mode.

Also I think I found a duplicate ticket on bug tracker ASTERISK-20486 and it looks like that reporter is much further along in diagnosing the problem than I am.

> 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