- sr-dev - kamailio.org

git:master:a0941254: db_schema: Create new table definitions
by Henning Westerholt 22 Oct '24

22 Oct '24

Module: kamailio Branch: master Commit: a094125433122313c2e02dfc0e9ad5d3a5beaa50 URL: https://github.com/kamailio/kamailio/commit/a094125433122313c2e02dfc0e9ad5d… Author: Xenofon Karamanos <22965395+xkaraman(a)users.noreply.github.com> Committer: Henning Westerholt <hw(a)gilawa.com> Date: 2024-10-22T12:59:03+02:00 db_schema: Create new table definitions --- Added: utils/kamctl/db_berkeley/kamailio/nds_trusted_domains Added: utils/kamctl/db_berkeley/kamailio/s_cscf Added: utils/… [View More]

1 0

git:master:e2ea7279: db_schema: Add ims_icscf db schema
by Henning Westerholt 22 Oct '24

22 Oct '24

Module: kamailio Branch: master Commit: e2ea727988828a9683ef112637e25ee4d58032f7 URL: https://github.com/kamailio/kamailio/commit/e2ea727988828a9683ef112637e25ee… Author: Xenofon Karamanos <22965395+xkaraman(a)users.noreply.github.com> Committer: Henning Westerholt <hw(a)gilawa.com> Date: 2024-10-22T12:59:03+02:00 db_schema: Add ims_icscf db schema --- Added: src/lib/srdb1/schema/kamailio-ims_icscf.xml Added: src/lib/srdb1/schema/nds_trusted_domains.xml Added: src/lib/srdb1/… [View More]

1 0

git:master:c823f413: core: parser sdp - check length for rtpmap extract
by Daniel-Constantin Mierla 22 Oct '24

22 Oct '24

Module: kamailio Branch: master Commit: c823f41350ab9186a323707e9be32e31922bec17 URL: https://github.com/kamailio/kamailio/commit/c823f41350ab9186a323707e9be32e3… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-22T07:41:08+02:00 core: parser sdp - check length for rtpmap extract --- Modified: src/core/parser/sdp/sdp_helpr_funcs.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

git:master:0cbb2eb0: jwt: print decode result in error log message
by Daniel-Constantin Mierla 22 Oct '24

22 Oct '24

Module: kamailio Branch: master Commit: 0cbb2eb035c7d2a29ae707cde94a2c0573e0ffd5 URL: https://github.com/kamailio/kamailio/commit/0cbb2eb035c7d2a29ae707cde94a2c0… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-22T07:34:29+02:00 jwt: print decode result in error log message --- Modified: src/modules/jwt/jwt_mod.c --- Diff: https://github.com/kamailio/kamailio/commit/0cbb2eb035c7d2a29ae707cde94a2c0…… [View More]

1 0

git:master:6b7894d6: modules: readme files regenerated - rtpengine ... [skip ci]
by Kamailio Dev 21 Oct '24

21 Oct '24

Module: kamailio Branch: master Commit: 6b7894d66ca65ca99b5987ddc35a7f28c7a88949 URL: https://github.com/kamailio/kamailio/commit/6b7894d66ca65ca99b5987ddc35a7f2… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2024-10-21T15:01:11+02:00 modules: readme files regenerated - rtpengine ... [skip ci] --- Modified: src/modules/rtpengine/README --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

