- sr-users - kamailio.org

Several crashs in prepare_new_uac
by Igor Potjevlesch 26 Sep '23

26 Sep '23

Hello! We had several crashs of Kamailio (5.3.4) in the last weeks. Each time, the last logs are: /usr/local/sbin/kamailio[20942]: CRITICAL: <core> [core/forward.c:347]: get_send_socket2(): unsupported proto 0 (*) /usr/local/sbin/kamailio[20966]: CRITICAL: <core> [core/forward.c:347]: get_send_socket2(): unsupported proto 111 (unknown) When we look to the coredump, here below the first traces: (gdb) bt #0 0x00007f70131b3d91 in prepare_new_uac (t=0x7f6fe1d45340, i_req=0x7f7016fbe208, branch=0, uri=0x7fff37142fa0, path=0x7fff37142f80, next_hop=0x7f7016fbe480, fsocket=0x0, snd_flags=..., fproto=0, flags=2, instance=0x7fff37142f70, ruid=0x7fff37142f60, location_ua=0x7fff37142f50) at t_fwd.c:463 #1 0x00007f70131b7c42 in add_uac (t=0x7f6fe1d45340, request=0x7f7016fbe208, uri=0x7f7016fbe480, next_hop=0x7f7016fbe480, path=0x7f7016fbe848, proxy=0x0, fsocket=0x0, snd_flags=..., proto=0, flags=2, instance=0x7f7016fbe858, ruid=0x7f7016fbe870, location_ua=0x7f7016fbe880) at t_fwd.c:805 #2 0x00007f70131bfebd in t_forward_nonack (t=0x7f6fe1d45340, p_msg=0x7f7016fbe208, proxy=0x0, proto=0) at t_fwd.c:1667 #3 0x00007f701316cf44 in t_relay_to (p_msg=0x7f7016fbe208, proxy=0x0, proto=0, replicate=0) at t_funcs.c:332 #4 0x00007f70131a3a11 in _w_t_relay_to (p_msg=0x7f7016fbe208, proxy=0x0, force_proto=0) at tm.c:1689 #5 0x00007f70131a4c51 in w_t_relay (p_msg=0x7f7016fbe208, _foo=0x0, _bar=0x0) at tm.c:1889 #6 0x00000000005a1f57 in do_action (h=0x7fff37143d90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1071 #7 0x00000000005aeb1e in run_actions (h=0x7fff37143d90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1576 #8 0x00000000005af1df in run_actions_safe (h=0x7fff37146e90, a=0x7f7016bd1b10, msg=0x7f7016fbe208) at core/action.c:1640 #9 0x000000000066aa50 in rval_get_int (h=0x7fff37146e90, msg=0x7f7016fbe208, i=0x7fff37144238, rv=0x7f7016bd1e60, cache=0x0) at core/rvalue.c:915 #10 0x000000000066f000 in rval_expr_eval_int (h=0x7fff37146e90, msg=0x7f7016fbe208, res=0x7fff37144238, rve=0x7f7016bd1e58) at core/rvalue.c:1913 #11 0x000000000066f453 in rval_expr_eval_int (h=0x7fff37146e90, msg=0x7f7016fbe208, res=0x7fff371446ec, rve=0x7f7016bd2588) at core/rvalue.c:1921 #12 0x00000000005a1a1d in do_action (h=0x7fff37146e90, a=0x7f7016bd2e08, msg=0x7f7016fbe208) at core/action.c:1047 #13 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016bcbd20, msg=0x7f7016fbe208) at core/action.c:1576 #14 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016ef19b8, msg=0x7f7016fbe208) at core/action.c:695 #15 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016e3f578, msg=0x7f7016fbe208) at core/action.c:1576 #16 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016c220a0, msg=0x7f7016fbe208) at core/action.c:695 #17 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c220a0, msg=0x7f7016fbe208) at core/action.c:1576 #18 0x00000000005aae93 in do_action (h=0x7fff37146e90, a=0x7f7016c23978, msg=0x7f7016fbe208) at core/action.c:1207 #19 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c20748, msg=0x7f7016fbe208) at core/action.c:1576 #20 0x00000000005a1ec6 in do_action (h=0x7fff37146e90, a=0x7f7016c576a0, msg=0x7f7016fbe208) at core/action.c:1062 #21 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016c0b770, msg=0x7f7016fbe208) at core/action.c:1576 #22 0x000000000059e97d in do_action (h=0x7fff37146e90, a=0x7f7016bc9920, msg=0x7f7016fbe208) at core/action.c:695 #23 0x00000000005aeb1e in run_actions (h=0x7fff37146e90, a=0x7f7016bb9100, msg=0x7f7016fbe208) at core/action.c:1576 #24 0x00000000005af2a7 in run_top_route (a=0x7f7016bb9100, msg=0x7f7016fbe208, c=0x0) at core/action.c:1661 #25 0x00000000005bcb7a in receive_msg ( buf=0xadbd80 <buf.6971> "INVITE sip:AAAAAAAAAA@W.X.Y.Z SIP/2.0\r\nVia: SIP/2.0/UDP W.X.Y.Z;rport;branch=z9hG4bKZD8Za7p2XF7cF\r\nMax-Forwards: 69\r\nFrom: \"AAAAAAAAAA\" sip:AAAAAAAAAA@W.X.Y.Z;tag=aXy4Na2NtvKBK\r\nTo: <"..., len=1011, rcv_info=0x7fff371474c0) at core/receive.c:423 #26 0x0000000000488e7f in udp_rcv_loop () at core/udp_server.c:548 #27 0x000000000042650f in main_loop () at main.c:1673 #28 0x000000000042ec18 in main (argc=7, argv=0x7fff37147c38) at main.c:2802 Is there anything relevant in this to know what's wrong? Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

3 4

Planning Kamailio Developers Meeting 2023
by Daniel-Constantin Mierla 26 Sep '23

26 Sep '23

Hello, we are considering to organize another edition of Kamailio Developers Meeting, to be hosted again by sipgate.de in Dusseldorf, Germany. There is no fee for participants (i.e., free entry), but each one has to take care of travelling and accommodation (drinks and food are provided during the day). A few developers are already on board, we are looking to see if anyone else from the broader community wants to join us. Likely it is going to be during 2 days (with the option of doing it during three days still open at this moment, if there is going to be enough interest to have it longer). The proposed time frames are: - Nov 7-9, 2023 - Nov 21-23, 2023 The event is about discussing the internals of Kamailio (e.g., architectural changes, development strategies) and writing code or documentation for it. This is not an event about learning how to use Kamailio, but to work on improving it. As a bonus, there will be a social networking event in the evening with some fun activities, drinks and food. If you want to join, state your preference for any of the two time frames (or even just for 2 days in one of the two time frames). It is not a large meeting room, if we get too many join requests, we may have to select based on past contributions, and if that is not the case, then is just the first come first served. You can reply to this thread or just write me directly if you want to join and when you prefer to happen. By mid of next week, we plan to select the event dates so everyone that comes to it can start planning the trip. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy - Training Services -- asipto.com Kamailio World Conference - kamailioworld.com

1 1

Iterating Through Multiple IP Peers for DID Call Termination in Kamailio
by Shah Hussain Khattak 26 Sep '23

26 Sep '23

Hello Team, I hope you're all doing well. I'm reaching out to request your insights on the following scenario. Overview: I have successfully configured Kamailio to authenticate IP addresses, primarily for PBXs and customers unable to register. With this setup, I can flawlessly receive incoming traffic and forward it to our internal FreeSwitch servers. Current issue: Now, I'm focusing on managing traffic in the opposite direction—specifically for DIDs. I have a DID table set up in Kamailio that associates DID numbers with their respective IP peers. Upon receiving a call, a database lookup is performed to find the destination number, after which the call is terminated at the customer's IP. I'm facing difficulty in handling situations where a customer has multiple IP peers (for redundancy). My aim is to try each of these IPs sequentially when terminating a specific DID call towards them. The current logic I'm employing for the INVITE lookup looks like this: # Database lookup for INVITEs if (is_method("INVITE")) { sql_query("didrouting_db", "SELECT route_to FROM did_routing WHERE did_number='$rU'", "result"); if ($dbr(result=>rows) > 0) { $var(route_to) = $dbr(result=>[0,0]); xlog("L_INFO", "Routing DID $rU to $var(route_to)\n"); $du = "sip:" + $var(route_to) + ":5060"; } else { $du = "sip:" + FS_IP + ":5060"; } } The above logic works fine for a single IP. I intend to use a comma-separated list of IPs in my route_to column (for example 192.168.1.2,192.168.1.3, ...) and then iterate through these IPs one by one. I'm having trouble coming up with a workable logic or loop to achieve this. Would you be able to offer any guidance or suggestions? Please also recommend if there is a better approach available to handle this scenario. Thank you in advance for your valuable input. Regards, Shah Hussain

4 3

TM max_inv_lifetime being reset by downstream responses
by James Browne 25 Sep '23

25 Sep '23

Hi all I see this old thread from 2015. - https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… It's about max_inv_lifetime not working properly. I have this problem today: SIP-180 responses from downstream apparently reset max_inv_lifetime, and the transaction can live for hours (apparently indefinitely) even though max_inv_lifetime is set to just over a minute. By spacing the SIP-180 responses (from downstream) slightly longer apart than than max_inv_lifetime in kamailio, I don't get the problem, so it looks to me that this is TM not matching what's in the documentation (which mentions that this should be a hard limit). With this configuration, SIP-180 responses every minute result in the transaction never ending (until the client CANCELs the call). - kamailio.cfg:modparam("tm", "fr_timer", 3000) - kamailio.cfg:modparam("tm", "fr_inv_timer", 300000) - kamailio.cfg:modparam("tm", "max_inv_lifetime", 65000) - kamailio.cfg:modparam("tm", "noisy_ctimer", 1) That other thread ends with Daniel mentioning that he'd have to look at the code, but nothing further. Running "git log --grep max_inv_lifetime" shows me that the last/only update that wasn't just documentation was in 2007. Has anyone got an ideas? James

2 2

Modifying SDP as drop-in replacement for overloaded Asterisk box - looking for help/paid consulting fast
by Markus 23 Sep '23

23 Sep '23

