sr-dev December 2021

sr-dev@lists.kamailio.org

11 participants
270 discussions

[kamailio/kamailio] Feature request: Increase number of "custom fields" in sipcapture-module (#1278)

by mihovilkolaric

The module sipcapture provides the modparams "custom_field1_header" to "custom_field3_header", to store the content of up to three arbitrary header fields as separate columns in the database. They can be used as all other "standard" columns in homer. However I found out that searching/filtering for even more (standardized, as well as private) header fields would be very helpful (I identified about ten interesting additional headers, but the number is constantly increasing ;-) ). Could you thus please increase the number of custom fields? (I suppose the most flexible solution could be something as the db_extra in the acc-module, which is not fixed to certain columns (regarding number of columns, as well as their names) (see https://www.kamailio.org/docs/modules/5.0.x/modules/acc.html#acc.p.db_extra ).) -- 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/1278

2 years, 10 months

[kamailio/kamailio] Diameter AVP handling from kamailio.cfg (#922)

by miricz

Below feature were discussed with Carsten Bock Currently Diameter AVP values and especially Experimental Result Code is not available from the kamailio.cfg Therefore I would like to request such kind of feature. I would like to use it mainly on Cx interface for Server-Assignment-Answer (SAA), Location-Info-Answer (LIA), Multimedia-Auth-Answer (MAA), Push-Profile-Answer (PPA) It should be implemented such a way like in the ims_charging module. Thank you very much in advance! _Cheers, Zoltan_ -- 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/922

2 years, 10 months

[kamailio] add socket activation support (#293)

by zabbal

Having (optional) support for socket activation in Kamailio would bring several benefits: * Security: systemd can listen on privileged ports or socket paths and start Kamailio with privileges already dropped. * Major upgrades or reconfigurations of Kamailio requiring a full restart are possible without having the listening socket(s) ever go away. * Any service dependent on Kamailio doesn't have to wait for it to finish starting (or start at all). --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/293

2 years, 10 months

[kamailio/kamailio] pv needed to get access to X509v3 Subject Alternative Names of peer's SSL certificate (#707)

by juha-h

A sip proxy may serve many domains listed in its SSL certificate X509v3 Subject Alternative Name field. In order to find out if a peer sip proxy is serving a particular domain, access would be needed in config file to this list of domains. --- 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/707

2 years, 10 months

[kamailio/kamailio] dispatcher: Fix handling of inactive destination for alg 13 (PR #2964)

by mtryfoss

#### 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 - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Alg 13 did try to distribute calls to inactive destinations. If the highest priority destination is inactive, hash is not updated and the xavp is not set. This is resulting in failover mechanism not working at all for the given call. When the hash variable is not updated, it makes alg 13 behave like round robin if the scenario above occurs. If you got two destinations and the highest priority is out of service, 50% of the calls will fail. Now I tried a more simple approach updating hash with the first entry of the sorted list. Also fixed a typo in a variable name. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2964 -- Commit Summary -- * dispatcher: Fix handling of inactive destination for alg 13 -- File Changes -- M src/modules/dispatcher/dispatch.c (21) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2964.patch https://github.com/kamailio/kamailio/pull/2964.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/2964

2 years, 10 months

[kamailio/kamailio] cannot use ring_insert_callid when defined log_prefix (Issue #2989)

by sergey-safarov

### Description I want to convert 183 messages to 180 using the `ring_insert_callid` function. This does not work when used `log_prefix`. Generated error like > siputils [ring.c:300]: conv183(): 183 message got parsed too far! #### Reproduction you can start kamailio using config file like ``` log_prefix="{$mt $hdr(CSeq) $ci} " listen=udp:eth0:5060 loadmodule "xlog.so" loadmodule "pv.so" loadmodule "sl.so" loadmodule "siputils.so" modparam("siputils", "ring_timeout", 30) request_route { xlog("L_ERR", "Test1: $rc\n"); if (is_request()) { ring_insert_callid(); } $du = "sip:192.168.0.1;tranport=udp"; forward(); } ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2989 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2989(a)github.com>

2 years, 10 months

[kamailio/kamailio] NATS: add new function `nats_publish()` (PR #2978)

by Emmanuel Schmidbauer

#### 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 Adds Publish function to NATS module. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2978 -- Commit Summary -- * NATS: add new function `nats_publish()` -- File Changes -- M src/modules/nats/Makefile (2) A src/modules/nats/defs.h (40) M src/modules/nats/doc/nats_admin.xml (23) M src/modules/nats/nats_mod.c (44) M src/modules/nats/nats_mod.h (17) A src/modules/nats/nats_pub.c (157) A src/modules/nats/nats_pub.h (46) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2978.patch https://github.com/kamailio/kamailio/pull/2978.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2978 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/2978(a)github.com>

2 years, 10 months

[kamailio/kamailio] core: Add virtual flag to listen config to ignore inactive ip addresses (PR #2985)

by rhys-hanrahan

#### 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 #2984 #### Description A new option to "listen" has been added called "virtual". This sets a flag on the listening socket to modify the behaviour of grep_sock_info. When this flag is set, grep_sock_info will only consider the listening IP a match if the IP is found in the system's current list of local IP addresses. If the IP is not currently local, then the matching IP is ignored. If the virtual flag is not set on the socket then existing behaviour used instead. This feature is intended for scenarios where you have two Kamailio nodes in active/active setup, with virtual IPs, where you need to be able to listen on a virtual IP but it may not always be active locally. With this flag applied to a `listen=` socket, Kamailio will only consider traffic destined to this IP local, when the IP is actually active on the system, and other times the match is ignored. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2985 -- Commit Summary -- * core: listen can now have a "virtual" flag to check for nonlocal floating IPs. * etc: kamailio.cfg - added example use of listen's new virtual flag. * core: Added virtual flag to output of core.sockets_list * corex: Added virtual flag to output of "corex.list_sockets" * ims_ipsec_pcscf: Added virtual flag to output of sockets list. -- File Changes -- M etc/kamailio.cfg (2) M src/core/cfg.lex (2) M src/core/cfg.y (83) M src/core/core_cmd.c (10) M src/core/ip_addr.h (1) M src/core/socket_info.c (85) M src/modules/corex/corex_rpc.c (5) M src/modules/ims_ipsec_pcscf/ims_ipsec_pcscf_mod.c (8) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2985.patch https://github.com/kamailio/kamailio/pull/2985.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2985 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/2985(a)github.com>

2 years, 10 months

[kamailio/kamailio] tcpclose event_routes issue (PR #2980)

by vlitvinov

#### 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) - [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) - [ ] New feature (non-breaking change which adds new functionality) - [x] 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  We faced an issue that tcp:close (timeout and reset) event routes don't execute in rare cases. Debugging and testing show that in the case when a connection is marked as BAD or write timeout etc our event routes don't execute. I found that executing event routes is in the read function only. So in case when a connection is destroyed triggered by other reasons we don't have a notification about this. I propose to do this in main file every time when we destroy connections. But in this case, we don't have I reason to destroy (timeout reset or EOF). In our lab with these changes issue is gone. But sure this is just a concept. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2980 -- Commit Summary -- * tcpclose event_routes issue -- File Changes -- M src/core/tcp_main.c (26) M src/core/tcp_read.c (26) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2980.patch https://github.com/kamailio/kamailio/pull/2980.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2980 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/2980(a)github.com>

2 years, 10 months

git:master:c4e462fa: core: parser sdp - print hdr name by length on error in get_sdp_hdr_field()

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: c4e462fa6bda38ac6fd814ce8d98ea030d4049b9 URL: https://github.com/kamailio/kamailio/commit/c4e462fa6bda38ac6fd814ce8d98ea0… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2021-12-28T20:27:43+01:00 core: parser sdp - print hdr name by length on error in get_sdp_hdr_field() --- Modified: src/core/parser/sdp/sdp_helpr_funcs.c --- Diff: https://github.com/kamailio/kamailio/commit/c4e462fa6bda38ac6fd814ce8d98ea0… Patch: https://github.com/kamailio/kamailio/commit/c4e462fa6bda38ac6fd814ce8d98ea0… --- diff --git a/src/core/parser/sdp/sdp_helpr_funcs.c b/src/core/parser/sdp/sdp_helpr_funcs.c index c62a347ddc..9b7a442e79 100644 --- a/src/core/parser/sdp/sdp_helpr_funcs.c +++ b/src/core/parser/sdp/sdp_helpr_funcs.c @@ -757,7 +757,8 @@ char* get_sdp_hdr_field(char* buf, char* end, struct hdr_field* hdr) if (match){ match++; }else { - LM_ERR("bad body for <%s>(%d)\n", hdr->name.s, hdr->type); + LM_ERR("bad body for <%.*s>(%d)\n", hdr->name.len, hdr->name.s, + hdr->type); tmp=end; goto error; }

2 years, 11 months

← Newer
1
...
8
9
10
11
12
13
14
...
27
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev December 2021