[asterisk-bugs] [JIRA] (ASTERISK-26984) chan_pjsip TLS incorrectly tears down connection

Ross Beer (JIRA) noreply at issues.asterisk.org
Fri May 5 06:17:57 CDT 2017


     [ https://issues.asterisk.org/jira/browse/ASTERISK-26984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ross Beer updated ASTERISK-26984:
---------------------------------

    Description: 
chan_pjsip attempts to create sessions to closed TLS connections on incorrect ports. This leads to the eventual teardown of the connected session by Asterisk.

The attaced image shows successful communication on port 35430 and then attempted SYN packets to other ports such as 37848, 57750 etc. These packets will never reach the endpoint as these have already been closed. This can be seen in the 'TCP Retransmission' entries.

Asterisk should either attempt to use the open connection to conact the endpoing or give up trying when timing out. However, at present, Asterisk closes the active connection making the endpoint go offline.

  was:
chan_pjsip attempts to create sessions to closed TLS connections on incorrect ports. This leads to the eventual teardown of the connected session by Asterisk.




> chan_pjsip TLS incorrectly tears down connection
> ------------------------------------------------
>
>                 Key: ASTERISK-26984
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26984
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: GIT
>         Environment: Fedora 23
>            Reporter: Ross Beer
>         Attachments: Capture.PNG
>
>
> chan_pjsip attempts to create sessions to closed TLS connections on incorrect ports. This leads to the eventual teardown of the connected session by Asterisk.
> The attaced image shows successful communication on port 35430 and then attempted SYN packets to other ports such as 37848, 57750 etc. These packets will never reach the endpoint as these have already been closed. This can be seen in the 'TCP Retransmission' entries.
> Asterisk should either attempt to use the open connection to conact the endpoing or give up trying when timing out. However, at present, Asterisk closes the active connection making the endpoint go offline.



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



More information about the asterisk-bugs mailing list