Hi list, I'm trying to use Kamailio 4.4.4 with rtpengine in a self-inflicted emergency situation (didn't monitor traffic growth properly and now encountering packet loss during peak times) as a drop-in replacement for an overloaded Asterisk box in a call-termination-to-upstream-carrier scenario. My test scenario is to make a call from a SIP softphone to Asterisk IP 1.1.1.1 -> Kamailio/rtpengine IP 2.2.2.2 -> Upstream carrier 3.3.3.3 sngrep on Kamailio box 2.2.2.2 - the following SDP will not work - carrier is rejecting it. Carrier is authenticating our calls based on our IP address 2.2.2.2, no username/pass involved. 2023/09/22 02:06:49.216136 2.2.2.2:5060 -> 3.3.3.3:5060 INVITE sip:+32xxxxxxxx@2.2.2.2;user=phone SIP/2.0 Record-Route: <sip:2.2.2.2;lr> Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKd9c3.d6fa3abe5d52b827e2054de5573028e0.0 Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK473270e8 Max-Forwards: 69 From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@1.1.1.1>;tag=as3d75aadd To: <sip:+32xxxxxxxx@2.2.2.2;user=phone> Contact: <sip:+61xxxxxxxxx@1.1.1.1:5060> Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@1.1.1.1:5060 CSeq: 102 INVITE User-Agent: Asterisk PBX 20.0.0 Date: Fri, 22 Sep 2023 00:06:50 GMT Session-Expires: 1800 Min-SE: 90 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer P-Asserted-Identity: <sip:+61xxxxxxxxx@2.2.2.2;user=phone> Content-Type: application/sdp Content-Length: 314 X-SIP: 1.1.1.1 v=0 o=root 1093000903 1093000903 IN IP4 1.1.1.1 s=Asterisk PBX 20.0.0 c=IN IP4 2.2.2.2 t=0 0 m=audio 25742 RTP/AVP 8 9 0 101 a=maxptime:150 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:25743 a=ptime:20 I'm comparing this rejected INVITE to a successful INVITE sent by the original Asterisk box at IP 2.2.2.2 (now Kamailio box) to the carrier without Kamailio in the path, and these are the differences I noticed, and probably the things I have to mimick with Kamailio in order to make it work: INVITE sip:+32xxxxxxxxx@2.2.2.2;user=phone SIP/2.0 should be INVITE sip:+32xxxxxxxxx@3.3.3.3;user=phone SIP/2.0 To: <sip:+32xxxxxxxx@2.2.2.2;user=phone> should be To: <sip:+32xxxxxxxx@3.3.3.3;user=phone> From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@1.1.1.1>;tag=as3d75aadd should be From: "61xxxxxxxxx" <sip:+61xxxxxxxxx@2.2.2.2>;tag=as3d75aadd Contact: <sip:+61xxxxxxxxx@1.1.1.1:5060> should be Contact: <sip:+61xxxxxxxxx@2.2.2.2:5060> Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@1.1.1.1:5060 should be Call-ID: 3f31e1622a72b6d17f24e42362f4f1d0@2.2.2.2:5060 o=root 1093000903 1093000903 IN IP4 1.1.1.1 should be o=root 1093000903 1093000903 IN IP4 2.2.2.2 My kamailio.cfg can be found here: https://pastebin.com/6PKcRjPU These are the Asterisk boxes I want to originate calls from to Kamailio: [root@voip30 ~]# kamctl address show +-----+-----+----------+------+------+-----------+ | id | grp | ip_addr | mask | port | tag | +-----+-----+----------+------+------+-----------+ | 195 | 1 | 1.1.1.1 | 32 | 0 | voip20.sv | | 196 | 1 | 1.1.1.2 | 32 | 0 | voip21.sv | | 197 | 1 | 1.1.1.3 | 32 | 0 | voip22.sv | | 198 | 1 | 1.1.1.4 | 32 | 0 | voip23.sv | | 199 | 1 | 1.1.1.5 | 32 | 0 | voip24.sv | | 200 | 1 | 1.1.1.6 | 32 | 0 | voip25.sv | | 201 | 1 | 1.1.1.7 | 32 | 0 | voip26.sv | | 202 | 1 | 1.1.1.8 | 32 | 0 | voip27.sv | | 203 | 1 | 1.1.1.9 | 32 | 0 | voip28.sv | +-----+-----+----------+------+------+-----------+ This is the upstream carrier I want Kamailio to proxy calls to: [root@voip30 ~]# kamctl dispatcher show dispatcher gateways +----+-------+------------------+-------+-------+------------+------+ | id | setid | destination | flags | prio. | attrs | desc | +----+-------+------------------+-------+-------+------------+------+ | 12 | 1 | sip:3.3.3.3:5060 | 0 | 0 | weight=100 | | +----+-------+------------------+-------+-------+------------+------+ (output manually slightly modified to look properly over E-Mail) As you might have guessed I'm a Kamailio noob... and don't have the resources to learn it as fast as I must to avoid further packet loss. If there's anyone available who can help me to get this done today, optionally in exchange for money, I'd be grateful. Thank you! Markus

5 11

Multi-dimensional data in htable
by Ben Kaufman 22 Sep '23

22 Sep '23

What's the best way to store multi-dimensional data within an htable? For example, storing an avp stack: $avp(foo) = "first"; $avp(foo) = "second"; $sht(bar=>foo) = $avp(foo); The result of which is that only $avp(foo[0]) is stored in the htable: kamcmd htable.dump bar { entry: 2 size: 1 slot: { { name: bar value: second type: str } } } The htable documentation shows support for lists, but it doesn't make clear if this is really usable outside of loading from a database, and looks like it's short hand for managing/creating linked lists. The other option would be to simply serialize the data before storing it in the htable - which is fine, I just want to be sure I'm not overlooking a more convenient method. Regards, Kaufman

4 5

no corresponding socket found error
by David Escartín 22 Sep '23

22 Sep '23

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) 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) 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) 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) 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) 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) 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) 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) 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) 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 listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 listen=tcp:192.168.96.105:8095 listen=tcp: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 listen=udp: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 we send it to 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"); set_send_socket("udp: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) 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) 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) 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) 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 aldso 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 -- <http://www.sonoc.io/> David Escartín NOC engineer www.sonoc.io [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Instagram] <https://www.instagram.com/sonoc.io/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: dataprotection(a)sonoc.io. <dataprotection(a)sonoc.io>

1 0

"no corresponding socket found" logs
by David Escartín 22 Sep '23

22 Sep '23

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) 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) 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) 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) 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) 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) 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) 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) 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) 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 listen=udp:192.168.99.81:5060 listen=udp:87.1.1.27:5060 listen=tcp:192.168.96.105:8095 listen=tcp: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 listen=udp: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 we send it to 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"); set_send_socket("udp: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) 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) 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) 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) 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 aldso 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 -- <http://www.sonoc.io/> David Escartín NOC engineer www.sonoc.io [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Instagram] <https://www.instagram.com/sonoc.io/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: dataprotection(a)sonoc.io. <dataprotection(a)sonoc.io>

1 0

Change in mailing list configuration related to DMARC spam filtering
by Henning Westerholt 22 Sep '23

22 Sep '23

Hello, due to some changes from certain cloud infrastructure provider related to spam filtering with DMARC, we need to change the list manager "mailman" configuration for the following lists: * sr-users * sr-user-es * sr-dev * business * sr-docs * kamailio-announce * the administrative mailing list The change will impact the "From" that is displayed in your email program. Without that change large e-mail providers (Gmail, Microsoft O365) will reject messages from a sender with certain strict DMARC policy. This is already affecting several people on the lists (for example with GitHub notice mails), but over time the problem will certainly increase. Regarding the technical change: We will munge the From: header so it doesn't contain the domain that triggers the DMARC rejection. Essentially, the Mailman list takes ownership of the message and injects its own address into the From: header. This can affect reply-to-sender, although we add the original From: address in the Reply-To: header (or sometimes the Cc: header) to reduce the impact of this. We plan to do this for all emails unconditionally, regardless of their sender DMARC policy, to have an identical behaviour for all users. Please refer to this [1] page for more details. For a general description of DMARC refer to this page [2]. This change should have not a big impact for you, but some users might need to adapt some mail filters. Therefore, we would like to gather feedback on that change from you. We expect that the most visible change is that It will be not possible anymore to just reply by e-mail to mails from GitHub and have them "automatically" added to the discussed issue. This feature was so far used rarely and only from a few people. We plan to implement this change by the end of this week, when its done it will be also shortly announced. Best regards, Henning Westerholt [1] https://wiki.list.org/DEV/DMARC [2] https://dmarc.org/overview/ -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

RTP traffic through kamailio
by Shravan 22 Sep '23

22 Sep '23

2 1

insert_dlg_timer(): Trying to insert a bogus dlg
by Benoît Panizzon 22 Sep '23

22 Sep '23

Hi Team Could anyone point me in the direction where I could find out more what's going wrong and what could be the cause of messages like: Sep 22 07:32:29 dev-core02 kamailio[915066]: CRITICAL: dialog [dlg_timer.c:129]: insert_dlg_timer(): Trying to insert a bogus dlg tl=0x7f9617d967b0 tl->next=0x7f9618e11198 tl->prev=0x7f9617e20548 Sep 22 07:32:29 dev-core02 kamailio[915066]: CRITICAL: dialog [dlg_dmq.c:314]: dlg_dmq_handle_msg(): Unable to insert dlg timer 0x7f9617d96750 [1598:12168] Are the numbers in brackets [hash_id:hash_entry] ? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Dialog: bogus event 2 in state 3
by Benoît Panizzon 21 Sep '23

21 Sep '23

