- sr-users - kamailio.org

load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules/>
by amit＠cosmicinfotech.com 08 Sep '23

08 Sep '23

using kamailio 5.3.9 [244@root ~]$ kamailio -f /etc/kamailio/kamailio.cfg -E loading modules under config path: /usr/lib64/kamailio/modules/ 0(1071336) ERROR: <core> [core/sr_module.c:500]: load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules/> 0(1071336) CRITICAL: <core> [core/cfg.y:3543]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 294, column 12-23: failed to load module 0(1071336) ERROR: <core> [core/… [View More]

2 2

Re: uac_replace_to() without RR params
by Duarte Rocha 08 Sep '23

08 Sep '23

2 1

Question about a Slow timer process.
by Володимир Іванець 07 Sep '23

07 Sep '23

Hello everyone! I'm running Kamailio 5.6.2 and having a potential problem on one of the systems. The Slow timer process slowly consumes more and more of its PKG memory. I did not allow it to use all memory by restartink Kamailio during afterhours so I'm not sure what the consequences might be. I'm suspecting that this could be caused by my configuration but not sure how exactly. Can anyone please tell me how the Slow timer process can be debugged? Is it possible to see what it is storing in … [View More]

1 0

uac_replace_to() without RR params
by Duarte Rocha 07 Sep '23

07 Sep '23

Hello all, I'm currently working on a proxy where I need to change To and From headers in order to normalize the numbers to +E164. I would like to be able to restore using and $avp() or $dlg_var() and without writing parameters on the Record-Route headers. I've tried to use restore_mode in auto mode and restore_dlg parameter with value 1 but still got the parameters on the inserted Record-Route. I've tried manual mode and using the configured $avp() to restore, but the parameters still got … [View More]

1 0

[Proposal] To add tlsa module to the package builder
by Denys Pozniak 07 Sep '23

07 Sep '23

Hello! Are there any technical difficulties in adding tlsa module with the statically linked OpenSSL v1.1.1 to the package builder (deb)? -- BR, Denys Pozniak

1 0

Unnecessary/Invalid AVPs in CCR message over Ro Interface
by s.ghahremannejad＠gmail.com 06 Sep '23

06 Sep '23

**Issue Description** I'm encountering an issue with my Kamailio configuration related to the inclusion of the "Accounting-Record-Type" (480) and "Accounting-Record-Number" (485) AVPs in Credit-Control Request (CCR) messages sent from the S-CSCF to the OCS. **Issue Details** - **Problem**: The "Accounting-Record-Type" and "Accounting-Record-Number" AVPs are being added to CCR messages generated by my Kamailio instance. - **Expected Behavior**: According to modern Diameter and 3GPP standards (… [View More]e.g., RFC 4006 and TS 32.299), these AVPs should not be included in CCR messages. **Configuration Details** - **Kamailio Version**: 5.3.0 - **SigScale OCS Version**: 3.2.9 Note that I have redacted some specific information for confidentiality reasons. The actual values are placed in my Kamailio main configuration file (`kamailio.cfg`) and Diameter-specific configuration files (where applicable). Kamailio.cfg: modparam("ims_charging", "db_url", DB_URL) modparam("ims_charging", "db_mode", 1) modparam("ims_charging", "origin_host", HOSTNAME); modparam("ims_charging", "origin_realm", NETWORKNAME); modparam("ims_charging", "destination_host", DESTINATION_HOST); modparam("ims_charging", "destination_realm", DESTINATION_REALM); modparam("ims_charging","service_context_id_root", RO_ROOT); modparam("ims_charging","service_context_id_ext", RO_EXT); modparam("ims_charging","service_context_id_mnc", MNC); modparam("ims_charging","service_context_id_mcc", MCC); modparam("ims_charging","interim_update_credits",30); modparam("ims_charging","timer_buffer",5); SCSCF.xml: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="scscf.mncXXX.mccXXX.3gppnetwork.org" Realm="ims.mncXXX.mccXXX.3gppnetwork.org" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <Peer FQDN="diameter" Realm="ims.mncXXX.mccXXX.3gppnetwork.org" port="3868"/> <Peer FQDN="192.168.2.31" Realm="ocs.ims.mncXXX.mccXXX.3gppnetwork.org" port="3868"/> <Acceptor port="3868" bind="eth0"/> <Auth id="16777216" vendor="10415"/> <Auth id="16777216" vendor="4491"/> <Auth id="16777216" vendor="13019"/> <Auth id="16777216" vendor="0"/> <Auth id="4" vendor="10415"/>  <Acct id="4" vendor="10415" />  <SupportedVendor vendor="10415" /> <Realm name="ocs.ims.mncXXX.mccXXX.3gppnetwork.org"> <Route FQDN="192.168.2.31" metric="10"/> </Realm> <DefaultRoute FQDN="diameter" metric="10"/> </DiameterPeer> I am using SigScale OCS as my Online Charging System. Here is the error log I received from SigScale OCS: ERROR REPORT==== 5-Sep-2023::07:27:01.393554 === "DIAMETER AVP unsupported" service_name: {ocs_diameter_acct_service,{0,0,0,0},3868} capabilities: {diameter_caps, {<<"host1">>, <<"scscf-1.ims.mncXXX.mccXXX.3gppnetwork.org">>}, {<<"COMPANYNAME.local">>, <<"ims.mncXXX.mccXXX.3gppnetwork.org">>}, {[{0,0,0,0}],[{172,18,0,7}]}, {50386,10415}, {<<"SigScale OCS">>,<<"CDiameterPeer">>}, {[],[]}, {[10415],[10415]}, {[4,16777238],[16777216]}, {[],[]}, {[],[]}, {[{'diameter_base_Vendor-Specific-Application-Id',10415,[16777238],[]}], [{'diameter_base_Vendor-Specific-Application-Id',10415,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',4491,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',13019,[16777216],[]}, {'diameter_base_Vendor-Specific-Application-Id',10415,[4],[]}, {'diameter_base_Vendor-Specific-Application-Id',10415,[],[4]}]}, {[329],[]}, {[],[]}} errors: [{5001, {diameter_avp,480,undefined,true,false, <<0,0,0,2>>, 'Accounting-Record-Type',2,'Enumerated',5}}, {5001, {diameter_avp,485,undefined,true,false, <<0,0,0,0>>, 'Accounting-Record-Number',0,'Unsigned32',6}}, {5001, {diameter_avp,260,undefined,true,false, <<0,0,1,10,64,0,0,12,0,0,40,175,0,0,1,2,64,0,0,12,0,0,0,4>>, 'Vendor-Specific-Application-Id', {'3gpp_ro_Vendor-Specific-Application-Id',10415,[4],[]}, 'Grouped',10}}] I would greatly appreciate it if someone from the community could provide insights into the following: 1. Possible Configurations: Are there specific configurations or modules in Kamailio that might cause the inclusion of non-standard AVPs in CCR messages? 2. IMS Ro Interface Behavior: Does anyone have experience with IMS Ro interface behavior using Kamailio that could shed light on this? If you have any guidance, suggestions, or solutions to help me troubleshoot and resolve this problem, please share them. Thank you for your assistance. [View Less]

2 1

kamcmd reload is slow or blocking additional reloads
by Martin Nyström 06 Sep '23

06 Sep '23

Hello, Running ”kamcmd permissions.trustedReload” it instantly returns “Reload OK” but I cannot repeat the reload for about 8 seconds. This is the same for dialplan.reload and dispatcher.reload. root@superman.local:/# kamcmd permissions.trustedReload Reload OK root@superman.local:/# kamcmd permissions.trustedReload error: 500 - ongoing reload root@superman.local:/# kamcmd permissions.trustedReload error: 500 - ongoing reload There are scenarios where I might need to reload the permission … [View More]

4 6

关于acc_cdr的问题，请教一下
by bikq＠163.com 05 Sep '23

05 Sep '23

目前进行一通呼叫后，在acc表中可以看到Invite、ack及bye的记录详情并带有时间，acc_cdrs表中只有start_time及end_time,是对应invite和bye的。现在我想在acc_cdrs中增加ack的时间我该如何去做呢？有没有大佬能解答一下？万分感谢！！！

1 0

Configuring package memory
by Ivan Ribakov 05 Sep '23

05 Sep '23

Is there any specific reason why shared memory can be configured via the config files ("shm_mem_size") AND CLI flags ("-m") but package memory can only be set via CLI flags ("-M")? Did no one ever came across the need to configure the package memory limit so far, or is there another way to achieve it without using the CLI flag? -- Ivan Ribakov Software Engineer www.zaleos.net

3 2

Re: Kamailio stops processing UDP on one interface
by Ihor Olkhovskyi 31 Aug '23

31 Aug '23

Bastian, According to mine stats all seems ok... # kamctl stats shmem { "jsonrpc": "2.0", "result": [ "shmem:fragments = 330", "shmem:free_size = 1889418024", "shmem:max_used_size = 258962624", "shmem:real_used_size = 258065624", "shmem:total_size = 2147483648", "shmem:used_size = 248809096" ], "id": 212042 } pkg.stats also not showing any signs of exhausting. For me what is working is server can send packets, but not receive em back even. And … [View More]it's happening only on 1 interface. Le 30/08/2023 à 21:44, Bastian Triller a écrit : > I'm asking, because we kind of observed similar behaviour after > overload. We've did some load testing and at some point SHM was > exhausted and that didn't recover itself. One process was using nearly > 100% CPU. And I guess that at least sl replies still works at that point. > > On Wed, Aug 30, 2023 at 9:28 PM Ihor Olkhovskyi > <igorolhovskiy(a)gmail.com> wrote: > > Bastian, > > I'm fine with retransmissions and so, but for me it's really > interesting, that server is not restoring it's state after a while > and only restart helps. And this is happening only with UDP on one > interface, others are working fine over UDP > > Le 30/08/2023 à 17:19, Bastian Triller a écrit : >> Maybe it's not beneficial to have a receive buffer that high. If >> your presence server is stateful, it will send retransmissions if >> packets get dropped. But it will also send retransmissions if >> your proxy does not reply fast enough. So your proxy may be >> damped by retransmissions. Did you check SHM/active transactions >> on your proxy? >> >> Regards, >> Bastian >> >> On Wed, Aug 30, 2023 at 3:56 PM Ihor Olkhovskyi >> <igorolhovskiy(a)gmail.com> wrote: >> >> They are increasing, actually >> >> # ss -l -u -m src X.X.X.X/Y >> State Recv-Q Send-Q Local >> Address:Port Peer Address:Port >> UNCONN 25167616 0 X.X.X.X:sip *:* >> skmem:(r25167616,rb25165824,t0,tb65536,f2304,w0,o0,bl0,d514894) >> >> Le mer. 30 août 2023 à 15:04, Bastian Triller >> <bastian.triller(a)gmail.com> a écrit : >> >> Are drops increasing on that socket while it is happening? >> ss -l src <local_interface> -u sport 5060 -m >> >> On Tue, Aug 29, 2023 at 3:26 PM Ihor Olkhovskyi >> <igorolhovskiy(a)gmail.com> wrote: >> >> Just to add some info >> >> netstat -nlp >> Active Internet connections (only servers) >> Proto Recv-Q Send-Q Local Address Foreign Address >> State PID/Program name >> ... >> udp 25167616 0 <local_interface>:5060 >> 0.0.0.0:* 211759/kamailio >> ... >> >> So I see a huge Receive Queue on UDP for Kamailio >> which is not clearing. >> >> Le mar. 29 août 2023 à 14:29, Ihor Olkhovskyi >> <igorolhovskiy(a)gmail.com> a écrit : >> >> Hello, >> >> I've faced a bit strange issue, but a bit of >> preface. I have Kamailio as a proxy (TLS/WS <-> >> UDP) and second Kamailio as a presence server. At >> some point presence server accepts around 5K >> PUBLISH within 1 minute and sending around the >> same amount of NOTIFY to proxy Kamailio. >> >> Proxy is "transforming" protocol to TLS, but at >> sime point I'm starting to get these type of errors >> >> tm [../../core/forward.h:292]: msg_send_buffer(): >> tcp_send failed >> tm [t_fwd.c:1588]: t_send_branch(): sending >> request on branch 0 failed >> <script>: [RELAY] Relay to >> <sip:X.X.X.X:51571;transport=tls> failed! >> tm [../../core/forward.h:292]: msg_send_buffer(): >> tcp_send failed >> tm [t_fwd.c:1588]: t_send_branch(): sending >> request on branch 0 failed >> >> Some of those messages are 100% valid as client >> can go away or so. Some are not, cause I'm sure >> client is alive and connected. >> >> But the problem comes later. At some moment proxy >> Kamailio just stops accept UDP traffic on this >> interface (where it also accepts all NOTIFY's), >> at the start of the "stopping accepting" Kamailio >> sends OPTIONS via DISPATCHER but not able to >> receive 200 OK. >> >> Over TLS on the same interface all is ok. On >> other (loopback) interface UDP is being processed >> fine, so I don't suspert some limit on open files >> here. >> >> Only restart of Kamailio proxy process helps in >> this case. >> >> I've tuned net.core.rmem_max and >> net.core.rmem_default to 25 Mb, so in theory >> buffer should not be the case. >> >> Is there some internal "interface buffer" in >> Kamailio that is not freed upon failure send or >> maybe I've missed somethig? >> >> Kamailio 5.6.4 >> >> fork=yes >> children=12 >> tcp_children=12 >> >> enable_tls=yes >> >> tcp_accept_no_cl=yes >> tcp_max_connections=63536 >> tls_max_connections=63536 >> tcp_accept_aliases=no >> tcp_async=yes >> tcp_connect_timeout=10 >> tcp_conn_wq_max=63536 >> tcp_crlf_ping=yes >> tcp_delayed_ack=yes >> tcp_fd_cache=yes >> tcp_keepalive=yes >> tcp_keepcnt=3 >> tcp_keepidle=30 >> tcp_keepintvl=10 >> tcp_linger2=30 >> tcp_rd_buf_size=80000 >> tcp_send_timeout=10 >> tcp_wq_blk_size=2100 >> tcp_wq_max=10485760 >> open_files_limit=63536 >> >> Sysctl >> >> # To increase the amount of memory available for >> socket input/output queues >> net.ipv4.tcp_rmem = 4096 25165824 25165824 >> net.core.rmem_max = 25165824 >> net.core.rmem_default = 25165824 >> net.ipv4.tcp_wmem = 4096 65536 25165824 >> net.core.wmem_max = 25165824 >> net.core.wmem_default = 65536 >> net.core.optmem_max = 25165824 >> >> # To limit the maximum number of requests queued >> to a listen socket >> net.core.somaxconn = 128 >> >> # Tells TCP to instead make decisions that would >> prefer lower latency. >> net.ipv4.tcp_low_latency=1 >> >> # Optional (it will increase performance) >> net.core.netdev_max_backlog = 1000 >> net.ipv4.tcp_max_syn_backlog = 128 >> >> # Flush the routing table to make changes happen >> instantly. >> net.ipv4.route.flush=1 >> -- >> Best regards, >> Ihor (Igor) >> >> >> >> -- >> Best regards, >> Ihor (Igor) >> __________________________________________________________ >> 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: >> >> __________________________________________________________ >> 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: >> >> >> >> -- >> Best regards, >> Ihor (Igor) >> __________________________________________________________ >> 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: >> >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email tosr-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: > [View Less]

1 0

Install Kamailio 5.3
by Daniel Oliveira Hilário 30 Aug '23

30 Aug '23

Hi people, I installed Kamailio 5.3 on Ubuntu Server 22 LTS, but I am not able to resolve several PHP errors that occur when I try to open the website http://localhost/siremis/. Which Linux distro and version is best suited for installation? Is Kamailio version 5.3 operational or is it better to use version 4.4? Att., Daniel Hilário INFRACOM/UFRGS 51 3308 4801

2 1

Kamailio stops processing UDP on one interface
by Ihor Olkhovskyi 30 Aug '23

30 Aug '23

Hello, I've faced a bit strange issue, but a bit of preface. I have Kamailio as a proxy (TLS/WS <-> UDP) and second Kamailio as a presence server. At some point presence server accepts around 5K PUBLISH within 1 minute and sending around the same amount of NOTIFY to proxy Kamailio. Proxy is "transforming" protocol to TLS, but at sime point I'm starting to get these type of errors tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed tm [t_fwd.c:1588]: t_send_branch(): … [View More]sending request on branch 0 failed <script>: [RELAY] Relay to <sip:X.X.X.X:51571;transport=tls> failed! tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed tm [t_fwd.c:1588]: t_send_branch(): sending request on branch 0 failed Some of those messages are 100% valid as client can go away or so. Some are not, cause I'm sure client is alive and connected. But the problem comes later. At some moment proxy Kamailio just stops accept UDP traffic on this interface (where it also accepts all NOTIFY's), at the start of the "stopping accepting" Kamailio sends OPTIONS via DISPATCHER but not able to receive 200 OK. Over TLS on the same interface all is ok. On other (loopback) interface UDP is being processed fine, so I don't suspert some limit on open files here. Only restart of Kamailio proxy process helps in this case. I've tuned net.core.rmem_max and net.core.rmem_default to 25 Mb, so in theory buffer should not be the case. Is there some internal "interface buffer" in Kamailio that is not freed upon failure send or maybe I've missed somethig? Kamailio 5.6.4 fork=yes children=12 tcp_children=12 enable_tls=yes tcp_accept_no_cl=yes tcp_max_connections=63536 tls_max_connections=63536 tcp_accept_aliases=no tcp_async=yes tcp_connect_timeout=10 tcp_conn_wq_max=63536 tcp_crlf_ping=yes tcp_delayed_ack=yes tcp_fd_cache=yes tcp_keepalive=yes tcp_keepcnt=3 tcp_keepidle=30 tcp_keepintvl=10 tcp_linger2=30 tcp_rd_buf_size=80000 tcp_send_timeout=10 tcp_wq_blk_size=2100 tcp_wq_max=10485760 open_files_limit=63536 Sysctl # To increase the amount of memory available for socket input/output queues net.ipv4.tcp_rmem = 4096 25165824 25165824 net.core.rmem_max = 25165824 net.core.rmem_default = 25165824 net.ipv4.tcp_wmem = 4096 65536 25165824 net.core.wmem_max = 25165824 net.core.wmem_default = 65536 net.core.optmem_max = 25165824 # To limit the maximum number of requests queued to a listen socket net.core.somaxconn = 128 # Tells TCP to instead make decisions that would prefer lower latency. net.ipv4.tcp_low_latency=1 # Optional (it will increase performance) net.core.netdev_max_backlog = 1000 net.ipv4.tcp_max_syn_backlog = 128 # Flush the routing table to make changes happen instantly. net.ipv4.route.flush=1 -- Best regards, Ihor (Igor) [View Less]

