[asterisk-bugs] [JIRA] (ASTERISK-25196) res_pjsip_nat: rewrite_contact should not be applied to Contact header when Record-Route headers are present

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-25196:
-----------------------------------

    Target Release Version/s: 13.5.0

> res_pjsip_nat: rewrite_contact should not be applied to Contact header when Record-Route headers are present
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25196
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25196
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_nat
>    Affects Versions: SVN, 13.4.0
>            Reporter: Mark Michelson
>      Target Release: 13.5.0
>
>
> (This issue is mainly a placeholder for https://gerrit.asterisk.org/#/c/711)
> The issue was discovered at Digium when performing provider testing. The observed issue was that Asterisk sent an INVITE to sip:foo. The 200 OK that Asterisk received had a Contact header of sip:bar, and Record-Route headers of sip:baz and sip:foo in that order.
> The result was that Asterisk rewrote the Contact header from sip:bar to sip:foo. The resulting ACK that Asterisk sent had R-URI of sip:foo, and Route headers sip:foo and sip:baz in that order. The problem is that the ACK never reached sip:bar since that was completely removed from the route set.



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