Kamailio isn’t working on my Azure VM, even though it’s set up to use port 5060. The network rules on Azure have both inbound and outbound traffic open for all protocols. I also tried using advertised_address, but that didn’t help either. It looks like no traffic is even hitting Kamailio — none of the routing blocks are triggered.
Kamailio.cfg alias=<PUBLIC-IP> listen=udp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060 listen=tcp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060
Sip Message: 2025/06/04 15:50:37.870679 64.16.250.10:5060 -> 10.0.0.4:5060 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0 Record-Route: sip:64.16.250.10;r2=on;lr;ftag=DpHvv09240egQ Record-Route: sip:10.255.0.2;r2=on;lr;ftag=DpHvv09240egQ Via: SIP/2.0/UDP 64.16.250.10;branch=z9hG4bKd59a.fb67bf395ea20488a7a5ebf76b9b5685.0 v:SIP/2.0/UDP 10.239.196.24:6000;received=10.239.196.24;rport=6000;branch=z9hG4bKy9ZvBZcgretvr Max-Forwards:48 f:"+351908020050"sip:+351908020050@sip.telnyx.com;tag=DpHvv09240egQ t:<sip:+351200600020@<PUBLIC-IP>:5060> i:122d71bb-4f3d-473f-8853-9137023f1f14 CSeq:99972326 INVITE m:sip:mod_sofia@10.239.196.24:6000 Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOTIFY k:timer,path u:talk,hold,conference,refer Privacy:none c:application/sdp Content-Disposition:session l:202 P-Asserted-Identity:"+351908020050"sip:+351908020050@sip.telnyx.eu;verstat=No-TN-Validation
v=0 o=Telnyx 1749019739 1749019740 IN IP4 50.114.147.4 s=Telnyx c=IN IP4 50.114.147.4 t=0 0 m=audio 32498 RTP/AVP 9 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:32499 IN IP4 50.114.147.4 a=ptime:20
On Jun 4, 2025, at 11:59 AM, Fernando Lopes via sr-users sr-users@lists.kamailio.org wrote:
Kamailio isn’t working on my Azure VM, even though it’s set up to use port 5060. The network rules on Azure have both inbound and outbound traffic open for all protocols. I also tried using advertised_address, but that didn’t help either. It looks like no traffic is even hitting Kamailio — none of the routing blocks are triggered.
Kamailio.cfg alias=<PUBLIC-IP> listen=udp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060 listen=tcp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060
Sip Message: 2025/06/04 15:50:37.870679 64.16.250.10:5060 -> 10.0.0.4:5060 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0 Record-Route: sip:64.16.250.10;r2=on;lr;ftag=DpHvv09240egQ Record-Route: sip:10.255.0.2;r2=on;lr;ftag=DpHvv09240egQ Via: SIP/2.0/UDP 64.16.250.10;branch=z9hG4bKd59a.fb67bf395ea20488a7a5ebf76b9b5685.0 v:SIP/2.0/UDP 10.239.196.24:6000;received=10.239.196.24;rport=6000;branch=z9hG4bKy9ZvBZcgretvr Max-Forwards:48 f:"+351908020050"sip:+351908020050@sip.telnyx.com;tag=DpHvv09240egQ t:<sip:+351200600020@<PUBLIC-IP>:5060> i:122d71bb-4f3d-473f-8853-9137023f1f14 CSeq:99972326 INVITE m:sip:mod_sofia@10.239.196.24:6000 Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOTIFY k:timer,path u:talk,hold,conference,refer Privacy:none c:application/sdp Content-Disposition:session l:202 P-Asserted-Identity:"+351908020050"sip:+351908020050@sip.telnyx.eu;verstat=No-TN-Validation
v=0 o=Telnyx 1749019739 1749019740 IN IP4 50.114.147.4 s=Telnyx c=IN IP4 50.114.147.4 t=0 0 m=audio 32498 RTP/AVP 9 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:32499 IN IP4 50.114.147.4 a=ptime:20
I’d suggest you increase logging as well as make sure that the system is even seeing the traffic. Something like sngrep will let you see that the NIC is seeing it.
You will then need to confirm nothing is blocking kamailio (ufw,iptables,etc) from seeing the packets. And then, if Kamailio is seeing it, advise of the error and or message.
Fred Posner Tel: +1 (352) 664-3733 Alt: +1 (224) 334-3733
Contact info at https://fredp.xyz
sudo ufw status Status: inactive sudo iptables -L -n -v | grep 5060 319 273K ACCEPT 17 -- * * 0.0.0.0/0 10.0.0.4 udp dpt:5060 540 28028 ACCEPT 6 -- * * 0.0.0.0/0 10.0.0.4 tcp dpt:5060 4 192 ACCEPT 6 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.5 tcp dpt:5060 0 0 ACCEPT 17 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.5 udp dpt:5060
can you stop IPTables (just in case...) and redo a test call?
And what about SELinux settings? had some issues with it on RH9+ lately....
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Wed, Jun 4, 2025 at 6:59 PM Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
sudo ufw status Status: inactive sudo iptables -L -n -v | grep 5060 319 273K ACCEPT 17 -- * * 0.0.0.0/0 10.0.0.4 udp dpt:5060 540 28028 ACCEPT 6 -- * * 0.0.0.0/0 10.0.0.4 tcp dpt:5060 4 192 ACCEPT 6 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.5 tcp dpt:5060 0 0 ACCEPT 17 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.5 udp dpt:5060 __________________________________________________________ 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!
This is a long shot, but .... to disable SELinux, edit the SELinux config file at /etc/selinux/config and change the SELinux setting to disabled, save the file, and then reboot the system for the changes to take effect. You may also temporarily disable SELinux by running the command; setenforce 0
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Wed, Jun 4, 2025 at 6:43 PM Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
Sorry, could you tell me how to do that? __________________________________________________________ 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!
install sngrep and run it, even if kamailio doesn't receive the packet, if it gets to the vm, you'll see it. If you don't, something before it reaches the vm is blocking it. also set listen to 0.0.0.0:5060 just in case Regards,
David Villasmil email: david.villasmil.work@gmail.com
On Thu, Jun 5, 2025 at 12:50 AM Sergio Charrua via sr-users < sr-users@lists.kamailio.org> wrote:
This is a long shot, but .... to disable SELinux, edit the SELinux config file at /etc/selinux/config and change the SELinux setting to disabled, save the file, and then reboot the system for the changes to take effect. You may also temporarily disable SELinux by running the command; setenforce 0
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Wed, Jun 4, 2025 at 6:43 PM Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
Sorry, could you tell me how to do that? __________________________________________________________ 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!
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!
The sip message reaches inside the vm, I can see it U 2025/06/04 16:40:24.026418 192.76.120.10:5060 -> 10.0.0.4:5060 #8 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0, the strange thing is that kamailio is working(can send pings to asterisk), it just doesn't want to enter any type of route, I think maybe because advertise doesn't work or any other config is also not working
When you start kamailio it shows the message with aliases and domains associated with it via configuration file. If you see advertise address there - it works.
On Thu, Jun 5, 2025, 10:17 Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
The sip message reaches inside the vm, I can see it U 2025/06/04 16:40:24.026418 192.76.120.10:5060 -> 10.0.0.4:5060 #8 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0, the strange thing is that kamailio is working(can send pings to asterisk), it just doesn't want to enter any type of route, I think maybe because advertise doesn't work or any other config is also not working __________________________________________________________ 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!
Can you confirm that Kamailio is listening on the port 5060 udp/tcp ?
something list using NetCat:
nc -v -u -z -w 3 host.ip.address 5060-5070
This will check if anything is listening to the port range from 5060 to 5070 on UDP (default transport for SIP).
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Thu, Jun 5, 2025 at 10:13 AM Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
The sip message reaches inside the vm, I can see it U 2025/06/04 16:40:24.026418 192.76.120.10:5060 -> 10.0.0.4:5060 #8 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0, the strange thing is that kamailio is working(can send pings to asterisk), it just doesn't want to enter any type of route, I think maybe because advertise doesn't work or any other config is also not working __________________________________________________________ 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!
The Problem was IPTables all along, when I reboot the rules get cleaned, and I need to add the first two. sudo iptables -L -n -v | grep 5060 4 208 ACCEPT 6 -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5060 13 13715 ACCEPT 17 -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:5060 0 0 ACCEPT 6 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.6 tcp dpt:5060 0 0 ACCEPT 17 -- !br-aeab3c66b5ee br-aeab3c66b5ee 0.0.0.0/0 172.19.0.6 udp dpt:5060
Sorry, the problem was iptables, I didn't check kamailio logs when I added the first 2 rules, and after reboot the machine cleans the rules.
Hello,
use some tools like ngrep, sgrep etc.. to see if the traffic is actually reaching the server. Maybe its not Kamailio fault.
Cheers,
Henning
-----Original Message----- From: Fernando Lopes via sr-users sr-users@lists.kamailio.org Sent: Mittwoch, 4. Juni 2025 17:59 To: sr-users@lists.kamailio.org Cc: Fernando Lopes fernandolopes20003@gmail.com Subject: [SR-Users] Why won't this work
Kamailio isn’t working on my Azure VM, even though it’s set up to use port 5060. The network rules on Azure have both inbound and outbound traffic open for all protocols. I also tried using advertised_address, but that didn’t help either. It looks like no traffic is even hitting Kamailio — none of the routing blocks are triggered.
Kamailio.cfg alias=<PUBLIC-IP> listen=udp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060 listen=tcp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060
Sip Message: 2025/06/04 15:50:37.870679 64.16.250.10:5060 -> 10.0.0.4:5060 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0 Record-Route: sip:64.16.250.10;r2=on;lr;ftag=DpHvv09240egQ Record-Route: sip:10.255.0.2;r2=on;lr;ftag=DpHvv09240egQ Via: SIP/2.0/UDP 64.16.250.10;branch=z9hG4bKd59a.fb67bf395ea20488a7a5ebf76b9b5685 .0 v:SIP/2.0/UDP 10.239.196.24:6000;received=10.239.196.24;rport=6000;branch=z9hG4bKy 9ZvBZcgretvr Max-Forwards:48 f:"+351908020050"sip:+351908020050@sip.telnyx.com;tag=DpHvv0924 0egQ t:<sip:+351200600020@<PUBLIC-IP>:5060> i:122d71bb-4f3d-473f-8853-9137023f1f14 CSeq:99972326 INVITE m:sip:mod_sofia@10.239.196.24:6000 Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOT IFY k:timer,path u:talk,hold,conference,refer Privacy:none c:application/sdp Content-Disposition:session l:202 P-Asserted- Identity:"+351908020050"sip:+351908020050@sip.telnyx.eu;verstat=No- TN-Validation
v=0 o=Telnyx 1749019739 1749019740 IN IP4 50.114.147.4 s=Telnyx c=IN IP4 50.114.147.4 t=0 0 m=audio 32498 RTP/AVP 9 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:32499 IN IP4 50.114.147.4 a=ptime:20 __________________________________________________________ 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!
U 2025/06/04 16:40:24.026418 192.76.120.10:5060 -> 10.0.0.4:5060 #8 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0. Record-Route: sip:192.76.120.10;r2=on;lr;ftag=r6S4SUtaQ92ja. Record-Route: sip:10.255.0.1;r2=on;lr;ftag=r6S4SUtaQ92ja. Via: SIP/2.0/UDP 192.76.120.10;branch=z9hG4bK20b.448fbb5154629b146382ecb9a8979f7a.0. v:SIP/2.0/UDP 10.239.230.24:6000;received=10.239.230.24;rport=6000;branch=z9hG4bKemQtB2tKF0HcD. Max-Forwards:48. f:"+3519080200501"sip:+351908020050@sip.telnyx.com;tag=r6S4SUtaQ92ja. t:<sip:+351200600020@<PUBLIC-IP>:5060>. i:17d501cf-9926-4e60-b92f-3e869a4fbb5d. CSeq:99973819 INVITE. m:sip:mod_sofia@10.239.230.24:6000. Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOTIFY. k:timer,path. u:talk,hold,conference,refer. Privacy:none. c:application/sdp. Content-Disposition:session. l:205. P-Asserted-Identity:"+351908020050"sip:+351908020050@sip.telnyx.eu;verstat=No-TN-Validation. . v=0. o=Telnyx 1749027375 1749027376 IN IP4 50.114.151.14. s=Telnyx. c=IN IP4 50.114.151.14. t=0 0. m=audio 27848 RTP/AVP 9. a=rtpmap:9 G722/8000. a=sendrecv. a=rtcp:27849 IN IP4 50.114.151.14. a=ptime:20.
If you run Kamailio via command line with -E option (ex.: kamailio -E -f kamailio.cfg) and set debug level to 3, what is the output? Do you see anything going on when an INVITE comes through?
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Wed, Jun 4, 2025 at 6:18 PM Fernando Lopes via sr-users < sr-users@lists.kamailio.org> wrote:
Kamailio isn’t working on my Azure VM, even though it’s set up to use port 5060. The network rules on Azure have both inbound and outbound traffic open for all protocols. I also tried using advertised_address, but that didn’t help either. It looks like no traffic is even hitting Kamailio — none of the routing blocks are triggered.
Kamailio.cfg alias=<PUBLIC-IP> listen=udp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060 listen=tcp:10.0.0.4:5060 advertise <PUBLIC-IP>:5060
Sip Message: 2025/06/04 15:50:37.870679 64.16.250.10:5060 -> 10.0.0.4:5060 INVITE sip:+351200600020@<PUBLIC-IP>:5060 SIP/2.0 Record-Route: sip:64.16.250.10;r2=on;lr;ftag=DpHvv09240egQ Record-Route: sip:10.255.0.2;r2=on;lr;ftag=DpHvv09240egQ Via: SIP/2.0/UDP 64.16.250.10;branch=z9hG4bKd59a.fb67bf395ea20488a7a5ebf76b9b5685.0 v:SIP/2.0/UDP 10.239.196.24:6000 ;received=10.239.196.24;rport=6000;branch=z9hG4bKy9ZvBZcgretvr Max-Forwards:48 f:"+351908020050"sip:+351908020050@sip.telnyx.com;tag=DpHvv09240egQ t:<sip:+351200600020@<PUBLIC-IP>:5060> i:122d71bb-4f3d-473f-8853-9137023f1f14 CSeq:99972326 INVITE m:sip:mod_sofia@10.239.196.24:6000 Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REFER,NOTIFY k:timer,path u:talk,hold,conference,refer Privacy:none c:application/sdp Content-Disposition:session l:202 P-Asserted-Identity:"+351908020050"sip:+351908020050@sip.telnyx.eu ;verstat=No-TN-Validation
v=0 o=Telnyx 1749019739 1749019740 IN IP4 50.114.147.4 s=Telnyx c=IN IP4 50.114.147.4 t=0 0 m=audio 32498 RTP/AVP 9 a=rtpmap:9 G722/8000 a=sendrecv a=rtcp:32499 IN IP4 50.114.147.4 a=ptime:20 __________________________________________________________ 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!
I have this in my kamailio just to see if I see something in var/log/kamailio.log request_route { xlog("AQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQUIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII"); } route { xlog("AQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQUIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII"); } Log(can't see any invite or anything related to this 2 routes): 2025-06-04T15:40:05.449399+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240461]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.450652+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240462]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.451250+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240466]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.451381+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240467]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.451461+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240472]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.451921+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240458]: NOTICE: <core> [main.c:750]: handle_sigs(): Thank you for flying kamailio!!! 2025-06-04T15:40:05.452151+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240465]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454252+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240464]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454402+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240463]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454607+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240459]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454749+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240468]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454869+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240460]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.454977+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240469]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.455115+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240470]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.455183+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240471]: INFO: <core> [main.c:874]: sig_usr(): signal 15 received 2025-06-04T15:40:05.456183+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240458]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2025-06-04T15:40:05.486969+00:00 vm-accelerat-prod-01 kamailio: INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module 2025-06-04T15:40:05.487686+00:00 vm-accelerat-prod-01 kamailio: INFO: <core> [core/tcp_main.c:5205]: init_tcp(): using epoll_lt as the io watch method (auto detected) 2025-06-04T15:40:05.494046+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240507]: INFO: rr [../outbound/api.h:53]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 2025-06-04T15:40:05.494141+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240507]: INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 2025-06-04T15:40:05.496028+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240507]: INFO: <core> [main.c:3189]: main(): processes (at least): 15 - shm size: 67108864 - pkg size: 8388608 2025-06-04T15:40:05.496157+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240507]: INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 1048576 for fd 9 2025-06-04T15:40:05.496216+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240507]: INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 1048576 on fd 9 2025-06-04T15:40:05.498340+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240508]: INFO: rtpengine [rtpengine.c:3040]: rtpp_test(): rtpengine instance udp:10.0.0.4:2223 found, support for it enabled 2025-06-04T15:40:05.502329+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240516]: INFO: jsonrpcs [jsonrpcs_sock.c:471]: jsonrpc_dgram_process(): a new child 0/240516 2025-06-04T15:40:35.527925+00:00 vm-accelerat-prod-01 /usr/sbin/kamailio[240514]: WARNING: <core> [core/tcp_main.c:1445]: tcp_do_connect(): 10.0.0.4:5061: could not find corresponding listening socket for 10.0.0.4, using default...
-
David Villasmil -
Fernando Lopes -
Fred Posner -
Henning Westerholt -
Sergio Charrua -
Yuriy G