3 5

[OT] Code 868 reply to SIP OPTIONS ?
by Olivier 30 Aug '23

30 Aug '23

Hello, Have you ever seen a SIP device replying with code 868 to a SIP OPTIONS request ? Best regards

1 1

How to forward 480
by Anthony Blandin 29 Aug '23

29 Aug '23

Hello, I have a Kamailio SBC connected to another foreign SBC and to a media server. In case of non response, Kamailio SBC receives a 480 Temporarily not available from the foreign SBC and I need to forward this 480 to my media server but I don't see how to do that. The 480 arrives in the onreply_route. If I use then a failure_route, it resends the initial INVITE and not the 480. Is there a way to do that? Thanks for your help. Anthony Blandin

2 1

Re: extreme dildoes
by Angel Elena 27 Aug '23

27 Aug '23

I think is better sip over tls to extra protection xD Sent from Android device El 26 ago 2023 12:59, Julien Chavanton <jchavanton(a)gmail.com> escribió: Are you trying to connect them over SIP ? On Sat, Aug 26, 2023, 6:06 AM <feigelwang(a)uusextoy.com <mailto:feigelwang@uusextoy.com> > wrote: So, when you still are alone, buying a huge dildo is worth it. Enjoy sex with the huge realistic dildo anytime and anywhere. Not only that, the big dildo brings completely different … [View More]

