Bogdan its only happening when the clients SIP ALG fixes the contact,
when the contact is broken I'm already using fix_nated_contact, do you
think I should use fix_nated_contact even when the contact was already
fixed by the SIP ALG?
The clients router does not support disabling SIP ALG, I can try using
a non standard port, I've sen some routers ALG ignoring the packets
when sent to alternative port.
I feel like its a bug in OpenSIPS, because the reinvite is routed to
the proper port, the issue starts with the ACK for the reinvite, I
will email the trace directly to you.
On Tue, Feb 13, 2018 at 12:04 PM, Bogdan-Andrei Iancu
> Hi Schneur,
> The ACK is routed back via the Route set (the Record Route headers from the
> initial Invite) and the Contact received in the final reply (in the 200 OK
> in your case). This is called in-dialog routing and is exclusively based on
> Route set (RR headers + Contact).
> The rport as part of via is used only for routing back the replies for a
> requests (in transaction routing) and has no impact on the in-dialog
> So, if the RURI in ACK (which should be the Contact in the received 200 OK)
> is broken, maybe you should do a fix_nated_contact() for the Contact when
> handling the 200 OK reply.
> Best regards,
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> OpenSIPS Summit 2018
> On 02/12/2018 05:05 PM, Schneur Rosenberg wrote:
>> I have this interesting scenario, caller sends call to our OpenSIPS
>> who actsd as a loadbalancer which sends the call to a gateway for
>> termination and the gateway sets Session-Expires: 1800;refresher=uas,
>> the caller sends call the call through port 1090 and the rport in the
>> Via shows rport=1090 and so far everything is ok, but after 15 minutes
>> the gateway sends a reinvite, OpenSIPS sends it to the client and the
>> client sends a OK and OpenSIPS properly sends the OK to the gateway,
>> the gateway sends a ACK to OpenSIPS, but here the problem starts
>> OpenSIPS sends the ACK to the port in the Contact header which is not
>> the same port as the rport, the clients router does not recognize the
>> packet and blocks it, the client sends multiple OK's to OpenSIPS who
>> ignores it because he has already moved on, as far as OpenSIPS is
>> concerned the ACK has already been sent to the next hop, and after
>> approx 30 seconds the client does not receive the ACK and sends a BYE
>> and the call terminates.
>> Why is OpenSIPS changing the port to the Contact port? and what can I
>> do to fix it?<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
>> <table style="border-top: 1px solid #D3D4DE;">
>> <td style="width: 55px; padding-top: 13px;"><a
>> alt="" width="46" height="29" style="width: 46px; height: 29px;"
>> <td style="width: 470px; padding-top: 12px; color:
>> font-size: 13px; font-family: Arial, Helvetica, sans-serif;
>> line-height: 18px;">Virus-free. <a
>> target="_blank" style="color: #4453ea;">www.avg.com</a>
>> </table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
>> Users mailing list
Users mailing list