[kamailio/kamailio] rtpengine: disable aggressive redetection by default (PR #3992)
by Stefan Mititelu 21 Oct '24

21 Oct '24

#### 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 - [X] Related to issue #3297 #### Description  The setup is a kamailio with no available rtpengine. (e.g. has a list with rtpengine urls but those are not reachable) Recently had a crash similar to #3297, but in an outdated kamailio version (5.5.7). Tried to reproduce this in 5.5.7 and 5.8.3 but could not crash any of them. However I managed to get the logs similar to ones right before the crash happened: ``` 2024-10-04T17:39:58.026206+03:00 kamailio[450237]: ERROR: {1 1 INVITE 203-450290(a)192.168.100.93} <core> [core/action.c:1595]: run_actions(): alert - action [corefunc (16)] cfg [/home/stefan/kamailio.cfg:625] took too long [29310906 us] ``` ...directly related to how much rtpengine_manage() function took to execute. So routing of SIP is delayed by that ammount. Tracked this in code, down to where this lock is get, when "aggressive_redetection" modparam is enabled: https://github.com/kamailio/kamailio/blob/66fe6eb71e58a02222d1a2fb00f9a0cdb… I will double check that part of the code, since I don't think a lock get is necessary. It only updates a value inside a node, inside the list of nodes, but not changes the list links at all. (this in another PR) For now I propose to disable this aggressive_redetection mechanism by default. Since it delays the SIP routing logic when no rtpengines available (and in some cases lead to crashes in transaction module). You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3992 -- Commit Summary -- * rtpengine: disable aggressive redetection by default -- File Changes -- M src/modules/rtpengine/config.c (2) M src/modules/rtpengine/doc/rtpengine_admin.xml (6) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3992.patch https://github.com/kamailio/kamailio/pull/3992.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3992 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3992(a)github.com> [View Less]

3 4

git:master:b1aae565: rtpengine: disable aggressive redetection by default (#3992)
by GitHub 21 Oct '24

21 Oct '24

Module: kamailio Branch: master Commit: b1aae5658e84453ce5849a627832efbbb6c20117 URL: https://github.com/kamailio/kamailio/commit/b1aae5658e84453ce5849a627832efb… Author: Stefan Mititelu <stefan.mititelu(a)net2phone.com> Committer: GitHub <noreply(a)github.com> Date: 2024-10-21T08:53:39-04:00 rtpengine: disable aggressive redetection by default (#3992) --- Modified: src/modules/rtpengine/config.c Modified: src/modules/rtpengine/doc/rtpengine_admin.xml --- Diff: https://github.… [View More]

1 0

[kamailio/kamailio] app_python3s: initial support for free-threading Python (PR #3987)
by space88man 19 Oct '24

19 Oct '24

#### 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 - Enable `app_python3s` module to build with Free Threading CPython builds - Can be gated with `-DKSR_PYTHON_DISABLE_FREETHREADING` - If Python is a non-free-threading build this change has no effect You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3987 -- Commit Summary -- * app_python3s: initial support for free-threading Python -- File Changes -- M src/modules/app_python3s/apy3s_kemi.c (5) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3987.patch https://github.com/kamailio/kamailio/pull/3987.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3987 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3987(a)github.com> [View Less]

3 17

git:master:62b4ee4a: app_python3s: refactor GIL and thread state handling
by S-P Chan 19 Oct '24

19 Oct '24

Module: kamailio Branch: master Commit: 62b4ee4a0d0b62b35c8bdf67e5daf9cbe9a28499 URL: https://github.com/kamailio/kamailio/commit/62b4ee4a0d0b62b35c8bdf67e5daf9c… Author: S-P Chan <shihping.chan(a)gmail.com> Committer: S-P Chan <shihping.chan(a)gmail.com> Date: 2024-10-19T10:15:34+08:00 app_python3s: refactor GIL and thread state handling * incorrectly using PyGILState_XXX functions; these functions are for threads launched by Python unaware libraries * if the KEMI script used … [View More]

1 0

git:master:c81b2b33: app_python3s: initial support for free-threading Python
by S-P Chan 19 Oct '24

19 Oct '24

Module: kamailio Branch: master Commit: c81b2b3383c5900aba83672da024c812d8e6d89d URL: https://github.com/kamailio/kamailio/commit/c81b2b3383c5900aba83672da024c81… Author: S-P Chan <shihping.chan(a)gmail.com> Committer: S-P Chan <shihping.chan(a)gmail.com> Date: 2024-10-19T10:15:34+08:00 app_python3s: initial support for free-threading Python * build the modules as free-threading compatible if free-threading Python is detected * can be gated by -DKSR_PYTHON_DISABLE_FREETHREADING … [View More]

1 0

git:master:c7f89e81: core: parser sdp - check if body is enough for rtpmap
by Daniel-Constantin Mierla 17 Oct '24

17 Oct '24

Module: kamailio Branch: master Commit: c7f89e81504c425a83f3423bc4b4d9d1a8a48909 URL: https://github.com/kamailio/kamailio/commit/c7f89e81504c425a83f3423bc4b4d9d… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-17T08:21:43+02:00 core: parser sdp - check if body is enough for rtpmap --- Modified: src/core/parser/sdp/sdp_helpr_funcs.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

[kamailio/kamailio] Usrloc keepalive: Not sending OPTIONS to UDP endpoints- 5.8.0 and 5.8.1 (Issue #3844)
by Luke Escudé 17 Oct '24

17 Oct '24

Running compiled Kamailio 5.8.1 (previously 5.8.0) on Debian 12 64-bit We're seeing an issue with UDP endpoints (this issue does not happen with TCP and TLS) where usrloc will not send OPTIONS packet keepalives. Here are all of our usrloc parameters: modparam("usrloc", "db_mode", 0) modparam("usrloc", "ka_domain", "SIPDOMAIN") #-- SIPDOMAIN is a fqdn modparam("usrloc", "ka_from", "sip:proxy-ping@SIPDOMAIN") modparam("usrloc", "ka_mode", 1) modparam("usrloc", "timer_interval", 20) #-- How … [View More]

4 9

git:master:1869a9d9: modules: readme files regenerated - async ... [skip ci]
by Kamailio Dev 16 Oct '24

16 Oct '24

Module: kamailio Branch: master Commit: 1869a9d9a7639c6e18e0cc14779a0078ae165917 URL: https://github.com/kamailio/kamailio/commit/1869a9d9a7639c6e18e0cc14779a007… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2024-10-16T12:01:11+02:00 modules: readme files regenerated - async ... [skip ci] --- Modified: src/modules/async/README Modified: src/modules/tls/README --- Diff: https://github.com/kamailio/kamailio/… [View More]

1 0

git:master:cce29af4: async: docs updates for async_sleep()
by Daniel-Constantin Mierla 16 Oct '24

16 Oct '24

Module: kamailio Branch: master Commit: cce29af41120cf30c4c22979e772d1ca666408c6 URL: https://github.com/kamailio/kamailio/commit/cce29af41120cf30c4c22979e772d1c… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-16T11:46:37+02:00 async: docs updates for async_sleep() --- Modified: src/modules/async/doc/async_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]cce29af41120cf30c4c22979e772d1c… Patch: https://github.com/kamailio/kamailio/commit/cce29af41120cf30c4c22979e772d1c… --- diff --git a/src/modules/async/doc/async_admin.xml b/src/modules/async/doc/async_admin.xml index 027cea11ed7..152c6be5db7 100644 --- a/src/modules/async/doc/async_admin.xml +++ b/src/modules/async/doc/async_admin.xml @@ -234,8 +234,11 @@ route[RESUME] { </title> <para> Simulate a sleep of 'seconds' and then continue the processing of SIP - request with the next action. In case of internal errors, the function - returns false. + request with the next action. Note that the processing continues till + the last action in the current route block. Consider using async_route() + instead if you want to control better what is executed after the wait + time. Beacuse the execution is resumed in another process, do not use + private memory variables before and after the async sleep. </para> <para> The sleep parameter represent the number of seconds to suspend the @@ -243,6 +246,9 @@ route[RESUME] { a static integer or a variable holding an integer. </para> <para> + In case of internal errors, the function returns false. + </para> + <para> This function can be used from REQUEST_ROUTE. </para> <example> @@ -262,15 +268,13 @@ exit; <function moreinfo="none">async_ms_sleep(milliseconds)</function> </title> <para> - Simulate a sleep of 'milliseconds' and then continue the processing of SIP - request with the next action. In case of internal errors, the function - returns false. - This function works only if the ms_timer parameter has a value greater than 0. + Similar to async_sleep(), but with a 'milliseconds' parameter. This + function works only if the ms_timer parameter has a value greater than 0. </para> <para> The sleep parameter represent the number of milliseconds to suspend the - processing of SIP request. Maximum value is 30000 (30 sec). The parameter can be - a static integer or a variable holding an integer. + processing of SIP request. Maximum value is 30000 (30 sec). The parameter + can be a static integer or a variable holding an integer. </para> <para> This function can be used from REQUEST_ROUTE. [View Less]

1 0

git:master:e18c5203: tls: docs - relocate overview notes to Important Notes section
by Daniel-Constantin Mierla 16 Oct '24

16 Oct '24

Module: kamailio Branch: master Commit: e18c52030e202716df9f5e8e953c19fb4a9c65e2 URL: https://github.com/kamailio/kamailio/commit/e18c52030e202716df9f5e8e953c19f… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-16T11:05:04+02:00 tls: docs - relocate overview notes to Important Notes section --- Modified: src/modules/tls/doc/tls.xml --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]e18c52030e202716df9f5e8e953c19f… Patch: https://github.com/kamailio/kamailio/commit/e18c52030e202716df9f5e8e953c19f… --- diff --git a/src/modules/tls/doc/tls.xml b/src/modules/tls/doc/tls.xml index 3a0416fed61..53397e2d50a 100644 --- a/src/modules/tls/doc/tls.xml +++ b/src/modules/tls/doc/tls.xml @@ -60,27 +60,9 @@ must be added to the Kamailio config file. </para> <para> - IMPORTANT: the tls module must be loaded before any other &kamailio; module - that uses libssl (OpenSSL library). A safe option is to have the tls module - loaded first (be in the first "loadmodule" in &kamailio;.cfg). - </para> - <para> - IMPORTANT: For libssl v3.x, the core parameter "tls_threads_mode" - has to be set, see the Core Cookbook for possible values. - </para> - <para> - IMPORTANT: using this module compiled with newer versions of libssl - (e.g., v1.1+) may require &kamailio; to be started with - <emphasis>--atexit=no</emphasis> command line parameters to avoid - calling C atexit callbacks inside the process ending during - daemonize procedure as well as during shut down, which can lead - to crashes because it destroys and then accesses shared memory. For - example, such case has been reported for Ubuntu 20.04 or RedHat 8. - </para> - <para> - Note: with some particular combination of OS, openssl and mysql-client - libraries, there were reports of random crashes, in such case try to set - the db_mysql module parameter opt_ssl_mode to 1. + Read the "Important Notes" section because it has relevant information + about configuring properly the module for various libssl versions, + components and operating systems. </para> </section> <section id="tls.quick_start"> @@ -134,7 +116,7 @@ request_route { <para> The TLS module needs some special options enabled when compiling Kamailio. These options are enabled by default, however in case - you're using a modified Kamailio version or Makefile, make sure + you are using a modified Kamailio version or Makefile, make sure that you enable -DUSE_TLS and -DTLS_HOOKS (or compile with make TLS_HOOKS=1 which will take care of both options). </para> @@ -188,6 +170,29 @@ request_route { </itemizedlist> The bug reports can be viewed at <ulink url="http://rt.openssl.org/">http://rt.openssl.org/</ulink>. </para> + <para> + Note 1: the tls module must be loaded before any other &kamailio; module + that uses libssl (OpenSSL library). A safe option is to have the tls module + loaded first (be in the first "loadmodule" in &kamailio;.cfg). + </para> + <para> + Note 2: for libssl v3.x, the core parameter "tls_threads_mode" + has to be set, see the Core Cookbook for possible values. + </para> + <para> + Note 3: using this module compiled with newer versions of libssl + (e.g., v1.1+) may require &kamailio; to be started with + <emphasis>--atexit=no</emphasis> command line parameters to avoid + calling C atexit callbacks inside the process ending during + daemonize procedure as well as during shut down, which can lead + to crashes because it destroys and then accesses shared memory. For + example, such case has been reported for Ubuntu 20.04 or RedHat 8. + </para> + <para> + Note 4: with some particular combination of OS, openssl and mysql-client + libraries, there were reports of random crashes, in such case try to set + the db_mysql module parameter opt_ssl_mode to 1. + </para> </section> [View Less]

1 0

git:master:a5b1099c: core: socket info - skip ipv6 link local on interface discovery
by Daniel-Constantin Mierla 16 Oct '24

16 Oct '24

Module: kamailio Branch: master Commit: a5b1099c9061551a0b31db8ef88efb2e376b290c URL: https://github.com/kamailio/kamailio/commit/a5b1099c9061551a0b31db8ef88efb2… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-16T10:49:16+02:00 core: socket info - skip ipv6 link local on interface discovery --- Modified: src/core/socket_info.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

[kamailio/kamailio] Pcv issue 3929 pr (PR #3994)
by Eik Rentzow 16 Oct '24

16 Oct '24

#### 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) - [x] New feature … [View More]

2 17

[kamailio/kamailio] sdpops: cannot parse big SDP (Issue #4000)
by sergey-safarov 15 Oct '24

15 Oct '24

### Description Cannot be parsed `$sdp(body)` when received to big SDP. ### Troubleshooting #### Reproduction To reproduce you can use minimal config like ``` listen=tcp:127.0.0.1:5060 loadmodule "xlog.so" loadmodule "pv.so" loadmodule "sdpops.so" route{ xerr("SDP: TEST $tu\n"); xerr("SDP: $sdp(body)\n"); drop; } ``` And send an INVITE message like in the attached file. In my case, the SDP size is 8710. [invite.txt](https://github.com/user-attachments/files/… [View More]17376561/invite.txt) #### Log Messages ``` ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` 12(143998) DEBUG: <core> [core/ip_addr.c:585]: print_ip(): tcpconn_new: new tcp connection: 2605:84c0:48:4:0:0:0:8 12(143998) DEBUG: <core> [core/tcp_main.c:1246]: tcpconn_new(): on port 42350, type 2, socket 24 12(143998) DEBUG: <core> [core/tcp_main.c:1649]: tcpconn_add(): hashes: 1814:1060:1991, 1 12(143998) DEBUG: <core> [core/io_wait.h:369]: io_watch_add(): processing io_watch_add(0xa15ab0, 24, 2, 0xffffa9cbe2c0) - fd_no=20 12(143998) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xa15ab0, 24, -1, 0x0) fd_no=21 called 12(143998) DEBUG: <core> [core/tcp_main.c:4705]: handle_tcpconn_ev(): sending to child, events 1 12(143998) DEBUG: <core> [core/tcp_main.c:4380]: send2child(): selected tcp worker idx:0 proc:4 pid:143990 for activity on [tcp:[2605:84c0:48:4::8]:5060], 0xffffa9cbe2c0 4(143990) DEBUG: <core> [core/tcp_read.c:1776]: handle_io(): received n=8 con=0xffffa9cbe2c0, fd=4 4(143990) DEBUG: <core> [core/tcp_read.c:1576]: tcp_read_req(): content-length=8710 4(143990) DEBUG: <core> [core/parser/parse_fline.c:247]: parse_first_line(): first line type 1 (request) flags 1 4(143990) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): SIP Request: 4(143990) DEBUG: <core> [core/parser/msg_parser.c:723]: parse_msg(): method: <INVITE> 4(143990) DEBUG: <core> [core/parser/msg_parser.c:725]: parse_msg(): uri: <sip:nga911@[2605:84c0:48:7:9e89:e249:e025:8c89]:11000;ippbx-uuid=SEC11-a46040a-b46040a-1-3GhFlTbDLgyj> 4(143990) DEBUG: <core> [core/parser/msg_parser.c:727]: parse_msg(): version: <SIP/2.0> 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Route] type 9 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Route] type 9 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Via] type 1 4(143990) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK8676587>; state=16 4(143990) DEBUG: <core> [core/parser/parse_via.c:2663]: parse_via(): end of header reached, state=5 4(143990) DEBUG: <core> [core/parser/msg_parser.c:591]: parse_headers(): Via found, flags=2 4(143990) DEBUG: <core> [core/parser/msg_parser.c:593]: parse_headers(): this is the first via 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [To] type 3 4(143990) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1FZy0t0K3Xj9j 4(143990) DEBUG: <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=29 4(143990) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [63]; uri=[sip:3015329632@[2605:97c0:2051:1033:a::1]] 4(143990) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (43)[<sip:3015329632@[2605:97c0:2051:1033:a::1]>], to tag (13)[1FZy0t0K3Xj9j] 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [From] type 4 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Call-ID] type 6 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [CSeq] type 5 4(143990) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <5911> <INVITE> 4(143990) DEBUG: <core> [core/receive.c:397]: _receive_msg(): --- received sip message - request - call-id: [b20ca364-3000-4938-bf40-5c4bf5f0e67c] - cseq: [5911 INVITE] 4(143990) DEBUG: <core> [core/receive.c:263]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 4(143990) DEBUG: <core> [core/receive.c:479]: _receive_msg(): preparing to run routing scripts... 4(143990) ERROR: <script>: SDP: TEST sip:3015329632@[2605:97c0:2051:1033:a::1] 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Contact] type 7 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Content-Type] type 11 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Session-Expires] type 35 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Allow] type 21 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Supported] type 17 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [User-Agent] type 28 4(143990) DEBUG: <core> [core/parser/parse_hname2.c:314]: parse_sip_header_name(): parsed header name [Content-Length] type 12 4(143990) DEBUG: <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=8710 4(143990) DEBUG: <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:692]: extract_sess_version(): oline(44): >o=- 5916726231183296689 3 IN IP4 127.0.0.1 < 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:721]: extract_sess_version(): end 1: >3< 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:572]: extract_mediaip(): located IP address [127.0.0.1] in `o=' field 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:572]: extract_mediaip(): located IP address [192.168.223.25] in `c=' field 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-ufrag:Wg73 a=...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-pwd:2trzRy7dCN...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=fingerprint:sha-25...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=setup:actpass a=m...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=mid:0 a=extmap:1 ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:1 urn:ietf:...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:2 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:3 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:4 urn:ietf:...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=msid:2bf68e42-fd5b...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-mux a=rtcp-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-rsize a=rtpm...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ssrc:954653789 cna...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ssrc:954653789 msi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:572]: extract_mediaip(): located IP address [192.168.223.25] in `c=' field 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-ufrag:Wg73 a=...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-pwd:2trzRy7dCN...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=fingerprint:sha-25...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=setup:actpass a=m...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=mid:1 a=extmap:14...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:14 urn:ietf...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:2 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:13 urn:3gpp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:3 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:5 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:6 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:7 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:8 http://ww...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:4 urn:ietf:...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:10 urn:ietf...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=extmap:11 urn:ietf...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=msid:2bf68e42-fd5b...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-mux a=rtcp-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-rsize a=rtpm...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:106 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:106 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:106 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:107 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:107 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:107 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:102 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:102 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:102 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:102 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:102 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:127 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:127 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:127 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:127 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:127 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:126 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:126 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:126 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:126 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:126 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:125 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:125 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:125 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:125 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:125 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:39 goog-re...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:39 transpo...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:39 ccm fir...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:39 nack a...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:39 nack pl...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:45 goog-re...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:45 transpo...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:45 ccm fir...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:45 nack a...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:45 nack pl...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:98 goog-re...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:98 transpo...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:98 ccm fir...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:98 nack a...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:98 nack pl...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:100 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:100 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:100 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:100 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:100 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:112 goog-r...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:112 transp...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:112 ccm fi...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:112 nack ...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=rtcp-fb:112 nack p...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ssrc:1414828106 cn...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ssrc:1414828106 ms...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp_helpr_funcs.c:572]: extract_mediaip(): located IP address [0.0.0.0] in `c=' field 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-ufrag:sO9Y a=...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=ice-pwd:3YgpASnwan...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=fingerprint:sha-25...' 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=setup:actpass a=m...' ...'43990) DEBUG: <core> [core/parser/sdp/sdp.c:656]: parse_sdp_session(): ignoring unknown type in a= line: `a=mid:2 4(143990) DEBUG: sdpops [sdpops_mod.c:2088]: pv_get_sdp(): param->pvn.u.isname.name.n=0 4(143990) ERROR: <core> [core/pvapi.c:1431]: pv_printf_mode(): no more space for spec value - printed:5 token:8710 buffer:4096 4(143990) ERROR: <core> [core/pvapi.c:1444]: pv_printf_mode(): buffer overflow -- increase the buffer size... 4(143990) DEBUG: <core> [core/receive.c:537]: _receive_msg(): request-route executed in: 1104 usec 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/usr_avp.c:654]: destroy_avp_list(): destroying list (nil) 4(143990) DEBUG: <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 4(143990) DEBUG: <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 4(143990) DEBUG: <core> [core/xavp.c:630]: xavp_destroy_list(): destroying xavp list (nil) 4(143990) DEBUG: <core> [core/receive.c:640]: _receive_msg(): cleaning up 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:941]: free_sdp(): _sdp = 0xffffadfa58e8 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:944]: free_sdp(): sdp = 0xffffadfa6eb0 4(143990) DEBUG: <core> [core/parser/sdp/sdp.c:946]: free_sdp(): session = 0xffffadfa6f60 4(143990) DEBUG: <core> [core/io_wait.h:369]: io_watch_add(): processing io_watch_add(0xa818a0, 4, 2, 0xffffa9cbe2c0) - fd_no=1 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4000 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4000(a)github.com> [View Less]

2 2

git:master:39f20537: modules: readme files regenerated - siputils ... [skip ci]
by Kamailio Dev 15 Oct '24

15 Oct '24

Module: kamailio Branch: master Commit: 39f2053769ea45b1d75a0b73f7f7c14397546b4e URL: https://github.com/kamailio/kamailio/commit/39f2053769ea45b1d75a0b73f7f7c14… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2024-10-15T14:01:10+02:00 modules: readme files regenerated - siputils ... [skip ci] --- Modified: src/modules/siputils/README --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]39f2053769ea45b1d75a0b73f7f7c14… Patch: https://github.com/kamailio/kamailio/commit/39f2053769ea45b1d75a0b73f7f7c14… --- diff --git a/src/modules/siputils/README b/src/modules/siputils/README index f66c7391747..2ab1d707a9a 100644 --- a/src/modules/siputils/README +++ b/src/modules/siputils/README @@ -36,6 +36,8 @@ Bogdan-Andrei Iancu Gabriel Vasile +Eik Rentzow + Copyright �� 2008, 2005, 2003 1&1 Internet AG, FhG Fokus, Voice Sistem SRL __________________________________________________________________ @@ -116,6 +118,7 @@ Gabriel Vasile 5.3. $pcv(genaddr) 5.4. $pcv(orig) 5.5. $pcv(term) + 5.6. $pcv(status) List of Examples @@ -249,6 +252,7 @@ Chapter 1. Admin Guide 5.3. $pcv(genaddr) 5.4. $pcv(orig) 5.5. $pcv(term) + 5.6. $pcv(status) 1. Overview @@ -1089,7 +1093,19 @@ if(is_first_hop("1")) { ... } 4.37. sip_p_charging_vector(flags) Manage the P-Charging-Vector header (RFC7315). The flags can be: 'r' - - remove; 'g' - generate; 'f' - force (remove + generate). + remove; 'g' - generate; 'f' - force (remove + generate). Once a new PCV + has been generated by 'g' or 'f' the PCV cannot be changed again. The + icid-generated-at parameter of a generated PCV will be set to the + sending interface.IP address. + + Return Codes: + * 1 - Nothing was done. + * (2 - intentionally left out) + * 3 - P-Charging-Vector header has been newly generated. + * 4 - P-Charging-Vector header has been deleted. + * 5 - P-Charging-Vector header has been replaced or inserted after + deletion. + * negative - Any error occured during execution. This function can be used from ANY_ROUTE. @@ -1227,6 +1243,7 @@ if (sip_parse_headers()) { 5.3. $pcv(genaddr) 5.4. $pcv(orig) 5.5. $pcv(term) + 5.6. $pcv(status) 5.1. $pcv(all) @@ -1247,3 +1264,16 @@ if (sip_parse_headers()) { 5.5. $pcv(term) term-ioi field (see RFC7315 section 5.6) + +5.6. $pcv(status) + + Returns whether the PCV header was successfully parsed, deleted, newly + generated or other. + * 0 - No P-Charging-Vector header in message. + * 1 - P-Charging-Vector header in message and parsed successfully. + * 2 - P-Charging-Vector is present, but has no valid icid-value + parameter. + * 3 - P-Charging-Vector header has been newly generated or replaced. + * 4 - P-Charging-Vector header has been deleted. + + Negative values indicate an internal error during the parsing process. [View Less]

1 0

git:master:d7c8bc5c: siputils: bug fix for sip_p_charging_vector
by Victor Seva 15 Oct '24

15 Oct '24

Module: kamailio Branch: master Commit: d7c8bc5c58f672004894733d0e6d2a7cb00efe7a URL: https://github.com/kamailio/kamailio/commit/d7c8bc5c58f672004894733d0e6d2a7… Author: Eik Rentzow <rentzow(a)gmx.de> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: 2024-10-15T13:48:35+02:00 siputils: bug fix for sip_p_charging_vector - Bug fix for #3929 and further improvements. - New buffer usage for P-Charging-Vector handling. - Added $pcv(status) pseudo-var. - Added return … [View More]

1 0

git:master:05a30ed5: siputils/doc: updated pcv documentation [skip ci]
by Victor Seva 15 Oct '24

15 Oct '24

Module: kamailio Branch: master Commit: 05a30ed53fc5657a2d86e1c1bdb9277571a8d17e URL: https://github.com/kamailio/kamailio/commit/05a30ed53fc5657a2d86e1c1bdb9277… Author: Eik Rentzow <rentzow(a)gmx.de> Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org> Date: 2024-10-15T13:48:35+02:00 siputils/doc: updated pcv documentation [skip ci] - Updated documentation to reflect the changes to the $pcv pseudo-var and the sip_p_charging_vector() function. --- Modified: src/… [View More]modules/siputils/doc/siputils.xml Modified: src/modules/siputils/doc/siputils_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/05a30ed53fc5657a2d86e1c1bdb9277… Patch: https://github.com/kamailio/kamailio/commit/05a30ed53fc5657a2d86e1c1bdb9277… --- diff --git a/src/modules/siputils/doc/siputils.xml b/src/modules/siputils/doc/siputils.xml index d537da1fb15..08d3d8fb4d9 100644 --- a/src/modules/siputils/doc/siputils.xml +++ b/src/modules/siputils/doc/siputils.xml @@ -95,6 +95,14 @@ </address> </editor> + <editor> + <firstname>Eik</firstname> + <surname>Rentzow</surname> + <address> + <email>rentzow(a)gmx.de</email> + </address> + </editor> + </authorgroup> <copyright> <year>2008</year> diff --git a/src/modules/siputils/doc/siputils_admin.xml b/src/modules/siputils/doc/siputils_admin.xml index 6850f53e9bf..e92472284df 100644 --- a/src/modules/siputils/doc/siputils_admin.xml +++ b/src/modules/siputils/doc/siputils_admin.xml @@ -1279,7 +1279,33 @@ if(is_first_hop("1")) { ... } <para> Manage the P-Charging-Vector header (RFC7315). The flags can be: 'r' - remove; 'g' - generate; 'f' - force (remove + generate). + Once a new PCV has been generated by 'g' or 'f' the PCV cannot be changed again. + The icid-generated-at parameter of a generated PCV will be set to + the sending interface.IP address. </para> + <para> + Return Codes: + </para> + <itemizedlist> + <listitem><para> + <emphasis>1</emphasis> - Nothing was done. + </para></listitem> + <listitem><para> + <emphasis>(2</emphasis> - <emphasis>intentionally left out)</emphasis> + </para></listitem> + <listitem><para> + <emphasis>3</emphasis> - P-Charging-Vector header has been newly generated. + </para></listitem> + <listitem><para> + <emphasis>4</emphasis> - P-Charging-Vector header has been deleted. + </para></listitem> + <listitem><para> + <emphasis>5</emphasis> - P-Charging-Vector header has been replaced or inserted after deletion. + </para></listitem> + <listitem><para> + <emphasis>negative</emphasis> - Any error occured during execution. + </para></listitem> + </itemizedlist> <para> This function can be used from ANY_ROUTE. </para> @@ -1532,6 +1558,32 @@ if (sip_parse_headers()) { term-ioi field (see RFC7315 section 5.6) </para> </section> + <section id="siputils.v.pcv_status"> + <title><varname>$pcv(status)</varname></title> + <para> + Returns whether the PCV header was successfully parsed, deleted, + newly generated or other. + <itemizedlist> + <listitem><para> + <emphasis>0</emphasis> - No P-Charging-Vector header in message. + </para></listitem> + <listitem><para> + <emphasis>1</emphasis> - P-Charging-Vector header in message and parsed successfully. + </para></listitem> + <listitem><para> + <emphasis>2</emphasis> - P-Charging-Vector is present, but has no valid + <emphasis>icid-value</emphasis> parameter. + </para></listitem> + <listitem><para> + <emphasis>3</emphasis> - P-Charging-Vector header has been newly generated or replaced. + </para></listitem> + <listitem><para> + <emphasis>4</emphasis> - P-Charging-Vector header has been deleted. + </para></listitem> + </itemizedlist> + Negative values indicate an internal error during the parsing process. + </para> + </section> </section> </chapter> [View Less]

1 0

git:master:e802f918: core: parser sdp - check field length when extracting the value
by Daniel-Constantin Mierla 11 Oct '24

11 Oct '24

Module: kamailio Branch: master Commit: e802f9187383feb7fdd96c4ded44fda403da4535 URL: https://github.com/kamailio/kamailio/commit/e802f9187383feb7fdd96c4ded44fda… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-11T12:37:08+02:00 core: parser sdp - check field length when extracting the value --- Modified: src/core/parser/sdp/sdp_helpr_funcs.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

git:master:d4bbde61: core: parse sdp - check for body limit on mixed content
by Daniel-Constantin Mierla 11 Oct '24

11 Oct '24

Module: kamailio Branch: master Commit: d4bbde619bbf808edebb31e131b3783ba2a4b34d URL: https://github.com/kamailio/kamailio/commit/d4bbde619bbf808edebb31e131b3783… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-11T12:00:53+02:00 core: parse sdp - check for body limit on mixed content --- Modified: src/core/parser/sdp/sdp.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

git:master:fc481706: core: parser sdp - check for length of sendrecv attribute
by Daniel-Constantin Mierla 11 Oct '24

11 Oct '24

Module: kamailio Branch: master Commit: fc4817064f81ef9a82b1b1468b1b8a4ae352c1f2 URL: https://github.com/kamailio/kamailio/commit/fc4817064f81ef9a82b1b1468b1b8a4… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2024-10-11T11:41:02+02:00 core: parser sdp - check for length of sendrecv attribute --- Modified: src/core/parser/sdp/sdp_helpr_funcs.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

Inconsistencies in SIP Parsing with Embedded tel: URIs and Documentation Issues
by Xenofon Karamanos 11 Oct '24

11 Oct '24

Hi all, I’d like to bring up some development topics related to the SIP parsing logic, specifically when handling sip: with embedded tel URIs scheme. The current behaviour, particularly when user=phone is present, is leading to some inconsistencies and potential confusion, and I believe it might require some refactoring or documentation updates. Current Parsing Behavior: When a tel: URI is embedded in a sip: scheme (e.g., user=phone is present), the parser currently copies the URI parsed … [View More]parameters to sip_params, then splits the user part (like 123;param=value;param2=value2) into user and all the rest tel parameters to params. This behaviour is only triggered when the global phone2tel configuration option is enabled (which is the default). Issues: 1. Inconsistent Handling of URI Parameters There’s no consistency across modules on whether they use sip_params or params to get the URI parameters. While most modules correctly use sip_params, others use params. Normally, this works fine because sip_params and params hold the same data when user=phone is not present or phone2tel is disabled. However, when user=phone is present and phone2tel is enabled, params may be empty, leading to unexpected behavior in modules relying on it. For example, the following modules are using params and many others: * dmqnode.c (line 204)<https://github.com/kamailio/kamailio/blob/ba6ab04e06b0dfd66874749e0cb1225f2…> * notification_peer.c (line 432)<https://github.com/kamailio/kamailio/blob/ba6ab04e06b0dfd66874749e0cb1225f2…> While some may handle the differences between sip_params and params, not all of them do. 2. Unclear Intention of the phone2tel Global Parameter The current parser code is quite old, and it’s unclear what the original intention behind the phone2tel global parameter was. As far as I understand, the sip: scheme can handle tel: URIs, and this is the most widely accepted specification. The role of phone2tel seems to blur the lines between the two schemes, leading to unexpected transformations. Example of Unexpected Behavior: Consider the following header: P-Asserted-Identity: Display <sip:+1234;pname=pval@domain;user=phone>;tag=1234 If we apply the {tobody.user} transformation, the expected output should be the user part of the URI. Based on the RFC, we expected the transformation to return +1234;pname=pval. However, due to the phone2tel global configuration parameter, the parser treats it as a tel: scheme and returns only +1234. This behavior seems to be influenced by how the global parameter forces the parser to handle the URI. Proposal: To resolve these issues, I suggest the following: 1. Refactor Parameter Handling: Introduce a more explicit separation of tel_params and sip_params, and ensure all modules use the correct set of parameters based on the context. This would help enforce consistency across the codebase. 2. Update Documentation: Provide clear documentation regarding the behavior of phone2tel and how it impacts URI parsing. In particular, the transformation documentation should reflect the expected behavior depending on whether the URI is treated as sip: or tel:. 3. Review and Fix Modules: We should audit the modules that currently rely on params and ensure they are using sip_params where appropriate, especially in cases where user=phone could be present. Any guidance or feedback on these points would be greatly appreciated. If you’ve encountered any related bugs or discovered other edge cases, please let me know so we can address them. Best regards, Xenofon [View Less]

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev