sr-users

sr-users@lists.kamailio.org

37388 discussions

Kamailio 5.4.3 crash at SSL error
by Igor Olhovskiy 14 Sep '21

14 Sep '21

Hello. Kamailio 5.4.3 crashes at CentOS 7 with following error logs Sep 13 13:15:11 /usr/local/sbin/kamailio[44592]: ERROR: <core> [core/tcp_read.c:1500]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f3b93734cf8 r: 0x7f3b93734e20 (-1) Sep 13 13:15:12 /usr/local/sbin/kamailio[44594]: NOTICE: tls [tls_domain.c:747]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 13 13:15:12 kernel: traps: kamailio[44594] general protection ip:7f3ba8fb3c09 sp:7ffe2c3aff70 error:0 in libssl.so.1.0.2k[7f3ba8f87000+67000] Sep 13 13:15:12 /usr/local/sbin/kamailio[44597]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 38 Sep 13 13:15:12 /usr/local/sbin/kamailio[44597]: CRITICAL: <core> [core/pass_fd.c:85]: recv_all(): 1st recv on 41 failed: Connection reset by peer Sep 13 13:15:12/usr/local/sbin/kamailio[44597]: CRITICAL: <core> [core/tcp_main.c:3543]: handle_tcp_child(): read from tcp child 2 (pid 44594, no 19) Connection reset by peer [104] Sep 13 13:15:12/usr/local/sbin/kamailio[44561]: ALERT: <core> [main.c:777]: handle_sigs(): child process 44594 exited by a signal 11 Sep 13 13:15:12/usr/local/sbin/kamailio[44561]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated Sep 13 13:15:12 /usr/local/sbin/kamailio[44561]: INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD I'm pretty sure these logs are mostly not usable, but maybe they will point to some bugs. To add, this happened just occasionally and I can't reproduce it at the moment. -- Regards, Igor

2 3

Manage blacklisting on network errors
by Marat Gareev 14 Sep '21

14 Sep '21

Hello! I have a simple config for routing requests with failover and blacklisting on 408, 480 and 503 codes from servers. This is a part of config: # Wrapper for relaying requests route[RELAY] { # the base event routes t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); if (!t_relay()) { sl_reply_error(); } exit; } # Manage incoming replies onreply_route[MANAGE_REPLY] { xlog("L_NOTICE", "$rr ($rs) [$cs] ($ci) $si:$sp - $ua\n"); if ( t_check_status("(503)|(408)|(480)") ) { xlog("L_WARN", "Server will be blacklisted: $si:$sp ($rs)\n"); } } # Manage failure routing cases failure_route[MANAGE_FAILURE] { if ( !t_check_status("(503)|(408)|(480)") ) { exit; } ds_mark_dst("IP"); # blacklist if (t_is_canceled()) exit; if (!ds_next_domain()) { send_reply("503", "Service Unavailable"); exit; } route(RELAY); } If there is a timeout or network error on the server side, it is blacklisted. How can such cases be managed and how can they be logged? I didn't find this on the module page: https://www.kamailio.org/docs/modules/stable/modules/tm.html

2 2

Question about suspected memory leak presence module
by Albert Petit 14 Sep '21

14 Sep '21

Hi, I am suspecitng presence module might be having a memory leak on a production server used by an end user (not have access to it). The output of command kamcmd mod.stats presence shm is Module: presence { mem_copy_subs(148): 25720 mem_copy_subs_noc(214): 1672201904 mem_copy_subs_noc(251): 678406560 add_event(181): 88 shm_copy_event(57): 40 shm_copy_event(50): 312 add_event(156): 40 add_event(149): 456 new_shtable(66): 5767168 new_shtable(53): 262144 init_evlist(289): 16 Total: -1938302848 } I am not sure what mem_copy_subs_noc is meaning. And final output is negative, SHM is incfreasing all the time but not sure of the root cause is this a reasonable hint that a memory leak is related to presence?

2 3

Empty Subnets in Permissions Module
by Tom Dworakowski 14 Sep '21

14 Sep '21

