[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=245143#comment-245143 ] 

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

Unfortunately, the server has thousands of registrations and it is not easy to collect logs. But it is possible.

Collecting the logs, I found the following sequence of events:
1. client establishes TCP connection
2. the client sends a REGISTER (authorized). Contact becomes Available
3. the server, using the Contact parameters, sends OPTIONS to check the connection on the desired destination port
4 at some point, the client does not respond in time to OPTIONS (in my case, the delay was 7 seconds). Not an important reason (I will understand from the author of PhonerLite)
5. server marks Contact as Unavailable. The connection between the client and the server is NOT LOST. The client does not know about the problems.
6. The client then sends the REGISTER packets and receives responses over the existing connection. The server, seeing that Contact is unavailable, tries to establish a new connection from another server port and does not reach the client.

> 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
>            Assignee: Dmitriy Serov
>            Severity: Minor
>              Labels: pjsip
>         Attachments: debug9-1.txt, 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)