[SR-Users] forcing socket doesn't work for ACK

[Sergiu Pojoga]

I suppose you've also defined your `listen=` list?

On Mon, Apr 1, 2019 at 2:25 PM David Villasmil <
david.villasmil.work at gmail.com> wrote:

> Thanks Sergiu,
>
> yep, mhomed=1 is there
>
> But it's still failing to select the right socket
> Regards,
>
> David Villasmil
> email: david.villasmil.work at gmail.com
> phone: +34669448337
>
>
> On Mon, Apr 1, 2019 at 7:19 PM Sergiu Pojoga <pojogas at gmail.com> wrote:
>
>> Have you tried proposed suggestions?
>>
>> On Mon, Apr 1, 2019, 2:12 PM David Villasmil, <
>> david.villasmil.work at gmail.com> wrote:
>>
>>> Hello guys,
>>>
>>>
>>> this is my scenario, as you see, the public-facing ip is using port 5060
>>> while the internal 5066.
>>> All works ok (with force_socket), but when forwarding the ACK, kamailio
>>> uses the wrong ip (5060), when it should be using 5066.
>>>
>>>
>>> U PUBLIC:58031 -> 172.31.69.53:5060
>>> INVITE sip:*TESTCALL at myserver.com;transport=UDP SIP/2.0.
>>>
>>> U 172.31.69.53:5060 -> PUBLIC:58031
>>> SIP/2.0 100 trying -- your call is important to us.
>>>
>>> U 172.31.69.53:5066 -> 172.31.65.238:5080
>>> INVITE sip:*TESTCALL at myserver.com;transport=UDP SIP/2.0.
>>>
>>> U 172.31.65.238:5080 -> 172.31.69.53:5066
>>> SIP/2.0 100 Trying.
>>>
>>> U 172.31.65.238:5080 -> 172.31.69.53:5066
>>> SIP/2.0 200 OK.
>>>
>>> U 172.31.69.53:5060 -> PUBLIC:58031
>>> SIP/2.0 200 OK.
>>>
>>> U PUBLIC:58031 -> 172.31.69.53:5060
>>> ACK sip:*TESTCALL at 172.31.65.238:5080;transport=udp SIP/2.0.
>>> ************BELOW*************
>>>
>>> U 172.31.69.53:5060 -> 172.31.65.238:5080
>>> ACK sip:*TESTCALL at 172.31.65.238:5080;transport=udp SIP/2.0.
>>>
>>>
>>> Regards,
>>>
>>> David Villasmil
>>> email: david.villasmil.work at gmail.com
>>> phone: +34669448337
>>>
>>>
>>> On Mon, Apr 1, 2019 at 7:08 PM Antony Stone <
>>> Antony.Stone at kamailio.open.source.it> wrote:
>>>
>>>> On Monday 01 April 2019 at 17:37:45, David Villasmil wrote:
>>>>
>>>> > Hello guys,
>>>> > I have public and private IPs, and i need to force the sending socket
>>>> > replying to internal out externals endpoint
>>>>
>>>> > This works nicely, except for ACKs and potentially other packets sent
>>>> > statelessly?
>>>> >
>>>> > Anyone knows how to fix this?
>>>>
>>>> Have you tried something like:
>>>>
>>>> ip rule add from int.ernal.ip.addr lookup mytable
>>>> ip route add default dev external_interface_device table mytable
>>>>
>>>> echo "234 mytable" >>/etc/iproute2/rt_tables
>>>>
>>>>
>>>> Antony.
>>>>
>>>> --
>>>> 3 logicians walk into a bar. The bartender asks "Do you all want a
>>>> drink?"
>>>> The first logician says "I don't know."
>>>> The second logician says "I don't know."
>>>> The third logician says "Yes!"
>>>>
>>>>                                                    Please reply to the
>>>> list;
>>>>                                                          please *don't*
>>>> CC me.
>>>>
>>>> _______________________________________________
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users at lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>> _______________________________________________
>>> Kamailio (SER) - Users Mailing List
>>> sr-users at lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190401/e4817d89/attachment.html>