[Home]

Summary:ASTERISK-30453: On external transfer Contact header rewriten with external_signaling_address
Reporter:Rafal Ramocki (rafal.ramocki)Labels:
Date Opened:2023-03-06 06:11:20.000-0600Date Closed:2023-03-06 06:14:16.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:18.16.0 Frequency of
Occurrence
Related
Issues:
duplicatesASTERISK-30451 res_pjsip: Contact header set incorrectly for call redirect (302 Moved temp.) when external_* set
Environment:Oracle Linux 8Attachments:
Description:When PJSIP option external_signaling_address is set because node is behind NAT when Transfer() application is executed to redirect call incomming on SIP Trunk back to the same trunk Contact: header of 302 responce is rewriten with external_signaling_address.  Transfer() is executed in following way:

Transfer(PJSIP/sip:XXXXXXXXX@sip.example.com);

And this results in following responce:

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 87.204.129.4:5060;rport=5060;received=87.204.129.4;branch=z9hG4bK5fpi6q209g1s0s873tq0.1
Call-ID: SD6bg3a01-d831b6e708921fa733c1a098525082f7-ag3jn70
From: <sip:XXXXXXXXX@xxx.com;user=phone>;tag=SD6bg3a01-1699263443-1678104169287-
To: "xxxxxxxxx xxxxxxxxx" <sip:xxxxxxxxx@xxx.com.pl;line=xzlstoa>;tag=542f525d-dda1-446a-9641-3675c9e0a70e
CSeq: 459720100 INVITE
Server: Asterisk PBX 18.16.0
Contact: <sip:XXXXXXXXX@1.2.3.4>
Reason: Q.850;cause=0
Supported: histinfo
Content-Length:  0

Where 1.2.3.4 from Contact: header is the same as external_signaling_address. When external_signaling_address is not set in pjsip.conf, 1.2.3.4 is the domain that the same as one in parameter of Transfer applicaation.

In my opinion expected behaviour is to not rewrite Contact: headers with external_signaling_address at transfer.
Comments:By: Asterisk Team (asteriskteam) 2023-03-06 06:11:24.013-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/].