Hi Team I'm still hunting dialog errors which cause my dialog counters to divert and stick around, basically exploding in my face now and then. I suppose they are DMQ related (maybe packet loss, maybe retransmissions, maybe generic overloading of the virtualized kamailio instances) causing issues with inserting dialog timers on the peer etc. So for the moment I'm running only one instance, no DMQ peer. What I still occasionally see are messages: INVITE]dialog [dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 3 for dlg 0x7ff906294be8 [2482:872] with clid 'A8459C74@7f33ff47' and tags '7f33ff47+1+7d820120+89494caf' '3904288054-1882699775' I found an ancient post, confirming this to be an open bug in Kamailio 1.4 and race condition between the 200 OK reply to an INVITE and the ACK confirming the 200 OK. Someone attempted to backport a fix for opensips to kamailio. Indeed, I see this message occur occasionally after managing the 200 OK reply and routing the ACK. Does anyone know, if this is still a open bug with Kamailio 5.5? Or what else could be the cause of this message? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Floating Point in variables and arithmetic
by Barry Flanagan 21 Sep '23

21 Sep '23

Hi I need to take in a priority (from 0 to 100, 0 being highest prio) and convert this into a Q value between 0 and 1.0 My idea was to simply do: q_value = 1 - ($var(priority)/100) However, it seems Kamailio only deals in integers in the config. A Previous post suggested using xavp vars, but this ends up the same result. Apart from doing a pseudo SQL query "SELECT 1 - (20/100)" is there any way within the config I can do such maths? Thanks -- -Barry Flanagan

2 8

uac_auth() in KEMI Python - Drop 401 sent to caller
by Marrold 21 Sep '23

21 Sep '23

Hi all, I'm attempting to use the uac module in KEMI (Python) to authenticate outbound requests. When the downstream replies with a 401 the proxy correctly re-sends the request with a Authorization header, but the 401 is also relayed to the caller. As far as I can tell I've converted the example to KEMI correctly, but no matter what I try the 401 is still sent to the caller. Any ideas? The config I'm using is below - The avps are set when the request is sent so aren't visible here. Thanks def ksr_failure_manage(self, msg): if self.ksr_route_natmanage(msg)==-255 : return 1 if KSR.tm.t_is_canceled()>0 : return 1 if KSR.tm.t_check_status("401|407") >0 : KSR.info(f"Got a 40X, should attempt authentication") if KSR.uac.uac_auth()>0: KSR.tm.t_relay() KSR.info (f"Dropping further replies") KSR.set_drop() exit() return 1

2 1

Handle the DNS SRV to manage failover
by Massimo Dal Sasso 20 Sep '23

20 Sep '23

I need to manage failover in the connection between SCSCF and AS. I need to understand how it is possible to configure Kamailio to handle the DNS SRV to manage failover for UAS transaction like REGISTER. I see that it works for UAC transaction like INVITE, but I am not able to configure Kamailio to work for UAS transaction. Thanks, Massimo ________________________________ Massimo Dal Sasso SW Developer massimo.dalsasso(a)ext.athonet.com [Athonet logo]<https://www.athonet.com/> the mobile core that works for you Athonet Italy Via Cà del Luogo 6/8 36050 Bolzano Vicentino Vicenza-Italy +39 0444 750045 This email and any attachments are confidential and intended solely for the use of the intended recipient. If you are not the named addressee, please be aware that you shall not distribute, copy, use or disclose this email. If you have received this email by error, please notify us immediately and delete this email from your system. Email transmission cannot be guaranteed to be secured or error-free or not to contain viruses. Athonet S.r.l. processes any personal data exchanged in email correspondence in accordance with EU Reg. 679/2016 (GDPR) - you may find here the privacy policy with information on such processing and your rights. Any views or opinions presented in this email are solely those of the sender and do not necessarily represent those of Athonet S.r.l.

1 0

Creating CDRs for Missed and failed calls
by Marrold 19 Sep '23

19 Sep '23

Hi all, I'm using the acc module along with postgres to generate CDRs. For connected calls the CDRs are created as expected, but in the scenario where a lookup() fails and Kamailio sends a stateless 404 there's no CDR logged. I'm setting the FLT_ACCMISSED and FLT_ACCFAILED flags in the initial request route, but perhaps I have a misunderstanding of how these work? Thanks Matthew

2 2

How to validate re-invites without challenging them?
by Benoit Panizzon 19 Sep '23

19 Sep '23

Hi List At the moment, we challenge every invite (and re-invite) to make sure the customer is authenticated. Now we have one kind of PBX, which never does not authenticate when we challenge a Re-Invite. According to the vendor of that PBX's RFC interpretation, answering a challenge to a re-invite is optional. If that is ignored by the PBX, then the existing established dialog shall not end. Unfortunately this causes the session timer to run out. I am therefore wondering, if there is a safe way not to challenge re-invites. A Re-Invite contains a To-Tag. So I could bypass authentication on presence of a to-Tag. But then, how do I prevent a customer to just set a spoofed To-Tag to circumvent authentication? Is there a feasible way? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 3

DBTEXT + TOPOS
by James Lipski 19 Sep '23

19 Sep '23

Hello, I'm doing an experiment with the DB_TEXT module. I have the topos module enabled; however it doesn't seem to function properly with db_text. Going over my syslog I see the following, and not quite understanding why it's failing to insert the row; I was hoping someone can point me in the right direction. This is a fresh install/ fresh DB. Thank you. Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[5] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[6] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[6] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[7] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[7] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:200]: dbt_load_file(): column[8] is INT! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[9] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[9] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[9] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[10] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[10] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[11] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[11] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[11] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[12] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[12] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[12] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[13] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[13] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:239]: dbt_load_file(): column[13] NULL flag set! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[14] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[14] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[15] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[15] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[16] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[16] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[17] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[17] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[18] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[18] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[19] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[19] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[20] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[20] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[21] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[21] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[22] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[22] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[23] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[23] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[24] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[24] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:195]: dbt_load_file(): column[25] is STR! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_file.c:227]: dbt_load_file(): column[25] is actually STRING! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:156]: db_allocate_columns(): allocate 160 bytes for result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:167]: db_allocate_columns(): allocate 80 bytes for result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_api.c:73]: dbt_get_columns(): allocate 16 bytes for RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1244]: tps_db_load_branch(): no stored record for <z9hG4bK22d5.7fedda308f2b91b2c0c83021c6adfaec.0> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:79]: db_free_columns(): freeing 20 columns Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[0] at 0x7fd70cacad00 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[1] at 0x7fd70cacad78 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[2] at 0x7fd70cacadf0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[3] at 0x7fd70cacae68 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[4] at 0x7fd70cacaee0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[5] at 0x7fd70cacaf58 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[6] at 0x7fd70cacafd0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[7] at 0x7fd70cacb048 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[8] at 0x7fd70cacb0c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[9] at 0x7fd70cacb138 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[10] at 0x7fd70cacb1b0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[11] at 0x7fd70cacb228 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[12] at 0x7fd70cacb2a0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[13] at 0x7fd70cacb318 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[14] at 0x7fd70c7c2368 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[15] at 0x7fd70c7c23e0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[16] at 0x7fd70c7c2458 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[17] at 0x7fd70c7c24d0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[18] at 0x7fd70c7c2548 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:83]: db_free_columns(): freeing RES_NAMES[19] at 0x7fd70c7c25c0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:96]: db_free_columns(): freeing result names at 0x7fd70cacabf8 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:101]: db_free_columns(): freeing result types at 0x7fd70c7f4ce0 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7fd70c7f4c40 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} <core> [core/utils/sruid.c:214]: sruid_nextx(): new sruid is [tpsh-6508d6d9-14577b-1] (1 / 22) Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:451]: tps_storage_fill_contact(): td->bs <sip:leg_a@host1.sip-example.com;ccr=btpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:454]: tps_storage_fill_contact(): td->as <sip:leg_b@host1.sip-example.com;ccr=atpsh-6508d6d9-14577b-1> Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:552]: tps_storage_link_msg(): downstream: yes - acontact: [sip:133@172.16.1.169:33880;line=g2l0pi9q;alias=72.255.5255.255~33880~1] - bcontact: [] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: DEBUG: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_lib.c:285]: dbt_db_get_table(): cache or mtime succeeded for [topos_t] Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_tb.c:468]: dbt_table_check_row(): null value not allowed - field 2 Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} db_text [dbt_base.c:525]: dbt_insert(): cannot insert the new row!! Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:1004]: tps_db_insert_branch(): failed to store message Sep 18 23:01:59 localhost /opt/kamailio/sbin/kamailio[1333115]: ERROR: {1 2 INVITE e0d608658658-eqkmzxcvr8vd} topos [tps_storage.c:615]: tps_storage_record(): failed to store

2 1

Using maxload in dispatcher list
by Calvin E. 19 Sep '23

19 Sep '23

Should maxload work with all dispatcher algorithms? I'm trying to add a test node to dispatcher.list with maxload=1 and it is getting a lot more than one concurrent call. The test node is the last one in the list. 16 sip:10.x.x.43:5070 0 0 duid=duid01;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.44:5070 0 0 duid=duid02;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.47:5070 0 0 duid=duid03;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.48:5070 0 0 duid=duid04;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.56:5070 0 0 duid=duid05;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.57:5070 0 0 duid=duid06;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.58:5070 0 0 duid=duid07;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.x:5070 0 0 duid=duid08;user=+10007787878;sockname=floating-internal-ip;maxload=0 16 sip:10.x.x.104:5060 0 0 duid=duid09;user=+10007787878;sockname=floating-internal-ip;maxload=1

2 1

SIP Registartion Sharing between two kamailio
by Lewis Hutchinson 19 Sep '23

19 Sep '23

On the understanding that you have checked the INVITE to 802 and it looks OK but not getting there then I would probably start digging on the networking side of it. You have said no Firewalls however there may be Security Groups and VPC bits going on in AWS. It's hard to say as the level of detail is not in the ticket. Can 802 call 801? What happens if you log 802 into Kamailio 1 and 801 into Kamailio 2 and call either way. Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

SIP Registartion Sharing between two kamailio using AWS NLB having issue.
by pra.savaliya1987＠gmail.com 19 Sep '23

19 Sep '23

Hello All, I have two kamailio servers and shared the database between two kamailio. version: kamailio 5.5.6 (x86_64/linux) . I have used AWS network load balancer. domain pointed to AWS network load balancer IP address,AWS Network Load Balancer (NLB) to distribute incoming requests to kamailio servers. I have two users in same domain(dev.domain.com). 1. 801(a)dev.domain.com --> Registered on kamailio 1 2. 802(a)dev.domain.com --> Registered on kamailio 2 Two call invites have been received, one for extension 801 and another for extension 802. These call invites will reach kamailio Server 1. kamailio Lookup the users and send call invite to both the devices. 801 registered user will get a ring because it is registered from kamailio 1. but 802 will not get a ring because it's register from kamailio 2. I can able see kamailio send call invite to the both registered devices using sngrep. but it not reach to the 802 device. there i no firewalls so far. also i have took 802 Registered device IP phone logs but there is no Call Invite reach to the 802 device. I have also tried by using "dmq" and "dmq_usrloc" module but the same behavior. what could be the reason? It will be appreciable if anyone help to resolve the issue. Thank you in advance! Pratik Svaliya.

2 1

Increase MAX_BRANCHES_LIMIT
by Lars Jansson 18 Sep '23

18 Sep '23

Hi, I am building a configuration script where for some traffic flows parallel forking will be needed, and in this case I need to go beyond the default max limit of the max amount of branches. Apart from this specific case the traffic load that kamailio will need to handle is very low, let's say just one second here and there with up to 5 concurrent calls at most. This limit is as far as I understand set here: usr/local/src/kamailio-5.6/kamailio/src/core/config.h And the default limit is: #define MAX_BRANCHES_LIMIT 32 /*!< limit of maximum number of branches per transaction */ Here are the questions I have related to this: 1) If I increase the value of this constant in config.h, how high is it reasonable to set this value and still have a stable system? 2) If I increase MAX_BRANCHES_LIMIT beyond 32, are there also other parameters that needs to be changed for the system to be able to cope, and if so whichparameters? Regards, Lars

4 9

. Re: Multiple headers in http client request
by Lewis Hutchinson 18 Sep '23

18 Sep '23

Hi Matteo I have used http_async_client and http_client in both Native & KEMI to good affect for handling SUBSCRIBE & NOTIFY flows however did have a few issues with formatting which took a bit of work to get right. Just to note, something you may want to test. Initially I set about my task using http client within Python (aiohttp and ayncio) and stepped in and out of it from various points in the logic depending on the config I was using at the time. Under load this proved to be a bottle neck and failed load testing. The best options under load were using http_async_client or http_client modules which offered significantly better performance. In the end we took a different approach of using Kafka Module as that had even better performance but that was a decision taken our side not through any fault of the http_async_client or http_client modules Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

Add Header to reply on failure_route
by Benoit Panizzon 18 Sep '23

18 Sep '23

Hi List I'm attempting to add a header to a reply message on failure. Situation: Registrar => Core => (dispatcher list) => Various IC I would like to know on the registrar, which of the dispatcher groups failed. What I attempted sofar: failure_route[DISPATCH_FAILURE] { append_to_reply("X-RR: (append reply) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); append_hf("X-RR: (append hf) Final Dispatch Failure $avp(dispgroup):$avp(trunkname)\r\n"); $avp(rstatus) = t_get_status_code(); $avp(rtext) = $T_rpl($rr); $avp(rtext) = "REMOTE REPLY: " + $T_rpl($rr); t_send_reply("$avp(rstatus)", "$avp(rtext)"); } I only get status text is getting through to my reply. I would much prefer to add a header which I could then extract on the registrar. Am I missing something which could prevent addition of a header in a reply? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

Multiple headers in http client request
by Matteo Brancaleoni 17 Sep '23

17 Sep '23

Hello all :) I'm struggling to add two headers to an http client request, but cannot find a proper way to do it. The headers are Authorization and Content-Type. The first try is with http_client module, beside undocumented, is possible to add multiple headers separating them with "\r\n". What I see is the correct Authorization header, and two Content-Type headers, one with my content type the other with x-www-form-urlencoded, which no one sets ? Second try is with http_async_client which supports multiple headers, but since I'm calling it from an xhttp event route, there's no transaction and request cannot be suspended, so I cannot get results before sending out xhttp response... Any hint? br, Mat

2 3

Orphan Dialog Vars: Probable cause found!
by Benoît Panizzon 15 Sep '23

15 Sep '23

Hi List I wonder if some of the devs could look at the dialog code and maybe confirm my observation of this supposed Bug in Kamailio 5.6 Situation: Two Kamailio, dialog counters synced via DMQ and each node using a local DB as dialog backend. Goal is to count channel usage per customer. modparam("dialog", "db_mode", 1 ) modparam("dialog", "enable_dmq", 1) modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) modparam("dialog", "profiles_with_value", "custcallcounter") If 'JohnDoe' is involved in a call, I do: set_dlg_profile("custcallcounter","JohnDoe"); To check how many calls are busy by JohnDoe I do: get_profile_size("custcallcounter","JohnDoe","$var(channel_use)"); Picture this situation: JohnDoe is initiating a first call via Node1: Node1 created the dialogue and variables, writes them to the database and replicates the dialog vars to Node2 => IN MEMORY Nothing about the running dialog is being written to the Database on Node2, but get_profile_size returns the count on Node2. So while the first call aka dialog is running via Node1, JohnDoe is initiating a second call, this time via Node2. Node2 creates the dialog and writes this to the database. Then the profile with Name 'JohnDoe' is INCREASED on Node2. This is when I suddenly find the dialog_vars on the Node2 database containing information about the dialog started on Node1. So I guess writing to a dialog counter triggers the dialog_vars being written to the Database. When JohnDoe is ending it's first call, then the dialog and dialog_vars are cleaned out of the database on Node1, but NOT on Node2 What I fear happens next: They dialog_vars remaining on the Database of Node 2 accumulate more and more, making the database slower. When a call happens to re use the same hash id and entry, things start going really badly. Could I be right? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Set a License for Kamailio
by Ali Taher 15 Sep '23

15 Sep '23

Hello, Is it possible to put a kind of license for Kamailio, in a way that it works for 1 week for example, and after that it will not process new requests? Regards,

3 4

client sending message and refresh register normal. But KSR.uac.uac_req_send() ERROR
by riffs＠sina.cn 14 Sep '23

14 Sep '23

The client uses the TLS protocol registered and TCP Connection established . There is a problem now, sending message KSR.uac.uac_req_send() from the kamilio server to client failed sometimes,and the error is as follows： “2023-09-04T17:22:01.515763+08:00 (3429) ERROR: tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed 2023-09-04T17:22:01.515763+08:00 (3429) ERROR: tm [uac.c:678]: send_prepared_request_impl(): Attempt to send to precreated request failed ”. meantime, the client sending message to Kamalio server succeded, and the register status and tcp connection is normal. After 30s, obtained the $uac_req(evcode) from the event_route[uac:reply] is 408.After this error appears, all the messages sent to this client are 408. " 2023-08-29T03:48:43.738152+08:00 (3349) NOTICE: <script>: ===uac reply received, callid = 0B6ECB534AE24281AED9BBBC56B140A6`yangwang2`1693252093, code is: 408 2023-08-29T03:48:43.738825+08:00 (3349) NOTICE: <script>: ===uac reply received, callid = 0B6ECB534AE24281AED9BBBC56B140A6`yangwang2`1693252093, code is: 408 " But from other information, the TCP connection is normal. Because from Kamailio to querying this user's Location, it has not changed all day. The client sends messages is also normal. That is, the user's registration and sending messages can receive 200 OK. We use netstat commands to view the user's TCP connection information on the client and server, and the connection status is also normal.The status of the corresponding port of the TCP connection is ESTABLISHED. client: netstat -ano | findstr 49957 "172. 17. 47.125:49957 XXX.96.XXX.XXX:5061 ESTABLISHED 10516" server: "tcp 0 0 10.11.xx.xx:5061 xxx.xxx.xxx.xxx:49957 ESTABLISHED 3467/kamailio" This client is normal after logging in, and the problem that occurs after a period of use (maybe some hours), and once it occurs, it fails until the user creates a new connection and logs back in. Not all users will appear. Why is this the case? The socket connection is fine, but uac_req_send () get an ERROR? I found a problem from the log file. Is it caused by duplicate callids pushed to the same user at the same second? Looking forward to your answer, thank you very much Script information that may be required kamailio.cfg ： tm mode # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) modparam("tm", "auto_inv_100", 1) kamalio.lua uac_req_send() " --uac_req_send KSR.pv.sets("$uac_req(hdrs)", hdrs) KSR.pv.sets("$uac_req(method)", "MESSAGE") KSR.pv.sets("$uac_req(ruri)", "sip:" .. to .. "@" .. KAM_DOMAIN) KSR.pv.sets("$uac_req(furi)", "sip:" .. from .. "@" .. KAM_DOMAIN) KSR.pv.sets("$uac_req(turi)", "sip:" .. to .. "@" .. KAM_DOMAIN) KSR.pv.seti("$uac_req(evroute)", 1) KSR.pv.sets("$uac_req(body)", content) local ouri = (row.received ~= "" and row.received) or row.contact KSR.pv.sets("$uac_req(ouri)", ouri) local callid = rows[i].clientid .. "`" .. rows[i].username .. "`" .. os.time() KSR.pv.sets("$uac_req(callid)", callid) KSR.uac.uac_req_send()

1 0

MS Teams and ca_list.pem
by Social Boh 13 Sep '23

13 Sep '23

Hello, I'd like to know where i can download/search ca_list.pem file to use in tls.cfg configuration file for MS TEAMS. Without the file: ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS write:error:0A000086:SSL routines::certificate verify failed (sni: unknown) ERROR: tls [tls_server.c:1336]: tls_h_read_f(): src addr: 52.114.76.76:506 ERROR: tls [tls_server.c:1339]: tls_h_read_f(): dst addr: KamailioIP:0 ERROR: <core> [core/tcp_read.c:1476]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fb6a23ba4f8 r: 0x7fb6a23ba620 (-1) Thank you Regards -- --- I'm SoCIaL, MayBe

1 0

number based routing and NATed peers
by Kiss Zoltán 12 Sep '23

12 Sep '23

Hello, Im gathering ideas about routing based on caller number to multiple peers and -lets say- subscribers. As far as i know we can route the calls with LCR based on prefix or the whole number to the LCR gateways which are specified in the LCR module gateway table. This is working very well with public IP based "peers". We can route calls to these gateways. But what can we do if we have to route to a "peer" which is behind NAT. Basically they have to REGISTER as a subscriber, but we cannot add a subscriber to the LCR gateway table, beacuse LCR module needs a directly reachable IP address with a fixed port. Does anyone have any ideas on how to handle these mixed type peers? Or maybe we have to add the fixed IP peers which are not REGISTERing to the usrloc database somehow and then we can do a lookup location based on $rU. To make myself clear, it would be nice if we can handle those 2 types of our peers unifromly in terms of SIP routing, thats why im looking for a "unified" solution. Thanks for your suggestions. With kind regards, Zoltan

1 0

Skip/discard branch in branch route?
by Benoît Panizzon 11 Sep '23

11 Sep '23

Hi all Is there a way to skip a branch in branch route? Situation: Two registrar server with DMQ synced location database. CPE register via TCP or TLS. To properly work, message have to be sent over the existing TCP connection. Multiple CPE register to one AOR. CPE1 and CPE2 register to Registrar 1 CPE3 registers to Registrar 2 On Registrar 1 there is an established TCP connection to CPE1 and CPE2 but not to CPE3. Within the Branch Route to the CPE I can check if there is a TCP as the Branch Route is executed for every contact in that AOR: branch_route[BR_TO_CPE] { [...] $var(reg_contact_addr) = $(ulc(aor=>addr)[$T_branch_idx]{uri.host}); $var(socket) = $(ulc(aor=>socket)[$T_branch_idx]); if ($var(socket) == 0) { xlog("L_ERROR", "$cfg(route): No Socket for: $var(reg_contact_addr)"); } [...] } This log an error if the socket is not present on the local registrar. But is there a way to tell kamailio to skip/discard that contact? My intention is to parallel branch from the core to both registrars, that way all contacts would still get the call but via established TCP socket (and in case of UDP and NAT via correct know ip for ALG port-forwarding). -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 12

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/modparam.c:176]: set_mod_param_regex(): No module matching <mi_fifo> found 0(1071336) CRITICAL: <core> [core/cfg.y:3546]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 582, column 63: Can't set module parameter ERROR: bad config file (2 errors) 0(1071336) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized please help!

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 the memory and what data is piling up? Thanks a lot! Regarts, Volodymyr Ivanets.

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 written on the Request-URI. I thought of using restore_mode with value "none" saving original values in an $avvp() and doing the replace, however, uac_replace() on Request Route or branch routes. That way i can't replace the values of To and From in the replies. That being said, my questions are : - Is there a way to use manual or auto mode without writing info on the Record-Route and only using $avp() ? - Is there a way to make changes on the To and From header on replies? Thanks in advance, Best Regards, Duarte Rocha

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 (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.

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 table multiple times within this 8 second window. Is this some kind of intended block or is something at fault? modparam("db_mysql", "ping_interval", 60) modparam("db_mysql", "timeout_interval", 4) modparam("db_mysql", "auto_reconnect", 1) modparam("db_mysql", "opt_ssl_mode", 0) modparam("permissions", "db_url", "mysql://kamailio:xxxxx@aws-rds-database /kamailio") version: kamailio 5.7.1 (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, MEM_JOIN_FREE, 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 10.2.1 /M

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 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: >

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(): 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)

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 sexual stimulation. Maybe you want to enjoy full sex, should try some other sex toys. https://www.hugedildo.com/ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave(a)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:

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{proxy="127.0.0.1",request="offer"} 539.270967 rtpengine_request_seconds_total{proxy="127.0.0.1",request="answer"} 367.237641 rtpengine_request_seconds_total{proxy="127.0.0.1",request="delete"} 0.000000 is it normal? (large number of timeouts, "zero" terminated) or i have missing rtpengine_manage (rtpengine_delete) somewhere? (os rocky 9.2, kamailio 5.6.4, rtpengine 11.3.1) thanks Marek

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 <-----> 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

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 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

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 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

1 0

Check refer-to number
by David Cunningham 17 Aug '23

17 Aug '23

Hello, We want to check if the number in a REFER's Refer-To header begins with 011, and if so reject the request as not allowed. What would be the most effective way to do that? Thanks in advance, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

4 4

Unable to get avp value in response
by peter＠alienzombie.co.uk 17 Aug '23

17 Aug '23

I am trying to set a value to an avp on the request route, but when I try to read the avp on the reply route I always get nil. On the route I have this: KSR.xlog.xinfo("invite_request: ********** Setting avp test\n") KSR.pv.seti("$avp(test)", 1) KSR.xlog.xinfo("invite_request: **** " .. tostring(KSR.pv.get("$avp(test)")).."\n") On the reply route I have this: KSR.xlog.xinfo("response_invite: **** " .. tostring(KSR.pv.get("$avp(test)")).."\n") In the logs I see on the INVITE: Aug 8 13:49:15 test /usr/sbin/kamailio[1927947]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 1]invite_request: ********** Setting avp test Aug 8 13:49:15 test /usr/sbin/kamailio[1927947]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 1]invite_request: **** 1 ... ... Aug 8 13:49:15 test /usr/sbin/kamailio[1927968]: INFO: [a0748d39-3f17-4080-b5ed-0a6b7019cb95 INVITE 2]response_invite: **** nil Do avp not cover the transaction?

2 2

Kamailio behind TLS-TCP load balancer
by David Villasmil 17 Aug '23

17 Aug '23

Hello all, I’m having lots of problems when trying to configure Kamailio behind an AWS tls load balancer to offload tls and receive on tcp on Kamailio. Everything else inside is UDP. I found I need to manually add record-route presets every time and invite comes in. And when trying to forward an ACK to the client via tls/tcp load balancer Kamailio complaint the socket is not TLS so it fails. Is there a simpler way of doing this via some parameters I don’t know? Thanks for helping me with this! David -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 9

kamailio-postgres on RHEL 9
by Ali Taher 17 Aug '23

17 Aug '23

Hello, I'm trying to install latest Kamailio version on RHEL 9.2. All is good, but I couldn't find kamailio-postgres package related to postgres module, knowing that I have installed Postgresql 15. Is there a rpm file that I can download to install kamailio-postgres ? Regards,

3 2

siremis Config.xml
by Maryam Baghdadi 15 Aug '23

15 Aug '23

Hello every one, How to set Remote Mysql database login ssl-mode in Config.xml file for siremis ???

1 0

Kamailio dns-failover / dns-loadbalancing with slow responding client.
by Mattis Lind 14 Aug '23

14 Aug '23

Hello! I am looking into a problem where we have Kamailio forwarding calls to two or more "recording-clients". I will try my best to describe the problem and would appreciate it if someone has an idea what to do. Please feel free to ask if you think I have forgotten to describe something that might be important or something is unclear in what I have written. We use use_dns_failover=yes and dns_srv_lb=yes so calls get load balancing to the "recording-clients". There is also the t_set_fr(60000,1000) parameter set so that if there is no response within 1 second it would try the next recording-client. The SRV record points to two or more recording clients. It now happens that the recording-clients sometimes have some kind of temporary problem so it will respond with a 503 after 5 seconds. What happens is that after the 1 second timeout trying to get the INVITE through to the first recording-client Kamailio will internally generate a 408. This will cause it to failover to another recording-client which happily takes care of the INVITE and responds properly with a 200 OK. Everything would have been just fine except for the fact that the first recording-client is just slow and finally responds with a 503. This 503 is not relayed backwards since a 200 has already been forwarded back to the caller. But when receiving the 503 Kamailio will initiate a new INVITE which is trying to set up a new call to a recording client. It looks like it is doing a new failover regardless if it already has done a failover for this failed transaction. I don't want Kamailio to send that last INVITE when receiving the 503. How can I configure Kamailio to disregard the last 503 (except for responding with an ACK) and not initiate a new INVITE? I have tried a lot of different changes to the configuration but failed to achieve this, unfortunately. Do I need to use the dispatcher module to achieve this? /Mattis

4 6

Modify To URI in Multiple Choices
by Ali Taher 11 Aug '23

11 Aug '23

Hello, I'm using Kamailio as SIP redirect where SBC sends INVITE packet to kamailio and "302","Multiple Choices" is sent back to SBC. What I want is to modify the URI part in the To header of the Multiple Choices packet sent from kamailio. I tried to use uac_replace_to("","sip:$var(cdpn)@$td") where $var(cdpn) is already defined in the routing logic, but it's not reflected and the original TO URI is sent instead. Any help to handle this issue is much appreciated. Regards,

2 2

how to get value of next hop
by Sergey Safarov 10 Aug '23

10 Aug '23

I receiving INVITE with two Route header (no to tag). First Route header is my Kamailio host. Second Route header is next hop after Kamailio. I need to get value of next hop. I tried to use "$route_uri" after "loose_route" but his deos works. "$route_uri" always use top Route header. But in the INVITE first Route header is Kamailio host. Is any change to get top Route header after "loose_route"?

3 2

Kamailio-asterisk BYE
by Dr. Barabás Péter 09 Aug '23

09 Aug '23

Hello, we work on a mobile softphone which connects to asterisk through kamailio. Almost everything is fine except one thing. Asterisk allows only one registration to an AOR. In mobile environment network can change, register/unregister can be called frequently in foreground/background cases. Kamailio forwards every request to asterisk. Until I have only one connection between kamailio – asterisk, everything is fine. The next situation is problematic: 1. Client A and client B register to asterisk through kamailio. –> there will be one connection between kamailio and asterisk 2. Client A calls client B. • one connection exist still 3. If client A terminates the call -> one connection remains. It is okay. 4. If client B terminates the call -> a new connection appears (kamailio IP with new port) After case 4 If I try to register again, I got 403 from asterisk, since the setting of asterisk does not allowed to register from different IP:port for the same AOR. (this behaviour cannot be changed now). The question: is there any setting/config exist in kamailio not to create new connection for a BYE in above case. Thanks in advance for your reply. Peter

1 0

Htable question
by Stefan-Cristian Mititelu 09 Aug '23

09 Aug '23

Hello, Can one kama process iterate a htable using sht_iterator_start(), sht_iterator_next(), sht_iterator_rm(), sht_iterator_end() while some other kama process call sht_rm(htable, item) ? I've looked into code and to me it looks like slots are locked ok. The entire linked list(specific to a slot) where the item might be, is locked, so this means there should be no problems, right? Thank you, Stefan

1 0

problem relay re-INVITE
by beer Ll 09 Aug '23

09 Aug '23

Hi I have a kamailio 5.7.1 running as TLS gateway for PBXs in private LAN network: UAC-WAN(sip-tls) <--> kamailio-WAN(sip-tls) - kamailio-LAN(sip) <--> PBX-LAN(sip) 80.0.0.1 <--> 80.0.0.2 - 10.0.0.1 <--> 10.0.0.2 All communications tested works well except for re-INVITE like when UAC put the call on hold . The re-INVITE packet is managed like a new call and the tm module doesn't match transaction : matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-524287-1---5e900485d5ad0faf] t_lookup_request(): no transaction found build_cell(): created new cell t_relay_to(): new INVITE I try to send the interesting logs and config call logs and pcap : https://filebin.net/vdezuhyn7wdy3lqc kamailio config : ... request_route { if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); } route(WITHINDLG); if ($si=="PBXIP0" || $si=="PBXIP1" || $si=="PBXIP2" || $si=="PBXIP3" ) { if (!loose_route()) { switch($rc) { case -2: sl_send_reply("403", "Forbidden"); exit; } } remove_hf("Route"); force_rport(); record_route(); $fs = "tls:WANIP:5061"; } if (is_method("INVITE|SUBSCRIBE")){ record_route(); } t_on_failure("MANAGE_FAILURE"); $fs = "udp:LANIP:5060"; } route(RELAY); exit; } route[WITHINDLG] { if (!has_totag()) return; if ($si=="PBXIP0" || $si=="PBXIP1" || $si=="PBXIP2" || $si=="PBXIP3") { route(RTPMANAGE); route(RELAY); exit; } if (loose_route()) { if ( is_method("NOTIFY") ) { record_route(); } route(RTPMANAGE); route(RELAY); exit; } if ( is_method("ACK|BYE") ) { route(RTPMANAGE); route(RELAY); } sl_send_reply("404","Not here"); exit; } How can I solve this ? Best Regards Leo

1 0

No
by Sergey Safarov 09 Aug '23

09 Aug '23

I catched issue with In the Kamailio logs i see ssl bug #1491 workaround: not enough memory for safe operation: shm=10219080 threshold2=11796480 Current stat about shared memory [root@sbc-a1 ~]# kamctl stats shmem { "jsonrpc": "2.0", "result": [ "shmem:fragments = 528", "shmem:free_size = 11343104", "shmem:max_used_size = 124449952", "shmem:real_used_size = 122874624", "shmem:total_size = 134217728", "shmem:used_size = 58728144" ], "id": 703182 } But when kamailio started [root@sbc-a1 ~]# kamctl stats shmem { "jsonrpc": "2.0", "result": [ "shmem:fragments = 122", "shmem:free_size = 112534264", "shmem:max_used_size = 22372528", "shmem:real_used_size = 21683464", "shmem:total_size = 134217728", "shmem:used_size = 12833888" ], "id": 703670 } What is stange a lot of fragments. How it can be troubleshooted? Can memory manager show info about each fragment like when fragment are created an and which module requested fragment?

2 3

Problem connecting to Redis DB using DB_REDIS module with a Password
by Nick Digalakis 08 Aug '23

08 Aug '23

Hello everyone! I had a Kamailio 5.6.4 server using the DB_REDIS module for quite some time without a password on the Redis DB working just fine. A few days ago I decided to add a password to Redis and modify the Kamailio config file with the following line per the documentation to be able to authenticate: modparam("db_redis", "db_pass", "r3d1sPass") Since that moment, I see the following errors in the Kamailio logs: ...... kamailio: ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <db_pass> of type <1:string> not found in module <db_redis> kamailio: CRITICAL: <core> [core/cfg.y:3790]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 556, column 49: Can't set module parameter ...... The documentation I am reading is here: https://www.kamailio.org/docs/modules/devel/modules/db_redis.html#db_redis.… Could someone help me figure out what I am doing wrong? Many thanks, Nick

2 2

pua_json mwi minimal json
by David VILLAUME 08 Aug '23

08 Aug '23

Hello, On 5.6.4, i’m trying to perform mwi pua_json, but cannot get it working. I have a doubt about my json and spent some time to make variations on json without success. Does one of you played with it and can tell me if something is wrong about this json ? { "Event-Package":"message-summary", "Event-Name":"update" "expires":3600, "From":sip:ccoca@dff.com, "To":sip:ccoca@dff.com, "Message-Account":sip:ccoca@dff.com, "Messages-Waiting":"yes", "MWI-Voice-Message":"2/8 (0/0)", "Messages-New":"2", "Messages-Saved":"8", "Messages-Urgent":"0", "Messages-Urgent-Saved":"0", "From-Realm":"dff.com", "From-User":"ccoca", "Call-ID":0_845806535@10.22.22.22<mailto:0_845806535@10.22.22.22>, } Regards, David

3 3

Subscribers and peers handling
by Kiss Zoltán 08 Aug '23

08 Aug '23

Hello, We are trying to build a lightweight SBC solution for some external peers, but currently there is a mixed environment which is handled by Asterisk. We have some "peers" with IP based auth, and also some "subscribers" with register. We have succeded with the subscribers, because we can handle the numbers for those type of users with aliases in Kamailio. So basically we have a subscriber, lets call it "test", and we can add aliases for the subscriber like "3612345678@localhost", then if we are calling the number the routing goes to the contact of "test" subscriber. Currently the problem is that we dont have any idea about the IP based peers, because those peers not registering, so we cannot create aliases for them as far as i know. How do you solve this type of problem? Maybe im overcomplicating the situation, but i havent got any solutions in my mind currently. Thanks for your help and ideas. With kind regards, Zoltan

1 0

Connection to AWS services (e.g DynamoDB)
by Lewis Hutchinson 07 Aug '23

07 Aug '23

Hi Jakub Although no direct experience with this exactly as you have described I have used HTTP API out of Kamailio quite a bit and into other services. Which yes some ultimatly end in AWS> Having done our's in KEMI there is some difference however from our experience we did notice some of this didn't fair well under a loads test scenario. We tested Kafka vs Kamailio HTTP API Modules vs Aiohttp (Python in Kemi) and Kafka significantly out perfomed in terms of the load test. We then had to rejig things to account for this instead of HTTP API. If this is ever going to be under intense load. Maybe make sure you do the load testing early on before you ratify your design. Also make sure all your error habndling is in place and working to prevent issues in Kamailio if something API side goes wrong. Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

1 0

Setting up rtpengine to relay RTP
by Alvaro Escobar 05 Aug '23

05 Aug '23

Hello I have debian 11 with kamailio 5.6.4 (x86_64/linux). The kamailio is working fine. Now I need to setup rtprngine to relay RTP. I have installed the rtpengine using this guide: https://dfx.at/rtpengine/ Version: 10.5.4.3-1+b1 When I run: systemctl status rtpengine-daemon I got: ● rtpengine-daemon.service - RTP/media Proxy Daemon Loaded: loaded (/lib/systemd/system/rtpengine-daemon.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2023-08-01 20:58:23 -05; 51min ago Docs: man:rtpengine(8) Process: 468 ExecStartPre=/usr/sbin/rtpengine-iptables-setup start (code=exited, status=0/SUCCESS) Main PID: 535 (rtpengine) Tasks: 22 (limit: 2323) Memory: 42.1M CPU: 720ms CGroup: /system.slice/rtpengine-daemon.service └─535 /usr/bin/rtpengine -f -E --no-log-timestamps --pidfile /run/rtpengine/rtpengine-daemon.pid --config-file /etc/rtpengine/rtpengine.conf Aug 01 20:58:22 debian systemd[1]: Starting RTP/media Proxy Daemon... Aug 01 20:58:23 debian rtpengine[535]: INFO: [crypto] Generating new DTLS certificate Aug 01 20:58:23 debian rtpengine[535]: INFO: [core] Startup complete, version 10.5.4.3-1+b1 Aug 01 20:58:23 debian systemd[1]: Started RTP/media Proxy Daemon. Aug 01 20:58:23 debian rtpengine[535]: INFO: [http] Websocket listener thread running I edited /etc/kamailio/kamailo.cfg with: #!define WITH_RTPENGINE #!ifdef WITH_RTPENGINE loadmodule "rtpengine.so" modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223") systemctl restart kamilio To check if the rtpengine module is running: kamcmd core.modules I got: permissions auth_db auth counters acc cfg_rpc ctl sanity xlog siputils textopsx textops registrar usrloc maxfwd pv rr sl tmx tm corex kex jsonrpcs db_mysql The point is that I don't see the rtpengine module. There is another way to check if the rtpengine module is running ? Regards

2 2

Connection to AWS services (e.g DynamoDB)
by jakub.smadis＠cloudtalk.io 04 Aug '23

04 Aug '23