Greetings all! I have two deployments of Kamailio: one running version 5.3 and one 5.5 with practically identical configurations, same (MySQL and REDIS) data sources. We have customers that we assign an ACL "group" to, where the ID of this group resolves to records in the "address" table in our MySQL database - using the "grp" field. On the box running Kamailio 5.5, we have noticed that if a group has ip_addr=0.0.0.0, mask=0, port=0 - and we try to run the allow_source_address() - it will return false, thus failing this phase of the authentication process. However, on Kamailio 5.3 we are not seeing this issue, i.e. if a customer is assigned a group where the ACL is 0.0.0.0/0 - it will let him through. Has something changed that I'm not aware of? Any suggestions on how to resolve this? My best, Tom

2 1

Kamailio dispatcher -> FreeSWITCH transfers handling.
by Тимур Ситдиков 11 Sep '21

11 Sep '21

Hi list! :-) I'm a total newbie in Kamailio. Trying to study) Sorry for lots of text, I'm simply don't know how to explain my questions shorter :-D I want to configure Kamailio as dispatcher, registrar and NAT traversal in front of FS farm. I've managed to set up Kamailio and Fswitches. Now I need to handle "special cases" with confs, REFER transfers etc Giovanni Maruzzelli once presented solution for this, with following logic: ------------------------------------------------------------------------------------------------------- 1) Kamailio by default distribute calls to various FSs - dispatch or load_balance 2) Each time Kamailio sends a call to a FS, it writes down which destination "number" is going to which FS server and from which UserID 3) if another call comes for the same (or related) destination, or is originated from the same UserID then Kamailio sends the call to that same FS server, bypassing default distribution algorithm ------------------------------------------------------------------------------------------------------- Sounds good and helpful, but I'm stuck :-( *Can someone please share an example or point me how and in what form should I write down call info,and how can I control it (delete on BYE or CANCEL)?* Actually there are 2 questions It seems to me that recordings can be made using HTABLEs but here's a problem: ===================================================================================== ============================================================================================= 1) PROBLEM WITH WRITING TO HTABLE ON ATT TRANSFER After the dispatcher sets $du - I write an htable entry $sht(fsdest=>$fU:$rU) = $du; Existing entries are removed on catching 'BYE' for normal clearing, and with failure_route for all failures. BYE logic is: IN WITHINNDLG route if (has_totag()) { if (loose_route()) { if (is_method("BYE")) { if (sht_match_name("fsdest", "eq", "$fU:$rU")) { $sht(fsdest=>$fU:$rU) = $null; //BYE A->B } else { $sht(fsdest=>$rU:$fU) = $null; //BYE A<-B } } handle_ruri_alias(); route(RELAY); } } Another entry is setting up if blind transfer is made. If INVITE is coming from one of FSs, and have 'Referred-By' field. IN DIALOG route: if (is_present_hf("Referred-By")) { $sht(fsdest=>$fU:$rU) = $si; } For now it's working. Entries are written and deleted properly. *Problem with Attended transfer.* 1) A --> B = htable entry A:B=xxxx 2) A --> C = htable entry A:C=xxxx(checked and set same FS addr because $fU is present (If only it's worked as it should)) 3) Att transfer (Refer $rU B, referred-by - A. Refer-To - C) B --> C = all related entries deleted from table over BYE logic. 4) No entry B --> C (no INVITE was sent, bridged by REFER) So, logic for check active calls in htable is broken now, because we don't have entry B-->C *How can I handle writing to htable in Attended transfer case?* If another Invite will come FROM or TO B or C = there will be no htable entry. I'm not sure this is even a correct way. Surely missing something. ============================================================================================= ============================================================================================= 2) PROBLEM WITH IDENTIFYING TABLE ENTRIES Anyway, the main problem is with identifying those htables to set proper $du. If INVITE is coming TO FSs I need to check if caller ID ($fU) or dest ($rU) is present in htables. Form I need to write to hash must be like $fU:$rU Entry must be unique or it will be: 1) rewrited anytime a new invite is going to the same dest. 2) deleted anytime BYE or failure will come eg: If $sht(fsdest=>$rU) = $dd 1) 1000 --> 3200 = htable entry 3200 = xxxx 2) 1005 --> 3200 = htable entry rewriten to the same 3200 = xxxx When 1000 or 1005 leaving conf, it sends BYE and removes entry. So, next call to 3200 may be sent to the wrong FS. Ok, we have a unique entry ($fU:$rU). Checking for active destination: if (sht_match_name("fsdest", "re", ":$rU")) {} If there's an htable with $rU in key - we got a match. Now we need to assign a value from htable to $du. But, I don't know how to get the name of this entry. There's always different $fU: (or $rU if we check for the same caller ID ($fU)). eg: 1000 --> 3200 = htbale 1000 --> 3200 New call 1005 --> 3200 Check sht_match name ":3200" - got match We need to set: $du = $sht(fsdest=>$fU:$rU) But it will be $sht(fsdest=>1005:3200) and we don't have this entry. We need (fsdest=>1003:3200) But i don't see any way to get needed $fU. *Is there any way to search or identify these tables?* ============================================================================================= ============================================================================================= Can someone help me with this, please? :-) Or maybe there is a better way to do this? *My kamailio.cfg routing block in pastebin, if neededhttps://pastebin.com/1PZ0QSDW <https://pastebin.com/1PZ0QSDW>* Thank you! Regards, Tim

4 5

Info: Kamailio World 2021 starting soon - live stream
by Daniel-Constantin Mierla 10 Sep '21

10 Sep '21

Hello, to sync better on time, Kamailio World 2021 online edition is starting in about 2 hours from now (12:50 UTC Welcome and 13:00UTC the first session) - the agenda is available at: * https://kamailioworld.com/k09-online/ In short: participation is free, no registration is needed. The sessions are live streamed to YouTube KamailioWorld channel: * https://www.youtube.com/c/KamailioWorld/ YouTube chat next to the live stream can be used for addressing questions to speakers -- we will monitor it and ask the speaker inside the video conferencing room. For community interaction via text chatting, you can join the Matrix room #kamailio:matrix.kamailio.dev : * https://riot.kamailio.dev/#/room/#kamailio:matrix.kamailio.dev Questions for speakers can also be addressed in this chat room. If anyone wants to participate in the live video conferencing room, the URL is: * https://meet.kamailioworld.com/live Just note that we may have to limit the number of participants in the live session in order to ensure proper streaming quality. See you soon online! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

5 9

RPC usrloc ul.add problem
by Pepelux 09 Sep '21

09 Sep '21

Hi all I have problems adding a new location by RPC command. *# kamailio -v* version: kamailio 5.5.0 (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 A simple example, adding an AOR which expires in 1 hour: *# date ; kamcmd ul.add kam_location 1002-test1(a)sipserver.com <1002-test1(a)sipserver.com> sip:1002-test1@192.168.89.82 <sip%3A1002-test1(a)192.168.89.82> 3600 0.0 . 0 0 0 .* Wed 08 Sep 2021 01:58:00 PM CEST Location record has been inserted correctly: *# date ; kamcmd ul.dump | grep test -A24* Wed 08 Sep 2021 01:58:02 PM CEST AoR: 1002-test1(a)sipserver.com HashID: -597689288 Contacts: { Contact: { Address: sip:1002-test1@192.168.89.82 Expires: 3598 Q: 0.000000 Call-ID: dfjrewr12386fd6-343(a)kamailio.rpc CSeq: 1 User-Agent: kamailio SIP Router - RPC Server Received: [not set] Path: [not set] State: CS_SYNC Flags: 0 CFlags: 0 Socket: [not set] Methods: 0 Ruid: ulcx-61389f47-2e44-01 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: 0 Keepalive: 0 Last-Keepalive: 1631102280 KA-Roundtrip: 0 Last-Modified: 0 } } } But a few seconds later, the location record has gone: * # date ; kamcmd ul.dump | grep test -A24* Wed 08 Sep 2021 01:58:26 PM CEST In kamailio logs I can see that: * Sep 8 13:58:00 sipserver /usr/sbin/kamailio[11844]: DEBUG: usrloc [ul_rpc.c:637]: ul_rpc_add(): path == 0 -> unset Sep 8 13:58:00 sipserver /usr/sbin/kamailio[11844]: DEBUG: usrloc [ul_rpc.c:652]: ul_rpc_add(): ret: 10 table:kam_location aor:1002-test1@sipserver.com <aor%3A1002-test1(a)sipserver.com> contact:sip:1002-test1@192.168.89.82 <contact%3Asip%3A1002-test1(a)192.168.89.82> expires:3600 dtemp:0.000000 path: flags:0 bflags:0 methods:0 Sep 8 13:58:00 sipserver /usr/sbin/kamailio[11844]: DEBUG: usrloc [ul_rpc.c:660]: ul_rpc_add(): q:0 Sep 8 13:58:00 sipserver /usr/sbin/kamailio[11844]: DEBUG: usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:00 sipserver /usr/sbin/kamailio[11844]: DEBUG: usrloc [ucontact.c:1868]: uldb_insert_attrs(): no location attributes* Sep 8 13:58:03 sipserver /usr/sbin/kamailio[11827]: DEBUG: {1 81337 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:03 sipserver /usr/sbin/kamailio[11827]: DEBUG: {1 81337 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:03 sipserver /usr/sbin/kamailio[11827]: DEBUG: {1 81337 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:04 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 141 REGISTER 1aa357700bd0696702c40340595d89e7(a)185.99.186.215 REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:04 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 141 REGISTER 1aa357700bd0696702c40340595d89e7(a)185.99.186.215 REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:04 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 141 REGISTER 1aa357700bd0696702c40340595d89e7(a)185.99.186.215 REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:06 sipserver /usr/sbin/kamailio[11852]: DEBUG: {1 114 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:06 sipserver /usr/sbin/kamailio[11852]: DEBUG: {1 114 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:06 sipserver /usr/sbin/kamailio[11852]: DEBUG: {1 114 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 12484 REGISTER 1382185578-19234-1(a)BJC.BGI.B.BGC REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 12484 REGISTER 1382185578-19234-1(a)BJC.BGI.B.BGC REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 12484 REGISTER 1382185578-19234-1(a)BJC.BGI.B.BGC REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes * Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11835]: DEBUG: usrloc [urecord.c:377]: wb_timer(): tcp connection has been lost, expiring contact sip:1002-test1@192.168.89.82 <sip%3A1002-test1(a)192.168.89.82> Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11835]: DEBUG: usrloc [urecord.c:387]: wb_timer(): Binding '1002-test1(a)sipserver.com <1002-test1(a)sipserver.com>','sip:1002-test1@192.168.89.82 <sip%3A1002-test1(a)192.168.89.82>' has expired Sep 8 13:58:23 sipserver /usr/sbin/kamailio[11835]: DEBUG: usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes* Sep 8 13:58:25 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 185389 REGISTER 1487655759-19321-1(a)BJC.BGI.B.BBB REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:25 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 185389 REGISTER 1487655759-19321-1(a)BJC.BGI.B.BBB REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:25 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 185389 REGISTER 1487655759-19321-1(a)BJC.BGI.B.BBB REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:33 sipserver /usr/sbin/kamailio[11853]: DEBUG: {1 3360 REGISTER pgmirc5oirbekeaj3tmrf7 REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:33 sipserver /usr/sbin/kamailio[11853]: DEBUG: {1 3360 REGISTER pgmirc5oirbekeaj3tmrf7 REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:33 sipserver /usr/sbin/kamailio[11853]: DEBUG: {1 3360 REGISTER pgmirc5oirbekeaj3tmrf7 REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 5645 REGISTER 89744034-6071-1(a)BJC.BGI.A.BJ REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 5645 REGISTER 89744034-6071-1(a)BJC.BGI.A.BJ REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 5645 REGISTER 89744034-6071-1(a)BJC.BGI.A.BJ REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 5683 REGISTER 1974024198-16543-1(a)BJC.BGI.B.BDE REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 5683 REGISTER 1974024198-16543-1(a)BJC.BGI.B.BDE REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:44 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 5683 REGISTER 1974024198-16543-1(a)BJC.BGI.B.BDE REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:50 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 144820 REGISTER 381139623-5062-1(a)BJC.BGI.B.BAD REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:50 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 144820 REGISTER 381139623-5062-1(a)BJC.BGI.B.BAD REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:50 sipserver /usr/sbin/kamailio[11829]: DEBUG: {1 144820 REGISTER 381139623-5062-1(a)BJC.BGI.B.BAD REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:58:59 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 84973 REGISTER 467700456-5060-1(a)BJC.BGI.B.BCI REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:58:59 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 84973 REGISTER 467700456-5060-1(a)BJC.BGI.B.BCI REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:58:59 sipserver /usr/sbin/kamailio[11828]: DEBUG: {1 84973 REGISTER 467700456-5060-1(a)BJC.BGI.B.BCI REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:59:01 sipserver /usr/sbin/kamailio[11854]: DEBUG: {1 116 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:59:01 sipserver /usr/sbin/kamailio[11854]: DEBUG: {1 116 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:59:01 sipserver /usr/sbin/kamailio[11854]: DEBUG: {1 116 REGISTER 5ne5ebv674tptk0p1uj4gg REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes Sep 8 13:59:04 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 81338 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:1801]: uldb_delete_attrs_ruid(): trying to delete location attributes Sep 8 13:59:04 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 81338 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:72]: ucontact_xavp_store(): trying to clone per contact xavps Sep 8 13:59:04 sipserver /usr/sbin/kamailio[11830]: DEBUG: {1 81338 REGISTER 1955770655-18357-1(a)BJC.BGI.B.BBF REGISTER} usrloc [ucontact.c:1857]: uldb_insert_attrs(): trying to insert location attributes What am I doing wrong? It is supposed that the connection is by UDP. I also tried to insert the socket value as UDP, but it had the same problem. Thanks!

3 6

Topos does not add record-route on invite
by Angelo Sipper 09 Sep '21

09 Sep '21

Hello, We have the following setup on Kamailio 5.3.7 (x86_64/linux) and I am trying to use topos module on Kamailio2 in order to hide our topology but, mostly to reduce the invite size as most of the times we have fragmentation on invites from Kamailio1 as Kamailio1 it adds 2 record-routes and two via as it handles TLS from one side and UDP on the other side and we have found no wat to avoid all this info even with topos enabled on Kamailio1 there is no change on this. UA (OverTLS) -> Kamailio1 (Over UDP)-> Kamailio2 (Over UDP)-> Provider UA :50.50.50.50:5065 (TLS) Kamailio1: 170.170.170.210:5061 (TLS),170.170.170.210:5060 (UDP) Kamailio2: 170.170.170.170:5060 (UDP) Provider: 200.200.200.193:5060 (UDP) Kamailio1 does not run topos. Kamailio2 does run topos and rr with bellow settings: # ------ topos ------ modparam("topos", "db_url", DBURL) modparam("topos", "mask_callid", 0) modparam("topos", "sanity_checks", 0) modparam("topos", "branch_expire", 130) # 3 Min modparam("topos", "dialog_expire", 10800) # 3 Hours modparam("topos", "clean_interval", 60) modparam("topos", "event_mode", 3) modparam("topos", "contact_host", " sbc181.myserver.com") # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) modparam("rr", "ignore_sips", 1) # 0 = do not append from tag to the RR, 0 = append from tag to the RR modparam("rr", "append_fromtag", 0) # dual RR 0 = No, 1 = Yes when needed 2 = Always modparam("rr", "enable_double_rr", 0) The problem is that on the invite from Kamailio2 to provider, topos adds only VIA kai new contact. No record route at all. So the provider sends multiple 200 ok SDPs to wrong IPs. If I disable topos module on kamailio2 everything works fine except that we have huge invite as another VIA and another record route is added having now three of each and fragmentation is present. *Invite from Kamailio1 to Kamailio2* ------------------------------------------------- 2021/09/08 21:41:57.698823 170.170.170.210:5060 -> 170.170.170.181:5060 INVITE sip:1234567890@sip.myserver.com:5060 SIP/2.0 Record-Route: <sip:170.170.170.210;r2=on;lr;ftag=1b973153-4034-4480-89d3-c47b411bd81e;vsf=AAAAAFpUAgEBBwEAAXABAG5BR0EAQUBCZXJ2b2ljZS5ldQ--;vst=AAAAAAoMDgsBBQcGAgIAdENbQG4AFxNUXAUaGQYXWAocY2UuZXU-;did=ff2.96a;nat=yes> Record-Route: <sip:170.170.170.210:5061 ;transport=tls;r2=on;lr;ftag=1b973153-4034-4480-89d3-c47b411bd81e;vsf=AAAAAFpUAgEBBwEAAXABAG5BR0EAQUBCZXJ2b2ljZS5ldQ--;vst=AAAAAAoMDgsBBQcGAgIAdENbQG4AFxNUXAUaGQYXWAocY2UuZXU-;did=ff2.96a;nat=yes> Via: SIP/2.0/UDP 170.170.170.210;branch=z9hG4bKd703.e095cdba1da1a4b1599119c9135b7838.0;i=8eb41 Via: SIP/2.0/TLS 50.50.50.50:5065 ;received=50.50.50.50;rport=31090;branch=z9hG4bKPj9196e5f9-977c-4a53-a4c0-c0ab82b095da;alias From: 987654321 <sip: 987654321(a)sip.myserver.com >;tag=1b973153-4034-4480-89d3-c47b411bd81e To: <sip: 1234567890(a)sip.myserver.com> Contact: <sip:customer1@50.50.50.50:5065 ;transport=TLS;alias=50.50.50.50~31090~3> Call-ID: cd64414e-77d5-45b4-a52d-74ec7fb5c7ef CSeq: 15776 INVITE Supported: 100rel, timer, replaces, norefersub Session-Expires: 1800 Min-SE: 90 Max-Forwards: 69 Content-Type: application/sdp Content-Length: 231 P-Asserted-Identity: <sip: 987654321(a)sip.myserver.com> v=0 o=- 391641952 391641952 IN IP4 170.170.170.216 s=Asterisk c=IN IP4 170.170.170.216 t=0 0 m=audio 29478 RTP/AVP 8 0 18 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=sendrecv a=rtcp:29479 a=ptime:20 *Invite from Kamailio2 to Provider* ------------------------------------------------- 2021/09/08 21:41:57.715881 170.170.170.181:5060 -> 200.200.200.193:5060 INVITE sip: 1234567890@sbc181.myserver.com:5060 SIP/2.0 Via: SIP/2.0/UDP 170.170.170.181;branch=z9hG4bKd703.d45db1fd910c43c5e7c4f8711a5fca92.0 From: 987654321 <sip: 987654321(a)sip.myserver.com >;tag=1b973153-4034-4480-89d3-c47b411bd81e To: <sip:1234567890@sip.myserver.com> Call-ID: cd64414e-77d5-45b4-a52d-74ec7fb5c7ef CSeq: 15776 INVITE Supported: 100rel, timer, replaces, norefersub Session-Expires: 1800 Min-SE: 90 Max-Forwards: 68 Content-Type: application/sdp Content-Length: 231 P-Asserted-Identity: <sip: 987654321(a)sip.myserver.com> Contact: <sip:btpsh-c9-613903ef-21d75-1@sbc181.myserver.com> v=0 o=- 391641952 391641952 IN IP4 170.170.170.184 s=Asterisk c=IN IP4 170.170.170.184 t=0 0 m=audio 11450 RTP/AVP 8 0 18 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=sendrecv a=rtcp:11451 a=ptime:20 *Bellow you can see the flow* ---------------------------------------- 170.170.170.210:5060 170.170.170.170:5060 200.200.200.193:5060 qqqqqqqqqqwqqqqqqqqq qqqqqqqqqqwqqqqqqqqq qqqqqqqqqqwqqqqqqqqq 21:41:57.698823 x INVITE (SDP) x x +0.003788 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x 21:41:57.702611 x 100 trying -- your call is x x +0.013270 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x 21:41:57.715881 x x INVITE (SDP) x +0.018529 x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x 21:41:57.734410 x x 100 Trying x +0.804083 x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x 21:41:58.538493 x x 183 Session Progress (SDP) x +0.014557 x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x 21:41:58.553050 x 183 Session Progress (SDP) x x +0.483907 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x 21:41:59.036957 x x 183 Session Progress (SDP) x +0.012009 x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x 21:41:59.048966 x 183 Session Progress (SDP) x x +0.988036 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:00.037002 x x 183 Session Progress (SDP) x +0.010960 x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x 21:42:00.047962 x 183 Session Progress (SDP) x x +1.989085 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:02.037047 x x 183 Session Progress (SDP) x +0.010947 x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x 21:42:02.047994 x 183 Session Progress (SDP) x x +3.989064 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:06.037058 x x 183 Session Progress (SDP) x +0.008860 x x <<<qqqqqqqqqqqqqqqqqqqqqqqq x 21:42:06.045918 x 183 Session Progress (SDP) x x +1.178240 x <<<qqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:07.224158 x CANCEL x x +0.002725 x qqqqqqqqqqqqqqqqqqqqqqqqqq> x x 21:42:07.226883 x x CANCEL x +0.000372 x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x 21:42:07.227255 x 200 canceling x x +0.016902 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:07.244157 x x 200 OK x +0.004590 x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x 21:42:07.248747 x x 487 Request Terminated x +0.003547 x x <qqqqqqqqqqqqqqqqqqqqqqqqqq x 21:42:07.252294 x x ACK x +0.003737 x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x 21:42:07.256031 x 487 Request Terminated x x +0.001161 x <qqqqqqqqqqqqqqqqqqqqqqqqqq x x 21:42:07.257192 x ACK x x x qqqqqqqqqqqqqqqqqqqqqqqqqq> x TCP is out of question from the provider. Any help to use topos or any other module to reduce the size of our invites to avoid fragmentation will be much appreciated! Regards, Angelo

2 1

manually append_branch to lookup result
by David Villasmil 07 Sep '21

07 Sep '21

Hello guys, I'm trying to dynamically add a branch after doing lookup. The user is found, but in some cases I need to add a branch and do parallel forking. So i'm basically doing: route[LOCATION] { if (!lookup("location")) { .... } if (something) { route(BRANCH_TO_EXTRA); } route(RELAY); } route[BRANCH_TO_EXTRA] { $fs = MY_SOCKET; append_branch("sip:$tU@" + $sel(cfg_get.pstn.gw_ip) + ":" + $sel(cfg_get.pstn.gw_port)); return; } For some reason only the branch appended is being used (I have append_branches=1) Ideas? David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 5

via header not removed wit hremove_hf()
by Richard Robson 07 Sep '21

07 Sep '21

during testing I need to remove a Via header This is the code snippet route[REPLACE_VIA] { xlog ("L_INFO", "[REPLACE_VIA] Start of block\n"); xlog ("L_INFO", "[REPLACE_VIA] $hdrc(Via) Via headers\n"); if(remove_hf("Via")) { xlog ("L_INFO", "[REPLACE_VIA] removed Via\n"); } else { xlog ("L_INFO", "[REPLACE_VIA] did not remove Via\n"); } xlog ("L_INFO", "[REPLACE_VIA] $hdrc(Via) Via headers\n"); and this is the logs output Sep 7 08:00:00 INFO: _LOG: 3a547f956d65fe985ba189916047fc320ae150ad: [REPLACE_RURI] Start of block Sep 7 08:00:00 INFO: _LOG: 3a547f956d65fe985ba189916047fc320ae150ad: [REPLACE_VIA] Start of block Sep 7 08:00:00 INFO: _LOG: 3a547f956d65fe985ba189916047fc320ae150ad: [REPLACE_VIA] 1 Via headers Sep 7 08:00:00 INFO: _LOG: 3a547f956d65fe985ba189916047fc320ae150ad: [REPLACE_VIA] removed Via Sep 7 08:00:00 INFO: _LOG: 3a547f956d65fe985ba189916047fc320ae150ad: [REPLACE_VIA] 1 Via headers From the logs it looks like the remove_hf returns true and we have the header removed, but its still counting the Via header and the Via Header is still present when the INVIE is releyed on Regards, Richard

2 4

Jump to page:

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