Hi Alex,
I had the same problem as you and I couldn't find a way to selectively
reply to via.
What I ended up doing is the following dirty trick...
Before a transaction is created for the processed message I do:
if (SOME CONDITION) {
remove_hf_value("Via[-1].rport");
msg_apply_chan
On 09/22/2016 10:55 AM, Daniel Tryba wrote:
force_rport seems to override any rport available in via, so reply_to_via
has no additional effects.
Thanks, that was helpful. But so, if force_rport() is not used, do I
need reply_to_via=1 in order to have replies go back to the declared
port in t
On Thu, Sep 22, 2016 at 09:58:33AM -0400, Alex Balashov wrote:
> Normally, we just force_rport() on all incoming requests so that we reply to
> the real source port of the request, since most endpoints on this
> installation are NAT'd.
>
> However, occasionally we run into a scenario where an ALG
