[asterisk-bugs] [JIRA] (ASTERISK-28075) Null pointer in SRTP Handling Crash

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28075:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Null pointer in SRTP Handling Crash
> -----------------------------------
>
>                 Key: ASTERISK-28075
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28075
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_srtp
>    Affects Versions: 15.2.2
>            Reporter: Joshua Elson
>         Attachments: core.dfw-2018-09-25T11-52-31-0600-brief.txt, core.dfw-2018-09-25T11-52-31-0600-full.txt, core.dfw-2018-09-25T11-52-31-0600-locks.txt, core.dfw-2018-09-25T11-52-31-0600-thread1.txt
>
>
> We've begun seeing this null pointer crash in SRTP handler multiple times per day in a handful of our clusters.
> Still looking to isolate a scenario that's causing it, but maybe there's an easy workaround or someone else has seen this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)