[Home]

Summary:ASTERISK-29918: res_pjsip_refer: Can not get custom headers from REFER
Reporter:Kozlov Aleksey (a.kozlov)Labels:
Date Opened:2022-02-13 11:24:33.000-0600Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:Channels/chan_pjsip Resources/res_pjsip
Versions:16.6.2 Frequency of
Occurrence
Constant
Related
Issues:
is related toASTERISK-27309 Feature Parity with chan_sip
Environment:Debian10, CenoOS7, Asterisk 16.6.2 (and up)Attachments:
Description:During the migration to PJSIP - there was a need to get custom headers from REFER.... In search of a solution, we looked at all the tickets related to this in Jira and fully studied wiki.asterisk.org. But what we found does not work for PJSIP.

What I'm trying to do:
1. From the external system comes the REFER
2. Asterisk receives it and transfers the call to the context specified in TRANSFER_CONTEXT
3. In this context, you need to get the headers. Have you tried to do it like here ASTERISK-27162 and https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Function_SIP_HEADER, but nothing works.

Because of this, we cannot abandon chan_sip.
Comments:By: Asterisk Team (asteriskteam) 2022-02-13 11:24:34.289-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

By: Joshua C. Colp (jcolp) 2022-02-13 12:52:10.555-0600

How was this done in your usage of chan_sip? Using the functionality added in 16 that you've linked?

By: Kozlov Aleksey (a.kozlov) 2022-02-14 02:16:54.836-0600

Yes, I use GET_TRANSFERRER_DATA and HASH KEYS(TRANSFER_DATA). But if you can do it in a more correct or convenient way (for example, through PJSIP_HEADERS), then this is very good.

By: Joshua C. Colp (jcolp) 2022-02-14 04:32:57.139-0600

This issue has now been marked as open. There is no time frame on when it would get looked into.