[asterisk-bugs] [JIRA] (ASTERISK-27474) PJSIP TLS Unstable

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Dec 11 07:45:08 CST 2017


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

Asterisk Team commented on ASTERISK-27474:
------------------------------------------

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].

> PJSIP TLS Unstable
> ------------------
>
>                 Key: ASTERISK-27474
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27474
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.18.2, GIT
>         Environment: Fedora 23
>            Reporter: Ross Beer
>
> When an endpoint is using chan_pjsip TLS  and there are a number of TLS connections, Asterisk starts to close connections incorrectly.
> This is fairly severe, to the point that any phone doesn't stay registered for more than a few seconds at a time.
> On performing a Wireshark, it is clear to see that Asterisk is sending FIN packets which in turn close the active TLS connection.
> I believe this is related to a previous ticket which was resolved by a patch being included with the bundled version 2.6 of PJSIP. 
> Other connection-oriented protocols such as TCP are not affected by this issue.



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



More information about the asterisk-bugs mailing list