1 0

extreme dildoes
by feigelwang＠uusextoy.com 27 Aug '23

27 Aug '23

So, when you still are alone, buying a huge dildo is worth it. Enjoy sex with the huge realistic dildo anytime and anywhere. Not only that, the big dildo brings completely different sexual stimulation. Maybe you want to enjoy full sex, should try some other sex toys. https://www.hugedildo.com/

6 5

large dildo
by feigelwang＠uusextoy.com 26 Aug '23

26 Aug '23

Or, if you are good at Google search, I believe you can definitely find more ways to play the big dildo. All in all, huge dildos are the best sex toy for singles. For single women, it’s vaginal masturbation. For single men, it’s anal sex. https://www.hugedildo.com/

1 0

large dildo
by feigelwang＠uusextoy.com 26 Aug '23

26 Aug '23

Or, if you are good at Google search, I believe you can definitely find more ways to play the big dildo. All in all, huge dildos are the best sex toy for singles. For single women, it’s vaginal masturbation. For single men, it’s anal sex.https://www.hugedildo.com/

1 0

extreme dildoes
by feigelwang＠uusextoy.com 26 Aug '23

26 Aug '23

So, when you still are alone, buying a huge dildo is worth it. Enjoy sex with the huge realistic dildo anytime and anywhere. Not only that, the big dildo brings completely different sexual stimulation. Maybe you want to enjoy full sex, should try some other sex toys.https://www.hugedildo.com/

