[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:all-tabpanel ]

Dmitriy Serov updated ASTERISK-27529:
-------------------------------------

    Attachment: TLS-Qualify-ServerPort-Bug.zip

I was hoping to work around the issue by disabling Qualify. But the problem remained. After some time, the INVITE packet was sent by the server not from port 5061, but from another (dynamic) port. The situation was repeated, but with the packet INVITE.

In the archive TLS-Qualify-ServerPort-Bug.zip two log files:
1. cutted.txt - abbreviated file with rows that relate to the endpoint 10228. 
You can see that 23:32:10 qualify was from port 5061 and was successful.
23:35:10 server src port somehow changed from 5061 to 33217. Port 33217 previously in the logs was not mentioned even once.
Something happened between the two.

2. full.txt - full log (debug level 9) between this two moments. 35 MB :(

"pjsip show contact" is useless. The client port does not change, and only the client port is displayed everywhere. The contact status changes to Unavailable after a timeout.

> 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, TLS-Qualify-ServerPort-Bug.zip
>
>
> 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)