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

[Kinsey Moore (JIRA)]

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

Kinsey Moore commented on ASTERISK-24486:
-----------------------------------------

Also of note is that this can only happen when the initiating connection is inbound.

A partial mitigation is to "undo" the effects of contact rewriting once the underlying transport has been torn down so that Asterisk may attempt to communicate with the remote server using the original contact information.

In the case where this was experienced, the original contact information was valid and accessible. This will not be true in all cases, but represents an improvement in functionality for a subset of cases.

> 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
>
> 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)