[asterisk-bugs] [JIRA] (ASTERISK-29999) pjsip: Get information from 200 OK INVITE reply headers

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Thu Mar 31 06:37:29 CDT 2022


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

Joshua C. Colp updated ASTERISK-29999:
--------------------------------------

    Assignee: José Lopes
      Status: Waiting for Feedback  (was: Triage)

Contributions require the signing of a license agreement which is done by clicking "Sign a License Agreement" at the top of the page and filling out the form. These are manually reviewed and once done you will be able to upload a patch. To have it be included in Asterisk the fastest option is to also put it up for code review after this, by following the instructions on the linked wiki page provided in the automatic comment on the issue.

> pjsip: Get information from 200 OK INVITE reply headers
> -------------------------------------------------------
>
>                 Key: ASTERISK-29999
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29999
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 18.8.0
>            Reporter: José Lopes
>            Assignee: José Lopes
>              Labels: patch
>         Attachments: nfon_res_pjsip_reply_header_funcs.patch
>
>
> There are some scenarios where we need to get information from 200 OK INVITE reply, like User-Agent and other X-*/P-* headers that can be provided.
> When we execute the Dial on dialplan, we want to get the reply header information from the pre-connect sub (U option on Dial).
> I created a patch with PJSIP_REPLY_HEADER function, based on PJSIP_HEADER function code, to allow to read the reply headers.
> This is working for me right now. I will be happy to improve this code if you provide me with some guidance.



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



More information about the asterisk-bugs mailing list