[asterisk-bugs] [JIRA] (ASTERISK-21761) sip call stuck, crash
Dmitry Melekhov (JIRA)
noreply at issues.asterisk.org
Mon May 20 22:37:01 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206649#comment-206649 ]
Dmitry Melekhov commented on ASTERISK-21761:
--------------------------------------------
Hello!
There was no such crash since May 7, so I don't think I'll able to reproduce it.
btw, I can't compile asterisk with DONT_OPTIMIZE, just because it leads to unacceptable performance in this case.
So, if my backtraces useless you can just close this issue :-)
Thank you!
> 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
More information about the asterisk-bugs
mailing list