Hello David,

 

if you are using Debian or similar on system or in docker container, you could just install the debug packages. There is no need to recompile the source code for it.

 

Cheers,

 

Henning

 

From: David Villasmil via sr-users <sr-users@lists.kamailio.org>
Sent: Donnerstag, 3. Oktober 2024 17:46
To: Ben Kaufman <bkaufman@bcmone.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>; David Villasmil <david.villasmil.work@gmail.com>
Subject: [SR-Users] Re: kamailio sending from udp non-listening port

 

hello and thanks for contributing to this!

 

for the time being i moved kamailio to a self-hosted VM, but it persisted. Like you i'm using host networking...

i don't really know how else to debug this without actually compiling and running a debug version... i had hoped someone would have gone through this and found a fix.

 


Regards,

 

David Villasmil

 

 

 

On Thu, Oct 3, 2024 at 5:39 PM Ben Kaufman <bkaufman@bcmone.com> wrote:

The capture was done on the EC2 host itself.  This is not observed only as when the packet arrives at the remote host.

 

regards,

Kaufman

 

From: Michal Popovič <michal.popovic@cloudtalk.io>
Sent: Thursday, October 3, 2024 9:06 AM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Cc: David Villasmil <david.villasmil.work@gmail.com>; Ben Kaufman <bkaufman@bcmone.com>
Subject: Re: [SR-Users] kamailio sending from udp non-listening port

 

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Check if you are not using NAT gateway IP address for outgoing packets.

 

On 3 Oct 2024, at 15:39, Ben Kaufman via sr-users <sr-users@lists.kamailio.org> wrote:

 

Following up here. On the host where I had the problem I changed from using docker's bridged network to using host mode networking, and the problem persisted, then matching your description.  I rebooted the host.  My only guess is that there was some type of state being inaccurately tracked by the host firewall as the underlying issue, because it happened with only one target, and the translated port was persistent across Kamailio restarts.  Did you find out anything more about your problem?

 

Regards,

Kaufman

 

 

From: David Villasmil <david.villasmil.work@gmail.com>
Sent: Tuesday, September 10, 2024 9:26 AM
To: Ben Kaufman <bkaufman@bcmone.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] kamailio sending from udp non-listening port

 

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hello ben,

 

Yes it’s running on kubernetes, but I’m using host networking, so it shouldn’t do that.. I don’t think it’s on Kamailio’s side, but maybe someone has gone through this and can help us!

Regards,

 

David Villasmil

email: david.villasmil.work@gmail.com

 

 

 

On Tue, 10 Sep 2024 at 15:30, Ben Kaufman <bkaufman@bcmone.com> wrote:

I have a similar issue, but my case is even more simple in that I have only a single UDP socket.  Are you running Kamailio in docker?  In my case, I was able to observe that Kamailio was using the correct socket address and port, but docker's outbound NAT, was changing not only the source address of the packet, but also the source port as well.  Host is running Amazon Linux 2023, docker from their packages.

 

Kaufman
Senior Voice Engineer



E: bkaufman@bcmone.com

 

SIP.US Client Support: 800.566.9810  |  SIPTRUNK Client Support: 800.250.6510  |  Flowroute Client Support: 855.356.9768

img

img

img

 

 

From: David Villasmil via sr-users <sr-users@lists.kamailio.org>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Cc: David Villasmil <david.villasmil.work@gmail.com>
Subject: [SR-Users] kamailio sending from udp non-listening port

 

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hello guys,

 

i'm seeing something weird, and i'm working if you can let me know.

I have a kamailio in AWS with a private IP listening on several sockets:

 

Listening on
             udp: 10.1.2.36:5070
             udp: 10.1.2.36:5080
             udp: 10.1.2.36:5160 advertise 4.3.2.1:5160
             udp: 0.0.0.0:5066
             tls: 10.1.2.36:443 advertise sip.something.com:443
             tls: 10.1.2.36:444 advertise sip.something.com:444

             tls: 10.1.2.36:5061 

 

When forwarding a udp invite received on 10.1.2.36:5080 to a public ip provider say on 8.8.8.8:5060, i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160. But the outgoing invite does NOT use 5160, it uses some random port...

 

Anybody knows why this might be?

 

my problem is, that call goes to freeswitch... call is setup properly and connects fine. But 15 minutes later the end provider sends back a reINVITE, which freeswitch then sends TO THE RANDOM PORT kamailio used to send the INVITE... but by this time kamailio doesn't seem to even see the packet...

 

help is greatly appreciated!

 

David

 

Regards,

 

David Villasmil

email: david.villasmil.work@gmail.com

 

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: