[asterisk-bugs] [JIRA] (ASTERISK-27455) PJSIP AOR Path header

[Joshua Colp (JIRA)]

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

Joshua Colp closed ASTERISK-27455.
----------------------------------

    Resolution: Not A Bug

This does not appear to be a bug in Asterisk. We are behaving under the recommendation of the RFC[1]:

{noformat}
   If a registrar receives a REGISTER request containing a Path header
   field and there is no indication of support for the extension in the
   UA (via a Supported header field), the registrar must rely on local
   policy in determining how to treat this request.  The recommended
   policy is for the registrar to reject the request with a 420 "Bad
   Extension" response indicating the Path extension.  This approach
   allows the UA to detect that an intermediate proxy has
   inappropriately added a Path header field.  However, the Path
   mechanism should technically work in the absence of UA support (at
   some compromise to security), so some registrars MAY choose to
   support the extension in the absence of a Supported header field
   value in the request.
{noformat}

The REGISTER you've provided does not have "path" as a supported extension but the Path header is present, so we respond with a 420.

[1] https://tools.ietf.org/html/rfc3327

> PJSIP AOR Path header
> ---------------------
>
>                 Key: ASTERISK-27455
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27455
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 14.6.0
>         Environment: fedora server x86_64
> asterisk-14.6.0-2.git9d8f7bf9b5.fc25.x86_64
>            Reporter: Slava Bendersky
>         Attachments: Asterisk_Path_trace.txt
>
>
> Hello Everyone,
> Please check attached trace when I enable suppport_path header in aor asterisk to reject understand it.
> Intention that upstream proxy supply Path header in register that it will use to generate Route header for non sequential request like OPTIONS NOTIFY



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