[asterisk-bugs] [JIRA] (ASTERISK-21761) sip call stuck, crash

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-21761:
------------------------------------

    Assignee: Dmitry Melekhov
      Status: Waiting for Feedback  (was: Triage)

1. Can you reproduce the issue? If so, please follow the compilation instructions [here|https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-PreparingAsteriskToProduceCoreFilesOnCrash] and gather a new set of backtraces

2. Do you have a packet capture from the unusually long SIP call?

3. Did you happen to capture an ASTERISK log (preferably with VERBOSE and DEBUG enabled) up to the crash?

If you have 2 and 3, can you attach them to the issue? (More Actions > Attach Files) 
                
> sip call stuck, crash
> ---------------------
>
>                 Key: ASTERISK-21761
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21761
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.3.0
>         Environment: Centos 6.4/x86
>            Reporter: Dmitry Melekhov
>            Assignee: Dmitry Melekhov
>            Severity: Minor
>         Attachments: bt, bt-full
>
>
> Hello!
> We have asterisk with pri connection to pbx as pri-h323 and pri-sip gateway.
> Some time I upgraded asterisk 10 to 11.3.0 and today I hit problem- all pri channels were busy, this is another issue, but, may be related, just because I had stange very long sip call ( I know this by info from zabbix monitoring) and I see this call in info from core, which asterisk generated during it's restart.
> bt and bt full files will be attached.
> I understand that this info may be useless, but I hope it can also help to find bug.
> Thank you!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira