[asterisk-bugs] [JIRA] (ASTERISK-27554) res_pjsip_rfc3326: Order of 'Reason' headers break many endpoints

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-27554:
------------------------------------------------

Change 8460 merged by Jenkins2:
res_pjsip_rfc3326: Order of 'Reason' headers break many endpoints

[https://gerrit.asterisk.org/8460|https://gerrit.asterisk.org/8460]

> res_pjsip_rfc3326: Order of 'Reason' headers break many endpoints
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-27554
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27554
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Resources/res_pjsip_rfc3326
>    Affects Versions: 13.18.5, 15.1.5
>         Environment: Fedora 23, Snom, Yealink, Grandstream
>            Reporter: Ross Beer
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: patch, pjsip
>         Attachments: ASTERISK-27554.diff
>
>
> The additional header added by chan_pjsip CANCEL causes many hardware endpoints to record missed calls. While this isn't directly an Asterisk issue and doesn't break RFCs, it is a change away from chan_sip.
> I believe that endpoints are only checking the fist Reason header for the string 'Call completed elsewhere' and therefore not matching this.
> The reason headers currently sent by chan_pjsip are as follows:
> {noformat}
> Reason: Q.850;cause=26
> Reason: SIP;cause=200;text="Call completed elsewhere"
> {noformat}
> I believe that changing the order of the headers to the following will resolve the issue with many manufacturers:
> {noformat}
> Reason: SIP;cause=200;text="Call completed elsewhere"
> Reason: Q.850;cause=26
> {noformat}
> While ideally getting each manufacturer to fix their firmware to check multiple headers would be ideal, some devices are no longer actively supported and therefore will never be updated.



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