[asterisk-bugs] [JIRA] (ASTERISK-29176) Private REDIRECTING party ID data not used in PJSIP headers

[Kris Shaw (JIRA)]

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

Kris Shaw commented on ASTERISK-29176:
--------------------------------------

That might suggest there's another related bug then. If the {{trust_id_outbound}} parameter is going to be honoured then presumably the presentation values need to be checked too. If they are set to {{prohib}} or {{unavailable}} then the related REDIRECTING values shouldn't be in the header anyway (unless {{trust_id_outbound}} is set)? I've interpreted Private REDIRECTING values to just mean they relate only to that particular channel/caller, instead of meaning some presentation value. That appears to be the case with other channel drivers and when used for CONNECTEDLINE.

> Private REDIRECTING party ID data not used in PJSIP headers
> -----------------------------------------------------------
>
>                 Key: ASTERISK-29176
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29176
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 16.15.0
>            Reporter: Kris Shaw
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: diversion-sip-trace.txt
>
>
> Unlike in chan_sip (and sig_pri), chan_pjsip does not take into account the priv* representations of the orig/from/to redirecting party IDs. When constructing the diversion and history headers via res_pjsip_diversion, the priv* values aren't merged with the standard party IDs to get the effective party IDs.
> Therefore, these headers may not be set as you might expect them to be from the documentation.



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