Hello, I am researching how I could communicate from Kamailio (which runs on an AWS EC2 instance) with AWS services (e.g. DynamoDB) using HTTP API. My Kamailio logic is written in Kamailio configuration files. I would like to ask you if anyone has some experience with such a setup and if so how did you manage to connect it? My current options are: * HTTP connection to DynamoDB API with HTTP module I would create a Python script that would generate signature headers for the [AWS API request](https://docs.aws.amazon.com/IAM/latest/UserGuide/create-signed-req…. Then I would use the headers in the HTTP request. (I am using the Kamailio module to keep the connection open to DynamoDB). * Middleman service Small service that provides HTTP API to Kamailio and manages the communication with DynamoDB. Easiest solution but it's harder to maintain it in high availability mode. * API gateway with VPC endpoint attached to the EC2 API gateway would be a proxy to DynamoDB and we would call the VPC endpoint from the Kamailio. We would use resource policies to allow requests without auth through the VPC endpoint. Any help or feedback would be valuable to me. Thank you very much! Regards, Jakub

1 0

change A number using a pool of numbers
by Ali Taher 03 Aug '23

03 Aug '23

Hello, I'm looking to change the A number (from number) to a number selected randomly from a pool of existing numbers (hundreds) and then relay the call to a certain gateway. What is the best and more efficient way to do it in kamailio? Thanks in advance

2 3

advertise transport
by David Villasmil 02 Aug '23

02 Aug '23

Hello guys, I have kamailio behind a TLS->TCP Load Balancer. I'm having problems because the outgoing packets have a record has the correct advertise BUT kamailio is assuming that because the outgoing socket is TCP, it adds ";transport=tcp"... is it possible to set that parameter to tls? Thanks! David Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 1

Saving credentials in yaml/txt format
by max＠telemessage.com 01 Aug '23

01 Aug '23

Hello all, I want to save some credentials for different users I have that are being used in a digest authorization (INVITE), with different realms (I don't want the credentials to be hardcoded). I tried to look at how can I read into my kamalio.cfg from yaml/txt file, but haven't found the right module for this. Thanks in advance, Max

4 3

Help
by Shravan Kumar 28 Jul '23

28 Jul '23

Hello, How can I configure my Kamalio server to work as multihoming for sctp testing... Please ASAP!!

2 1

Re: RTPENGINE - RTP Proxy
by Duarte Rocha 27 Jul '23

27 Jul '23

Hello Alex, Thank you for your answer, I still don't have sound but the behaviour is now different. Is it possible to configure this behaviour on a call by call basis with flags on the rtpengine_manage() function? Or in alternative having it consume the "direction=" attribute on the SDP? Cheers

1 0

Re: RTPENGINE - RTP Proxy
by Duarte Rocha 27 Jul '23

27 Jul '23

Hello Alex, Thank you for your answer, I still don't have sound but the behaviour is now different. Is it possible to configure this behaviour on a call by call basis with flags on the rtpengine_manage() function? Or in alternative having it consume the "direction=" attribute on the SDP? Cheers

1 0

RTPENGINE - RTP Proxy
by Duarte Rocha 26 Jul '23

26 Jul '23

Hello all, I'm currently doing some experiments with RTPENGINE and I need some help configuring it. First scenario i'm under NAT and Kamailio receives an INVITE with a private address, rewrites (c) line on SDP with it's own IP address and relays the message to the destination endpoint. After that the originator receives the 183 Session Progress with kamailio's IP as (c) parameter. After receiving the first RTP packet from the originator the media streams flow normally and I have sound on both sides including ringing. Second scenario I use different equipment that is not under NAT, but the remaining scenario is the same, except the originator doesn't send an RTP packet after the 183 Session Progress. However, in this case, no RTP stream is relayed to the originator and as a consequence it doesn't hear a ring or voice when the call is answered. As i see it, it looks like Kamailio is on passive mode to the A-Leg of the call and waits for a RTP packet to establish its stream. Is this correct? If so, how do i change this behaviour? Cheers

2 1

Re: Kamailio as SIP proxy for an Asterisk with Private IP Address
by Lewis Hutchinson 25 Jul '23

25 Jul '23

This is always a good place to start https://www.fredposner.com/1457/kamailio-behind-nat/ Lewis Mission Labs Limited is registered in England, company number 10040088. Trading Office: The Old Milk Depot, Bacup Rd, Rossendale, BB4 7FE. Registered office: The Scalpel, 18th Floor 52 Lime Street, London, EC3M 7AF. Email confidentiality notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Please consider the environment before you print this email.

5 6

tcpops: Variable conid on tcp-closed event
by Michal Hajek 24 Jul '23

24 Jul '23

Hi, I have problem with the conid variable, when I use in an event when closing a tcp connection. Simple kamailio.cfg: debug=3 log_stderror=no loadpath "/usr/lib64/kamailio/modules" memdbg=5 memlog=5 log_facility=LOG_LOCAL3 listen=udp:10.10.8.94:5060 listen=tcp:10.10.8.94:5060 loadmodule "sl.so" loadmodule "xlog.so" loadmodule "pv.so" loadmodule "tcpops.so" request_route { xlog("L_INFO", "Welcome TCP conn $conid\n"); exit; } event_route[tcp:closed] { xlog("L_INFO", "Close TCP conn $conid\n"); } Log: kamailio DEBUG: <core> [core/ip_addr.c:577]: print_ip(): tcpconn_new: new tcp connection: 10.10.9.64 kamailio DEBUG: <core> [core/tcp_main.c:1216]: tcpconn_new(): on port 38124, type 2, socket 34 kamailio DEBUG: <core> [core/tcp_main.c:1549]: tcpconn_add(): hashes: 3487:2267:2872, 19 kamailio DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): processing io_watch_add(0xb39c40, 34, 2, 0x14c2479867f0) - fd_no=28 kamailio DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xb39c40, 34, -1, 0x0) fd_no=29 called kamailio DEBUG: <core> [core/tcp_main.c:4557]: handle_tcpconn_ev(): sending to child, events 2001 kamailio DEBUG: <core> [core/tcp_main.c:4227]: send2child(): selected tcp worker idx:2 proc:14 pid:1203550 for activity on [tcp:10.10.8.94:5060], 0x14c2479867f0 kamailio DEBUG: <core> [core/tcp_read.c:1735]: handle_io(): received n=8 con=0x14c2479867f0, fd=6 kamailio DEBUG: <core> [core/tcp_read.c:284]: tcp_read_data(): EOF on connection 0x14c2479867f0 (state: 3, flags: 4118) - FD 6, bytes 218, rd-flags 10000 ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1533]: tcp_read_req(): content-length=0 kamailio DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 kamailio DEBUG: <core> [core/parser/msg_parser.c:678]: parse_msg(): SIP Request: kamailio DEBUG: <core> [core/parser/msg_parser.c:680]: parse_msg(): method: <OPTIONS> kamailio DEBUG: <core> [core/parser/msg_parser.c:682]: parse_msg(): uri: <sip:100@localhost> kamailio DEBUG: <core> [core/parser/msg_parser.c:684]: parse_msg(): version: <SIP/2.0> kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Via] type 1 kamailio DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKhjhs8ass877>; state=15 kamailio DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 kamailio DEBUG: <core> [core/parser/msg_parser.c:554]: parse_headers(): Via found, flags=2 kamailio DEBUG: <core> [core/parser/msg_parser.c:556]: parse_headers(): this is the first via kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Call-ID] type 6 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [From] type 4 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [To] type 3 kamailio DEBUG: <core> [core/parser/parse_addr_spec.c:884]: parse_addr_spec(): end of header reached, state=10 kamailio DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): <To> [20]; uri=[sip:100@localhost] kamailio DEBUG: <core> [core/parser/msg_parser.c:175]: get_hdr_field(): to body (20)[<sip:100@localhost> ], to tag (0)[] kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Content-Length] type 12 kamailio DEBUG: <core> [core/parser/msg_parser.c:186]: get_hdr_field(): content_length=0 kamailio DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [CSeq] type 5 kamailio DEBUG: <core> [core/parser/msg_parser.c:153]: get_hdr_field(): cseq <CSeq>: <63104> <OPTIONS> kamailio DEBUG: <core> [core/receive.c:389]: receive_msg(): --- received sip message - request - call-id: [ahoj423432432] - cseq: [63104 OPTIONS] kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:261]: ksr_evrt_pre_routing(): event route core:pre-routing not defined kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:471]: receive_msg(): preparing to run routing scripts... kamailio DEBUG: {1 ahoj423432432} <core> [core/tcp_main.c:1645]: _tcpconn_find(): found connection by id: 19 kamailio INFO: {1 ahoj423432432} <script>: Welcome TCP conn 19 kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:529]: receive_msg(): request-route executed in: 47 usec kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/xavp.c:640]: xavp_destroy_list(): destroying xavp list (nil) kamailio DEBUG: {1 ahoj423432432} <core> [core/receive.c:628]: receive_msg(): cleaning up kamailio DEBUG: <core> [core/tcp_read.c:1634]: tcp_read_req(): EOF after reading complete request ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1653]: release_tcpconn(): releasing con 0x14c2479867f0, state -1, fd=6, id=19 ([10.10.9.64]:38124 -> [10.10.9.64]:5060) kamailio DEBUG: <core> [core/tcp_read.c:1657]: release_tcpconn(): extra_data (nil) kamailio DEBUG: <core> [core/tcp_main.c:3653]: handle_tcp_child(): reader response= 14c2479867f0, -1 from 2 kamailio DEBUG: <core> [core/tcp_main.c:3578]: tcp_emit_closed_event(): TCP closed event creation triggered (reason: 0) kamailio DEBUG: tcpops [tcpops.c:295]: tcpops_handle_tcp_closed(): received TCP closed event kamailio DEBUG: tcpops [tcpops.c:249]: tcpops_tcp_closed_run_route(): event reason id: 0 rt: 1 kamailio INFO: <script>: Close TCP conn <null> Can you help me, where is issue?

1 0

Kamailio as SIP proxy for an Asterisk with Private IP Address
by John shuku 24 Jul '23

24 Jul '23

Dear Kamailio users, Im new to kamailio so excuse me if the question doesnt make sense. I have an asterisk server with private IP address behind the NAT . Is it possible to have a Kamailio Server with Public IP Address as a proxy server for my asterisk ? What I want to achieve is that remote users should be able to call internal users who are registered in the Asterisk . The problem here is that Asterisk does not have public IP address and I want the remote users to be registered in my asterisk . Best WishesJ. sh

3 4

Re: Add a digest authorization with password and username (INVITE)
by Max Kemel 20 Jul '23

20 Jul '23

Thank you very much Barry, that was it 🙂 Max Kemel

1 0

Add a digest authorization with password and username (INVITE)
by Max Kemel 20 Jul '23

20 Jul '23

Hello, I would appreciate any help you can provide on this matter, I would like to make an outgoing INVITE request which will have a digest authorization with password and username. I was wandering around the Auth module to find the most fit method to build this header but hadn't found anything. Maybe I am missing something really obvious here, thanks for the help in advance Best regards, Max.

2 1

Kamailio v5.5.7 Released
by Daniel-Constantin Mierla 19 Jul '23

19 Jul '23

Hello, Kamailio SIP Server v5.5.7 stable release is out. This is a maintenance release of the stable branch 5.5 that includes fixes since the release of v5.5.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.7. Note that 5.5 is now the third last stable branch, v5.5.7 being the last planned released in 5.5.x series. The latest two stable branch are 5.6 and 5.7, with v5.7.1 being released a while ago. For more details about version 5.5.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/07/kamailio-v5-5-7-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 0

Releasing Kamailio v5.5.7
by Daniel-Constantin Mierla 19 Jul '23

19 Jul '23

Hello, I am planning to release v5.5.7 our of branch 5.5 this week, most likely on Wednesday, July 19, 2023. It will mark the end of official packaging for release series 5.5.x, currently the latest two stable branches are 5.6 and 5.7. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 1

Re: WebRTC proxy with rtpengine - How to change from RTP to SRTP on 488 response
by Alex Balashov 18 Jul '23

18 Jul '23

