10 Sep
2024
10 Sep
'24
1:31 p.m.
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(a)gmail.com
10 Sep
10 Sep
1:50 p.m.
Hello guys,
maybe i need to add that i'm sending the call out from the internal fs
using the outbound_proxy parameter.
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
On Tue, Sep 10, 2024 at 12:31 PM David Villasmil <
david.villasmil.work(a)gmail.com> wrote:
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(a)gmail.com
2:41 p.m.
Hello guys,
also kamilio is running on a container with hostNetwork: true so it should
use the correct port.
The VIA looks ok (advertised ip and port are there)
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
On Tue, Sep 10, 2024 at 12:50 PM David Villasmil <
david.villasmil.work(a)gmail.com> wrote:
Hello guys,
maybe i need to add that i'm sending the call out from the internal fs
using the outbound_proxy parameter.
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
On Tue, Sep 10, 2024 at 12:31 PM David Villasmil <
david.villasmil.work(a)gmail.com> wrote:
> 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(a)gmail.com
>
>
4:30 p.m.
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(a)bcmone.com
SIP.US Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 |
Flowroute Client Support: 855.356.9768
[img]<https://www.sip.us/>
[img]<https://www.siptrunk.com/>
[img]<https://www.flowroute.com/>
________________________________
From: David Villasmil via sr-users <sr-users(a)lists.kamailio.org>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: David Villasmil <david.villasmil.work(a)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<http://10.1.2.36:5070/>
udp: 10.1.2.36:5080<http://10.1.2.36:5080/>
udp: 10.1.2.36:5160<http://10.1.2.36:5160/> advertise
4.3.2.1:5160<http://4.3.2.1:5160/>
udp: 0.0.0.0:5066<http://0.0.0.0:5066/>
tls: 10.1.2.36:443<http://10.1.2.36:443/> advertise
sip.something.com:443<http://sip.something.com:443/>
tls: 10.1.2.36:444<http://10.1.2.36:444/> advertise
sip.something.com:444<http://sip.something.com:444/>
tls: 10.1.2.36:5061<http://10.1.2.36:5061/>
When forwarding a udp invite received on 10.1.2.36:5080<http://10.1.2.36:5080/> to a
public ip provider say on 8.8.8.8:5060<http://8.8.8.8:5060/>, i'm forcing the
outgoing socket with force_socket via 10.1.2.36:5160<http://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<mailto:david.villasmil.work@gmail.com>
5:26 p.m.
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(a)gmail.com
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman <bkaufman(a)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(a)bcmone.com
SIP.US Client Support: 800.566.9810 * |* SIPTRUNK Client Support:
800.250.6510 *|* Flowroute Client Support: 855.356.9768
[image: img] <https://www.sip.us/>
[image: img] <https://www.siptrunk.com/>
*[image: img] <https://www.flowroute.com/>*
------------------------------
*From:* David Villasmil via sr-users <sr-users(a)lists.kamailio.org>
*Sent:* Tuesday, September 10, 2024 5:31 AM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Cc:* David Villasmil <david.villasmil.work(a)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(a)gmail.com
3 Oct
3 Oct
4:39 p.m.
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(a)gmail.com>
Sent: Tuesday, September 10, 2024 9:26 AM
To: Ben Kaufman <bkaufman(a)bcmone.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)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<mailto:david.villasmil.work@gmail.com>
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman
<bkaufman@bcmone.com<mailto: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<mailto:bkaufman@bcmone.com>
SIP.US<http://sip.us/> Client Support: 800.566.9810 | SIPTRUNK Client Support:
800.250.6510 | Flowroute Client Support: 855.356.9768
[img]<https://www.sip.us/>
[img]<https://www.siptrunk.com/>
[img]<https://www.flowroute.com/>
________________________________
From: David Villasmil via sr-users
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: David Villasmil
<david.villasmil.work@gmail.com<mailto: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<http://10.1.2.36:5070/>
udp: 10.1.2.36:5080<http://10.1.2.36:5080/>
udp: 10.1.2.36:5160<http://10.1.2.36:5160/> advertise
4.3.2.1:5160<http://4.3.2.1:5160/>
udp: 0.0.0.0:5066<http://0.0.0.0:5066/>
tls: 10.1.2.36:443<http://10.1.2.36:443/> advertise
sip.something.com:443<http://sip.something.com:443/>
tls: 10.1.2.36:444<http://10.1.2.36:444/> advertise
sip.something.com:444<http://sip.something.com:444/>
tls: 10.1.2.36:5061<http://10.1.2.36:5061/>
When forwarding a udp invite received on 10.1.2.36:5080<http://10.1.2.36:5080/> to a
public ip provider say on 8.8.8.8:5060<http://8.8.8.8:5060/>, i'm forcing the
outgoing socket with force_socket via 10.1.2.36:5160<http://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<mailto:david.villasmil.work@gmail.com>
5:06 p.m.
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(a)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(a)gmail.com
<mailto:david.villasmil.work@gmail.com>>
Sent: Tuesday, September 10, 2024 9:26 AM
To: Ben Kaufman <bkaufman(a)bcmone.com <mailto:bkaufman@bcmone.com>>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto: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(a)gmail.com <mailto:david.villasmil.work@gmail.com>
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman <bkaufman(a)bcmone.com
<mailto: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(a)bcmone.com <mailto:bkaufman@bcmone.com>
SIP.US
<https://www.google.com/url?q=http://sip.us/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw37L0ij8aOQb8-wBFWCUa-_>
Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 | Flowroute
Client Support: 855.356.9768
<https://www.google.com/url?q=https://www.sip.us/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw02JU_oSfqgH9BK9v5k8Qto>
<https://www.google.com/url?q=https://www.siptrunk.com/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3SJ9Vi5uKUE9l0Sy_wO1dN>
<https://www.google.com/url?q=https://www.flowroute.com/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3bIiB1z2lr8wz-kfgCGtaa>
From: David Villasmil via sr-users <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org
<mailto:sr-users@lists.kamailio.org>>
Cc: David Villasmil <david.villasmil.work(a)gmail.com
<mailto: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
<https://www.google.com/url?q=http://10.1.2.36:5070/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0DPm8YcAkmGRRF2AjIrB-p>
udp: 10.1.2.36:5080
<https://www.google.com/url?q=http://10.1.2.36:5080/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw1_GxG1eIBK02zzEZXOmWZ5>
udp: 10.1.2.36:5160
<https://www.google.com/url?q=http://10.1.2.36:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0YqWXjLvXCDs7TvofLr51b>
advertise 4.3.2.1:5160
<https://www.google.com/url?q=http://4.3.2.1:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw039p3o3LLRHohjyv74Ik53>
udp: 0.0.0.0:5066
<https://www.google.com/url?q=http://0.0.0.0:5066/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2pn-ls2XoqNhMCB9o9xGce>
tls: 10.1.2.36:443
<https://www.google.com/url?q=http://10.1.2.36:443/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2vTT6rqqni7NdTei3R3rFB>
advertise sip.something.com:443
<https://www.google.com/url?q=http://sip.something.com:443/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw09ml85A5cPLWH7Iots0ENy>
tls: 10.1.2.36:444
<https://www.google.com/url?q=http://10.1.2.36:444/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2iitiO3VCfeOPqA2vWDV1j>
advertise sip.something.com:444
<https://www.google.com/url?q=http://sip.something.com:444/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3phHn-MBN7P8TxYXOcgrJO>
tls: 10.1.2.36:5061
<https://www.google.com/url?q=http://10.1.2.36:5061/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0HjRKnDFlHM6dT3o4ODrU8>
When forwarding a udp invite received on 10.1.2.36:5080
<https://www.google.com/url?q=http://10.1.2.36:5080/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw1_GxG1eIBK02zzEZXOmWZ5>
to a public ip provider say on 8.8.8.8:5060
<https://www.google.com/url?q=http://8.8.8.8:5060/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw22D_m1M8rAFfjghqMFvrak>,
i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160
<https://www.google.com/url?q=http://10.1.2.36:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0YqWXjLvXCDs7TvofLr51b>.
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(a)gmail.com <mailto:david.villasmil.work@gmail.com>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
6:39 p.m.
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(a)cloudtalk.io>
Sent: Thursday, October 3, 2024 9:06 AM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: David Villasmil <david.villasmil.work(a)gmail.com>om>; Ben Kaufman
<bkaufman(a)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(a)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<mailto:david.villasmil.work@gmail.com>>
Sent: Tuesday, September 10, 2024 9:26 AM
To: Ben Kaufman <bkaufman@bcmone.com<mailto:bkaufman@bcmone.com>>
Cc: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto: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<mailto:david.villasmil.work@gmail.com>
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman
<bkaufman@bcmone.com<mailto: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<mailto:bkaufman@bcmone.com>
SIP.US<https://www.google.com/url?q=http://sip.us/&source=gmail-imap…
Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 | Flowroute
Client Support: 855.356.9768
[img]<https://www.google.com/url?q=https://www.sip.us/&source=gmail-i…
[img]<https://www.google.com/url?q=https://www.siptrunk.com/&source=g…
[img]<https://www.google.com/url?q=https://www.flowroute.com/&source=…
________________________________
From: David Villasmil via sr-users
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: David Villasmil
<david.villasmil.work@gmail.com<mailto: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<https://www.google.com/url?q=http://10.1.2.36:5070/&s…
udp:
10.1.2.36:5080<https://www.google.com/url?q=http://10.1.2.36:5080/&s…
udp:
10.1.2.36:5160<https://www.google.com/url?q=http://10.1.2.36:5160/&s…
advertise
4.3.2.1:5160<https://www.google.com/url?q=http://4.3.2.1:5160/&sourc…
udp:
0.0.0.0:5066<https://www.google.com/url?q=http://0.0.0.0:5066/&sourc…
tls:
10.1.2.36:443<https://www.google.com/url?q=http://10.1.2.36:443/&sou…
advertise
sip.something.com:443<https://www.google.com/url?q=http://sip.something.…
tls:
10.1.2.36:444<https://www.google.com/url?q=http://10.1.2.36:444/&sou…
advertise
sip.something.com:444<https://www.google.com/url?q=http://sip.something.…
tls:
10.1.2.36:5061<https://www.google.com/url?q=http://10.1.2.36:5061/&s…
When forwarding a udp invite received on
10.1.2.36:5080<https://www.google.com/url?q=http://10.1.2.36:5080/&s…
to a public ip provider say on
8.8.8.8:5060<https://www.google.com/url?q=http://8.8.8.8:5060/&sourc…rAFfjghqMFvrak>,
i'm forcing the outgoing socket with force_socket via
10.1.2.36:5160<https://www.google.com/url?q=http://10.1.2.36:5160/&s…XCDs7TvofLr51b>.
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<mailto:david.villasmil.work@gmail.com>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
6:45 p.m.
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
email: david.villasmil.work(a)gmail.com
On Thu, Oct 3, 2024 at 5:39 PM Ben Kaufman <bkaufman(a)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(a)cloudtalk.io>
*Sent:* Thursday, October 3, 2024 9:06 AM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Cc:* David Villasmil <david.villasmil.work(a)gmail.com>om>; Ben Kaufman <
bkaufman(a)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(a)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(a)gmail.com>
*Sent:* Tuesday, September 10, 2024 9:26 AM
*To:* Ben Kaufman <bkaufman(a)bcmone.com>
*Cc:* Kamailio (SER) - Users Mailing List <sr-users(a)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(a)gmail.com
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman <bkaufman(a)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(a)bcmone.com
SIP.US
<https://www.google.com/url?q=http://sip.us/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw37L0ij8aOQb8-wBFWCUa-_>
Client
Support: 800.566.9810 *|* SIPTRUNK Client Support: 800.250.6510 *|* Flowroute
Client Support: 855.356.9768
[image: img]
<https://www.google.com/url?q=https://www.sip.us/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw02JU_oSfqgH9BK9v5k8Qto>
[image: img]
<https://www.google.com/url?q=https://www.siptrunk.com/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3SJ9Vi5uKUE9l0Sy_wO1dN>
*[image: img]
<https://www.google.com/url?q=https://www.flowroute.com/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3bIiB1z2lr8wz-kfgCGtaa>*
------------------------------
*From:* David Villasmil via sr-users <sr-users(a)lists.kamailio.org>
*Sent:* Tuesday, September 10, 2024 5:31 AM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Cc:* David Villasmil <david.villasmil.work(a)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
<https://www.google.com/url?q=http://10.1.2.36:5070/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0DPm8YcAkmGRRF2AjIrB-p>
udp: 10.1.2.36:5080
<https://www.google.com/url?q=http://10.1.2.36:5080/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw1_GxG1eIBK02zzEZXOmWZ5>
udp: 10.1.2.36:5160
<https://www.google.com/url?q=http://10.1.2.36:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0YqWXjLvXCDs7TvofLr51b>
advertise
4.3.2.1:5160
<https://www.google.com/url?q=http://4.3.2.1:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw039p3o3LLRHohjyv74Ik53>
udp: 0.0.0.0:5066
<https://www.google.com/url?q=http://0.0.0.0:5066/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2pn-ls2XoqNhMCB9o9xGce>
tls: 10.1.2.36:443
<https://www.google.com/url?q=http://10.1.2.36:443/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2vTT6rqqni7NdTei3R3rFB>
advertise
sip.something.com:443
<https://www.google.com/url?q=http://sip.something.com:443/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw09ml85A5cPLWH7Iots0ENy>
tls: 10.1.2.36:444
<https://www.google.com/url?q=http://10.1.2.36:444/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw2iitiO3VCfeOPqA2vWDV1j>
advertise
sip.something.com:444
<https://www.google.com/url?q=http://sip.something.com:444/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw3phHn-MBN7P8TxYXOcgrJO>
tls: 10.1.2.36:5061
<https://www.google.com/url?q=http://10.1.2.36:5061/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0HjRKnDFlHM6dT3o4ODrU8>
When forwarding a udp invite received on 10.1.2.36:5080
<https://www.google.com/url?q=http://10.1.2.36:5080/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw1_GxG1eIBK02zzEZXOmWZ5>
to
a public ip provider say on 8.8.8.8:5060
<https://www.google.com/url?q=http://8.8.8.8:5060/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw22D_m1M8rAFfjghqMFvrak>,
i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160
<https://www.google.com/url?q=http://10.1.2.36:5160/&source=gmail-imap&ust=1728568955000000&usg=AOvVaw0YqWXjLvXCDs7TvofLr51b>.
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(a)gmail.com
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
4 Oct
4 Oct
10:53 a.m.
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(a)lists.kamailio.org>
Sent: Donnerstag, 3. Oktober 2024 17:46
To: Ben Kaufman <bkaufman(a)bcmone.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>rg>; David
Villasmil <david.villasmil.work(a)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
email: david.villasmil.work@gmail.com<mailto:david.villasmil.work@gmail.com>
On Thu, Oct 3, 2024 at 5:39 PM Ben Kaufman
<bkaufman@bcmone.com<mailto: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<mailto:michal.popovic@cloudtalk.io>>
Sent: Thursday, October 3, 2024 9:06 AM
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: David Villasmil
<david.villasmil.work@gmail.com<mailto:david.villasmil.work@gmail.com>>; Ben
Kaufman <bkaufman@bcmone.com<mailto: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<mailto: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<mailto:david.villasmil.work@gmail.com>>
Sent: Tuesday, September 10, 2024 9:26 AM
To: Ben Kaufman <bkaufman@bcmone.com<mailto:bkaufman@bcmone.com>>
Cc: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto: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<mailto:david.villasmil.work@gmail.com>
On Tue, 10 Sep 2024 at 15:30, Ben Kaufman
<bkaufman@bcmone.com<mailto: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<mailto:bkaufman@bcmone.com>
SIP.US<https://www.google.com/url?q=http://sip.us/&source=gmail-imap…
Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 | Flowroute
Client Support: 855.356.9768
[img]<https://www.google.com/url?q=https://www.sip.us/&source=gmail-i…
[img]<https://www.google.com/url?q=https://www.siptrunk.com/&source=g…
[img]<https://www.google.com/url?q=https://www.flowroute.com/&source=…
________________________________
From: David Villasmil via sr-users
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Sent: Tuesday, September 10, 2024 5:31 AM
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Cc: David Villasmil
<david.villasmil.work@gmail.com<mailto: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<https://www.google.com/url?q=http://10.1.2.36:5070/&s…
udp:
10.1.2.36:5080<https://www.google.com/url?q=http://10.1.2.36:5080/&s…
udp:
10.1.2.36:5160<https://www.google.com/url?q=http://10.1.2.36:5160/&s…
advertise
4.3.2.1:5160<https://www.google.com/url?q=http://4.3.2.1:5160/&sourc…
udp:
0.0.0.0:5066<https://www.google.com/url?q=http://0.0.0.0:5066/&sourc…
tls:
10.1.2.36:443<https://www.google.com/url?q=http://10.1.2.36:443/&sou…
advertise
sip.something.com:443<https://www.google.com/url?q=http://sip.something.…
tls:
10.1.2.36:444<https://www.google.com/url?q=http://10.1.2.36:444/&sou…
advertise
sip.something.com:444<https://www.google.com/url?q=http://sip.something.…
tls:
10.1.2.36:5061<https://www.google.com/url?q=http://10.1.2.36:5061/&s…
When forwarding a udp invite received on
10.1.2.36:5080<https://www.google.com/url?q=http://10.1.2.36:5080/&s…
to a public ip provider say on
8.8.8.8:5060<https://www.google.com/url?q=http://8.8.8.8:5060/&sourc…rAFfjghqMFvrak>,
i'm forcing the outgoing socket with force_socket via
10.1.2.36:5160<https://www.google.com/url?q=http://10.1.2.36:5160/&s…XCDs7TvofLr51b>.
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<mailto:david.villasmil.work@gmail.com>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to
sr-users-leave@lists.kamailio.org<mailto: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:
32
days inactive
56
days old
9 comments
4 participants
participants (4)
-
Ben Kaufman -
David Villasmil -
Henning Westerholt -
Michal Popovič