[asterisk-bugs] [JIRA] (ASTERISK-17119) Deadlock after receiving calls generated with sipp

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Jan 15 10:55:45 CST 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-17119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201534#comment-201534 ] 

Matt Jordan commented on ASTERISK-17119:
----------------------------------------

The deadlocks that occurred during an indicate operation and device state changes should all be resolved in Asterisk 1.8 and later at this point. If you are still having this problem, please contact a bug marshal in #asterisk-bugs and we'll reopen this issue.
                
> Deadlock after receiving calls generated with sipp
> --------------------------------------------------
>
>                 Key: ASTERISK-17119
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17119
>             Project: Asterisk
>          Issue Type: Bug
>          Components: General
>            Reporter: Claudio Villalobos
>            Severity: Minor
>         Attachments: backtrace-threads.txt, core_show_locks.txt, core-show-locks.txt, core_show_threads.txt, gdb_thread_apply_all_bt.txt
>
>
> I was testing asterisk with sipp and I got deadlocks everytime after about 2-3 minutes. 
> ./sipp -d 5000 -i 192.168.100.6 -l 10 -s 1337 -sf uac.xml sip.acme.net -r 5 -rp 1000 --trace_err

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list