[asterisk-bugs] [JIRA] (ASTERISK-27529) Endpoint with TLS lost inbound registration

[Dmitriy Serov (JIRA)]

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

Dmitriy Serov commented on ASTERISK-27529:
------------------------------------------

Asterisk 15.6.1
Endpoint has single transport (TLS).
I have noticed that contact keeps Reachable in for a while. All the while, asterisk sends an OPTIONS packet from port 5061 to the client port (and receives a response).
After a few hours, asterisk for some reason decides to send packets from another dynamic port.
In this case, the client is no longer responsible (of course). And netstats shows SYN_SENT state of this connection.
The connection from port 5061 is still in use (ESTABLISHED) and accepts and responds to REGISTER packets from the client. 
For this reason, the client considers the connection stable.

Question: why the server sends OPTIONS with port 5061?

> Endpoint with TLS lost inbound registration
> -------------------------------------------
>
>                 Key: ASTERISK-27529
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27529
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 15.2.0
>            Reporter: Dmitriy Serov
>            Severity: Minor
>              Labels: pjsip
>         Attachments: demon.tcpdump.txt, endpoint.txt, pjsip-config-tls-lost.txt, registration_with_lost.txt
>
>
> Regression.15.1.4 -> 15.2.0-rc. 
> Endpoint with TLS lost inbound registration.
> After some time of first register (connect) in asterisk log "is now Unreachable.  RTT: 0.000 msec".
> Homer shows packets REGISTER and answers OK. But no line on Reachable in logs.
> Client thinks is online. And asterisk does not. As a result - lost calls.



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