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

[Ross Beer (JIRA)]

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

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

    Status: Waiting for Feedback  (was: Triage)

Looking at the Wireshark and phone logs. The phone registered just before a disconnect for 120 seconds. Therefore the server should not have disconnected the TLS connection.

I have sent the full debug logs to you directly.

> 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: 13.15.0, GIT
>         Environment: Fedora 23
> TLS1.2
>            Reporter: Ross Beer
>            Assignee: Ross Beer
>         Attachments: Capture2.PNG, 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 attached 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 contact the endpoint or give up trying when timing out. However, at present, Asterisk closes the active connection making the endpoint go offline.
> The only reason asterisk would attempt to contact and endpoint would be if it is retaining information such as BLF subscriptions after an endpoint disconnects.
> The disconnect does not happen when using TCP, however, Asterisk still attempts connnections to closed ports.



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