[Home]

Summary:ASTERISK-30047: Local IP address in SDP when external_media_address is used
Reporter:Niksa Baldun (niksa)Labels:
Date Opened:2022-05-06 01:34:48Date Closed:2022-05-20 12:00:02
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:18.11.2 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Debian 11.3 containerAttachments:
Description:I have a system with 3 network adapters, with following IPs:

192.168.43.2/24
10.55.66.30/30
10.42.42.2/24

Default GW is 10.42.42.1.

If I use the following PJSIP transport definition:

[transport-udp]
type=transport
protocol=udp
bind=0.0.0.0:5060
local_net=192.168.43.0/24
local_net=10.42.42.0/24
external_media_address=x.x.x.x
external_signaling_address=x.x.x.x

external IP is put in contact header, but SDP always contains the local address 10.42.42.2. So audio obviously does not work. The trunk registers to a public Internet address.

It works as expected if I split transports like so:

[transport-udp]
type=transport
protocol=udp
bind=192.168.43.2:5060

[transport-udp-1]
type=transport
protocol=udp
bind=10.55.66.30:5060

[transport-udp-external]
type=transport
protocol=udp
bind=10.42.42.2:5060
external_media_address=x.x.x.x
external_signaling_address=x.x.x.x
Comments:By: Asterisk Team (asteriskteam) 2022-05-06 01:34:49.635-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: Joshua C. Colp (jcolp) 2022-05-06 04:11:00.031-0500

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Asterisk Team (asteriskteam) 2022-05-20 12:00:01.787-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

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