I wouldn't do a delete in that situation; it might be simpler to just do another rtpengine_offer() on a <Call-ID, From-tag> tuple that RTPEngine already knows about, just as one would in a reinvite. I believe rtpengine_manage() would cover this situation as well. And yes, then just t_relay() anew! > On Jul 18, 2023, at 11:41 AM, Barry Flanagan <barry(a)flantel.com> wrote: > > On 18/07/2023 16:33, Alex Balashov wrote: >> Barry, >> >> Might it not be simpler to follow Richard's first suggestion in that thread, and simply catch the 488 response in a failure_route and re-issue a non-SRTP offer on another branch? > > hi Alex, > > Might be. I am just unsure about how to instruct rtpengine to re-send the plain RTP invite. Do I do a rtpengine_delete and then restart with rtpengine_manage() then relay again? > > Thanks. > > -Barry > > >> >> -- Alex >> >>> On Jul 18, 2023, at 11:05 AM, Barry Flanagan <barry(a)flantel.com> wrote: >>> >>> Hi, >>> >>> I have implemented a WebRTC proxy using Kamailio and rtpengine, in front >>> of Asterisk servers. I have an issue where I do not know in advance >>> whether the Asterisk client is set to use RTP or SRTP. >>> >>> My implementation expects the web side to be SRTP and the Asterisk side >>> plain RTP. However, if the asterisk side requires SRTP I receive a 488 >>> Not Acceptable here. The same is true when an SRTP client from the >>> Asterisk side dials out to the webrtc client, I need to catch whether >>> the request is SRTP or RTP and generate rtpengine offer accordingly. >>> >>> This was discussed in github, with a description of a solution here: >>> https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398 - >>> however I am unsure how to implement this. >>> >>> Does anyone have an example of how I can change the rtpengine SDP in >>> such a case? >>> >>> Thanks >>> -- >>> -Barry >>> __________________________________________________________ >>> 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: > > -- > -Barry > -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

1 0

WebRTC proxy with rtpengine - How to change from RTP to SRTP on 488 response
by Barry Flanagan 18 Jul '23

18 Jul '23

Hi, I have implemented a WebRTC proxy using Kamailio and rtpengine, in front of Asterisk servers. I have an issue where I do not know in advance whether the Asterisk client is set to use RTP or SRTP. My implementation expects the web side to be SRTP and the Asterisk side plain RTP. However, if the asterisk side requires SRTP I receive a 488 Not Acceptable here. The same is true when an SRTP client from the Asterisk side dials out to the webrtc client, I need to catch whether the request is SRTP or RTP and generate rtpengine offer accordingly. This was discussed in github, with a description of a solution here: https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398 <https://github.com/sipwise/rtpengine/issues/435#issuecomment-391937398>- however I am unsure how to implement this. Does anyone have an example of how I can change the rtpengine SDP in such a case? Thanks -- -Barry

2 1

Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 18 Jul '23

18 Jul '23

Hi Daniel, thank you for your response. As you can see in the provided debug output: kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] dbmode is set to 1 in the config: modparam("htable", "db_url", "sqlite:////etc/kamailio/htable.sqlite") ... modparam("htable", "htable", "userpush=>size=3;autoexpire=600;dbtable=userpush;dbmode=1") If I execute kamcmd htable.store userpush I get Ok. Htable successfully stored to DB. But the table is still empty!!! In the log I found: ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database ERROR: db_sqlite [dbase.c:177]: db_sqlite_cleanup_query(): finalize failed: attempt to write a readonly database ERROR: htable [ht_db.c:668]: ht_db_delete_records(): failed to delete db records in [userpush] ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database Ok. But I can not see this entries if I shutdown kamailio. And: -rw-rw-rw- 1 kamailio root 16384 Jul 13 16:14 htable.sqlite I never used: modparam("db_sqlite","db_set_readonly" ... I also restarted kamailio. no difference. Now more errors then before: It is not written at shutdown. (no messages) It is not written (live) (with error messages, but why it is readonly?) The message of kamcmd is wrong (says Ok but it failed) Best regards, Bernd Am 17.07.2023 um 08:48 schrieb Daniel-Constantin Mierla: > Hello, > > is dbmode=1 in htable definition? > > If you run rpc command htable.store for the htable, are the records > saved to database? > > Cheers, > Daniel > > On 13.07.23 17:45, Bernd Krueger-Knauber wrote: >> Hi, >> >> I just tried to use sqlite and htable to load and save the values. >> At start I can see in the log, that all parameters are correct and >> that htable want to load the values from the table. >> No errors. >> >> But if I stop kamailio, nothing is written to the tables. >> >> At start I can see: >> >> kamailio[]: DEBUG: <core> [core/modparam.c:112]: >> set_mod_param_regex(): 'htable' matches module 'htable' >> kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): >> found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: <core> [core/modparam.c:128]: >> set_mod_param_regex(): found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable >> [callpush] - dbmode [1] >> kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable >> [callpush] - dbtable [userpush] >> kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable >> [callpush] - expire [86400] >> kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable >> [callpush] - size [10] >> >> >> >> kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): >> loading db table [userpush] in ht [userpush] >> kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): >> =============== loading hash table [userpush] from database [userpush] >> kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): >> submit_query: select key_name,key_type,value_type,key_value from >> userpush order by key_name >> kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): >> submitted query: select key_name,key_type,value_type,key_value from >> userpush order by key_name, result 0 >> kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 >> bytes for result set at 0x7f4882107938 >> kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 >> columns >> kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing >> result set at 0x7f4882107938 >> >> Ok, the file is empty, but it tries to load the data from the table. >> >> The table looks like: >> >> sqlite> .schema userpush >> CREATE TABLE userpush ( >> key_name TEXT, >> "key_type" INTEGER, >> value_type INTEGER, >> key_value TEXT >> ); >> >> >> I checked the source code and I saw that destroy() should be called. >> Inside is ht_db_open_con() called before ht_db_sync_tables(), were it >> happens. >> But I can even not see the debug message from ht_db_open_con() : >> >> LM_DBG("database connection opened successfully\n") >> and also not >> LM_ERR("failed to connect to the database\n"); >> >> For me it looks like, that the destroy() function is not called. >> >> Even with debug=3, I can only see: >> >> >> systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP >> Server... >> kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received >> systemd[]: kamailio.service: Deactivated successfully. >> systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP >> Server. >> >> I stopped kamailio with >> >> systemctl stop kamailio >> >> I'm sure that something was inside the htable before I stoped kamailio: >> >> { >> entry: 0 >> size: 1 >> slot: { >> { >> name: >> 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 >> value: >> 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 >> type: str >> } >> } >> } >> >> Any further ideas? >> >> Best regards, >> >> Bernd >> >> >> >> __________________________________________________________ >> 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: -- EDNT GmbH Werner-von-Siemens-Strasse 7 64625 Bensheim www.ednt.de Registergericht: Darmstadt Registernummer: 24972 Geschäftsführer: Karlheinz Knapp

6 8

Fwd: Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 17 Jul '23

17 Jul '23

-------- Weitergeleitete Nachricht -------- Betreff: Re: [SR-Users] Kamailio 5.6.4 and htable dbmode=1 Datum: Mon, 17 Jul 2023 09:50:37 +0200 Von: Bernd Krueger-Knauber <bkk(a)ednt.de> An: miconda(a)gmail.com Hi Daniel, thank you for your response. As you can see in the provided debug output: kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] dbmode is set to 1 in the config: modparam("htable", "db_url", "sqlite:////etc/kamailio/htable.sqlite") ... modparam("htable", "htable", "userpush=>size=3;autoexpire=600;dbtable=userpush;dbmode=1") If I execute kamcmd htable.store userpush I get Ok. Htable successfully stored to DB. But the table is still empty!!! In the log I found: ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database ERROR: db_sqlite [dbase.c:177]: db_sqlite_cleanup_query(): finalize failed: attempt to write a readonly database ERROR: htable [ht_db.c:668]: ht_db_delete_records(): failed to delete db records in [userpush] ERROR: db_sqlite [dbase.c:528]: db_sqlite_commit(): sqlite commit failed: attempt to write a readonly database Ok. But I can not see this entries if I shutdown kamailio. And: -rw-rw-rw- 1 kamailio root 16384 Jul 13 16:14 htable.sqlite I never used: modparam("db_sqlite","db_set_readonly" ... I also restarted kamailio. no difference. No more errors then before: It is not written at shutdown. (no messages) It is not written (live) (with error messages, but why it is readonly?) The message of kamcmd is wrong (says Ok but it failed) Best regards, Bernd Am 17.07.2023 um 08:48 schrieb Daniel-Constantin Mierla: > Hello, > > is dbmode=1 in htable definition? > > If you run rpc command htable.store for the htable, are the records > saved to database? > > Cheers, > Daniel > > On 13.07.23 17:45, Bernd Krueger-Knauber wrote: >> Hi, >> >> I just tried to use sqlite and htable to load and save the values. >> At start I can see in the log, that all parameters are correct and >> that htable want to load the values from the table. >> No errors. >> >> But if I stop kamailio, nothing is written to the tables. >> >> At start I can see: >> >> kamailio[]: DEBUG: <core> [core/modparam.c:112]: >> set_mod_param_regex(): 'htable' matches module 'htable' >> kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): >> found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: <core> [core/modparam.c:128]: >> set_mod_param_regex(): found <htable> in module htable >> [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] >> kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable >> [callpush] - dbmode [1] >> kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable >> [callpush] - dbtable [userpush] >> kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable >> [callpush] - expire [86400] >> kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable >> [callpush] - size [10] >> >> >> >> kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): >> loading db table [userpush] in ht [userpush] >> kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): >> =============== loading hash table [userpush] from database [userpush] >> kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): >> submit_query: select key_name,key_type,value_type,key_value from >> userpush order by key_name >> kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): >> submitted query: select key_name,key_type,value_type,key_value from >> userpush order by key_name, result 0 >> kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 >> bytes for result set at 0x7f4882107938 >> kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 >> columns >> kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing >> result set at 0x7f4882107938 >> >> Ok, the file is empty, but it tries to load the data from the table. >> >> The table looks like: >> >> sqlite> .schema userpush >> CREATE TABLE userpush ( >> key_name TEXT, >> "key_type" INTEGER, >> value_type INTEGER, >> key_value TEXT >> ); >> >> >> I checked the source code and I saw that destroy() should be called. >> Inside is ht_db_open_con() called before ht_db_sync_tables(), were it >> happens. >> But I can even not see the debug message from ht_db_open_con() : >> >> LM_DBG("database connection opened successfully\n") >> and also not >> LM_ERR("failed to connect to the database\n"); >> >> For me it looks like, that the destroy() function is not called. >> >> Even with debug=3, I can only see: >> >> >> systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP >> Server... >> kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received >> systemd[]: kamailio.service: Deactivated successfully. >> systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP >> Server. >> >> I stopped kamailio with >> >> systemctl stop kamailio >> >> I'm sure that something was inside the htable before I stoped kamailio: >> >> { >> entry: 0 >> size: 1 >> slot: { >> { >> name: >> 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 >> value: >> 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 >> type: str >> } >> } >> } >> >> Any further ideas? >> >> Best regards, >> >> Bernd >> >> >> >> __________________________________________________________ >> 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: -- EDNT GmbH Werner-von-Siemens-Strasse 7 64625 Bensheim www.ednt.de Registergericht: Darmstadt Registernummer: 24972 Geschäftsführer: Karlheinz Knapp

1 0

Kamailio 5.6.4 and htable dbmode=1
by Bernd Krueger-Knauber 17 Jul '23

17 Jul '23

