No subject
Fri Sep 2 03:59:05 CDT 2011
[2012-11-29 12:59:26] NOTICE[25858]: res_srtp.c:446 ast_srtp_create: srtp_diagnostic_patch: attempting srtp_create at 0x1ea63f0
[2012-11-29 12:59:26] NOTICE[25858]: res_srtp.c:448 ast_srtp_create: srtp_diagnostic_patch: srtp_errstr = unsupported parameter
[2012-11-29 12:59:26] NOTICE[25858]: res_srtp.c:450 ast_srtp_create: srtp_diagnosic_patch: result of srtp_create at 0x1ea63f0 was failure
[2012-11-29 12:59:26] NOTICE[25858]: res_srtp.c:475 ast_srtp_destroy: srtp_diagnostic_patch: attempting srtp_destroy at 0x1ea63f0
Other datas you asked for are in last attached file
> Crash in libsrtp srtp_unprotect_rtcp when SIP channel is bridged with non-optimizing Local channel
> --------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-20499
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20499
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/SRTP
> Affects Versions: 10.8.0
> Environment: RHEL 5.8 on IBM X3650 M4 - 12 core - Xeon E5-2640 @ 2,50 ghz
> Reporter: tootai
> Assignee: tootai
> Severity: Critical
> Attachments: asterisk-20499_20121127.log, asterisk-20499_20121127.pcap, asterisk-20499_20121129_01.txt, asterisk-20499.txt, backtrace.txt, backtrace.txt, backtrace.txt, backtrace.txt, coredump20121001205609.txt, gdb.txt, gdb.txt, gdb.txt, gdb.txt, libsrtp-1.4.4-fix_crash_on_rtcp_decode.patch, srtp_diagnostic_with_sleep.diff, srtp_fixes_it_maybe.diff
>
>
> A call from snom320 in SRTP mode to echo test or to another phone *NOT* using SRTP is OK. Now we installed PhonerLite softphone with TLS/SRTP stuf and test with echo test: everything is OK too.
> Now PhonerLite calls the snom: asterisk coredump after 3~5 seconds and we are NOT able to make anymore SRTP calls after this, they all crash asterisk. We had this issue with 10.7.0 and 10.8.0
> We have logfiel from strace as well as coredump.
--
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