sr-dev May 2023

sr-dev@lists.kamailio.org

16 participants
322 discussions

[kamailio/kamailio] rtp_media_server module hard codes contact header to "rms" (Issue #3380)

by Daniel Donoghue

### Description when using rtp_media_server module in my kamailio configuration, the `rms_answer` function generates a "200 OK" with a hard-coded Contact header user. I believe it would make more sense for this to use the To user (`$tU`) as that should be who is answering. #### Reproduction ``` route { if (t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); if (is_method("INVITE") && !has_totag()) { if (!rms_answer("rms:start_long")) { t_reply("503", "server error"); } exit; } if (rms_dialog_check()) { rms_sip_request(); } } ``` #### Debugging Data n/a #### Log Messages n/a #### SIP Traffic ``` INVITE sip:+461812345678@123.123.example.com SIP/2.0. Via: SIP/2.0/UDP 172.21.0.3:6060;branch=z9hG4bK6810d54f. Max-Forwards: 70. From: <sip:+461812345677@172.21.0.3:6060>;tag=as21f01093. To: <sip:+461812345678@123.123.example.com>. Contact: <sip:+461812345677@172.21.0.3:6060>. Call-ID: 4f56bf7336a114d75402e30f47013748@172.21.0.3:6060. CSeq: 102 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Type: application/sdp. Content-Length: 248. .. v=0. o=root 1511071437 1511071437 IN IP4 172.21.0.3. s=Asterisk PBX 18.10.0. c=IN IP4 172.21.0.3. t=0 0. m=audio 26516 RTP/AVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=maxptime:150. a=sendrecv. SIP/2.0 200 OK. Via: SIP/2.0/UDP 172.21.0.2;branch=z9hG4bK09e2.aa4ab6455ca95a0ee95268497e877cc4.2;rport=5060. Via: SIP/2.0/UDP 172.21.0.3:6060;rport=6060;branch=z9hG4bK6810d54f. From: <sip:+461812345677@172.21.0.3:6060>;tag=as21f01093. To: <sip:+461812345678@123.123.example.com>;tag=f46321019d9527ace4b30f86d231e4a2-cafc0000. Call-ID: 4f56bf7336a114d75402e30f47013748@172.21.0.3:6060. CSeq: 102 INVITE. Contact: <sip:rms@172.21.0.4:5060>. Content-Type: application/sdp. Server: kamailio (5.6.3 (aarch64/linux)). Content-Length: 99. .. v=0. o=- 1028316687 1 IN IP4 172.21.0.4. s=-. c=IN IP4 172.21.0.4. t=0 0. m=audio 51900 RTP/AVP 8. ``` ### Possible Solutions n/a ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.6.3 (aarch64/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-NOSMP, 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 12.2.0 ``` * **Operating System**: ``` debian bookworm ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3380 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3380(a)github.com>

11 months, 3 weeks

[kamailio/kamailio] List selectors (#2705)

by sergey-safarov

#### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] 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 the selectors feature for `lost` module. The module still in development but the core functionality is working. What need to do 1. separate feature into dedicated `.c` file; 2. rebase on current `lost` implementation; 3. add documentation; 4. add a unit test. Would be fine if we can merge this into 5.5. This branch based on e7d68556e3560f488c4f421731f78b3f9abe549e commit You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2705 -- Commit Summary -- * http_client: http_client_request (api) content-type header support * lost: new features, attributes and a new function to dereference location * lost: bug-fix due to a code formatting error * lost: DOM level count fix * http_client: duplicated code removed * lost: README update * lost: memory leak fix and code refactoring * lost: implemented sectors -- File Changes -- M src/modules/http_client/curl_api.c (1) M src/modules/http_client/curl_api.h (3) M src/modules/http_client/functions.c (30) M src/modules/http_client/functions.h (14) M src/modules/lost/doc/lost.xml (2) M src/modules/lost/doc/lost_admin.xml (172) M src/modules/lost/functions.c (921) M src/modules/lost/functions.h (3) M src/modules/lost/lost.c (754) A src/modules/lost/naptr.c (255) A src/modules/lost/naptr.h (38) M src/modules/lost/pidf.c (5) A src/modules/lost/response.c (991) A src/modules/lost/response.h (131) M src/modules/lost/utilities.c (532) M src/modules/lost/utilities.h (65) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2705.patch https://github.com/kamailio/kamailio/pull/2705.diff -- 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/pull/2705

11 months, 3 weeks

[kamailio/kamailio] janssonrpcc: No failover to lower prio server (Issue #3378)

by Alex Hermann

### Description I have 2 jsonrpc servers configured with different prio's. For testing, I have the servers configured to always delay the response to any request by more than the module's timout setting. The (initial) request is sent to the first server. As this one times out, I would expect a retry to go to the second servers, but instead, all retries are sent to the same server. The backup server is never contacted. This makes the whole "prio" system seem a bit useless.  ### Troubleshooting #### Reproduction ``` modparam("janssonrpcc", "server", "conn=test;addr=pc1;port=8081;priority=5;weight=10") modparam("janssonrpcc", "server", "conn=test;addr=pc1;port=8082;priority=5;weight=10") ``` ``` janssonrpc_request("test", "Test.Timeout", '[ { "Timout": 1000} ]', "route=JSONRPC_RESPONSE;retry=10;timeout=1000"); ```  #### Log Messages No useful logs are produced. I verified the described behavior on the jsonrpc server.  ``` 2023-02-23T16:59:34.585346+01:00 pc1 proxy1[340870]: INFO: janssonrpcc [janssonrpc_connect.c:361]: bev_connect(): Connecting to server pc1:8081 for conn rating. 2023-02-23T16:59:34.585420+01:00 pc1 proxy1[340870]: INFO: janssonrpcc [janssonrpc_connect.c:361]: bev_connect(): Connecting to server pc1:8082 for conn rating. 2023-02-23T16:59:34.585446+01:00 pc1 proxy1[340870]: INFO: janssonrpcc [janssonrpc_connect.c:290]: bev_connect_cb(): Connected to host pc1:8081 2023-02-23T16:59:34.585462+01:00 pc1 proxy1[340870]: INFO: janssonrpcc [janssonrpc_connect.c:290]: bev_connect_cb(): Connected to host pc1:8082 2023-02-23T17:05:10.903398+01:00 pc1 proxy1[340870]: WARNING: janssonrpcc [janssonrpc_request.c:247]: schedule_retry(): Number of retries exceeded. Failing request. ``` ### Possible Solutions  Retry in combination with a timeout and prio's is a bit tricky. When do what? Just retrying on the first prio makes the lower prio servers completely useless, while going to the next prio on every retry skips possibly useful high-prio servers and may exhaust the number of candidate servers very fast. Best solution IMHO would be to first try every server in the highest prio, before going to the next prio. Do not do (exponential) backoff between these steps. If there are still retries remaining after that, wrap around to the highest prio with the exponentional backoff delay. With the above, failover considers all servers and failover between servers is fast while not overloading a single server. BTW. If I configure multiple servers per prio, it seems to randomly select one of them for every (re)try. It never selects one form the next prio. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` 5.6.1 ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3378 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3378(a)github.com>

11 months, 3 weeks

[kamailio/kamailio] Add support for Linux kernel anyIP feature (Issue #3394)

by mohsen

Hi I have a kimailio box that receives messages from one interface and send it from another interface and I use dispatcher module successfully. Now I assigned an I range to Linux loopback interface through Linux kernel anyip feature. And I can ping the range. ip -4 route add local 192.168.0.0/24 dev lo I want to send messages from source of the ip in this range but kamailio cant do this in the right way. I added this two directives to kamailio.cfg: mhomed=yes ip_free_bind = 1 and when I want to use an ip from the list I use $fs=”udp:192.168.0.120:5060”; With no luck If I use force_send_socket(udp:192.168.0.120:5060); kamailio returns an error bad force_send_socket argument: 192.168.0.120:5060 (kamailio doesn't listen on it) and if I add listen directive for one ip like: listen=udp:192.168.0.120:5060 everything works fine but I want to be able to use any ip from list not just one ip. Thanks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3394 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3394(a)github.com>

1 year

[kamailio/kamailio] lib: big integers should not be treated as negative ones (#2106)

by Ivan Murashko

0xffffffff00000000ULL mask does not take into consideration signed 32 bit integers and as result 2147483648 will be stored as -2147483648. Another mask should be used to correct the issue: 0xffffffff80000000ULL. It processes correctly the case of integers that are greater than 2147483647. There are several gdb tests below: (gdb) p ((unsigned long long)2147483648 & 0xffffffff80000000ULL) $1= 2147483648 (gdb) p ((unsigned long long)2147483647 & 0xffffffff80000000ULL) $2 = 0 (gdb) p ((unsigned long long)2147483646 & 0xffffffff80000000ULL) $3 = 0 (gdb) p ((unsigned long long)4147483646 & 0xffffffff80000000ULL) $4 = 2147483648   #### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] 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) - [ ] 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 - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2106 -- Commit Summary -- * lib: big integers should not be treated as negative ones -- File Changes -- M src/lib/srdb1/db_ut.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2106.patch https://github.com/kamailio/kamailio/pull/2106.diff -- 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/pull/2106

1 year

[kamailio/kamailio] sslv3 errors showing up with 'tls_method' set as 'TLSv1.2+' (Issue #3085)

by Vinicius K. Ruoso

### Description Some users are having issues connecting to kamailio websocket using TLS. The logs show SSLv3 errors. Cannot find why that error would show up if SSLv2/3 is not enabled. Double checked it via SSLLabs that only TLSv1.2 is allowed in the service. Any pointers would be appreciated. Also, let me know if more debug information is needed. ### Troubleshooting #### Debugging Data This is the TLS config: ``` modparam("tls", "tls_method", "TLSv1.2+") modparam("tls", "verify_certificate", 0) modparam("tls", "require_certificate", 0) modparam("tls", "low_mem_threshold1", 0) modparam("tls", "low_mem_threshold2", 0) modparam("tls", "private_key", "/etc/certs/tls.key") modparam("tls", "certificate", "/etc/certs/tls.crt") ``` This is the output from tls module in kamcmd: ``` kamcmd> tls.info { max_connections: 2048 opened_connections: 353 clear_text_write_queued_bytes: 0 } kamcmd> tls.options { force_run: 0 method: TLSv1.2+ verify_certificate: 0 verify_depth: 9 require_certificate: 0 private_key: /etc/certs/tls.key ca_list: <null string> certificate: /etc/certs/tls.crt cipher_list: <null string> session_cache: 0 session_id: kamailio-tls-5.x.y config: <null string> log: 3 debug: 3 connection_timeout: 600 disable_compression: 1 ssl_release_buffers: -1 ssl_freelist_max: -1 ssl_max_send_fragment: -1 ssl_read_ahead: 0 send_close_notify: 0 low_mem_threshold1: 0 low_mem_threshold2: 0 ct_wq_max: 10485760 con_ct_wq_max: 65536 ct_wq_blk_size: 4096 } ``` #### Log Messages I see this log messages related to SSLv3: ``` 15(36) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown 15(36) ERROR: <core> [core/tcp_read.c:1512]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fafc8768190 r: 0x7fafc8768278 (-1) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.3.9 (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_BLACKLIST, 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 6.3.0 ``` * **Operating System**: Debian 9.13. ``` Linux 4.19.112+ #1 SMP Wed Sep 23 07:53:39 PDT 2020 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3085 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3085(a)github.com>

1 year

[kamailio/kamailio] topoh: uses socket IP when no mask_ip is defined (PR #3341)

by TorPetterson

#### 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) - [ ] 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) - [ ] 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 - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  topoh: uses socket IP when no mask_ip is defined If the parameter mask_ip is not defined the module finds the socket IP and uses that as mask IP for the message. If the socket has an advertised IP it is used, otherwise the socket IP is used. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3341 -- Commit Summary -- * topoh: uses socket IP when no mask_ip is defined * Merge remote-tracking branch 'upstream/master' -- File Changes -- M src/modules/topoh/doc/topoh_admin.xml (4) M src/modules/topoh/th_msg.c (55) M src/modules/topoh/th_msg.h (16) M src/modules/topoh/topoh_mod.c (309) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3341.patch https://github.com/kamailio/kamailio/pull/3341.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3341 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3341(a)github.com>

1 year, 1 month

[kamailio/kamailio] kazoo: build warning rmq (Issue #3464)

by sergey-safarov

warning on alpine dist ``` In file included from kz_amqp.c:32: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ In file included from kz_amqp.c:33: /usr/include/amqp_framing.h:8:2: warning: #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. [-Wcpp] 8 | #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. | ^~~~~~~ In file included from kz_amqp.c:34: /usr/include/amqp_tcp_socket.h:7:2: warning: #warning "amqp_tcp_socket.h is deprecated, use rabbitmq-c/tcp_socket.h instead." [-Wcpp] 7 | #warning "amqp_tcp_socket.h is deprecated, use rabbitmq-c/tcp_socket.h instead." | ^~~~~~~ In file included from kz_amqp.c:35: /usr/include/amqp_ssl_socket.h:9:2: warning: #warning "amqp_ssl_socket.h is deprecated, use rabbitmq-c/ssl_socket.h instead. [-Wcpp] 9 | #warning "amqp_ssl_socket.h is deprecated, use rabbitmq-c/ssl_socket.h instead. | ^~~~~~~ In file included from kz_amqp.h:35, from kazoo.c:36: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ kz_amqp.c: In function 'kz_amqp_connection_open_ssl': kz_amqp.c:815:13: warning: 'amqp_set_initialize_ssl_library' is deprecated [-Wdeprecated-declarations] 815 | amqp_set_initialize_ssl_library(1); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/amqp_ssl_socket.h:11: /usr/include/rabbitmq-c/ssl_socket.h:233:16: note: declared here 233 | void AMQP_CALL amqp_set_initialize_ssl_library(amqp_boolean_t do_initialize); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CC (gcc) [M kazoo.so] kz_fixup.o CC (gcc) [M kazoo.so] kz_hash.o In file included from kz_amqp.h:35, from kz_hash.h:33, from kz_hash.c:29: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ CC (gcc) [M kazoo.so] kz_json.o CC (gcc) [M kazoo.so] kz_pua.o kz_amqp.c: In function 'kz_amqp_send_ex': kz_amqp.c:2327:12: warning: 'num_headers' may be used uninitialized [-Wmaybe-uninitialized] 2327 | if (num_headers > 0) { | ^ kz_amqp.c:2281:9: note: 'num_headers' was declared here 2281 | int num_headers = 0; | ^~~~~~~~~~~ CC (gcc) [M kazoo.so] kz_trans.o In file included from kz_amqp.h:35, from kz_trans.c:54: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ make[3]: Entering directory '/usr/src/kamailio/pkg/kamailio/alpine/src/kamailio-95d33167cff13190b51c04b5347df6d419cf2630/src/lib/srdb1' make[3]: 'libsrdb1.so.1.0' is up to date. make[3]: Leaving directory '/usr/src/kamailio/pkg/kamailio/alpine/src/kamailio-95d33167cff13190b51c04b5347df6d419cf2630/src/lib/srdb1' LD (gcc) [M kazoo.so] kazoo.so make[2]: --libs: No such file or directory make[2]: --libs: No such file or directory CC (gcc) [M rabbitmq.so] rabbitmq.o CC (gcc) [M rabbitmq.so] utils.o In file included from utils.c:47: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ In file included from utils.c:48: /usr/include/amqp_framing.h:8:2: warning: #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. [-Wcpp] 8 | #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. | ^~~~~~~ In file included from rabbitmq.c:55: /usr/include/amqp_tcp_socket.h:7:2: warning: #warning "amqp_tcp_socket.h is deprecated, use rabbitmq-c/tcp_socket.h instead." [-Wcpp] 7 | #warning "amqp_tcp_socket.h is deprecated, use rabbitmq-c/tcp_socket.h instead." | ^~~~~~~ In file included from rabbitmq.c:56: /usr/include/amqp.h:7:2: warning: #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." [-Wcpp] 7 | #warning "amqp.h is deprecated, use rabbitmq-c/amqp.h instead." | ^~~~~~~ In file included from rabbitmq.c:57: /usr/include/amqp_framing.h:8:2: warning: #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. [-Wcpp] 8 | #warning "amqp_framing.h is deprecated, use rabbitmq-c/framing.h instead. | ^~~~~~~ LD (gcc) [M rabbitmq.so] rabbitmq.so CC (gcc) [M sctp.so] sctp_mod.o ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3464 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3464(a)github.com>

1 year, 1 month

[kamailio/kamailio] xhttp_prom_timeout keep default value (Issue #3439)

by Dakna adnane

hello , I 'm trying to change value "xhttp_prom_timeout" to specific value , for instance 1 minute , to do i set command : modparam("xhttp_prom", "xhttp_prom_timeout", 1) , but it seems metrics is not deleted after 1 minute of not using this metric , only metric is deleted after 10 hours , even i set xhttp_prom_timeoutto 1 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3439 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3439(a)github.com>

1 year, 1 month

[kamailio/kamailio] pv_cache gets filled if dynamic names are used (Issue #3440)

by Victor Seva

### Description _**Sipwise** hat on_ We noticed that pkg memory was getting exhausted and we found out that pv_cache_add() was the origin of the allocations. We are using ``$xavp(user_<UUID>)`` variables that, for sure, are kind of dynamic. There is a pv_cache_drop() that tries to remove ``$sht()`` occurrences when the cache is about to be filled but in our case that's not helping. #### Log Messages ``` WARNING: ROUTE_SET_CALLEE_DIALOG_TOTAL <core> [core/pvapi.c:340]: pv_cache_add(): pv cache limit is going to be exceeded - pkg memory may get filled with pv declarations WARNING: dialog:failed <core> [core/pvapi.c:340]: pv_cache_add(): pv cache limit is going to be exceeded - pkg memory may get filled with pv declarations ``` ### Possible Solutions Possible solutions that came on the top of my head: - add a datetime member to struct _pv_cache so we can keep the last time it was accessed and search for the oldest and remove them in pv_cache_drop() - add pv module parameter to define a magic prefix, for instance '__' that will mark those vars as "temporal" should remove it from cache when needed. - add pv module parameter to control what types of variables will be added to cache Any thoughts about this? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3440 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3440(a)github.com>

1 year, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2023