[Home]

Summary:ASTERISK-29461: Contact header format for inbound calls. One way audio inbound calls behind NAT.
Reporter:Maxim Grechikhin (magmsk)Labels:
Date Opened:2021-06-02 11:09:37Date Closed:2021-06-02 11:09:37
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:18.3.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Dear community,

I faced a situation of one way audio at inbound calls using PJSIP channel on Asterisk 18.3.0 installation. Previously I had the same situation when I was using SIP (chan_sip & sip.conf) channel and my SIP provider explained that they require Contact header in the following format: <sip:callee_number@external_ip:port> in transmitted portion of SIP headers to them. That time the issue was caused by private IP address used by Asterisk to form contact header and as I remember it has been fixed by "from_domain=" parameter in a trunk description. Here I would like to tell that despite the fact that Asterisk is located behind NAT, the firewall is configured correctly and allows inbound RTP sessions. Since migration to PJSIP channel the contact header looks like <sip: external_ip_addr:5060> and we do not have audio signal from remote parties. Is there a way to modify any settings in order to affect the format of contact header?  Or any other related suggestions much appreciated.
Comments:By: Asterisk Team (asteriskteam) 2021-06-02 11:09:37.618-0500

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: Asterisk Team (asteriskteam) 2021-06-02 11:09:37.820-0500

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

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