[kamailio/kamailio] no corresponding socket found error (Issue #3583)
Hello all we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio 5.5.6 ```Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[164.152.22.248:5060](http://164.152.22.248:5060/)) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.184:5060](http://208.74.138.184:5060/)) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.181:5060](http://208.74.138.181:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[38.102.250.60:5060](http://38.102.250.60:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[87.1.1.27:5060](http://87.1.1.27:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155697]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.184:5060](http://208.74.138.184:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[192.40.216.97:5060](http://192.40.216.97:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.180:5060](http://208.74.138.180:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155714]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[87.1.1.27:5060](http://87.1.1.27:5060/)) ``` The kamailio instance we are using is receiving around 1500 calls per second in average when we do start seeing these errors more frequently In this instance we are using multihomed the listen address list is ``` children=14 socket_workers=1 listen=udp:[192.168.99.70:5081](http://192.168.99.70:5081/) listen=udp:[192.168.99.81:5060](http://192.168.99.81:5060/) listen=udp:[87.1.1.27:5060](http://87.1.1.27:5060/) listen=tcp:[192.168.96.105:8095](http://192.168.96.105:8095/) listen=tcp:[87.1.1.27:5060](http://87.1.1.27:5060/) tcp_children=6 port=5060 ``` We use the first worker only to perform the OPTIONS requests from the dispatcher module. The sockets listen=udp:[192.168.99.81:5060](http://192.168.99.81:5060/) listen=udp:[87.1.1.27:5060](http://87.1.1.27:5060/) are used to communicate both A and B legs so when a message is received at [192.168.99.81:5060](http://192.168.99.81:5060/) we send it to [87.1.1.27:5060](http://87.1.1.27:5060/) and viceversa We were using $fs variable before doing the t_relay() function. This way is working, but when load increases, seems sometimes kamailio doesn't get the proper socket to forward the reply. I think the errors mainly are related to responses which are being forwarded, like if the function get_sock_info_list was not able to retrieve the listen interfaces we have tried to set in the onreply routes the commands set_recv_socket("udp:[192.168.99.81:5060](http://192.168.99.81:5060/)"); set_send_socket("udp:[87.1.1.27:5060](http://87.1.1.27:5060/)"); (when reply goes from private to public domain) and it seems it reduces the number of ``` Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[164.152.22.248:5060](http://164.152.22.248:5060/)) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.184:5060](http://208.74.138.184:5060/)) Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[208.74.138.181:5060](http://208.74.138.181:5060/)) Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]: ERROR: <core> [core/forward.c:183]: get_out_socket(): no corresponding socket found for(udp:[38.102.250.60:5060](http://38.102.250.60:5060/)) errors ``` But i honestly don't know why the ```Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27" af 2 Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]: ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1 (no corresponding listening socket) appear ``` We also tried to increase the kernel buffers rmem and wmem from 208KB (as we had by default) to 4MB Do you know a reason which could cause these logs to appear? Any setup that could mitigate them? thanks a lot and regards david escartin -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583@github.com>
Can it be that the responses were delayed and the corresponding transaction didn't exist anymore? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1735363255 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583/1735363255@github.com>
We have observed such messages when the default route via the network interface does not match to socket listened by Kamailio. Probable you need to output the socket you want to use for outbound message. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1737317203 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583/1737317203@github.com>
hello all I tried to set the machine default route to 87.1.1.1 but I still got messages of that kind I also tried to add force socket on cancel requests before the t_relay(), since I saw that maybe when the error generated was when we have a CANCEL request which seemed to not be processed the a-leg was retransmitting it i will check if that has any possitive effect best regards david -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1748416075 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583/1748416075@github.com>
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1815661344 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583/1815661344@github.com>
Closed #3583 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#event-11116747962 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issue/3583/issue_event/11116747962@github.com>
This happens when UA sends `REGISTER` from a port that doesn't match the one advertised in a `CONTACT` header (for example there is a port translation (like PAT) on your firewall, or maybe a bug in UA 🤷) Kamailio will store `AoR` with a port from `CONTACT`, and this may be not reachable. As an example see attached pictures with Zoiper and TCP: `REGISTER` packet received from port **50376** but AoR stored with port **60320**. Trying to connect to that port failed and thus error message from `tcp_do_connect()` <img width="1024" alt="kamailio_nat_issue_1" src="https://github.com/user-attachments/assets/50e543ac-8d8f-4725-8e68-fc1f55fbb57a"> <img width="705" alt="kamailio_nat_issue_2" src="https://github.com/user-attachments/assets/ce3e05bc-01de-4e3b-bec6-3cd02694eecd"> <img width="1275" alt="kamailio_nat_issue_3" src="https://github.com/user-attachments/assets/92fb56b3-2822-4d8e-b31a-dd83d6a3e838"> 👉 To fix that define `WITH_NAT`, use `received_avp` parameter of the `nathelper` module and the `registrar` module, and use `fix_nated_register()` for the `registrar` to store it in the received column in the location table <img width="1044" alt="kamailio_nat_issue_5_fix" src="https://github.com/user-attachments/assets/764578cc-359a-440f-afa9-c329abe95c56"> <img width="684" alt="kamailio_nat_issue_4_fix" src="https://github.com/user-attachments/assets/23934bd4-f2b5-4e2e-91b4-682f47fa154c"> -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-2480754616 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3583/2480754616@github.com>
participants (5)
-
Daniel-Constantin Mierla -
descartin
-
github-actions[bot]
-
Later
-
sergey-safarov