The capture was done on the EC2 host itself. This is not observed only as when the packet arrives at the remote host.
Check if you are not using NAT gateway IP address for outgoing packets.
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
|
|
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
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.
|
|
SIP.US Client
Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 | Flowroute Client Support: 855.356.9768
|
|
|
|
|
|
|
|
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:
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
__________________________________________________________
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:
