Summary: | ASTERISK-21761: sip call stuck, crash | ||
Reporter: | Dmitry Melekhov (slesru) | Labels: | |
Date Opened: | 2013-05-07 05:57:33 | Date Closed: | 2013-05-22 15:29:26 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | 11.3.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Centos 6.4/x86 | Attachments: | ( 0) bt ( 1) bt-full |
Description: | 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! | ||
Comments: | By: Rusty Newton (rnewton) 2013-05-20 17:10:35.789-0500 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) By: Dmitry Melekhov (slesru) 2013-05-20 22:35:56.410-0500 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! By: Rusty Newton (rnewton) 2013-05-22 15:29:26.713-0500 Thanks! |