Hello,
I have been using the siptrace module on a multihomed kamailio setup for some time now, with kamailio 5.5.7 and 5.6.6, without incident.
I am listening to my external interface using something like:
listen=tls:external_ip:5061 listen=tcp:external_ip:5060 Listen=tcp:internal_ip:5000 name "homer"
And for siptrace...
modparam("siptrace", "duplicate_uri", "sip:homer_ip:9060;transport=tcp") modparam("siptrace", "send_sock_name", "homer")
I have also used send_sock_addr and force_send...
This works as expected.
I recently deployed this same setup using kamailio 6.0.1 and discovered that the send_sock is not being respected, even though the logs say it has been selected. Instead, tcpdump and careful examination of all the file descriptors for the kamailio processes reveal it is sending with the source set to my external_ip instead of the internal_ip.
I have verified this on the same server, ruling out os level issues routing issues and have tried manually connecting using nc with the internal ip address for the source, which works.
I tried downgrading, and found that the same is true for kamailio 5.7.6, 5.8.6 and 6.0.1
This issue only appears to affect siptrace as other sockets appear to use the correct source ip to, for example, connect to a database.
I had a look at the change logs and documentation and cant see anything obvious that I need to change from a configuration perspective.
Could anybody help? I would prefer to be running 6.0+ in my new production environment but wont be able to if this cannot be solved quickly.
Many thanks for your help.
With every blessing, -- Daniel Donoghue
Hello,
do you have IP routing path from the external_ip to the homer server? Like, it is possible to open connection to the homer server from both internal_ip and external_ip? If yes, even when the application tries to indicate the desired local ip:port when creating a tcp connection, it is the tcp stack/kernel that makes the final decision.
If you switch to udp for homer traffic, is the expected network interface used?
Cheers, Daniel
On 27.05.25 16:11, Daniel Donoghue via sr-users wrote:
Hello,
I have been using the siptrace module on a multihomed kamailio setup for some time now, with kamailio 5.5.7 and 5.6.6, without incident.
I am listening to my external interface using something like:
listen=tls:external_ip:5061 listen=tcp:external_ip:5060 Listen=tcp:internal_ip:5000 name "homer"
And for siptrace...
modparam("siptrace", "duplicate_uri", "sip:homer_ip:9060;transport=tcp") modparam("siptrace", "send_sock_name", "homer")
I have also used send_sock_addr and force_send...
This works as expected.
I recently deployed this same setup using kamailio 6.0.1 and discovered that the send_sock is not being respected, even though the logs say it has been selected. Instead, tcpdump and careful examination of all the file descriptors for the kamailio processes reveal it is sending with the source set to my external_ip instead of the internal_ip.
I have verified this on the same server, ruling out os level issues routing issues and have tried manually connecting using nc with the internal ip address for the source, which works.
I tried downgrading, and found that the same is true for kamailio 5.7.6, 5.8.6 and 6.0.1
This issue only appears to affect siptrace as other sockets appear to use the correct source ip to, for example, connect to a database.
I had a look at the change logs and documentation and cant see anything obvious that I need to change from a configuration perspective.
Could anybody help? I would prefer to be running 6.0+ in my new production environment but wont be able to if this cannot be solved quickly.
Many thanks for your help.
With every blessing,
Daniel Donoghue
Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.org 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!
Hi Daniel,
Thanks for getting back to me.
The os routing path for the ip address of the homer7 server takes the default gateway which is on the internal network and has access to the server. The connection is only possible on the internal connenction.
I cannot use udp for traffic as my packets are too large and subject to packet fragmentation.
The ip source/routing works correctly on the same server when running kamailio 5.6.6 but nothing since. And when attempting this manually using telnet, nc, and other tools, the packets go from the correct interface and everything looks as expected.
I am running multihomed=1 and configure listen differently for each interface: external interface has udp, tcp and tls listenerrs, a private tunnel interface has a udp listener, the internal interface has a tcp listener just for the homer access.
Is there anything kamailio config/os config related that it would be of benefit to see?
For now I have had to downgrade kamailio to 5.6.6 in my production environment.
With every blessing, -- Daniel Donoghue
________________________________ From: Daniel-Constantin Mierla miconda@gmail.com Sent: 06 June 2025 10:22 AM To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Cc: Daniel Donoghue oneofsomany@hotmail.com Subject: Re: [SR-Users] siptrace module not respecting send_sock after kamailio 5.6.6
Hello,
do you have IP routing path from the external_ip to the homer server? Like, it is possible to open connection to the homer server from both internal_ip and external_ip? If yes, even when the application tries to indicate the desired local ip:port when creating a tcp connection, it is the tcp stack/kernel that makes the final decision.
If you switch to udp for homer traffic, is the expected network interface used?
Cheers, Daniel
On 27.05.25 16:11, Daniel Donoghue via sr-users wrote: Hello,
I have been using the siptrace module on a multihomed kamailio setup for some time now, with kamailio 5.5.7 and 5.6.6, without incident.
I am listening to my external interface using something like:
listen=tls:external_ip:5061 listen=tcp:external_ip:5060 Listen=tcp:internal_ip:5000 name "homer"
And for siptrace...
modparam("siptrace", "duplicate_uri", "sip:homer_ip:9060;transport=tcp") modparam("siptrace", "send_sock_name", "homer")
I have also used send_sock_addr and force_send...
This works as expected.
I recently deployed this same setup using kamailio 6.0.1 and discovered that the send_sock is not being respected, even though the logs say it has been selected. Instead, tcpdump and careful examination of all the file descriptors for the kamailio processes reveal it is sending with the source set to my external_ip instead of the internal_ip.
I have verified this on the same server, ruling out os level issues routing issues and have tried manually connecting using nc with the internal ip address for the source, which works.
I tried downgrading, and found that the same is true for kamailio 5.7.6, 5.8.6 and 6.0.1
This issue only appears to affect siptrace as other sockets appear to use the correct source ip to, for example, connect to a database.
I had a look at the change logs and documentation and cant see anything obvious that I need to change from a configuration perspective.
Could anybody help? I would prefer to be running 6.0+ in my new production environment but wont be able to if this cannot be solved quickly.
Many thanks for your help.
With every blessing, -- Daniel Donoghue
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org To unsubscribe send an email to sr-users-leave@lists.kamailio.orgmailto:sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!
-- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Scalability Training - Online, June 16-19, 2025 -- asipto.com
-
Daniel Donoghue -
Daniel-Constantin Mierla