I always set the advertised address in request route.

Also as the original issue noted the second INVITE does go out with the correct 
advertised address in the VIA. It is only the local ACK for the failed second 
request that contains the wrong address in the VIA. So set_advertised_address 
appears to be working, but the local generated ACK is not using that address.


Ben Newlin

From: Bogdan-Andrei Iancu <bog...@opensips.org>
Date: Monday, June 27, 2016 at 5:37 AM
To: "users@lists.opensips.org" <users@lists.opensips.org>, "Newlin, Ben" 
<ben.new...@inin.com>
Subject: Re: [OpenSIPS-Users] ACK after set_advertised_address contains wrong 
address in VIA header

Hi Ben,

Where in the script do you do the first advertise_address ? In the request 
route or in a branch route ?

Regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 25.06.2016 03:41, Newlin, Ben wrote:
I have run into the same problem that was described in this previous post [1], 
however it doesn’t appear it was ever solved at the time.

I am using the dispatcher module to route calls to external carriers and I am 
using set_advertised_address to set the outgoing public address prior to 
sending the request. If the first destination returns failure, the ACK is sent 
correctly. Then I select a different destination and set a different public 
address using set_advertised_address. If this second call also fails, the ACK 
that is sent out uses the first advertised address, not the current on for the 
request.

Has anyone figured this out? I am using 1.11.6.

[1] http://lists.opensips.org/pipermail/users/2014-August/029779.html


Ben Newlin




_______________________________________________

Users mailing list

Users@lists.opensips.org<mailto:Users@lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to