Hi, I just tried to use sqlite and htable to load and save the values. At start I can see in the log, that all parameters are correct and that htable want to load the values from the table. No errors. But if I stop kamailio, nothing is written to the tables. At start I can see: kamailio[]: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'htable' matches module 'htable' kamailio[]: DEBUG: <core> [core/sr_module.c:814]: find_param_export(): found <htable> in module htable [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] kamailio[]: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <htable> in module htable [/usr/lib/x86_64-linux-gnu/kamailio/modules/htable.so] kamailio[]: DEBUG: htable [ht_api.c:1046]: ht_table_spec(): htable [callpush] - dbmode [1] kamailio[]: DEBUG: htable [ht_api.c:1027]: ht_table_spec(): htable [callpush] - dbtable [userpush] kamailio[]: DEBUG: htable [ht_api.c:1036]: ht_table_spec(): htable [callpush] - expire [86400] kamailio[]: DEBUG: htable [ht_api.c:1041]: ht_table_spec(): htable [callpush] - size [10] kamailio[]: DEBUG: htable [ht_api.c:1084]: ht_db_load_tables(): loading db table [userpush] in ht [userpush] kamailio[]: DEBUG: htable [ht_db.c:232]: ht_db_load_table(): =============== loading hash table [userpush] from database [userpush] kamailio[]: DEBUG: db_sqlite [dbase.c:223]: db_sqlite_submit_query(): submit_query: select key_name,key_type,value_type,key_value from userpush order by key_name kamailio[]: DEBUG: <core> [db_query.c:72]: db_do_submit_query(): submitted query: select key_name,key_type,value_type,key_value from userpush order by key_name, result 0 kamailio[]: DEBUG: <core> [db_res.c:119]: db_new_result(): allocate 56 bytes for result set at 0x7f4882107938 kamailio[]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns kamailio[]: DEBUG: <core> [db_res.c:138]: db_free_result(): freeing result set at 0x7f4882107938 Ok, the file is empty, but it tries to load the data from the table. The table looks like: sqlite> .schema userpush CREATE TABLE userpush ( key_name TEXT, "key_type" INTEGER, value_type INTEGER, key_value TEXT ); I checked the source code and I saw that destroy() should be called. Inside is ht_db_open_con() called before ht_db_sync_tables(), were it happens. But I can even not see the debug message from ht_db_open_con() : LM_DBG("database connection opened successfully\n") and also not LM_ERR("failed to connect to the database\n"); For me it looks like, that the destroy() function is not called. Even with debug=3, I can only see: systemd[]: Stopping kamailio.service - Kamailio - the Open Source SIP Server... kamailio[]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received systemd[]: kamailio.service: Deactivated successfully. systemd[]: Stopped kamailio.service - Kamailio - the Open Source SIP Server. I stopped kamailio with systemctl stop kamailio I'm sure that something was inside the htable before I stoped kamailio: { entry: 0 size: 1 slot: { { name: 07db580a6c13e798a5acc0d123d6e957897c8650b43f99d6d5cb9c2cb5ba4fa4 value: 3a28dcb73eb65722df5a261983b7692cecdca482bf8725032e46a0c6b89fb355 type: str } } } Any further ideas? Best regards, Bernd

2 1

Using Kamailio in front of Freeswitch for load balancing REG and Calls
by Shah Hussain Khattak 12 Jul '23

12 Jul '23

Hello Awesome people, I have configured Kamailio in front of two Freeswitch servers. I am using the dispatcher module to load and balance the traffic between the two FS boxes. My dispatcher is configured in a round-robin fashion. If I send a register to my FS servers, the re-register post-challenge (401) message is routed to the second FS server and the registration fails. I want to check with you guys how are you handling this in your setups. I am sure a lot of companies are using Kamailio to load balance traffic toward the FS and Asterisk servers. UAC --- > Kamailio --- > FS1 REG ---- > REG ---- > REG 401 <---- 401 < ---- 401 re-register with authorization data: UAC --- > Kamailio --- > FS2 REG --- > REG ---- > REG 401 <---- 401 < ---- 401 it just create this loop and register fails. Ideally, I want Kamailio to send the re-register (with auth data) to the same FS server that challenged it. Any ideas or pointers to fix this issue would be highly appreciated, maybe I am missing some very basic configuration. Or maybe there is another simpler way instead of using a dispatcher module. Thank you! Regards, Shah Hussain

2 4

Re: sr-users Digest, Vol 218, Issue 16
by satyaprakash ch 11 Jul '23

11 Jul '23

Hi Please find some more before and after, Ip address and number is masked FYI. INFO: <script>: TIME : TEST - Rewriting To header with Request line so that vendor prefix is present INFO: <script>: TIME : TEST2 - tu is sip:+123456789@10.0.77.88 and ru is sip:10.0.1.47:5060 INFO: <script>: TIME : TEST3 - tu is sip:+123456789@10.0.77.88 and ru is sip:10.0.1.47:5060 ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [31bca077-99fa-123c-eb84-00219b9e3ef4] [WITHINDIALOG] The request is [ACK] INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [31bca077-99fa-123c-eb84-00219b9e3ef4] [PROXY_OUTBOUND_HANDLE] [ACK] INFO: <script>: TIME : [Mon Jul 10 12:24:14 2023] CALL ID : [ 205526695_49743609(a)206.147.84.20] [WITHINDIALOG] The request is [ACK] Here is the code i suspect, Let me know if you can find some thing why the error usually gets, *failure_route["serial"] { if (!t_next_contacts()) { exit; } t_on_failure("serial"); xlog("L_INFO","TIME : [$Tf] CALL ID : [$ci] [serial]The altered ruri is [$ru] \n"); xlog("L_INFO", "TIME : TEST - Rewriting To header with Request line so that vendor prefix is present"); xlog("L_INFO","TIME : TEST2 - tu is $tu and ru is $ru \n"); $tu = $ru; xlog("L_INFO","TIME : TEST3 - tu is $tu and ru is $ru \n"); t_relay();}event_route[tm:branch-failure:REMOVE_OLD_REGISTER] { if (t_check_status("(404)|(410)")) { xlog("L_INFO","TIME : Received code [$T(reply_code)] from SBC, need to remove registration \n"); xlog("L_INFO","TIME : [$Tf] CALL ID : [$ci] [REMOVE_OLD_REGISTER] contact is [$ct]Unregister section is entered [$ru] \n"); unregister("location", "$tu", "$T_reply_ruid"); }}* Thank you. On Tue, Jul 11, 2023 at 3:46 PM <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > Today's Topics: > > 1. Need an error description (satyaprakash ch) > 2. Re: Need an error description (Alex Balashov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Jul 2023 22:25:31 +0530 > From: satyaprakash ch <chiramchetty.satyaprakash(a)gmail.com> > Subject: [SR-Users] Need an error description > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.kamailio.org> > Message-ID: > < > CAO-xAtGhcDMiPtoGdBeb6qvhOg8u7hxKt-w-5oU4KuOkdRHuqg(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000005a4339060024dadd" > > Hi, > > Can anyone help me with the error why can we get this? > > ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm > [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for > failure handler > > Thank you. >

2 1

Need an error description
by satyaprakash ch 10 Jul '23

10 Jul '23

Hi, Can anyone help me with the error why can we get this? ERROR: tm [tm.c:1752]: _w_t_relay_to(): t_forward_noack failed ERROR: tm [t_reply.c:1081]: run_failure_handlers(): error running run_top_route for failure handler Thank you.

2 1

event_route[tm:local-response] only executes a few times
by Kaufman 10 Jul '23

10 Jul '23

Hello, I'm writing a 302 redirect server and wanting to capture some events on all replies, so I'm trying to do this in event_route[tm:local-response], but I noticed that the event route is only called a few times for the first few requests, and then never gets executed again. This is the simplest case in which I can reproduce the issue: #!KAMAILIO loadmodule "pv" loadmodule "tm" loadmodule "xlog" route { xinfo("[$rm $ci-$cs] Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n"); t_send_reply("404", "Not Found"); exit; } event_route[tm:local-response] { xcrit("[$rm $ci-$cs] tm:local-response replied locally\n"); } If I start Kamailio with kamailio -ddDDeE it has 8 children. If I use sipp to send 10 requests, this is what I see in the kamailio logs. The critical line in the event route is only printed four times. This is tested on 5.7.0 and 5.6.4 9(66) INFO: <script>: [INVITE 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) CRITICAL: <script>: [INVITE 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] tm:local-response replied locally 10(67) INFO: <script>: [ACK 1-14(a)172.26.0.3-1<mailto:1-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) CRITICAL: <script>: [INVITE 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] tm:local-response replied locally 12(69) INFO: <script>: [ACK 2-14(a)172.26.0.3-1<mailto:2-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) INFO: <script>: [INVITE 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) CRITICAL: <script>: [INVITE 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] tm:local-response replied locally 14(71) INFO: <script>: [ACK 3-14(a)172.26.0.3-1<mailto:3-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) INFO: <script>: [INVITE 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) CRITICAL: <script>: [INVITE 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] tm:local-response replied locally 16(73) INFO: <script>: [ACK 4-14(a)172.26.0.3-1<mailto:4-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) INFO: <script>: [INVITE 5-14(a)172.26.0.3-1<mailto:5-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 10(67) INFO: <script>: [ACK 5-14(a)172.26.0.3-1<mailto:5-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 6-14(a)172.26.0.3-1<mailto:6-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 12(69) INFO: <script>: [ACK 6-14(a)172.26.0.3-1<mailto:6-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 13(70) INFO: <script>: [INVITE 7-14(a)172.26.0.3-1<mailto:7-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 14(71) INFO: <script>: [ACK 7-14(a)172.26.0.3-1<mailto:7-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 15(72) INFO: <script>: [INVITE 8-14(a)172.26.0.3-1<mailto:8-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 16(73) INFO: <script>: [ACK 8-14(a)172.26.0.3-1<mailto:8-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 9(66) INFO: <script>: [INVITE 9-14(a)172.26.0.3-1<mailto:9-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 10(67) INFO: <script>: [ACK 9-14(a)172.26.0.3-1<mailto:9-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 11(68) INFO: <script>: [INVITE 10-14(a)172.26.0.3-1<mailto:10-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] 12(69) INFO: <script>: [ACK 10-14(a)172.26.0.3-1<mailto:10-14@172.26.0.3-1>] Src:[172.26.0.3:5060] RURI:[sip:service@172.26.0.2:5060] To:[sip:service@172.26.0.2:5060] From:[sip:sipp@172.26.0.3:5060] Kaufman

2 2

Random number
by Ali Taher 07 Jul '23

07 Jul '23

Hello, As per Kamailio documentation, $RANDOM returns a random value from the [0 - 2^31) range. But when testing it it's always returning a random number of 9 or 10 digits. I'm not sure if it's always the case or if it can also returns numbers with 1 or 2 digits as well. Another question, how can I force it to return a number of specific digits starting with certain prefix. Regards,

2 1

Finding a way to gracefully restart kamailio with dialog module enabled and DMQ sync
by Benoît Panizzon 07 Jul '23

07 Jul '23

Hi Gang We are still having massive issues on how to safely reload kamailio after config changes when using the dialog module and DMQ. If there are active dialogues, kamailio corrupts them on a restart even when using MySQL as dialog backend. As we use two core nodes for redundancy, I am looking for a way to gracefully restart kamailio. I am considering adding some key in a hash table or anything else I can reload on runtime to indicate to kamailio not to accept any new calls (effectively rejecting Invites without To-Tag with 503 causing the registrar or IC peer to hopefully resend the invite to the other node). Then wait, until no more dialogues are active, so kamailio can safely be restarted. My Issue now: How can I find out, one specific node does not have any active dialogues? 'kamcmd dlg.stats_active' returns the count of all DMQ synced nodes, not of the local one. And suggestions or any other ideas how I can 'reload' the kamailio config without disrupting active dialogues? My last resort would be to look into the database: modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) So odd/even H_ID should tell me the number per node. But I see a lot of orphan dialogues hanging around in the database not being cleaned so I guess that will not be reliable at all. Yes, I know I will get the question: 'Why do you need to restart kamailio that often'. We have started production on our kamailio based TSP platform. And of course, despite a LOT of testing beforehand, there is always some issue that pops up. At the moment, I have to implement a config change about once or twice a week to fix some new minor issues. I hope, somewhen in the future we will hopefully have a stable config which will last for several months, but at the moment this is the situation. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

Randomize calling number
by Ali Taher 06 Jul '23

06 Jul '23

Hello, What is the best way to change the calling number to a random number (based on specific pattern, like number of digits for example) in an invite packet without using a database. So the scenario is : * receive an invite packet from certain source * change the calling number * send back the invite packet including the new calling number to the original source. Regards, Ali Taher

3 7

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