[Home]

Summary:ASTERISK-28309: res_pjsip: Wrong Contact and Via fields with multiple UDP interfaces
Reporter:Nikolay shakin (post@itprofit32.ru)Labels:pjsip
Date Opened:2019-02-26 13:09:07.000-0600Date Closed:2019-03-01 08:03:52.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:16.2.0 Frequency of
Occurrence
Related
Issues:
Environment:centos 7Attachments:( 0) cli.txt
( 1) cli.txt
( 2) debug_log_pjsip.txt
( 3) debug_log_pjsip.txt
( 4) network.txt
( 5) network.txt
( 6) pjsip.aor.conf
( 7) pjsip.endpoint.conf
( 8) pjsip.transports_custom_post.conf
( 9) Screenshot_41.png
(10) Screenshot_41.png
Description:There are two intertaces and two transports.
{quote}
Transport:  udp                       udp      3     96  10.32.0.109:5060
Transport:  udp2                      udp      3     96  10.55.55.10:5060
{quote}
There is endpoint 222 (on transport 10.32.0.109:5060)
But OPTIONS op INVITEs messages to the endpoint contain IP-address from another transtort

Comments:By: Asterisk Team (asteriskteam) 2019-02-26 13:09:08.740-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.

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.
By: Joshua C. Colp (jcolp) 2019-02-26 13:18:08.451-0600

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

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

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


By: Joshua C. Colp (jcolp) 2019-02-26 13:18:29.710-0600

We will also need information about the network setup, such as routing tables, bound interfaces, etc.
By: Joshua C. Colp (jcolp) 2019-02-26 13:31:35.737-0600

I can't view the attachments as I believe you have marked them as contributions, which are not viewable without a license agreement. Please don't mark them as contributions.
By: Nikolay shakin (post@itprofit32.ru) 2019-02-26 13:36:46.943-0600

Sorry for my misstake, now it's ok?
By: Joshua C. Colp (jcolp) 2019-02-26 13:38:59.651-0600

I see them, yes, but you didn't provide the full transport configuration information and ideally things should be as a .conf as it makes it easier/quicker to investigate.
By: Joshua C. Colp (jcolp) 2019-02-28 06:09:47.016-0600

I've isolated this to the following change:

https://gerrit.asterisk.org/c/asterisk/+/6953

I'm reaching out to [~seanbright] to confirm why I think it was done.
By: Joshua C. Colp (jcolp) 2019-02-28 06:56:51.345-0600

As I thought I remembered, it was done to improve performance a bit for the scenario but unfortunately broke this. We're going to revert it so in the next releases it should be resolved.
By: Nikolay shakin (post@itprofit32.ru) 2019-02-28 10:11:15.933-0600

Looking forward to next release, thank you
By: Sean Bright (seanbright) 2019-02-28 10:15:15.585-0600

[~post@itprofit32.ru], it's a one line patch so you should be able to test it easily if you are building from source. In {{res/res_pjsip/pjsip_message_filter.c}}, look for (should be around line 239):

{code}
prm.local_if = is_bound_any(tdata->tp_info.transport);
{code}

And change it to:

{code}
prm.local_if = PJ_TRUE;
{code}

Then do a {{make && sudo make install}} and you should be in business.
By: Nikolay shakin (post@itprofit32.ru) 2019-02-28 10:46:38.098-0600

I'll try it right now
By: Friendly Automation (friendly-automation) 2019-03-01 08:03:52.764-0600

Change 11064 merged by Friendly Automation:
Revert "pjsip_message_filter: Only do interface lookup for wildcard addresses."

[https://gerrit.asterisk.org/c/asterisk/+/11064|https://gerrit.asterisk.org/c/asterisk/+/11064]
By: Friendly Automation (friendly-automation) 2019-03-01 08:03:57.771-0600

Change 11066 merged by Joshua Colp:
Revert "pjsip_message_filter: Only do interface lookup for wildcard addresses."

[https://gerrit.asterisk.org/c/asterisk/+/11066|https://gerrit.asterisk.org/c/asterisk/+/11066]
By: Friendly Automation (friendly-automation) 2019-03-01 08:05:04.251-0600

Change 11065 merged by Joshua Colp:
Revert "pjsip_message_filter: Only do interface lookup for wildcard addresses."

[https://gerrit.asterisk.org/c/asterisk/+/11065|https://gerrit.asterisk.org/c/asterisk/+/11065]