[OpenSIPS-Users] strange behavior with TCP reply port

[Jeff Pyle]

Hi Liviu,

You're probably right.  And, force_rport() appears to solve the problem.
I'm calling it first thing in the script so all the replies go to the right
place.  Basic testing seems okay, even on UDP connections into proxy where
everything is 5060.

Do you have any thoughts what this might break?


- Jeff


On Mon, Aug 16, 2021 at 4:06 PM Liviu Chircu <liviu at opensips.org> wrote:

> On 11.08.2021 22:01, Jeff Pyle wrote:
>
> the sl_send_reply() function opens a new TCP socket to the UAC on the
> IP:port listed in the original message's Contact, rather than sending the
> 100 on the existing socket (using the ephemeral port)
>
> Hi, Jeff!
>
> Just to frame the problem better: are you sure the reply's target IP:port
> is equal to the request's Contact header and not the topmost Via header?
> Maybe a *force_rport()* before calling *sl_send_reply()* is everything
> that's needed here.  *fingers crossed*
>
> Best,
>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210819/72e08467/attachment.html>