[asterisk-bugs] [JIRA] (ASTERISK-28502) chan_pjsip incorrectly re-writes REGISTER 200 Response Contact

[George Joseph (JIRA)]

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

George Joseph commented on ASTERISK-28502:
------------------------------------------

For reference, here's what we were talking about...
https://tools.ietf.org/html/rfc3261#page-61

??The 200 (OK) response from the registrar contains a list of Contact fields enumerating all current bindings.  The UA compares each contact address to see if it created the contact address, using comparison rules in Section 19.1.4.  If so, it updates the expiration time interval according to the expires parameter or, if absent, the Expires field value.  The UA then issues a REGISTER request for each of its bindings before the expiration interval has elapsed.  It MAY combine several updates into one REGISTER request.??

If we've rewritten the contact and send it back in the response the client may not be able to match it.


> chan_pjsip incorrectly re-writes REGISTER 200 Response Contact
> --------------------------------------------------------------
>
>                 Key: ASTERISK-28502
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28502
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.28.0, GIT
>         Environment: Centos 7
>            Reporter: Ross Beer
>              Labels: pjsip
>
> When rewrite_contact is set on an endpoint Asterisk is rewriting the contact on a 200 response to a REGISTER request.
> This causes some clients to fail registration locally as the contact header does not match that of the original request.



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