1 0

rtpengine large number used RTP ports
by marek 25 Aug '23

25 Aug '23

hi, i have open around ~8000 rtp ports for around ~200calls (in peak) with this statistic (current data, not from peak) rtpengine_closed_sessions_total{reason="rejected"} 0 rtpengine_closed_sessions_total{reason="timeout"} 237405 rtpengine_closed_sessions_total{reason="silent_timeout"} 103 rtpengine_closed_sessions_total{reason="final_timeout"} 0 rtpengine_closed_sessions_total{reason="offer_timeout"} 0 rtpengine_closed_sessions_total{reason="terminated"} 0 rtpengine_request_seconds_total{… [View More]

2 3

excessive CANCELs
by James Lipski 23 Aug '23

23 Aug '23

Hello, I've already suppressed this via routing logic, however I was wondering if there is a dedicated parameter that handles this. I'm currently running version 5.6.4. Scenario: UA-1 registered towards kamailio, calls UA-2 which is registered towards a different platform (non kamailio); so there are 2 proxys involved. kamailio is set to fork the call to voicemail if there is either no response completely from the other end, or the call goes unanswered. So the initial leg is: UA-1 <-----… [View More]> kamailio <-----> second proxy <-----> UA-2 Issue: I'm trying to catch a case where the second proxy does issue a "100 Trying" for the initial INVITE; and then timesout. The call does fork to voicemail; however 14000+ SIP packets are generated between kamailio and the second proxy of CANCEL and "100 Trying" (the 100 Trying has a CSeq for INVITE still). Is there a way to suppress the amount of CANCELs that is transmitted in this situation? I'm using the following as my "tm" parameters: modparam("tm", "failure_reply_mode", 3) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 300000) modparam("tm", "auto_inv_100_reason", "Trying") Thanks. Example SIP trace: (UA-1 --> kamailio) 72.255.255.255 --> 10.64.52.110 INVITE sip:131@sip-example.com SIP/2.0 v: SIP/2.0/UDP 10.0.0.102:51519;branch=z9hG4bK-xfelmyyjzne5;rport f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 70 User-Agent: snomD785/10.1.152.12 m: <sip:133@10.0.0.102:51519;line=6dv00d6r>;reg-id=1 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 Proxy-Authorization: Digest username="133",realm="sip-example.com",nonce="ZOTEBGTkwtiM22ZE8IJsn/esiW3CZrt0"[,uri="sip:131@sip-example.com](mailto:,uri=)",response="fb44b4fe0f8fb17de13f043cf1248e14",algorithm=MD5 c: application/sdp l: 309 v=0 o=root 481174289 481174289 IN IP4 10.0.0.102 s=call c=IN IP4 10.0.0.102 t=0 0 m=audio 50864 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- (UA-1 <-- kamailio) 72.255.255.255 <-- 10.64.52.110 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.0.0.102:51519;branch=z9hG4bK-xfelmyyjzne5;rport=51519;received=72.255.255.255 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Content-Length: 0 -------------------------------------------- (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 INVITE sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 15 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 313 Contact: <sip:leg_1@sip-example.com;ccr=btpsh-64e387e0-ee528-2> v=0 o=root 481174289 481174289 IN IP4 10.64.52.111 s=call c=IN IP4 10.64.52.111 t=0 0 m=audio 34084 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- (kamailio <-- second proxy) 10.64.52.110 <-- 10.64.52.100 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE l: 0 -------------------------------------------- After 10 seconds of no further response from second proxy, call is forked to voicemail (kamailio --> voicemail) 10.64.52.110 --> 10.64.56.10 INVITE sip:voicemail@voicemail-example.com SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.1 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Max-Forwards: 15 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, replaces, from-change Session-Expires: 3600 Min-SE: 90 c: application/sdp l: 313 Contact: <sip:leg_1@sip-example.com;ccr=btpsh-64e387e0-ee533-3> v=0 o=root 481174289 481174289 IN IP4 10.64.52.111 s=call c=IN IP4 10.64.52.111 t=0 0 m=audio 38722 RTP/AVP 9 0 8 18 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv -------------------------------------------- At roughly the same time, CANCEL is issued towards the second proxy (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 CANCEL sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 CANCEL Max-Forwards: 15 l: 0 -------------------------------------------- (kamailio <-- voicemail) 10.64.52.110 <-- 10.64.56.10 SIP/2.0 200 Ok Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.1 From: <sip:133@sip-example.com>;tag=i4mlq4jr0y To: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133>;tag=vzx5x3mlbd Call-ID: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Contact: <sip:voicemail@10.64.56.10:5078> Require: timer Session-Expires: 3600;refresher=uac Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Supported: timer, 100rel, replaces Content-Type: application/sdp Content-Length: 264 v=0 o=root 1084843702 1084843703 IN IP4 10.64.56.10 s=call c=IN IP4 10.64.56.10 t=0 0 m=audio 31908 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=alt:1 0.9 : user 9kksj== 10.64.56.10 31908 a=sendrecv -------------------------------------------- (UA-1 <-- kamailio) 72.255.255.255 <-- 10.64.52.110 SIP/2.0 200 Ok From: <sip:133@sip-example.com>;tag=i4mlq4jr0y To: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133>;tag=vzx5x3mlbd Call-ID: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE Require: timer Session-Expires: 3600;refresher=uac Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Supported: timer, 100rel, replaces Content-Type: application/sdp Content-Length: 270 Via: SIP/2.0/UDP 10.0.0.102:51519;received=72.255.255.255;branch=z9hG4bK-xfelmyyjzne5;rport=51519 Contact: <sip:leg_2@sip-example.com;ccr=atpsh-64e387e0-ee533-3> v=0 o=root 1084843702 1084843703 IN IP4 10.64.52.110 s=call c=IN IP4 10.64.52.110 t=0 0 m=audio 33552 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=alt:1 0.9 : user 9kksj== 10.64.56.10 31908 a=sendrecv =============================================== These next 2 SIP packets repeat, generating 14000+ CANCEL <--> 100 Trying transactions between kamailio, and the second proxy. (kamailio --> second proxy) 10.64.52.110 --> 10.64.52.100 CANCEL sip:second-proxy-example.com:5066;ua=43a58ecca39c9c8f37515e55b5b37ed7 SIP/2.0 Via: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com> i: 95c3e4642670-rx28v46dte4p CSeq: 1 CANCEL Max-Forwards: 15 l: 0 -------------------------------------------- (kamailio <-- second proxy) 10.64.52.110 <-- 10.64.52.100 SIP/2.0 100 Trying v: SIP/2.0/UDP 10.64.52.110:5060;branch=z9hG4bKecf9.6d10880e1353b8a7bbf0383d934a38a5.0 f: <sip:133@sip-example.com>;tag=i4mlq4jr0y t: <sip:131@sip-example.com?vm-ext%3D100%26ext-to%3D131%26ext-from%3D133> i: 95c3e4642670-rx28v46dte4p CSeq: 1 INVITE l: 0 [View Less]

2 2

Force communications for I-CSCF and S-CSCF to be TCP only
by hvanhelmondt＠peratonlabs.com 23 Aug '23

23 Aug '23

Hi, I would like to force the transport protocol between the I-CSCF and S-CSCF to be TCP only. How would I do that exactly? I'm using an older Kamailio release 5.0.8. Regards,

2 2

use_dns_failover default value
by Silvan Nagl 23 Aug '23

23 Aug '23

Hi, I would like to know the reason for having "off" as default value for use_dns_failover. https://github.com/kamailio/kamailio/issues/3547 Greetings, Silvan

5 4

Kamailio 5.5.4 pua module memory leak
by Vladyslav Korniiaka 20 Aug '23

20 Aug '23

Hello! We are facing a Kamailio memory leak with the pua module, pua module consumes about 2GBs: kamcmd mod.stats all shm Module: pua { add_pua_event(72): 648 init_pua_evlist(36): 56 new_htable(79): 8192 init_puacb_list(35): 16 new_htable(64): 8 publ_cback_func(409): 12451504 publ_cback_func(363): 1658482848 update_htable(203): 210590960 new_htable(93): 131512 Total: 1881665744 } Module: pua_dialoginfo { get_str_list(463): 344 get_dialog_data(500): 1744 Total: 2088 } PUA … [View More]Module parameters: loadmodule "pua.so" loadmodule "pua_dialoginfo" # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) modparam("pua", "outbound_proxy", PUA_PROXY) modparam("pua", "db_table_lock_write", 0) modparam("pua", "update_period", 0) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 0) modparam("pua", "fetch_rows", 1000) modparam("pua", "default_expires", 30) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_PUBLISH) modparam("pua_dialoginfo", "caller_confirmed", 1) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "include_localremote", 0) modparam("pua_dialoginfo", "use_pubruri_avps", 1) modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") *- Kamailio 5.5.4 (x86_64/linux), installed from .deb packages:* kamailio --version version: kamailio 5.5.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 8.3.0 *- Kamailio is runned in Docker:* docker --version Docker version 20.10.21, build baeda1f *- With “Debian GNU/Linux 10” docker image:* cat /etc/issue Debian GNU/Linux 10 \n \l *- Host OS is “Ubuntu 18.04.6 LTS”:* cat /etc/issue Ubuntu 18.04.6 LTS \n \l *- Server is AWS EC2 with CPU:* lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz Stepping: 7 CPU MHz: 3599.769 BogoMIPS: 5999.98 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 36608K NUMA node0 CPU(s): 0-7 Please tell me if you need any additional information about this issue. Thanks for helping me with this! -- Regards, Vladyslav Korniiaka vladyslav.korniiaka(a)net2phone.com [View Less]

2 1

Kamailio 5.5.4 pua module memory leak
by vladyslav.korniiaka＠idt.net 20 Aug '23

20 Aug '23

Hello! We are facing a Kamailio memory leak with the pua module, pua module consumes about 2GBs: kamcmd mod.stats all shm Module: pua { add_pua_event(72): 648 init_pua_evlist(36): 56 new_htable(79): 8192 init_puacb_list(35): 16 new_htable(64): 8 publ_cback_func(409): 12451504 publ_cback_func(363): 1658482848 update_htable(203): 210590960 new_htable(93): 131512 Total: 1881665744 } Module: pua_dialoginfo { get_str_list(463): 344 get_dialog_data(500): 1744 Total: 2088 } PUA … [View More]Module parameters: loadmodule "pua.so" loadmodule "pua_dialoginfo" # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) modparam("pua", "outbound_proxy", PUA_PROXY) modparam("pua", "db_table_lock_write", 0) modparam("pua", "update_period", 0) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 0) modparam("pua", "fetch_rows", 1000) modparam("pua", "default_expires", 30) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_PUBLISH) modparam("pua_dialoginfo", "caller_confirmed", 1) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "include_localremote", 0) modparam("pua_dialoginfo", "use_pubruri_avps", 1) modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") - Kamailio 5.5.4 (x86_64/linux), installed from .deb packages: - Kamailio 5.5.4 (x86_64/linux), installed from .deb packages: kamailio --version version: kamailio 5.5.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 8.3.0 - Kamailio is runned in Docker: docker --version Docker version 20.10.21, build baeda1f - With “Debian GNU/Linux 10” docker image: cat /etc/issue Debian GNU/Linux 10 \n \l - Host OS is “Ubuntu 18.04.6 LTS”: cat /etc/issue Ubuntu 18.04.6 LTS \n \l - Server is AWS EC2 with CPU: lscpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz Stepping: 7 CPU MHz: 3599.769 BogoMIPS: 5999.98 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 36608K NUMA node0 CPU(s): 0-7 Please tell me if you need any additional information about this issue. Thanks for helping me with this! -- Regards, Vladyslav Korniiaka vladyslav.korniiaka(a)net2phone.com [View Less]

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users