[asterisk-bugs] [JIRA] (ASTERISK-24486) PJSIP contact rewriting fails to account for TCP timeout

[Matt Jordan (JIRA)]

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

Matt Jordan closed ASTERISK-24486.
----------------------------------

    Resolution: Won't Fix

With the keep alive messages put into the PJSIP stack, this issue essentially no longer happens. Given the complexity of trying to figure out who a request should be sent to when a TCP connection breaks and a UDP transport is chosen, this issue is no longer really worth trying to "fix" (particularly when a different method already "fixed" it by preventing the TCP connection from breaking in the first place).

> PJSIP contact rewriting fails to account for TCP timeout
> --------------------------------------------------------
>
>                 Key: ASTERISK-24486
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24486
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Resources/res_pjsip_nat
>    Affects Versions: 12.6.1, 13.0.0-beta3
>            Reporter: Kinsey Moore
>            Assignee: Kinsey Moore
>
> This issue affects endpoints where contact rewriting is enabled and the transport being used is reliable (TCP or TLS).
> If these conditions are met, the call will operate properly until the underlying transport hits an inactivity timeout around 30 seconds at which point the reliable transport will be torn down. Once this happens, Asterisk is unable to send communications to the remote endpoint to tear down the call which can leave the call dangling on the remote server for an unspecified period of time.



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