[asterisk-bugs] [JIRA] (ASTERISK-28924) Imposible to add or read sip headers from a 302 Redirect

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Sat May 30 14:02:25 CDT 2020


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

Joshua C. Colp commented on ASTERISK-28924:
-------------------------------------------

Features requests without patches are not accepted through the issue tracker. Features requests are openly discussed on the mailing lists, forums, and IRC [1]. Please see the Asterisk Issue Guidelines [2] for more information on feature request and patch submission.

[1] http://asterisk.org/community/discuss
[2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

Additionally this is not possible in either chan_pjsip or chan_sip currently.

> Imposible to add or read sip headers from a 302 Redirect
> --------------------------------------------------------
>
>                 Key: ASTERISK-28924
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28924
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.33.0, 16.10.0
>         Environment: Linux
>            Reporter: Private Name
>
> I received this response from a provider I cannot extract the header X-Identity it with PJSIP nor I can add the same with 
> PJSIP_HEADER(add,X-Identity)=${X})
> where X= any string at all.
> Is this even possible or is a new feature?
> SIP/2.0 302 Moved Temporarily
> Via: SIP/2.0/UDP 172.16.7.254:52169;rport=52169;received=47.205.172.89;branch=z9hG4bK-524287-1---129f4244aaba9f04
> Call-ID: 102650Mzg4NmFiNTQzOGY5NDJmNjM3OTYzNmE5MzNlZDIwZmI
> From: "XXXXX" <sip:XXX4433019 at XXX.124.224.87>;tag=81a25c36
> To: <sip:16317918378 at XXX.124.224.87>;tag=9e198dc4-7ce8-433d-ae23-05b9bc14d55a
> X-Identity:eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwicHB0Ijoic2hha2VuIiwieDV1IjoiaHR0cHM6Ly9jZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyI2MzE3OTE4Mzc4Il19LCJpYXQiOjE1OTA4MTEyMzgsIm9yaWciOnsidG4iOiI3Mjc0NDMzMDE5In0sIm9yaWdpZCI6IjEyM2U0NTY3LWU4OWItMTJkMy1hNDU2LTQyNjY1NTQ0MDAwMCJ9.AKViDWA3uonP6tt5cKBh0FUPY5zBuJnwZLQNTrp9LCWJ-vLY1Xx5i3_oXGh1ERL4tnD-KK5wsP3FdByDa_cjGw;info=<https://cert.example.org/passport.cer>;alg=ES256;ppt=shaken
> CSeq: 1 INVITE
> Server: Asterisk PBX 16.10.0
> Contact: <sip:16317918378>
> Reason: Q.850;cause=0
> Content-Length:  0



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



More information about the asterisk-bugs mailing list