sr-dev September 2023

sr-dev@lists.kamailio.org

17 participants
299 discussions

[kamailio/kamailio] Support for Password Authentication in Sentinel for NDB Redis in kamailio (Issue #3530)
by hemanth-vulavala 22 Nov '23

22 Nov '23

### Description Currently, kamailio NDB Redis integration with Sentinel does not offer support for password authentication, leading to potential security concerns in our system. As a result, we are unable to ensure the desired level of protection for sensitive data stored in Redis. *Expected Behavior:* We expect Kamailio to allow the configuration of password authentication for Sentinel in the NDB Redis integration, enabling a secure and password-protected connection to the Redis instances. *Proposed Solution:* To address this issue, we recommend implementing a feature that enables password authentication for the Sentinel-based NDB Redis connections. This improvement will provide an added layer of security, ensuring that only authorized users can access the Redis instances. *Impact:* The absence of password authentication support poses a security risk, making our system vulnerable to potential unauthorized access and data breaches. Implementing this enhancement will safeguard sensitive information and strengthen our Redis integration's security framework. Note: as of now NDB REDIS support redis authentication using password  ### Troubleshooting #### Reproduction Steps to Reproduce:* 1. Attempt to configure password authentication for Sentinel in kamailio NDB Redis integration. ex: modparam("ndb_redis", "server", "name=srvZ;sentinel_group=group_name;sentinel_master=1;sentinel=1.2.3.4:26379;sentinel=1.2.3.5:26379";pass=mypassword") *It is failed to connect the sentinel *  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3530 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3530(a)github.com>

2 2

[kamailio/kamailio] [rtpengine] Support syntax for new "sdp-attr" manipulations (Issue #3509)
by George Diamantopoulos 22 Nov '23

22 Nov '23

### Description Newer rtpengine versions support manipulating SDP "a=" lines directly. Although kamailio is quite versatile when it comes to editing SIP message body, this functionality is often rather frail, especially when forking and having to use msg_apply_changes several times. I believe it would be beneficial to be able to offload such functionality to rtpengine, especially if one wants to apply different manipulations per outgoing branch. ### Expected behavior There should be a way to issue rtpengine ng-control protocol commands compatible with the sdp-attr dictionary syntax. #### Actual observed behavior Currently sdp-attr tokens are not properly evaluated. For example, **doing**: > rtpengine_manage("ICE=remove rtcp-mux-demux trust-address replace-origin replace-session-connection replace-SDP-version direction=internal direction=external sdp-attr-audio-substitute=$avp(fmtp_line) sdp-attr-audio-substitute=fmtp:101 0-15"); _[NOTE: $avp(fmtp_line) seems to expand in empty string here, which is a config error, but it doesn't affect the syntax demonstration in this example IMO]_ **results in**: ``` { "supports": [ "load limit" ], "sdp": "...", "ICE": "remove", "sdp-attr-audio-substitute": "", "sdp-attr-audio-substitute": "fmtp:101", "direction": [ "internal", "external" ], "flags": [ "trust-address", "0-15" ], "replace": [ "origin", "session-connection", "SDP-version" ], "rtcp-mux": [ "demux" ], "call-id": "...", "received-from": [ "IP4", "..." ], "from-tag": "...", "to-tag": "...", "command": "answer" } ``` ### Possible Solutions Support the special syntax of sdp-attr as documented here: https://github.com/sipwise/rtpengine/blob/master/docs/ng_control_protocol.md Here's one way to do it (I guess). In order to get this: ``` "sdp-attr" : { "audio" : { "add" : [ "ptime:20", "sendrecv" ], "substitute": [["fmtp:101 0-15" , "fmtp:126 0-16" ]] }, "video": { "remove" : [ "rtpmap:101 telephone-event/8000" ] }, "none" : { "substitute": [[ "sendrecv" , "sendonly" ], [ "ptime:20" , "ptime:40" ]] } } ``` Use a syntax similar to the following: > rtpengine_manage("... sdp-attr-audio-add=ptime:20 sdp-attr-audio-add=sendrecv sdp-attr-audio-substitute=fmtp:101 0-15 sdp-attr-audio-substitute=fmtp:101 0-16 sdp-attr-video-remove=rtpmap:101 telephone-event/8000 sdp-attr-none-substitute=sendrecv sdp-attr-none-substitute=sendonly sdp-attr-none-substitute=ptime:20 sdp-attr-none-substitute=ptime:40 ..."); It's not very pretty, but it could work. Caveats: * How to handle whitespace (e.g. there's a space in "fmtp:101 0-15" and in "rtpmap:101 telephone-event/8000" ) * substitute commands must always be in pairs, data type is a list of lists containing exactly two items as value in "substitute" key Unfortunately my C skills are not up to this task, but if I can provide any other kind of help please let me know. Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3509 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3509(a)github.com>

3 5

[kamailio/kamailio] core: add socket timestamp of received packets and keep track of receive delay (PR #3404)
by Nicolas C 20 Nov '23

20 Nov '23

#### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description This is a proposed evolution that adds socket timestamping of received UDP packets (using SO_TIMESTAMPNS). It computes the delay between this timestamp and the time at which the packet is read by Kamailio. This can then be accessed using pv "$TV(RD)" (RD for "receive relay"). Rationale : The Kamailio server is handling traffic that is irregular and can temporarily spike to a point where all children are still busy when new packets are incoming on the network interface. Consequently, these packets have to wait until a worker is available. The client will see a higher response time, that currently cannot be monitored by Kamailio itself. This evolution allows to make this wait time observable by Kamailio, allowing to log or write the information to CDR for example. If this is possible, I'd like to merge this feature in Kamailio. Of course, I'm ready to discuss the PR and make any necessary changes. All comments and reviews are most welcome. I've tested this locally on Linux (3.10.0-957.10.1.el7.x86_64) with the latest Kamailio master as of 2023/03/23. Thanks! You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3404 -- Commit Summary -- * core: add socket timestamp of received packets and keep track of receive delay * pv: add $TV(RD) to get the new information "receive delay" -- File Changes -- M src/core/ip_addr.h (1) M src/core/parser/msg_parser.h (1) M src/core/receive.c (8) M src/core/udp_server.c (60) M src/core/ut.h (34) M src/modules/pv/pv_time.c (15) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3404.patch https://github.com/kamailio/kamailio/pull/3404.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3404 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3404(a)github.com>

5 8

[kamailio/kamailio] Allow function set_advertised_address to receive variable as parameter (#2137)
by pwakano 17 Nov '23

17 Nov '23

### Description Currently the functions set_advertised_address and set_advertised_port only accept strings as parameters. Trying to use it with variable causes an error. Having the function using a hard coded value is not a good practice and in order to add flexibility to the script in different installations it would be nice to have this function accepting variables. Also, the 'advertise' option on the 'listen' parameter is not always desired because it apply for all messages sent via the socket, and there are situations where different advertised IP for the same interface are necessary. ### Expected behavior set_advertised_address should receive a variable as parameter and use its value to change the SIP headers. ### Actual observed behavior Kamailio won't start if set_advertised_address is used with a variable due to script parse error or it will set the SIP message with the literal string "$var(test)" for example, instead of using the value of $var(test). ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` # kamailio -v version: kamailio 5.2.2 (x86_64/linux) 67f967 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: 67f967 compiled on 11:40:41 Mar 11 2019 with gcc 4.8.5 ``` * **Operating System**:  ``` # uname -a Linux voice-conn-kamailio-1 3.10.0-514.21.2.el7.x86_64 #1 SMP Tue Jun 20 12:24:47 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/2137

7 9

[kamailio/kamailio] Memory leak in dns_cache.c / dns_cache_mk_rd_entry (Issue #3523)
by Sebastian Damm 15 Nov '23

15 Nov '23

### Description We have some Kamailio servers running as an outboundproxy. Requests go to different domains. Over the time, there is a slow but steady shared memory increase. We don't see the behavior on our Kamailio servers serving as endpoint proxies using the same code. I did a memory dump, and on two systems I inspected, I saw the same result: A really high memory usage for the `dns_cache_mk_rd_entry` function.  ### Troubleshooting #### Reproduction When we restart our Kamailio, it starts off with just a few megabytes of shared mem used. After running for a month or two, this has increased to some hundred megabytes used.  #### Debugging Data This is the output of the shm dump: ``` Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): summarizing all alloc'ed. fragments: Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 592 bytes from tm: t_reply.c: _reply_light(500) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 45 size= 43576 bytes from core: core/msg_translator.c: build_req_buf_from_sip_req(2233) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 44 size= 33232 bytes from tm: t_reply.c: relay_reply(2061) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 45 size= 376840 bytes from tm: h_table.c: build_cell(334) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 4 size= 224 bytes from pike: ip_tree.c: new_ip_node(201) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 45 size= 275304 bytes from core: core/sip_msg_clone.c: sip_msg_shm_clone(495) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 16 size= 1528 bytes from core: core/usr_avp.c: create_avp(176) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 45 size= 16728 bytes from core: core/sip_msg_clone.c: msg_lump_cloner(973) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 12 size= 488 bytes from tls: tls_ct_q.h: tls_ct_q_add(58) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 12 size= 584 bytes from tls: tls_server.c: tls_complete_init(276) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 59 size= 3776 bytes from rtpengine: ../../core/parser/../ut.h: shm_str_dup(859) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 212 size= 15720 bytes from core: core/xavp.c: xavp_new_value(116) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 59 size= 3888 bytes from rtpengine: rtpengine.c: rtpp_function_call(2775) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 29 size= 2680 bytes from core: core/dns_cache.c: dns_cache_mk_bad_entry(770) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count=856568 size= 311761008 bytes from core: core/dns_cache.c: dns_cache_mk_rd_entry(1117) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 13941 size= 2741784 bytes from htable: ht_api.c: ht_cell_new(186) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 2 size= 104 bytes from xhttp_prom: prom_metric.c: prom_metric_lvalue_create(513) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 24 size= 3752 bytes from tmx: tmx_pretran.c: tmx_check_pretran(250) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 24 size= 6776 bytes from tmx: tmx_pretran.c: tmx_check_pretran(271) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 553 size= 10177808 bytes from core: core/tcp_main.c: tcpconn_new(1175) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 53760 bytes from core: core/counters.c: counters_prefork_init(212) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 2 size= 976 bytes from tls: tls_domain.c: ksr_tls_fix_domain(1057) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8064 bytes from sl: sl_stats.c: init_sl_stats_child(125) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 512 bytes from tmx: tmx_pretran.c: tmx_init_pretran_table(90) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 10752 bytes from tm: t_stats.c: init_tm_stats_child(56) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 2016 bytes from kex: pkg_stats.c: pkg_proc_stats_init(78) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 8 size= 176 bytes from core: core/cfg/cfg_struct.c: cfg_clone_str(130) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 992 bytes from core: core/cfg/cfg_struct.c: cfg_shmize(217) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: main.c: main_loop(1334) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/pt.c: init_pt(107) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/pt.c: init_pt(106) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 6216 bytes from core: core/pt.c: init_pt(105) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from app_python3: apy_kemi.c: apy_sr_init_mod(2095) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from app_python3: apy_kemi.c: apy_sr_init_mod(2088) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from xhttp_prom: prom_metric.c: prom_metric_init(219) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from pike: pike.c: pike_init(127) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 1040 bytes from pike: ../../core/lock_alloc.h: lock_set_alloc(66) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 4112 bytes from pike: ip_tree.c: init_ip_tree(115) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from pike: pike.c: pike_init(109) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 4 size= 120 bytes from core: core/cfg_parser.c: cfg_parse_str(907) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 2 size= 448 bytes from tls: tls_domain.c: tls_new_domain(187) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 48 bytes from tls: tls_domain.c: tls_new_cfg(1553) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from tls: tls_ct_wrq.c: tls_ct_wq_init(49) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from tls: tls_mod.c: mod_init(373) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from tls: tls_mod.c: mod_init(357) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from siptrace: siptrace.c: mod_init(338) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 256 size= 14336 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(111) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 256 size= 2048 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(96) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 1024 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(85) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 2048 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(76) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 2048 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(67) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 32 bytes from rtpengine: rtpengine_hash.c: rtpengine_hash_table_init(58) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 24 bytes from rtpengine: rtpengine.c: add_rtpengine_socks(1021) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 64 bytes from rtpengine: rtpengine.c: add_rtpengine_socks(1002) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from rtpengine: rtpengine.c: get_rtpp_set(916) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 56 bytes from rtpengine: rtpengine.c: get_rtpp_set(907) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from rtpengine: rtpengine.c: mod_init(1683) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 24 bytes from rtpengine: rtpengine.c: mod_init(1676) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from rtpengine: rtpengine.c: mod_init(1650) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from rtpengine: rtpengine.c: mod_init(1643) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from rtpengine: rtpengine.c: mod_init(1629) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 5 size= 1581568 bytes from htable: ht_api.c: ht_init_tables(394) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from usrloc: ul_callback.c: init_ulcb_list(44) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 4 size= 288 bytes from core: core/timer.c: register_timer(995) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from sl: sl_funcs.c: sl_startup(90) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from sl: sl_stats.c: init_sl_stats(110) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from tm: t_hooks.c: init_tmcb_lists(71) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from tm: t_hooks.c: init_tmcb_lists(69) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 2097152 bytes from tm: h_table.c: init_hash_table(482) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from tm: rpc_uac.c: tm_rpc_response_list_init(77) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from kex: mod_stats.c: mod_stats_init_rpc(294) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 4 size= 128 bytes from core: core/cfg/cfg_ctx.c: cfg_register_ctx(47) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1089 size= 82016 bytes from tls: tls_init.c: ser_realloc(299) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8192 bytes from core: core/tcp_main.c: init_tcp(5051) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 32768 bytes from core: core/tcp_main.c: init_tcp(5046) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/tcp_main.c: init_tcp(5037) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/tcp_main.c: init_tcp(5030) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/tcp_main.c: init_tcp(5023) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/tcp_main.c: init_tcp(5017) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/tcp_main.c: init_tcp(5005) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/usr_avp.c: init_avps(90) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/usr_avp.c: init_avps(89) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16384 bytes from core: core/dst_blocklist.c: init_dst_blocklist(437) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/dst_blocklist.c: init_dst_blocklist(430) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 2 size= 96 bytes from core: core/timer.c: timer_alloc(498) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/dns_cache.c: init_dns_cache(368) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16384 bytes from core: core/dns_cache.c: init_dns_cache(359) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16 bytes from core: core/dns_cache.c: init_dns_cache(351) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/dns_cache.c: init_dns_cache(343) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(267) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 16384 bytes from core: core/timer.c: init_timer(266) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(265) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(264) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(253) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(221) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 278544 bytes from core: core/timer.c: init_timer(210) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(209) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/timer.c: init_timer(197) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 64 bytes from core: core/cfg/cfg_struct.c: cfg_child_cb_new(829) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/cfg/cfg_struct.c: sr_cfg_init(361) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/cfg/cfg_struct.c: sr_cfg_init(354) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/cfg/cfg_struct.c: sr_cfg_init(347) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/cfg/cfg_struct.c: sr_cfg_init(335) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/cfg/cfg_struct.c: sr_cfg_init(323) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/sr_module.c: ksr_shutdown_phase_init(124) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 36864 bytes from core: core/kemi.c: sr_kemi_cbname_list_init(3605) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/kemi.c: sr_kemi_cbname_list_init(3596) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/kemi.c: sr_kemi_cbname_list_init(3586) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 3 size= 72 bytes from xhttp_prom: ../../core/ut.h: shm_str_dup(859) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 5 size= 96 bytes from xhttp_prom: prom_metric.c: prom_lb_node_add(813) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 5 size= 120 bytes from xhttp_prom: prom_metric.c: prom_lb_node_add(791) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 3 size= 48 bytes from xhttp_prom: prom_metric.c: prom_lb_create(873) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 3 size= 168 bytes from xhttp_prom: prom_metric.c: prom_counter_create(978) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 9 size= 128 bytes from pv: pv_shv.c: set_shvar_value(243) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 40 size= 472 bytes from pv: pv_shv.c: add_shvar(177) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 40 size= 2608 bytes from pv: pv_shv.c: add_shvar(170) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 80 bytes from pv: ../../core/lock_alloc.h: lock_set_alloc(66) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 5 size= 1600 bytes from htable: ht_api.c: ht_add_table(289) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 10464 size= 1453800 bytes from tls: tls_init.c: ser_malloc(293) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): count= 1 size= 8 bytes from core: core/mem/q_malloc.c: qm_shm_lock_init(1277) Jul 25 15:08:52 sipproxy /usr/sbin/kamailio[122]: NOTICE: qm_sums: qm_sums(): ----------------------------- ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.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 9.4.0 ``` * **DNS related kamailio.cfg Settings** ``` dns_retr_time=3 dns_retr_no=3 dns_use_search_list=no dns_try_naptr=yes use_dns_failover=yes ``` * **Operating System**:  ``` Podman container with Ubuntu Focal. ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3523 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3523(a)github.com>

2 7

[kamailio/kamailio] core: Add TCP_USER_TIMEOUT socket option on listening socket. (PR #3528)
by schoberw 13 Nov '23

13 Nov '23

Use tcp_send_timeout config option also on listening socket to timeout outbound messages sent on passive inbound connections. #### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [x] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #3443 #### Description Based on the description of core parameter "tcp_send_timeout" the timeout should also work for sending on forked incoming tcp connections. But sending on a broken connection causes the kernel to use the default values of `tcp_retries1` and `tcp_retries2` , leading to try to send a SIP message for 15 minutes. This makes absolutely no sense in a real time kamailio application. Following man 7 tcp TCP_USER_TIMEOUT can be used on recent Linux kernels to utilize tcp_send_timeout: TCP_USER_TIMEOUT (since Linux 2.6.37) This option takes an unsigned int as an argument. When the value is greater than 0, it specifies the maximum amount of time in milliseconds that transmitted data may remain unacknowledged before TCP will forcibly close the corresponding connection and return ETIMEDOUT to the application. If the option value is specified as 0, TCP will use the system default. Increasing user timeouts allows a TCP connection to survive extended periods without end-to-end connectivity. De‐ creasing user timeouts allows applications to "fail fast", if so desired. Otherwise, failure may take up to 20 minutes with the current system defaults in a normal WAN environment. This option can be set during any state of a TCP connection, but is effective only during the synchronized states of a connection (ESTABLISHED, FIN-WAIT-1, FIN-WAIT-2, CLOSE-WAIT, CLOSING, and LAST-ACK). Moreover, when used with the TCP keepalive (SO_KEEPALIVE) option, TCP_USER_TIMEOUT will override keepalive to determine when to close a connection due to keepalive failure. The option has no effect on when TCP retransmits a packet, nor when a keepalive probe is sent. This option, like many others, will be inherited by the socket returned by accept(2), if it was set on the listen‐ ing socket. Further details on the user timeout feature can be found in RFC 793 and RFC 5482 ("TCP User Timeout Option"). Having a tcp connection break by firewall or network breakdown the retransmits to this destination are now aborted after `tcp_send_timeout` seconds with a NOTICE: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection timed out (110) ([1.2.3.4]:51151 -> You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3528 -- Commit Summary -- * core: Add TCP_USER_TIMEOUT socket option on listening socket. -- File Changes -- M src/core/tcp_main.c (13) M src/core/tcp_options.h (7) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3528.patch https://github.com/kamailio/kamailio/pull/3528.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3528 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3528(a)github.com>

3 6

[kamailio/kamailio] dialplan: implement Iterative dialplan matching (#764)
by Victor Seva 13 Nov '23

13 Nov '23

>From http://lists.kamailio.org/pipermail/sr-dev/2016-August/036231.html On 24/08/16 10:17, Andreas Granig wrote: > Hi, > > When translating strings with the dialplan module, you sometimes end up > with very complex patterns for sanitizing the target string and > performing some replacements, since for a given dialplan id, processing > stops on the first match within the dialplan entries for a given dpid. > > The idea is to introduce a "continue" flag (default 0) in the dialplan > table indicating to proceed with processing further dialplan entries > within the given dpid after a match. The use case is to have a sanitize > rule with highest priority which e.g. removes any spaces, dashes and > parentheses from the target string, then with a lower priority do > further processing with the cleaned up string, e.g. stripping leading > double-zeroes or a plus when normalizing to E164 numbers, or replacing a > single leading zero with the country code and so on. > > This is particularly useful when a user dials a number from an address > book of some sort (e.g. on a mobile app) where number formats are stored > with country-specific formating characters like "+1-(234)-567 890", and > catching all of that in one rule results in really messy match/replace > patterns. -- 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/764

4 5

[kamailio/kamailio] kamailio 5.5 (commit 54c9df) SIGSEGV on run_dlg_callbacks (Issue #3106)
by MayamaTakeshi 13 Nov '23

13 Nov '23

### Description Crash occurred during load test. #### Reproduction This cannot be reproduced at will. It happened after about 40 days of load testing. #### Debugging Data ``` [root@lab002201-flip-server ~]$ gdb /usr/local/src/git/kamailio-5.5/src/kamailio /core GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/src/git/kamailio-5.5/src/kamailio... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 730446] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/src/git/kamailio-5.5/src/kamailio -m 1024 -f /usr/local/etc/kamailio'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fb609cba495 in run_dlg_callbacks (type=4, dlg=0x7fb5ca1798d0, req=0x7fb5ce0a7380, rpl=0xffffffffffffffff, dir=2, dlg_data=0x0) at dlg_cb.c:273 273 cb->callback( dlg, type, &params ); (gdb) bt full #0 0x00007fb609cba495 in run_dlg_callbacks (type=4, dlg=0x7fb5ca1798d0, req=0x7fb5ce0a7380, rpl=0xffffffffffffffff, dir=2, dlg_data=0x0) at dlg_cb.c:273 cb = 0x7fb609ce7a23 <dlg_iuid_sfree> __func__ = "run_dlg_callbacks" #1 0x00007fb609ceb3ee in dlg_onreply (t=0x7fb5cfa8a1f0, type=1048576, param=0x7fff4bdc6060) at dlg_handlers.c:576 dlg = 0x7fb5ca1798d0 iuid = 0x7fb5cca0bbf0 new_state = 5 old_state = 2 unref = 1 event = 4 tag = {s = 0x80d000001ff <error: Cannot access memory at address 0x80d000001ff>, len = 174085573} req = 0x7fb5ce0a7380 rpl = 0xffffffffffffffff __func__ = "dlg_onreply" #2 0x00007fb60a53c399 in run_trans_callbacks_internal (cb_lst=0x7fb5cfa8a268, type=1048576, trans=0x7fb5cfa8a1f0, params=0x7fff4bdc6060) at t_hooks.c:258 cbp = 0x7fb5cb5b2520 backup_from = 0x5591e2acbe90 <def_list+16> backup_to = 0x5591e2acbe98 <def_list+24> backup_dom_from = 0x5591e2acbea0 <def_list+32> backup_dom_to = 0x5591e2acbea8 <def_list+40> backup_uri_from = 0x5591e2acbe80 <def_list> backup_uri_to = 0x5591e2acbe88 <def_list+8> backup_xavps = 0x5591e2acbfd8 <_xavp_list_head> backup_xavus = 0x5591e2acbfe0 <_xavu_list_head> backup_xavis = 0x5591e2acbfe8 <_xavi_list_head> __func__ = "run_trans_callbacks_internal" #3 0x00007fb60a53c5b2 in run_trans_callbacks_with_buf (type=1048576, rbuf=0x7fb5cfa8a2c0, req=0x7fb5ce0a7380, repl=0xffffffffffffffff, flags=0) at t_hooks.c:303 params = {req = 0x7fb5ce0a7380, rpl = 0xffffffffffffffff, param = 0x7fb5cb5b2530, code = 408, flags = 0, branch = 0, t_rbuf = 0x7fb5cfa8a2c0, dst = 0x7fb5cfa8a310, send_buf = { s = 0x7fb5caa9cda0 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 192.168.2.202:5020;rport=5020;branch=z9hG4bK-2375372-4769-10;received=192.168.2.202\r\nFrom: \"0312341234\" <sip:0312341234@fakedomain.com>;tag=2375372SIPpTag"..., len = 407}} trans = 0x7fb5cfa8a1f0 #4 0x00007fb60a5b322d in relay_reply (t=0x7fb5cfa8a1f0, p_msg=0xffffffffffffffff, branch=0, msg_status=408, cancel_data=0x7fff4bdc6280, do_put_on_wait=0) at t_reply.c:2094 relay = 0 save_clone = 0 buf = 0x7fb60a8f6b68 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 192.168.2.202:5020;rport=5020;branch=z9hG4bK-2375372-4769-10;received=192.168.2.202\r\nFrom: \"0312341234\" <sip:0312341234@fakedomain.com>;tag=2375372SIPpTag"... res_len = 407 relayed_code = 408 relayed_msg = 0xffffffffffffffff reply_bak = 0x7fff4bdc6220 bm = {to_tag_val = { s = 0x7fb60a8f6c5f "0a86cd31e4e6805cdd7f1dffc4ec5169-53cd2e21\r\nCall-ID: 4769-2375372(a)192.168.2.202\r\nCSeq: 801 INVITE\r\nServer: kamailio (5.5.4 (x86_64/linux))\r\nContent-Length: 0\r\n\r\n", len = 41}} totag_retr = 0 reply_status = RPS_COMPLETED uas_rb = 0x7fb5cfa8a2c0 to_tag = 0x7fb60a61cb30 <tm_tag> reason = {s = 0x5591e2933463 "Request Timeout", len = 15} onsend_params = {req = 0x40, rpl = 0x0, param = 0x1c9f56660, code = -923035960, flags = 32693, branch = 0, t_rbuf = 0x7fff4bdc61b0, dst = 0x5591e27f9149 <futex_release+29>, send_buf = { s = 0x2260 <error: Cannot access memory at address 0x2260>, len = -923035960}} ip = {af = 3407219152, len = 32693, u = {addrl = {140418773026976, 1}, addr32 = {3407218848, 32693, 1, 0}, addr16 = {2208, 51990, 32693, 0, 1, 0, 0, 0}, addr = "\240\b\026˵\177\000\000\001\000\000\000\000\000\000"}} __func__ = "relay_reply" #5 0x00007fb60a540ec0 in fake_reply (t=0x7fb5cfa8a1f0, branch=0, code=408) at timer.c:295 --Type <RET> for more, q to quit, c to continue without paging--c cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = -811032080}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = -811032080}}}} do_cancel_branch = 1 reply_status = 730446 #6 0x00007fb60a54132e in final_response_handler (r_buf=0x7fb5cfa8a490, t=0x7fb5cfa8a1f0) at timer.c:462 silent = 0 branch_ret = 0 prev_branch = 0 now = 0 #7 0x00007fb60a5413f2 in retr_buf_handler (ticks=280654947, tl=0x7fb5cfa8a4b0, p=0x7d0) at timer.c:518 rbuf = 0x7fb5cfa8a490 fr_remainder = 0 retr_remainder = 32693 retr_interval = 3371932768 new_retr_interval_ms = 4294967296 crt_retr_interval_ms = 0 t = 0x7fb5cfa8a1f0 __func__ = "retr_buf_handler" #8 0x00005591e27bda9f in timer_list_expire (t=280654947, h=0x7fb5c8ffdd40, slow_l=0x7fb5c8fff2a8, slow_mark=48435) at core/timer.c:857 tl = 0x7fb5cfa8a4b0 ret = 0 #9 0x00005591e27bdfa9 in timer_handler () at core/timer.c:922 saved_ticks = 280654947 run_slow_timer = 0 i = 307 __func__ = "timer_handler" #10 0x00005591e27be4ac in timer_main () at core/timer.c:961 No locals. #11 0x00005591e25066cf in main_loop () at main.c:1839 i = 12 pid = 0 si = 0x0 si_desc = "udp receiver child=11 sock=192.168.2.201:9060\000\270\000\340e\334K\377\177\000\000\000\000\000\000\000\000\000\000\360e\334K\377\177\000\000)+\373\b\266\177\000\000\b\024l\n\266\177\000\000]q\373\b\266\177", '\000' <repeats 14 times>, "\001\000\000\000\360e\334K\377\177\000\000⌀\342\221U\000" nrprocs = 12 woneinit = 1 __func__ = "main_loop" #12 0x00005591e25112ab in main (argc=8, argv=0x7fff4bdc6bd8) at main.c:3053 cfg_stream = 0x5591e46482d0 c = -1 r = 0 tmp = 0x7fff4bdc8d08 "" tmp_len = 0 port = 0 proto = 0 ahost = 0x0 aport = 0 options = 0x5591e291d0b8 ":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 = 529371157 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0xc2 <error: Cannot access memory at address 0xc2> st = {st_dev = 22, st_ino = 2420, st_nlink = 2, st_mode = 16877, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1646813990, tv_nsec = 961425837}, st_mtim = {tv_sec = 1647220116, tv_nsec = 385726158}, st_ctim = {tv_sec = 1647220120, tv_nsec = 853813654}, __glibc_reserved = {0, 0, 0}} tbuf = "\020\357\027\v\266\177\000\000\300\372\344\n\001\000\000\000\377\377\377\377", '\000' <repeats 12 times>, "(\326\030\v\266\177\000\000\350\211\033\v\266\177\000\000\377\377\377\377", '\000' <repeats 12 times>, "@\265\343\n\266\177\000\000\020\364\027\v\266\177\000\000\350\224\033\v\266\177\000\000\204\331\030\v\266\177\000\000\060\324\030\v\266\177\000\000XR\001\v\266\177\000\000h\211\033\v\266\177\000\000`\200\033\v\266\177\000\000 l\334K\377\177\000\000\200\221\033\v\266\177\000\000\000\000\000\000\000\000\000\000#\306\031\v\266\177\000\000\001", '\000' <repeats 23 times>, "(\326\030\v\266\177\000\000\060j\334K\377\177\000\000"... option_index = 12 long_options = {{name = 0x5591e291f516 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x5591e291a514 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x5591e291f51b "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x5591e291f521 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x5591e291f527 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x5591e291f530 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x5591e291f53a "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x5591e291f544 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x5591e291f54f "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x5591e291f558 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x5591e291f563 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x5591e291f569 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x5591e291f573 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) info locals cb = 0x7fb609ce7a23 <dlg_iuid_sfree> __func__ = "run_dlg_callbacks" (gdb) list 268 269 for ( cb=dlg->cbs.first; cb; cb=cb->next) { 270 if ( (cb->types)&type ) { 271 LM_DBG("dialog=%p, type=%d\n", dlg, type); 272 params.param = &cb->param; 273 cb->callback( dlg, type, &params ); 274 } 275 } 276 return; 277 } (gdb) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.4 (x86_64/linux) 54c9df 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: 54c9df compiled on 10:32:51 Mar 9 2022 with gcc 10.2.1 ``` * **Operating System**: ``` [root@lab002201-flip-server ~]$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye [root@lab002201-flip-server ~]$ uname -a Linux lab002201-flip-server 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3106 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3106(a)github.com>

4 6

[kamailio/kamailio] tcp_send_timeout not used on reused socket (Issue #3443)
by schoberw 13 Nov '23

13 Nov '23

### Description Having clients connected via TCP doing only passive connections in the kamailio server it seems the tcp_send_timeout is not used on messages going out to the clients. While tcp_keepalive is doing well as long as there was not sent any packet to the client tcp_send_timout does nothing. The underlying Linux tries to send the SIP message for ages (15 minutes in my case). Do I have a wrong understanding of tcp_send_timeout? I tried with tcp_async yes and no with same results. ### Troubleshooting These are my tcp settings: ``` # def = 10 Time in seconds after a TCP connection will be closed if it is not available for writing in this interval (and Kamailio wants to send something on it). # Lower this value for faster detection of broken TCP connections. tcp_send_timeout=3 tcp_connect_timeout=10 # def = 10 tcp_connection_lifetime=3605 tcp_rd_buf_size=32768 tcp_max_connections=2048 tcp_connection_match=1 # match also local port tcp_keepalive=yes # Enables keepalive for tcp (sets SO_KEEPALIVE socket option) tcp_keepcnt=3 # Number of keepalives sent before dropping the connection (TCP_KEEPCNT socket option). Linux only. tcp_keepidle=30 # Time before starting to send keepalives, if the connection is idle (TCP_KEEPIDLE socket option). Linux only. tcp_keepintvl=10 # Time interval between keepalive probes, when the previous probe failed (TCP_KEEPINTVL socket option). Linux only. tcp_async=yes # alias tcp_buf_write, default=yes tcp_crlf_ping=no ``` I also tried to set the tcp_send_timeout to much too high value 333666 to trigger this line of code in tcp_options.c: ``` WARN("%s: timeout too big (%u), the maximum value is %u\n", name, *to, max_val); ``` But even in -d -d -d debugging that line never hits. I do **not** make any connections outbound (senseless on NAT). Instead I'd like to reject this: ``` if ($dP =~ "tcp") { set_forward_no_connect(); xlog("L_INFO", ">> checking tcp connection to $dd:$dp"); if(tcp_get_conid("$dd:$dp", "$var(conid)")) { xlog("L_INFO", ">> connection id to $dd:$dp is: $var(conid)"); } else { xlog("L_ERR", ">> connection to $dd:$dp is no longer connected. Client must reregister!"); sl_send_reply("480", "TCP not connected"); exit; } } ``` But the connection ID is still there for a long time. And there are no keepalives done since the outgoing packets are in the queue. #### Reproduction 1. Register a client with TCP. 2. Pull the plug. 3. Make a call to it. 4. Run a `'watch 'netstat -tapen | grep <client_ip>'`: The connected client never vanishes. 5. Run a `tcpdump -i ethX tcp port <kamailio_server_port>`: the system tries to send the packet for a long time #### Log Messages There is not much to see in the log, even in debug level. `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.sbc.pid -f /etc/kamailio.sbc/kamailio.cfg -m 48 -M 24 -u kamailio -g kamailio -d -d -d` At that moment the switchport was already shutdown: ``` May 9 10:48:19 p01t-1 kamailio.sbc[150273]: INFO: sbc:<script>: Network sending: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> INVITE sip:22@ws2.domain.tld;user=phone SIP/2.0 Record-Route: <sip:192.168.48.131:5065;r2=on;lr;ftag=97p54nlxgb;x-rtpp=1> Record-Route: <sip:10.101.65.131:5082;r2=on;lr;ftag=97p54nlxgb;x-rtpp=1> Via: SIP/2.0/UDP 192.168.48.131:5065;branch=z9hG4bKe01f.07e0d03fb0af18dcdb76154be67bea1d.0 Via: SIP/2.0/UDP 192.168.41.57:48310;received=10.101.65.130;branch=z9hG4bK-nzdt1be9c4xn;rport=48310 From: "01/301102-21" <sip:15553010221@ws2.domain.tld>;tag=97p54nlxgb To: <sip:22@ws2.domain.tld;user=phone> Call-ID: 3136383336323230393839333336-jg7spjsktbm2 CSeq: 2 INVITE Max-Forwards: 69 User-Agent: snomD765/10.1.49.11 Contact: <sip:15553010221@192.168.48.131:5065;ntv3=2;alias=10.101.65.130~48310~1;fs=udp:10.101.65.131:5082;uri=sip:15553010221%40192.168.41.57:48310%3bline%3dbq029ivo;line=bq029ivo>;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, 100rel, replaces, from-change Session-Expires: 3600 Min-SE: 90 Proxy-Authorization: Digest username="45487cfdffef4777",realm="ws2.domain.tld",nonce="d84c8d657ba6e3081547bbb6e0c1817c",uri="sip:22@ws2.domain.tld;user=phone",qop=auth,nc=00000001,cnonce="6be15ae9",response="9455eafa4f6b2b78e971a87cb2716132",opaque="485307819b9fa9a1f7e2ca58ae77f795",algorithm=MD5 Content-Type: application/sdp Content-Length: 258 P-Charging-Vector: icid-value=31363833363232;icid-generated-at=c5sbcp01t X-User: <sip:45487cfdffef4777@ws2.domain.tld> X-Location: dev.DefaultGroup;reg=192.168.48.68:5060;sig=192.168.48.74:5060;bt=0 X-Realm: p01t v=0 o=root 711904586 711904586 IN IP4 10.101.65.133 s=call c=IN IP4 10.101.65.133 t=0 0 m=audio 10490 RTP/AVP 9 8 101 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:10491 a=ptime:20 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:tm [t_funcs.c:373]: t_relay_to(): new transaction forwarded May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/receive.c:528]: receive_msg(): request-route executed in: 45584 usec May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/receive.c:628]: receive_msg(): cleaning up May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:863]: free_sdp(): _sdp = 0x7fa8d478c728 May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:865]: free_sdp(): sdp = 0x7fa8d44ef100 May 9 10:48:19 p01t-1 kamailio.sbc[150273]: DEBUG: sbc:<core> [core/parser/sdp/sdp.c:867]: free_sdp(): session = 0x7fa8d44ee018 ... May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:1664]: _tcpconn_find(): found connection by peer address (id: 1) May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2541]: tcpconn_send_put(): found fd in cache (11, 0x7fa8d0965140, 1) May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2763]: tcpconn_do_send(): sending... May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2796]: tcpconn_do_send(): after real write: c= 0x7fa8d0965140 n=1261 fd=11 May 9 10:48:19 p01t-1 kamailio.sbc[150271]: DEBUG: sbc:<core> [core/tcp_main.c:2797]: tcpconn_do_send(): buf= INVITE sip:22@192.168.41.157:39342;line=5z2d2k8i;ob SIP/2.0 ... ``` Finally the Application Server in front cancels the call. But look at this: ``` root@p01t-1:~# tcpdump -nn -i eth1 tcp port 5082 tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on eth1, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:47:31.915062 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [.], ack 3024626659, win 501, options [nop,nop,TS val 924881395 ecr 4525523], length 0 10:47:31.916129 IP 10.101.65.130.39342 > 10.101.65.131.5082: Flags [.], ack 1, win 4836, options [nop,nop,TS val 4528662 ecr 924819977], length 0 10:48:02.635024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [.], ack 1, win 501, options [nop,nop,TS val 924912115 ecr 4528662], length 0 10:48:02.636100 IP 10.101.65.130.39342 > 10.101.65.131.5082: Flags [.], ack 1, win 4836, options [nop,nop,TS val 4531734 ecr 924819977], length 0 ----- switch port port shutdown ------ ----- make the call: 10:48:19.690401 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929170 ecr 4531734], length 1261 10:48:19.899036 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929379 ecr 4531734], length 1261 10:48:20.331011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924929811 ecr 4531734], length 1261 10:48:21.194994 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924930675 ecr 4531734], length 1261 10:48:22.891001 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924932371 ecr 4531734], length 1261 10:48:26.446978 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924935927 ecr 4531734], length 1261 10:48:33.355070 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924942835 ecr 4531734], length 1261 10:48:40.011057 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924949491 ecr 4531734], length 1261 10:48:46.667041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924956147 ecr 4531734], length 1261 10:48:53.323039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924962803 ecr 4531734], length 1261 10:48:59.979042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924969459 ecr 4531734], length 1261 10:49:06.635029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924976115 ecr 4531734], length 1261 10:49:13.291079 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924982771 ecr 4531734], length 1261 10:49:19.947045 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924989427 ecr 4531734], length 1261 10:49:26.603048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 924996083 ecr 4531734], length 1261 10:49:33.259016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925002739 ecr 4531734], length 1261 10:49:39.915052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925009395 ecr 4531734], length 1261 10:49:46.571046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925016051 ecr 4531734], length 1261 10:49:53.227015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925022707 ecr 4531734], length 1261 10:49:59.883017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925029363 ecr 4531734], length 1261 10:50:06.539037 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925036019 ecr 4531734], length 1261 10:50:13.195051 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925042675 ecr 4531734], length 1261 10:50:19.850986 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925049331 ecr 4531734], length 1261 10:50:26.507018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925055987 ecr 4531734], length 1261 10:50:33.163011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925062643 ecr 4531734], length 1261 10:50:39.819015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925069299 ecr 4531734], length 1261 10:50:46.475056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925075955 ecr 4531734], length 1261 10:50:53.135023 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925082615 ecr 4531734], length 1261 10:51:00.043094 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925089523 ecr 4531734], length 1261 10:51:06.699024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925096179 ecr 4531734], length 1261 10:51:13.355049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925102835 ecr 4531734], length 1261 10:51:20.011080 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925109491 ecr 4531734], length 1261 10:51:26.667023 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925116147 ecr 4531734], length 1261 10:51:33.323042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925122803 ecr 4531734], length 1261 10:51:39.979029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925129459 ecr 4531734], length 1261 10:51:46.635040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925136115 ecr 4531734], length 1261 10:51:53.291007 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925142771 ecr 4531734], length 1261 10:51:59.947009 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925149427 ecr 4531734], length 1261 10:52:06.603019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925156083 ecr 4531734], length 1261 10:52:13.259033 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925162739 ecr 4531734], length 1261 10:52:19.915011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925169395 ecr 4531734], length 1261 10:52:26.571014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925176051 ecr 4531734], length 1261 10:52:33.227032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925182707 ecr 4531734], length 1261 10:52:39.883041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925189363 ecr 4531734], length 1261 10:52:46.539013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925196019 ecr 4531734], length 1261 10:52:53.199018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925202679 ecr 4531734], length 1261 10:53:00.107035 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925209587 ecr 4531734], length 1261 10:53:06.763039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925216243 ecr 4531734], length 1261 10:53:13.419041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925222899 ecr 4531734], length 1261 10:53:20.075014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925229555 ecr 4531734], length 1261 10:53:26.731046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925236211 ecr 4531734], length 1261 10:53:33.387027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925242867 ecr 4531734], length 1261 10:53:40.043077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925249523 ecr 4531734], length 1261 10:53:46.699076 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925256179 ecr 4531734], length 1261 10:53:53.355055 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925262835 ecr 4531734], length 1261 10:54:00.011019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925269491 ecr 4531734], length 1261 10:54:06.667071 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925276147 ecr 4531734], length 1261 10:54:13.323026 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925282803 ecr 4531734], length 1261 10:54:19.979077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925289459 ecr 4531734], length 1261 10:54:26.635284 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925296115 ecr 4531734], length 1261 10:54:33.291019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925302771 ecr 4531734], length 1261 10:54:39.946998 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925309427 ecr 4531734], length 1261 10:54:46.603049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925316083 ecr 4531734], length 1261 10:54:53.259008 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925322739 ecr 4531734], length 1261 10:54:59.915019 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925329395 ecr 4531734], length 1261 10:55:06.571100 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925336051 ecr 4531734], length 1261 10:55:13.227056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925342707 ecr 4531734], length 1261 10:55:19.883016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925349363 ecr 4531734], length 1261 10:55:26.539021 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925356019 ecr 4531734], length 1261 10:55:33.195043 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925362675 ecr 4531734], length 1261 10:55:39.850991 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925369331 ecr 4531734], length 1261 10:55:46.507013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925375987 ecr 4531734], length 1261 10:55:53.163060 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925382643 ecr 4531734], length 1261 10:55:59.819014 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925389299 ecr 4531734], length 1261 10:56:06.475045 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925395955 ecr 4531734], length 1261 10:56:13.131065 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925402611 ecr 4531734], length 1261 10:56:19.787052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925409267 ecr 4531734], length 1261 10:56:26.443048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925415923 ecr 4531734], length 1261 10:56:33.099016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925422579 ecr 4531734], length 1261 10:56:39.755032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925429235 ecr 4531734], length 1261 10:56:46.411005 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925435891 ecr 4531734], length 1261 10:56:53.067116 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925442547 ecr 4531734], length 1261 10:56:59.723032 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925449203 ecr 4531734], length 1261 10:57:06.379062 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925455859 ecr 4531734], length 1261 10:57:13.035003 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925462515 ecr 4531734], length 1261 10:57:19.691077 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925469171 ecr 4531734], length 1261 10:57:26.347050 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925475827 ecr 4531734], length 1261 10:57:33.003004 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925482483 ecr 4531734], length 1261 10:57:39.659029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925489139 ecr 4531734], length 1261 10:57:46.314989 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925495795 ecr 4531734], length 1261 10:57:52.971040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925502451 ecr 4531734], length 1261 10:57:59.631026 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925509111 ecr 4531734], length 1261 10:58:06.539039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925516019 ecr 4531734], length 1261 10:58:13.195056 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925522675 ecr 4531734], length 1261 10:58:19.851012 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925529331 ecr 4531734], length 1261 10:58:26.507049 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925535987 ecr 4531734], length 1261 10:58:33.163017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925542643 ecr 4531734], length 1261 10:58:39.819091 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925549299 ecr 4531734], length 1261 10:58:46.475017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925555955 ecr 4531734], length 1261 10:58:53.131046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925562611 ecr 4531734], length 1261 10:58:59.786990 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925569267 ecr 4531734], length 1261 10:59:06.443029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925575923 ecr 4531734], length 1261 10:59:13.099009 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925582579 ecr 4531734], length 1261 10:59:19.754984 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925589235 ecr 4531734], length 1261 10:59:26.411053 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925595891 ecr 4531734], length 1261 10:59:33.067041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925602547 ecr 4531734], length 1261 10:59:39.723053 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925609203 ecr 4531734], length 1261 10:59:46.379016 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925615859 ecr 4531734], length 1261 10:59:53.035054 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925622515 ecr 4531734], length 1261 10:59:59.691058 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925629171 ecr 4531734], length 1261 11:00:06.347021 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925635827 ecr 4531734], length 1261 11:00:13.003052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925642483 ecr 4531734], length 1261 11:00:19.659043 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925649139 ecr 4531734], length 1261 11:00:26.315011 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925655795 ecr 4531734], length 1261 11:00:32.971015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925662451 ecr 4531734], length 1261 11:00:39.627039 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925669107 ecr 4531734], length 1261 11:00:46.283052 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925675763 ecr 4531734], length 1261 11:00:52.939024 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925682419 ecr 4531734], length 1261 11:00:59.595048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925689075 ecr 4531734], length 1261 11:01:06.251017 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925695731 ecr 4531734], length 1261 11:01:12.907013 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925702387 ecr 4531734], length 1261 11:01:19.563042 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925709043 ecr 4531734], length 1261 11:01:26.219027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925715699 ecr 4531734], length 1261 11:01:32.875010 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925722355 ecr 4531734], length 1261 11:01:39.531004 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925729011 ecr 4531734], length 1261 11:01:46.187040 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925735667 ecr 4531734], length 1261 11:01:52.843002 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925742323 ecr 4531734], length 1261 11:01:59.499048 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925748979 ecr 4531734], length 1261 11:02:06.155027 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925755635 ecr 4531734], length 1261 11:02:12.811044 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925762291 ecr 4531734], length 1261 11:02:19.467018 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925768947 ecr 4531734], length 1261 11:02:26.123041 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925775603 ecr 4531734], length 1261 11:02:32.779046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925782259 ecr 4531734], length 1261 11:02:39.435015 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925788915 ecr 4531734], length 1261 11:02:46.091034 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925795571 ecr 4531734], length 1261 11:02:52.747128 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925802227 ecr 4531734], length 1261 11:02:59.403096 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925808883 ecr 4531734], length 1261 11:03:06.059012 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925815539 ecr 4531734], length 1261 11:03:12.715029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925822195 ecr 4531734], length 1261 11:03:19.370993 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925828851 ecr 4531734], length 1261 11:03:26.027010 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925835507 ecr 4531734], length 1261 11:03:32.683029 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925842163 ecr 4531734], length 1261 11:03:39.339046 IP 10.101.65.131.5082 > 10.101.65.130.39342: Flags [P.], seq 1:1262, ack 1, win 501, options [nop,nop,TS val 925848819 ecr 4531734], length 1261 ``` ### Possible Solutions I have no idea why tcp_send_timeout is not set on the connected socket during spawning the listener for this client. ### Additional Information ``` root@p01t-1:~# kamailio -V version: kamailio 5.6.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 10.2.1 ``` * **Operating System**: ``` root@p01t-1:~# cat /etc/debian_version 11.7 Linux p01t-1.neotel.at 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux ``` [debug.log](https://github.com/kamailio/kamailio/files/11429302/debug.log) -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3443 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3443(a)github.com>

3 7

[kamailio/kamailio] app_ruby: print backtrace when ruby exception occurs (#1766)
by Fatih Orhan 13 Nov '23

13 Nov '23

### Description Hello, When there is an error in my ruby script, app_ruby prints exception message without a stack trace, like this: ``` Dec 14 16:25:17 servername /usr/sbin/kamailio[24313]: ERROR: app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: wrong number of arguments (1 for 2..3) Dec 14 16:25:17 servername /usr/sbin/kamailio[24313]: ERROR: app_ruby [app_ruby_api.c:1078]: app_ruby_run_ex(): ruby exception (6) on callback for: ksr_request_route (res type: 17) ``` Altough this message tells what is the error, it doesn't tell **where** the error happened, so it's hard to find the source of the problem. In ruby, exceptions have _backtrace()_ method returning stack trace as an array of strings. It would be really helpful if app_ruby also call this method and append its result to error message. ### Reproduction in kamailio.cfg ``` loadmodule "app_ruby.so" modparam("app_ruby", "load", "/etc/kamailio/ruby/routes.rb") cfgengine "ruby" ``` in /etc/kamailio/ruby/routes.rb ``` def some_method(param1, param2) end def ksr_request_route some_method(1) end ``` ### Expected behavior ``` Dec 14 16:46:24 servername /usr/sbin/kamailio[24314]: ERROR: <core> [core/kemi.c:87]: sr_kemi_core_err(): wrong number of arguments (1 for 2): /etc/kamailio/ruby/routes.rb:1:in `some_method' /etc/kamailio/ruby/routes.rb:4:in `ksr_request_route' ``` #### Actual observed behavior ``` Dec 14 16:45:42 servername /usr/sbin/kamailio[24311]: ERROR: app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: wrong number of arguments (1 for 2) ``` ### Possible Solutions Relevant code seem to be here: https://github.com/kamailio/kamailio/blob/master/src/modules/app_ruby/app_r… I found example C code to print stack trace here but couldn't figure out how to integrate to app_ruby: http://zoo-project.org/svn/trunk/zoo-project/zoo-kernel/service_internal_ru… Equivalent ruby code would be (this code is not idiomatic, my aim is to provide C-like ruby code): ``` def some_error_generating_method method_taking_two_params(1) rescue => exception message = exception.to_s() + "\n" stack_trace = exception.backtrace() for line in stack_trace message = message + line + "\n" end print(message) end ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.2.0 (x86_64/linux) 535e13 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: 535e13 compiled on 10:26:34 Nov 28 2018 with gcc 4.8.5 ``` * **Operating System**: Centos 7.2 64bit ``` Linux servername 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 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/1766

3 3

← Newer
1
...
9
10
11
12
13
14
15
...
30
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev September 2023