sr-dev November 2021

sr-dev@lists.kamailio.org

20 participants
310 discussions

[kamailio/kamailio] lost: lost_held_dereference do not handles error message (#2724)

by sergey-safarov

### Description When LIS server failed, then LIS send message like ``` The error response to the request is an error document. The following response shows an example error response. HTTP/1.1 200 OK Server: Example LIS Expires: Tue, 10 Jan 2006 03:49:20 GMT Cache-control: private Content-Type: application/held+xml;charset=utf-8 Content-Length: 182 <?xml version="1.0"?> <error xmlns="urn:ietf:params:xml:ns:geopriv:held" code="locationUnknown"> <message xml:lang="en">Unable to determine location </message> </error> ``` Here is HTTP code is 200. lost_held_dereference now simply check HTTP code and do not check XML body. Expected XML content check for: 1. XML HELD error message 2. check `findServiceResponse` or `presence` element check like it done for `lost_query`. This check is important because PIDF-LO object may be added to the multipart body. And HELD XML error handling prevents error message addition as PDF-LO object. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724

1 year

[kamailio/kamailio] Kamailio resets $ru in branch_route context, probably race condition (#2708)

by Henning Westerholt

### Description Kamailio resets the $ru in a branch_route context, probably due a race condition and/or bug. Scenario: - Calls is established and answered with 404 - Kamailio enters failure_route - failure_route calls t_relay() - branch_route is entered - new branch is created with $ru = $ru; - next operation trying to access content of the $ru fails: Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: pv [pv_core.c:325]: pv_get_ruri_attr(): failed to parse the R-URI ### Troubleshooting Happens on a production system, after upgrade from 5.2.x to 5.3.9. Research regarding similar bugs have not produced something useful so far. #### Reproduction Issue happens less than 10 times a day and so far could not be easily reproduced. #### Debugging Data Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: NOTICE: 7e8bb2ba47f5ccc |-----> Failure Code 404<- Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[Failure] c=[/etc/kamailio/kamailio.cfg] l=1720 a=5 n=route Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=703 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=699 a=25 n=is_method Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=702 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=701 a=25 n=t_is_set Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=701 a=25 n=t_on_branch Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=707 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=703 a=25 n=is_method Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=706 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=705 a=25 n=t_is_set Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=707 a=25 n=t_on_branch_failure Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=720 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=711 a=25 n=is_method Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=714 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=713 a=25 n=t_is_set Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=713 a=25 n=t_on_failure Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=742 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:failure_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=720 a=24 n=t_relay Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:branch_route=[MANAGE_BRANCH] c=[/etc/kamailio/kamailio.cfg] l=2142 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:branch_route=[MANAGE_BRANCH] c=[/etc/kamailio/kamailio.cfg] l=2135 a=63 n=assign Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:branch_route=[MANAGE_BRANCH] c=[/etc/kamailio/kamailio.cfg] l=2147 a=16 n=if Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:branch_route=[MANAGE_BRANCH] c=[/etc/kamailio/kamailio.cfg] l=2142 a=25 n=is_method Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: *** cfgtrace:branch_route=[MANAGE_BRANCH] c=[/etc/kamailio/kamailio.cfg] l=2142 a=63 n=assign Apr 13 11:44:39 proxy1 /usr/sbin/kamailio[2202]: ERROR: pv [pv_core.c:325]: pv_get_ruri_attr(): failed to parse the R-URI #### Log Messages See cfgtrace logging above. #### SIP Traffic Not easily to provide as its a productive system in a clustered setup. ### Possible Solutions Ideas on how to further debug this error are welcome. ### Additional Information * kamailio 5.3.9 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2708

1 year

[kamailio/kamailio] [Feature] RFC 8760 support (#2668)

by Timothy Vanderaerden

### Description As far as I know there is currently no support for [RFC-8760](https://tools.ietf.org/html/rfc8760) yet. It modifies the Digest Access Authentication scheme to add support for more secure digest algorithms, e.g., SHA-256 and SHA-512/256, to replace the obsolete MD5 algorithm. Are there any plans to implement this? ### Possible Solutions Extending the auth module to accept these algorithms as a function parameter would be nice to have since older clients may not support them. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2668

1 year

[kamailio/kamailio] tlsf memory manager status weirdness (#2628)

by lazedo

### Description TLSF mem manager accounting for wrong values was trying to debug a crash and this popped up. using a lot of small allocs until pkg_alloc returns NULL (when exhausted) when NULL is returned the memory **used+overhead** exceeds the heap allocated.  ### Troubleshooting #### Reproduction use frequent small memory allocs until pool is exausted (returns NULL) , check tlsf status. static void do_test_mem() { void* chunk; tlsf_t pool = NULL; size_t total = 16 * 1024 * 1024; size_t half = 8 * 1024 * 1024; size_t sz = 6; int x; void* mem = malloc(total); char* mem2 = tlsf_cast(char*, tlsf_cast(ptrdiff_t, mem) + half); memset(mem2, 'X', half); assert(*mem2 == 'X'); pool = tlsf_create_with_pool(mem, half); do { chunk = tlsf_malloc(pool, sz); } while(chunk != NULL); tlsf_status(pool); for(x=0; x < half; x++) { assert(*mem2 == 'X'); mem2++; } free(mem); }   ``` heap size= **8388592** used= **6285144**, used+overhead=**12578696**, free=**18446744073705361512**, fragments=0 max used (+overhead)=12578696, max fragments=1 Free blocks matrix ('.': none, 'X': between 2^X and (2^(X+1)-1) free blocks, X=A..Z, A=0, B=1, ...) > first-level: 32 block list arrays between 2^fl and 2^(fl+1) bytes (fl=8..39) v second-level: 32 block lists between 2^fl+sl*2^(fl-5) and 2^fl+(sl+1)*2^(fl-5)-1 bytes (sl=0..31) 0|................................| 1|................................| 2|................................| 3|................................| 4|................................| 5|................................| 6|................................| 7|................................| 8|................................| 9|................................| 10|................................| 11|................................| 12|................................| 13|................................| 14|................................| 15|................................| 16|................................| 17|................................| 18|................................| 19|................................| 20|................................| 21|................................| 22|................................| 23|................................| 24|................................| 25|................................| 26|................................| 27|................................| 28|................................| 29|................................| 30|................................| 31|................................| ``` #### Log Messages  ``` identical to reproduce step when calling mem debug on a running instance ``` ### Possible Solutions  ### Additional Information ``` * **Kamailio Version** - built from master ``` * **Operating System**:  ``` CentOS7 and alpine ``` ## comments heap size= **8388592** shouldn't it be **8388608** ? used+overhead=**12578696** misleading free=**18446744073705361512** misleading, looks like it has a negative value the map doesn't look ok (or i'm not understanding what it should show), its the same output before the alloc and after. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2628

1 year

[kamailio/kamailio] SLA presence not working proper with (SCA module) (#2583)

by aatif218

Hello I configure my kamailio.cfg to handle SLA using (SCA module) and shared presence is working but still facing some issue in case of hold invite and BYE and the reason behind of that issue is following error Nov 26 07:38:40 SBC-4-1 /usr/local/sbin/kamailio[104107]: ERROR: sca [sca_call_info.c:1008]: sca_call_info_invite_request_handler(): Failed to update sip:4569@test.sip.abcd.com appearance-index 0 to active actually, in Kamailio appearances, I can see the entry for this call but the index is 1 instead of 0, and Kamailio going to update with a 0 index [root@SBC-4-1 ntcarfte-kamailio]# kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 active 1606376289 sip:4569@10.xx.xx.xx:5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120MTQ5OTcyZjFhMjMyNmI1ZGE1MWY4ODc2M2RkN2VmZmQ 45dc18d8 H6cS9vecZ248B if I manually update appearances using RPC command with index 1 then the phone started blinking as I change state to held # kamcmd sca.update_appearance sip:4569@sc4test.sip.teledge.com 1 held # kamcmd sca.all_appearances sip:4569@test.sip.abcd.com 1 held 1606376516 sip:4569@10.xx.xx.xx:5070;transport=udp sip:2003@test.sip.abcd.com 186161_mobile-rel120NzE5MDgyZDc1NjJiYjcwMWFlYmI3NzM3NjE2OTRhZjU 08f005cb eK9ratm83g92e kamailio.cfg route[SCA] { if(is_method("SUBSCRIBE")) { if ($hdr(Event) == "call-info" || $hdr(Event) == "line-seize") { xlog("L_INFO","(MAIN) :HELLO ($avp(uuid)) : $avp(rsi) $sp $hdr(Event)"); xdbg("SCA: $hdr(Event) SUBSCRIBE $ru from $si:$sp"); sca_handle_subscribe(); exit; } return; } if (!is_method("BYE|CANCEL|INVITE|PRACK|REFER")) { return; } sca_call_info_update(); } route[RELAY_OUTBOUND_FS] { xlog("L_INFO","(RELAY_OUTBOUND_FS) : ($avp(uuid)) : INSIDE ROUTE "); if (!has_totag()){ $avp(set_h) = 1; } t_on_reply("REPLY_OUTBOUND_FS"); route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } route[RELAY_INBOUND_FS] { if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { $avp(s:puburis_caller) = $fu; setflag(8); dlg_manage(); } if(is_method("REGISTER")) { t_on_reply("REPLY_REGISTER"); } else { t_on_reply("REPLY_INBOUND_FS"); } route(SCA); if (!t_relay()) { sl_reply_error(); } exit; } onreply_route[REPLY_INBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } onreply_route[REPLY_OUTBOUND_FS] { xdbg("incoming reply\n"); if (status =~ "[456][0-9][0-9]") { # don't update SCA state here, since there may be # failure route processing (e.g., call forwarding). # update state in failure route instead. return; } route(SCA); } -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2583

1 year

[kamailio/kamailio] CDRs not produced when websocket has closed (#2587)

by kmduk

With the dialog and acc modules configured to generate CDRs to syslog, sometimes a CDR is not generated when a call ends. It appears that this is because some callers are closing the websocket just after sending the BYE. That means that when the 200 response to the BYE arrives it can't be relayed as the websocket has closed. It does seem to be timing related. We use the websocket close event to shorten the dialog timeout to 1 second. We also don't get a CDR if we close the websocket while a call is active. The dialog times out and sends a BYE to the callee (it fails to send to the caller, not because the websocket is closed but because the *.invalid contact address can't be resolved!) and then destroys the dialog. [kamailio.log](https://github.com/kamailio/kamailio/files/5702715/kamailio.l… [kamailio-sipdump-2020-12-16--11-13-52.data.log](https://github.com/kamailio… * **Kamailio Version** - output of `kamailio -v` version: kamailio 5.3.6 (x86_64/linux) fb26c8 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_BLACKLIST, HAVE_RESOLV_RES 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: fb26c8 compiled on 11:51:56 Nov 17 2020 with gcc 4.8.5 * **Operating System**: Linux ip-172-30-0-66 4.14.114-83.126.amzn1.x86_64 #1 SMP Tue May 7 02:26:58 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2587

1 year

[kamailio/kamailio] Kamailio 5.4.2 Crash - core/timer.c & cdp/peermanager.c (#2581)

by Hamid R. Hashmi

### Description We are using kamailio as P-CSCF and its time 2 time crashing only on production Envoirnmnet with sig11 and sig6. ### Troubleshooting As my little understanding, issue is with core/timer.c for signal 11 crash and ims_qos for sig6. #### Reproduction Issue only occour on our Production envoirnmnet. I dont have reproduction steps. #### Debugging Data Sig 11 ``` Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -f /usr/local/etc/kamailio_pcscf/kamailio.cfg -P /var/'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00000000006a16fc in timer_list_expire (t=1339518316, h=0x7facee484fd0, slow_l=0x7facee488208, slow_mark=7936) at core/timer.c:846 846 _timer_rm_list(tl); /* detach */ (gdb) bt #0 0x00000000006a16fc in timer_list_expire (t=1339518316, h=0x7facee484fd0, slow_l=0x7facee488208, slow_mark=7936) at core/timer.c:846 #1 0x00000000006a1c19 in timer_handler () at core/timer.c:922 #2 0x00000000006a20ba in timer_main () at core/timer.c:961 #3 0x000000000042ac0a in main_loop () at main.c:1753 #4 0x000000000043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856 (gdb) bt full #0 0x00000000006a16fc in timer_list_expire (t=1339518316, h=0x7facee484fd0, slow_l=0x7facee488208, slow_mark=7936) at core/timer.c:846 tl = 0x7facf048e1b8 ret = 0 #1 0x00000000006a1c19 in timer_handler () at core/timer.c:922 saved_ticks = 1339518316 run_slow_timer = 0 i = 768 __FUNCTION__ = "timer_handler" #2 0x00000000006a20ba in timer_main () at core/timer.c:961 No locals. #3 0x000000000042ac0a in main_loop () at main.c:1753 i = 32 pid = 0 si = 0x0 si_desc = "udp receiver child=31 sock=10.161.224.211:5060", '\000' <repeats 11 times>, "\354\325K\346\060\375\350\003\000\000\000\314\000\000\000\365k\000\000\000\000\000\000P\272A\000\000\000\000\000P\343o%\374\177", '\000' <repeats 18 times>, "\320\335o%\374\177\000\000\215\006Z\000\000\000\000" nrprocs = 32 woneinit = 1 __FUNCTION__ = "main_loop" #4 0x000000000043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856 cfg_stream = 0x2674010 c = -1 r = 0 tmp = 0x7ffc256fff2c "" tmp_len = 32685 port = -1767840736 proto = 32685 ahost = 0x0 aport = 0 options = 0x7e2058 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1101782887 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fad96a1d5f7 p = 0x7fad96a0e77c "free" st = {st_dev = 17, st_ino = 15237, st_nlink = 2, st_mode = 16877, st_uid = 105, st_gid = 112, __pad0 = 0, st_rdev = 0, st_size = 120, st_blksize = 4096, st_blocks = 0, st_atim = { tv_sec = 1607000056, tv_nsec = 100000000}, st_mtim = {tv_sec = 1607002632, tv_nsec = 716000000}, st_ctim = {tv_sec = 1607003887, tv_nsec = 44000000}, __glibc_reserved = {0, 0, 0}} tbuf = "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\210'Ö\255\177\000\000\030\207\241\226\255\177\000\000\000\000\000\000\000\000\000\000\220\340o%\374\177\000\000`\261w%\374\177\000\000\240\341o%\374\177\000\000رw%\374\177\000\000\220\341o%\374\177\000\000\000\000\000\000\000\000\000\000<\177\241\226\255\177\000\000\000\000\000\000\000\000\000\000.N=\366\000\000\000\000\004\000\000\000\000\000\000\000\006\000\000\000\000\000\000\000\250u\302\226\255\177\000\000\266\210\241\226\255\177", '\000' <repeats 11 times>, "\341o%\374\177\000\000\060=\362\225\255\177\000\000\020\342o%\374\177\000\000\370\001\363\225\255\177\000\000\070\365\330\003\000\000\000\000\000\342o%\374\177\000\000\350*Ö"... option_index = 0 long_options = {{name = 0x7e424f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x7df854 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x7e4254 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x7e425a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x7e4260 "substdef", has_arg = 1, flag = 0x0, val = 1026}, { name = 0x7e4269 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x7e4273 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x7e427d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x7e4288 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x7e4291 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, { name = 0x7e429c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __FUNCTION__ = "main" (gdb) ``` Sig 6: ``` Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -f /usr/local/etc/kamailio_pcscf/kamailio.cfg -P /var/'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fad95f56c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007fad95f56c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fad95f5a028 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x000000000041e39d in sig_alarm_abort (signo=14) at main.c:687 #3 <signal handler called> #4 0x00007fad960183c7 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007fad6f5c024b in futex_get (lock=0x7facee70baa0) at ../../core/mem/../futexlock.h:121 #6 0x00007fad6f5c2167 in get_peer_by_fqdn (fqdn=0x7faceeb377b0) at peermanager.c:240 #7 0x00007fad6f5e6c31 in get_first_connected_route (cdp_session=0x7faceeb37768, r=0x7facee70a220, app_id=16777236, vendor_id=10415) at routing.c:110 #8 0x00007fad6f5ea8b2 in get_routing_peer (cdp_session=0x7faceeb37768, m=0x7facef617fb0) at routing.c:272 #9 0x00007fad6f5ac72d in AAASendMessage (message=0x7facef617fb0, callback_f=0x0, callback_param=0x0) at diameter_comm.c:137 #10 0x00007fad6ef05dbb in rx_send_str (rx_session_id=0x7facf0849d50) at rx_str.c:157 #11 0x00007fad6eeb25c4 in callback_dialog (dlg=0x7facf0036d70, type=8192, params=0x7fad72b2a1c0 <params>) at ims_qos_mod.c:453 #12 0x00007fad728973af in run_dlg_callbacks (type=8192, dlg=0x7facf0036d70, req=0x0, rpl=0x0, dir=0, dlg_data=0x0) at dlg_cb.c:274 #13 0x00007fad728d5315 in destroy_dlg (dlg=0x7facf0036d70) at dlg_hash.c:219 #14 0x00007fad728d5b1b in destroy_dlg_table () at dlg_hash.c:291 #15 0x00007fad7290b71e in mod_destroy () at ims_dialog.c:627 #16 0x0000000000616ae1 in destroy_modules () at core/sr_module.c:746 #17 0x000000000041ce17 in cleanup (show_status=1) at main.c:563 #18 0x000000000041e6ef in shutdown_children (sig=15, show_status=1) at main.c:706 #19 0x0000000000421755 in handle_sigs () at main.c:806 #20 0x000000000042bc85 in main_loop () at main.c:1817 #21 0x000000000043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856 (gdb) bt full #0 0x00007fad95f56c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007fad95f5a028 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x000000000041e39d in sig_alarm_abort (signo=14) at main.c:687 __FUNCTION__ = "sig_alarm_abort" #3 <signal handler called> No symbol table info available. #4 0x00007fad960183c7 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #5 0x00007fad6f5c024b in futex_get (lock=0x7facee70baa0) at ../../core/mem/../futexlock.h:121 v = 1 i = 0 #6 0x00007fad6f5c2167 in get_peer_by_fqdn (fqdn=0x7faceeb377b0) at peermanager.c:240 i = 0x7f4d8a #7 0x00007fad6f5e6c31 in get_first_connected_route (cdp_session=0x7faceeb37768, r=0x7facee70a220, app_id=16777236, vendor_id=10415) at routing.c:110 peers = {0x7facee9f4870, 0x18, 0x1, 0x0, 0x102ef763ea8, 0xc, 0x0, 0x11b00000000, 0x0, 0x7facef617fb0, 0x7facf0a3f2d0, 0x7facef2b5f90, 0x8, 0x7facee407000, 0x7ffc256fd0d0, 0x7ffc256fd0dc, 0x3007df3d8, 0x7fad6f617680, 0x41b610 <syslog@plt>, 0x7f4d8a} peer_count = 0 prev_metric = 0 i = 0x1007f4d8a p = 0x7ffc256fcff0 j = 628084656 least_recent_time = 7234707 time_spec = {tv_sec = 140382874676976, tv_nsec = 1569531277302} __FUNCTION__ = "get_first_connected_route" #8 0x00007fad6f5ea8b2 in get_routing_peer (cdp_session=0x7faceeb37768, m=0x7facef617fb0) at routing.c:272 destination_realm = {s = 0x7facef6d38f0 "isbvpcrf001.zte.com", len = 19} destination_host = {s = 0x0, len = 0} avp = 0x7facef2b5f90 avp_vendor = 0x0 avp2 = 0x0 group = {head = 0x0, tail = 0x0} p = 0x0 rr = 0x0 app_id = 16777236 vendor_id = 10415 __FUNCTION__ = "get_routing_peer" #9 0x00007fad6f5ac72d in AAASendMessage (message=0x7facef617fb0, callback_f=0x0, callback_param=0x0) at diameter_comm.c:137 cdp_session = 0x7faceeb37768 p = 0x7facef7fdce0 __FUNCTION__ = "AAASendMessage" #10 0x00007fad6ef05dbb in rx_send_str (rx_session_id=0x7facf0849d50) at rx_str.c:157 __FUNCTION__ = "rx_send_str" auth = 0x7faceeb37768 str = 0x7facef617fb0 avp = 0x7facef2b5f90 x = "\000\000\000\001" #11 0x00007fad6eeb25c4 in callback_dialog (dlg=0x7facf0036d70, type=8192, params=0x7fad72b2a1c0 <params>) at ims_qos_mod.c:453 msg = 0x0 parsed_cseq = 0x7facee4406c8 rx_session_id = 0x7facf0849d50 ---Type <return> to continue, or q <return> to quit--- auth = 0x0 p_session_data = 0x0 current_fd = 0x0 new_fd = 0x0 current_has_video = 0 new_has_video = 0 must_unlock_aaa = 1 __FUNCTION__ = "callback_dialog" #12 0x00007fad728973af in run_dlg_callbacks (type=8192, dlg=0x7facf0036d70, req=0x0, rpl=0x0, dir=0, dlg_data=0x0) at dlg_cb.c:274 cb = 0x7facf0849e68 __FUNCTION__ = "run_dlg_callbacks" #13 0x00007fad728d5315 in destroy_dlg (dlg=0x7facf0036d70) at dlg_hash.c:219 ret = 0 var = 0x7faceea76348 __FUNCTION__ = "destroy_dlg" #14 0x00007fad728d5b1b in destroy_dlg_table () at dlg_hash.c:291 dlg = 0x0 l_dlg = 0x7facf0036d70 i = 120 __FUNCTION__ = "destroy_dlg_table" #15 0x00007fad7290b71e in mod_destroy () at ims_dialog.c:627 No locals. #16 0x0000000000616ae1 in destroy_modules () at core/sr_module.c:746 t = 0x7fad75fcae18 foo = 0x7fad75fca710 __FUNCTION__ = "destroy_modules" #17 0x000000000041ce17 in cleanup (show_status=1) at main.c:563 memlog = 0 __FUNCTION__ = "cleanup" #18 0x000000000041e6ef in shutdown_children (sig=15, show_status=1) at main.c:706 __FUNCTION__ = "shutdown_children" #19 0x0000000000421755 in handle_sigs () at main.c:806 chld = 0 chld_status = 139 any_chld_stopped = 1 memlog = 0 __FUNCTION__ = "handle_sigs" #20 0x000000000042bc85 in main_loop () at main.c:1817 i = 32 pid = 27887 si = 0x0 si_desc = "udp receiver child=31 sock=10.161.224.211:5060", '\000' <repeats 11 times>, "\354\325K\346\060\375\350\003\000\000\000\314\000\000\000\365k\000\000\000\000\000\000P\272A\000\000\000\000\000P\343o%\374\177", '\000' <repeats 18 times>, "\320\335o%\374\177\000\000\215\006Z\000\000\000\000" nrprocs = 32 woneinit = 1 __FUNCTION__ = "main_loop" #21 0x000000000043400c in main (argc=13, argv=0x7ffc256fe358) at main.c:2856 cfg_stream = 0x2674010 c = -1 r = 0 tmp = 0x7ffc256fff2c "" tmp_len = 32685 ---Type <return> to continue, or q <return> to quit--- port = -1767840736 proto = 32685 ahost = 0x0 aport = 0 options = 0x7e2058 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1101782887 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fad96a1d5f7 p = 0x7fad96a0e77c "free" st = {st_dev = 17, st_ino = 15237, st_nlink = 2, st_mode = 16877, st_uid = 105, st_gid = 112, __pad0 = 0, st_rdev = 0, st_size = 120, st_blksize = 4096, st_blocks = 0, st_atim = { tv_sec = 1607000056, tv_nsec = 100000000}, st_mtim = {tv_sec = 1607002632, tv_nsec = 716000000}, st_ctim = {tv_sec = 1607003887, tv_nsec = 44000000}, __glibc_reserved = {0, 0, 0}} tbuf = "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\210'Ö\255\177\000\000\030\207\241\226\255\177\000\000\000\000\000\000\000\000\000\000\220\340o%\374\177\000\000`\261w%\374\177\000\000\240\341o%\374\177\000\000رw%\374\177\000\000\220\341o%\374\177\000\000\000\000\000\000\000\000\000\000<\177\241\226\255\177\000\000\000\000\000\000\000\000\000\000.N=\366\000\000\000\000\004\000\000\000\000\000\000\000\006\000\000\000\000\000\000\000\250u\302\226\255\177\000\000\266\210\241\226\255\177", '\000' <repeats 11 times>, "\341o%\374\177\000\000\060=\362\225\255\177\000\000\020\342o%\374\177\000\000\370\001\363\225\255\177\000\000\070\365\330\003\000\000\000\000\000\342o%\374\177\000\000\350*Ö"... option_index = 0 long_options = {{name = 0x7e424f "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x7df854 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x7e4254 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x7e425a "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x7e4260 "substdef", has_arg = 1, flag = 0x0, val = 1026}, { name = 0x7e4269 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x7e4273 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x7e427d "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x7e4288 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x7e4291 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, { name = 0x7e429c "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __FUNCTION__ = "main" (gdb) ``` There so many udp_send_failed error in logs so I tried to debug that process ``` #0 0x00007f668aa94013 in recvfrom () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00000000006638d0 in udp_rcv_loop () at core/udp_server.c:460 len = 638 buf = "SUBSCRIBE tel:+923492324215 SIP/2.0\r\nFrom: <tel:+923492324215>;tag=2869510412\r\nTo: <tel:+923492324215>\r\nCSeq: 722026762 SUBSCRIBE\r\nCall-ID: 2869510410_3596082716(a)10.100.217.241\r\nVia: SIP/2.0/UDP 10.100"... tmp = 0xdf831260 <error: Cannot access memory at address 0xdf831260> from = 0x7f666ac86e78 fromlen = 16 ``` another proocess ``` #0 0x00007f668aa94013 in recvfrom () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00000000006638d0 in udp_rcv_loop () at core/udp_server.c:460 len = 952 buf = "REGISTER sip:ims.mnc006.mcc410.3gppnetwork.org SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.213.50;rport;branch=z9hG4bKL60mek0i6jXu6V\r\nFrom: <sip:410060265715793@ims.mnc006.mcc410.3gppnetwork.org>;tag=jYbVBQiAfL1"... tmp = 0xdf831260 <error: Cannot access memory at address 0xdf831260> from = 0x7f666ac86e78 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {140072621270026, 140723275665552}, addr32 = {852845578, 32613, 2967179408, 32764}, addr16 = {25610, 13013, 32613, 0, 37008, 45275, 32764, 0}, addr = "\nd\325\062e\177\000\000\220\220۰\374\177\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {3839926538, 0}, addr32 = {3839926538, 0, 0, 0}, addr16 = {41226, 58592, 0, 0, 0, 0, 0, 0}, addr = "\n\241\340\344", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304\nd\325\062\000\000\000\000\000\000\000"}, sin = { sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 852845578}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 852845578, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7f666aa23d78, proto = 1 '\001'} evp = {data = 0x0, rcv = 0x0, dst = 0x0} printbuf = "P\221۰\374\177\000\000\005\364<\337e\177\000\000 \221۰\374\177\000\000\265˧\337e\177\000\000\340\223۰\374\177\000\000L\221۰\374\177\000\000\340\223۰\004\000\000\000\360\005|\000\016\000\000\000n\365\023o\016\000\000\000\177$\000\000\000\000\000\000P\221۰\374\177\000\000(6\373\337e\177\000\000`\211A\000\000\000\000\000`\227۰\374\177", '\000' <repeats 18 times>, "\020\222۰\374\177\000\000\035\261]", '\000' <repeats 21 times>, "\300\022\262\000\000\000\000\000I/e\025\000\000\000\000`\211A\000\000\000\000\000`\227۰\374\177", '\000' <repeats 19 times>, "\222"... i = -537187496 j = 32613 l = 32613 __FUNCTION__ = "udp_rcv_loop" #2 0x0000000000424c4c in main_loop () at main.c:1628 ``` #### Log Messages There are lot of such error in log level 0. ``` Dec 10 17:01:30 pcscf [Proxy-CSCF][5798]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5798]: WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5798]: ERROR: <script>: [+923335050681 03469646904 51D4A031-5FD20DB4000DF0EC-6DCDF700 INVITE] t_relay returned code - -1 Dec 10 17:01:30 pcscf [Proxy-CSCF][5798]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Dec 10 17:01:30 pcscf [Proxy-CSCF][5827]: ERROR: <script>: [+923335050681 03469646904 51D4A031-5FD20DB4000DF0EC-6DCDF700 ACK] Relaying Request to sip:10.100.19.40:5060 Dec 10 17:01:30 pcscf [Proxy-CSCF][5815]: ERROR: <script>: [+923335050681 03469646904 0f7e963a-edba-4818-96c1-5b86c5ab460f ACK] Relaying Request to sip:10.100.19.40:5060 Dec 10 17:01:30 pcscf [Proxy-CSCF][5843]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff7695d0,879,0,10.100.217.32:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5843]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5843]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5712]: ERROR: <script>: Re-Transmit: REGISTER (sip:410060543905859@ims.mnc006.mcc410.3gppnetwork.org (10.100.32.122:5060) to sip:410060543905859@ims.mnc006.mcc410.3gppnetwork.org, 3133259377_751769164(a)10.100.32.122) Dec 10 17:01:30 pcscf [Proxy-CSCF][5763]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff76a678,348,0,10.100.247.52:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5763]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5763]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5770]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff769b10,929,0,10.100.191.77:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5770]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5770]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5697]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff7688b0,346,0,10.100.34.62:5060,16): Invalid argument(22)Dec 10 17:01:30 pcscf [Proxy-CSCF][5697]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5697]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5811]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff7685b0,934,0,10.100.251.103:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5811]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5811]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5742]: ERROR: <script>: [410060460486067 410060460486067 QichLJ2zkELhtXoCr6g REGISTER] Relaying Request to sip:ims.mnc006.mcc410.3gppnetwork.org Dec 10 17:01:30 pcscf [Proxy-CSCF][5916]: ERROR: <core> [core/tcp_read.c:301]: tcp_read_data(): error reading: Connection timed out (110) ([10.100.183.203]:1030 -> Dec 10 17:01:30 pcscf [Proxy-CSCF][5916]: ERROR: <core> [core/tcp_read.c:302]: tcp_read_data(): -> [10.161.224.228]:5060) Dec 10 17:01:30 pcscf [Proxy-CSCF][5916]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f5e3a198cd0 r: 0x7f5e3a198d50 Dec 10 17:01:30 pcscf [Proxy-CSCF][5736]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff76a7d8,358,0,10.100.49.211:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5736]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5736]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5736]: ERROR: <script>: [410060741303598 410060741303598 xq2Tdyiihj7vlodiPoI REGISTER] Relaying Request to sip:ims.mnc006.mcc410.3gppnetwork.org Dec 10 17:01:30 pcscf [Proxy-CSCF][5733]: ERROR: <script>: Re-Transmit: REGISTER (sip:410060256289042@ims.mnc006.mcc410.3gppnetwork.org (10.100.166.211:5060) to sip:410060256289042@ims.mnc006.mcc410.3gppnetwork.org, HoMEyy6arvvc1vvehJe) Dec 10 17:01:30 pcscf [Proxy-CSCF][5733]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5efed06560,882,0,10.100.166.211:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5733]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5733]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5733]: WARNING: tm [t_reply.c:1581]: t_retransmit_reply(): send pr buffer failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5696]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff7690d8,349,0,10.100.165.192:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5696]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5696]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5788]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff76ba08,926,0,10.100.6.243:5060,16): Invalid argument(22)Dec 10 17:01:30 pcscf [Proxy-CSCF][5788]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5788]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5885]: ERROR: cdp [authstatemachine.c:404]: auth_client_statefull_sm_process(): auth_client_statefull_sm_process(): Received invalid event 6 while in state Open! Dec 10 17:01:30 pcscf [Proxy-CSCF][5717]: ERROR: <script>: Re-Transmit: REGISTER (sip:410060548570762@ims.mnc006.mcc410.3gppnetwork.org (10.100.193.242:5060) to sip:410060548570762@ims.mnc006.mcc410.3gppnetwork.org, 3146661978_3836711884(a)10.100.193.242) Dec 10 17:01:30 pcscf [Proxy-CSCF][5717]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5efed06560,957,0,10.100.193.242:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5717]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5717]: ERROR: tm [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5717]: WARNING: tm [t_reply.c:1581]: t_retransmit_reply(): send pr buffer failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5918]: ERROR: <script>: [03497290720 +923481006204 xHiYwrcWiZ65jbLKA76 ACK] Relaying Request to sip:10.161.224.212:5080 Dec 10 17:01:30 pcscf [Proxy-CSCF][5776]: ERROR: <script>: [03497290720 +923481006204 2A24C52B-5FD20DA600002FE3-76C6E700 ACK] Relaying Request to sip:03497290720@10.161.225.14:15080;transport=udp Dec 10 17:01:30 pcscf [Proxy-CSCF][5747]: ERROR: <script>: [410060261800036 410060261800036 5aP3ApQicP7xocoTOT9 REGISTER] Relaying Request to sip:ims.mnc006.mcc410.3gppnetwork.org Dec 10 17:01:30 pcscf [Proxy-CSCF][5764]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff768628,344,0,10.100.2.48:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5764]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5764]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5753]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff76a338,356,0,10.100.40.40:5060,16): Invalid argument(22)Dec 10 17:01:30 pcscf [Proxy-CSCF][5753]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5753]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed Dec 10 17:01:30 pcscf [Proxy-CSCF][5753]: ERROR: <script>: [410060561499599 410060561499599 FMmoB0mfycODVi76kdn REGISTER] Relaying Request to sip:ims.mnc006.mcc410.3gppnetwork.org Dec 10 17:01:30 pcscf [Proxy-CSCF][5743]: ERROR: <core> [core/udp_server.c:596]: udp_send(): sendto(sock,0x7f5eff76aa50,358,0,10.100.161.17:5060,16): Invalid argument(22) Dec 10 17:01:30 pcscf [Proxy-CSCF][5743]: CRITICAL: <core> [core/udp_server.c:601]: udp_send(): invalid sendtoparameters#012one possible reason is the server is bound to localhost and#012attempts to send to the net Dec 10 17:01:30 pcscf [Proxy-CSCF][5743]: ERROR: sl [../../core/forward.h:219]: msg_send_buffer(): udp_send failed ``` ### Additional Information * **Kamailio Version** - output of `kamailio -I` ``` Version: kamailio 5.4.2 (x86_64/linux) Default config: /usr/local/etc/kamailio/kamailio.cfg Default paths to modules: /usr/local/lib64/kamailio/modules Compile 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_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE=262144 MAX_URI_SIZE=1024 BUF_SIZE=65535 DEFAULT PKG_SIZE=8MB DEFAULT SHM_SIZE=64MB ADAPTIVE_WAIT_LOOPS=1024 TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select Source code revision ID: unknown Compiled with: gcc 4.8.4 Compiled architecture: x86_64 Compiled on: 12:54:15 Dec 2 2020 Thank you for flying kamailio! ``` * **Operating System**: ``` $ cat /etc/*lease DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" NAME="Ubuntu" VERSION="14.04.5 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.5 LTS" VERSION_ID="14.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" $ uname -a Linux pcscf 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2581

1 year

[kamailio/kamailio] cannot my loaded ims_dialog-create.sql into mysql (#2575)

by sergey-safarov

### Description When I try to load kamailio schema into MySQL database I get an error "Duplicate entry 'dialog_vars' for key 'PRIMARY'". I have checked the duplicated `dialog_vars` table definition at 1. [dialog-create.sql#L32-L38](https://github.com/kamailio/kamailio/blob/master… 2. [ims_dialog-create.sql#L41-L49](https://github.com/kamailio/kamailio/blob/ma… #### Reproduction Load schemas from dialog-create.sql and from ims_dialog-create.sql. ### Possible Solutions Remove `dialog_vars` table definition from `ims_dialog-create.sql` shema file. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` @safarov-dell:/usr/share/kamailio$ kamailio -v version: kamailio 5.5.0-dev3 (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 on 12:51:16 Dec 4 2020 with gcc 10.2.1 ``` * **Operating System**: ``` @safarov-dell:/usr/share/kamailio$ cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.13.0_alpha20200917 PRETTY_NAME="Alpine Linux edge" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://bugs.alpinelinux.org/" ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2575

1 year

[kamailio/kamailio] presence not work proper with subs_db_mode = 2 (#2540)

by aatif218

Hello I have problem with Kamailio presence,i have configure my kamailio.cfg to handle dialog presence and facing issue in case of subs_db_mode = 2 in case of mode 2 facing following presence issue. 1) after hangup presence is still up 2) sometimes stuck in ringing state 3) sometime presence not came..etc but in case of subs_db_mode = 3 (DB ONLY) mode presence working fine not facing any issue with this mode. I noticed that sometimes Kamailio will throw following message during PUBLISH processesing and it will not generate appropriate NOTIFY i also verify in active watcher subscription is thare for that user and also proper entry in dialog table. MSG during PUBLISH processesing and it will not generate appropriate NOTIFY Oct 30 07:42:10 NC-HOSTED-1 /usr/local/sbin/kamailio[2409]: DEBUG: presence [notify.c:1444]: publ_notify(): Could not find subs_dialog kamailio.cfg param modparam("pua", "db_url", DBURL_KAMAILIO) modparam("pua", "db_mode", 2) modparam("pua", "update_period", 100) modparam("pua", "dlginfo_increase_version", 1) modparam("pua", "default_expires", 3600) modparam("pua", "fetch_rows", 1000) modparam("pua", "outbound_proxy", SERVER_IP) modparam("dialog", "db_url", DBURL_KAMAILIO ) modparam("dialog", "db_mode", 1) modparam("dialog", "db_update_period", 260) modparam("dialog", "db_fetch_rows", 500) modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", 8) modparam("pua_dialoginfo", "caller_confirmed", 0) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "use_pubruri_avps", 1) modparam("pua_dialoginfo", "include_localremote", 1) modparam("pua_dialoginfo", "override_lifetime", 300) modparam("pua_dialoginfo", "pubruri_caller_avp", "$avp(s:puburis_caller)") modparam("pua_dialoginfo", "pubruri_caller_dlg_var", "pubruri_caller") modparam("pua_dialoginfo", "pubruri_callee_dlg_var", "pubruri_callee") modparam("pua_dialoginfo", "pubruri_callee_avp", "$avp(s:puburis_callee)") modparam("presence_dialoginfo", "force_single_dialog", 1) modparam("presence", "db_table_lock_type", 0) modparam("presence", "db_url", DBURL_KAMAILIO) modparam("presence", "db_update_period", 5) modparam("presence", "send_fast_notify", 1) modparam("presence", "clean_period", 100) modparam("presence", "subs_db_mode", 2) //modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 1) //new/ //modparam("presence", "notifier_processes", 2) //new// modparam("presence", "notifier_poll_rate", 20) //new// modparam("presence", "waitn_time",1) modparam("presence", "fetch_rows", 1000) modparam("presence", "presentity_table", "presentity") modparam("presence", "active_watchers_table", "active_watchers") modparam("presence", "watchers_table", "watchers") modparam("presence", "max_expires", 3600) modparam("presence_xml", "db_url", DBURL_KAMAILIO) modparam("presence_xml", "force_active", 1) logic for presence request_route { if(is_method("PUBLISH") || is_method("SUBSCRIBE")) { route(HANDLE_PRESENCE); } } route[HANDLE_PRESENCE] { if (! t_newtran()) { sl_reply_error(); exit; } if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if( is_method("SUBSCRIBE")) { handle_subscribe(); t_release(); } exit; } route[RELAY] { if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { $avp(t_ext) = $tU ; $avp(domain) = $fd ; $avp(et) = $_s(sip:$avp(t_ext)@$avp(domain)) ; $avp(s:puburis_callee) = $avp(et); setflag(8); dlg_manage(); } } -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2540

1 year

[kamailio/kamailio] tm remap_503_500 breaks dialogs (#2405)

by geejay101

### Description Apparently the remapping of 503 to 500 codes in the tm module does also change the to-tag. This behaviour breaks dialogs with yate and therefore calls hang and the 503 remains unacknowledged. Removing to-tags seems to contradict RFC3261 "12 Dialogs A dialog is identified at each UA with a dialog ID, which consists of a Call-ID value, a local tag **and a remote tag**…" Due to the bug the UA cannot identify the dialog the 500 belongs to. Therefore the dialog remains open and Kamailio keeps repeating 500 messages. ### Troubleshooting After disabling the 503 to 500 remapping with modparam("tm", "remap_503_500", 0) dialogs get properly terminated . #### Reproduction 503 to 500 remapping is enabled by default. Inspect the to tags of the incoming 503 and outgoing 500 messages. #### Debugging Data Henning added this comment: Apparently, this is the way the code works: t_reply.c: if (relayed_code==503 && tm_remap_503_500){ /* replace a final 503 with a 500: * generate a "FAKE" reply and a new to_tag (for easier * debugging)*/ ### Possible Solutions Dont change the to-tag ### Additional Information kamailio -v version: kamailio 5.2.3 (x86_64/linux) c36229 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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_BLACKLIST, HAVE_RESOLV_RES 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: c36229 compiled on 10:34:54 Jun 13 2019 with gcc 4.8.5 * **Operating System**: CentOS Linux release 7.6.1810 (Core) 3.10.0-957.12.2.el7.x86_64 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2405

1 year

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev November 2021