[Home]

Summary:ASTERISK-27455: PJSIP AOR Path header
Reporter:Slava Bendersky (volga629)Labels:
Date Opened:2017-12-02 18:47:42.000-0600Date Closed:2017-12-02 19:13:34.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:14.6.0 Frequency of
Occurrence
Related
Issues:
Environment:fedora server x86_64 asterisk-14.6.0-2.git9d8f7bf9b5.fc25.x86_64Attachments:( 0) Asterisk_Path_trace.txt
Description: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
Comments:By: Asterisk Team (asteriskteam) 2017-12-02 18:47:43.397-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Slava Bendersky (volga629) 2017-12-02 18:52:16.224-0600

Configuration part



AOR settings in mysql
MariaDB [asterisk]> select * from ps_aors\G
1. row
                 id: 47520-10
            contact: NULL
 default_expiration: NULL
          mailboxes: 47520@10
       max_contacts: 99
 minimum_expiration: NULL
    remove_existing: NULL
  qualify_frequency: NULL
authenticate_qualify: NULL
 maximum_expiration: NULL
     outbound_proxy: NULL
       support_path: NULL
    qualify_timeout: NULL
voicemail_extension: NULL
By: Slava Bendersky (volga629) 2017-12-02 18:54:11.998-0600

trace for Path present in header
By: Joshua C. Colp (jcolp) 2017-12-02 19:13:34.345-0600

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
By: Slava Bendersky (volga629) 2017-12-02 19:25:11.765-0600

Hello Joshua,
You refer to Supported line in header

Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri

that should contain path
By: Asterisk Team (asteriskteam) 2017-12-02 19:25:11.947-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.
By: Joshua C. Colp (jcolp) 2017-12-02 19:29:56.540-0600

Yes, that should contain "path" but does not.
By: Slava Bendersky (volga629) 2017-12-02 19:32:36.599-0600

Joshua,
Thank you for clear explanation, right it easy to fix.
By: Asterisk Team (asteriskteam) 2017-12-02 19:32:36.763-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.