Module: kamailio
Branch: master
Commit: b85471a7c28324fcb890961a1ad67810bfbb8ac4
URL:
https://github.com/kamailio/kamailio/commit/b85471a7c28324fcb890961a1ad67810bfbb8ac4
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-02-02T08:56:52+01:00
Makefile.defs: version
Module: kamailio
Branch: master
Commit: 8c5e97589fc0fed121ee6e8ca4adbf9ec63ad2eb
URL:
https://github.com/kamailio/kamailio/commit/8c5e97589fc0fed121ee6e8ca4adbf9ec63ad2eb
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-02-02T08:55:38+01:00
Makefile.defs: version
Module: kamailio
Branch: master
Commit: 03e60c809a0ac26b402bdf1154d6ec7b0476f26a
URL:
https://github.com/kamailio/kamailio/commit/03e60c809a0ac26b402bdf1154d6ec7b0476f26a
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-02-02T07:35:48+01:00
Makefile.groups: added
This issue is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3234#issuecomment-1922685515
You are receiving this because yo
### Description
partition is now a reserved word in MariaDB 10.
the column name is correctly quoted with native libmysqlclient/libmariadb so
works
the column name is not quoted with unixodbc+(libmyodbc8|libmaodbc) and so fails
### Troubleshooting
try unquoted insert
-- fails unixodbc+libmaodbc
Module: kamailio
Branch: master
Commit: 40b735216c610cae2da5b0758af31b1d3ade4731
URL:
https://github.com/kamailio/kamailio/commit/40b735216c610cae2da5b0758af31b1d3ade4731
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-02-01T21:38:25+01:00
rtpengine: optional pi
Module: kamailio
Branch: master
Commit: 49bc5b266dad33e418e8895e9ed7ead46e254016
URL:
https://github.com/kamailio/kamailio/commit/49bc5b266dad33e418e8895e9ed7ead46e254016
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-02-01T21:38:25+01:00
rtpengine: new modpara
Adding a few more details, previous comment was done on mobile, typing there on
the web form is not the easiest.
I think that log_file would be a candidate for the name of a module that writes
all the logs in a file, similar to log_custom that sends all the log to an udp
target. Then having a m
Module: kamailio
Branch: master
Commit: 4c144ac1ad40008b5bd9396aa18d7630145b4c4c
URL:
https://github.com/kamailio/kamailio/commit/4c144ac1ad40008b5bd9396aa18d7630145b4c4c
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2024-02-01T19:22:53Z
file_out: small doc adaptions
---
Mod
Module: kamailio
Branch: master
Commit: df3d1e5cb80b7a6ac6ce93b582352aaa8e6fd369
URL:
https://github.com/kamailio/kamailio/commit/df3d1e5cb80b7a6ac6ce93b582352aaa8e6fd369
Author: Xenofon Karamanos
Committer: Henning Westerholt
Date: 2024-02-01T19:41:22Z
file_out: use name instead of index for
Module: kamailio
Branch: master
Commit: 6478ac00e9bf1180092010b0df4656630d4550c2
URL:
https://github.com/kamailio/kamailio/commit/6478ac00e9bf1180092010b0df4656630d4550c2
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2024-02-01T19:33:38Z
file_out: adjust syntax of examples to
Module: kamailio
Branch: master
Commit: a6892009361ceff1475b568a2317b5d8a7c889cc
URL:
https://github.com/kamailio/kamailio/commit/a6892009361ceff1475b568a2317b5d8a7c889cc
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2024-02-01T19:25:12Z
file_out: fix error in XML include for
Merged it like this for now as the freeze is coming up
* smaller refactorings will be done afterwards (use string in function for
names with internal matching, make worker sleep also configurable
* a round of tests has been done, but it will be certainly tested more in the
next days
--
Reply to
Module: kamailio
Branch: master
Commit: dd5c9a5204eb946e731550a0ee7f3046c7065515
URL:
https://github.com/kamailio/kamailio/commit/dd5c9a5204eb946e731550a0ee7f3046c7065515
Author: Xenofon Karamanos
Committer: GitHub
Date: 2024-02-01T18:15:17+01:00
file_out: Module to log custom strings to files
Merged #3741 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741#event-11673226574
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Developm
How about `f_print` or `file_print`?
In the end, it doesn't really matter, but `file_out` doesn't seem to be very
intuitive ... or maybe that's just me :)
Thanks for contributing this, it is a nice addition!
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamail
Ok, keep it like this then, no special preference from our side. :-)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741#issuecomment-1921712262
You are receiving this because you are subscribed to this thread.
Message ID:
If performance is crucial, we can keep the index as a first parameter for the
`file_out` function and we can change the definition of the `file_out` modparam:
```
modparam("file_out", "base_filename", "0:accounting")
modparam("file_out", "base_filename", "1:missed_calls")
```
Populate slot `0` wit
I would not recommend using the word `log` in the name. It has nothing to do
wit the internal logging frawork. The module is purely writings text to a file.
The core module has basic similar functionality, those functions are not
related to logging and this module should also keep away from brin
Thanks for the feedback as well @ovidiusas. The name file_log sounds also good.
Regarding the use of an actual file name, its a good idea and can be probably
done without performance impact with a fixup function. We will look into that.
I would merge the module manually in some hours (to do the
Sounds like the code path that is causing the error is not being run.
Is that on Debian 12?
Try with the following tls.cfg:
```
[server:default]
method = TLSv1.2+
verify_certificate = yes
require_certificate = yes
private_key = /etc/ssl/private/dsiprouter-key.pem
certificate = /etc/ssl/private
@miconda Thanks for the feedback, fixed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741#issuecomment-1921623583
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kama
@xkaraman pushed 2 commits.
ae4752366d5a558c54461ca86cdabbd3c3e13f14 file_out: Add copyright
7d08b018e5e54b998366b704c1d82f6c1ce643e4 file_out: Refactor to mach naming
conventions
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/3741/files/fb03cdc2d266e4b128b197c4261a4922c97d80
Hmmm ... not reproducible here
kamailio version 5.7.4 (x86_64/linux)
kamcmd tls.reload leads to
```
7(126739) INFO: tls [tls_domain.c:371]: ksr_tls_fill_missing(): TLSc:
ca_path='(null)'
7(126739) INFO: tls [tls_domain.c:378]: ksr_tls_fill_missing(): TLSc:
crl='(null)'
7(126739) INFO: tls [t
How about `f_log` or `file_log` instead of `file_out`?
Also, the first parameter of `file_out` function seems to be an index to the
defined filenames. If the order of the `file_out` modparams is changed, then
the script has to be updated. It would be more intuitive to use the actual
filename ins
Thanks for the feedback, the copyright will be added uniformly, and also extend
the prefix, sure. Then lets keep the file_out name for now until somebody else
has a better idea.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741#issuecomment-192
I have no suggesting about a better name right now, I can think about. Probably
`log_` prefix is not suitable, because it does not divert all the log messages
like log_custom.
Otherwise upon a quick look, some files are missing the copyright at the top.
And I would suggest to add prefix (rename
@space88man I shared a link below with an example key/cert pair from an
ephemeral VM.
I can provide access to that VM for testing if needed as well.
https://drive.google.com/drive/folders/1255E1iSUKaKbElwDsC8o3qsh6YTN5jrJ?usp=drive_link
--
Reply to this email directly or view it on GitHub:
ht
> I of course also appreciate the work @space88man put here into that. Maybe I
> am wrong, but right now the db_* modules in stable branches are not using the
> pthread approach. My question was about if its really necessary to apply this
> pthread logic to the DB modules. If the db_* modules ar
@miconda any suggestions regarding the name? Maybe going for the existing
"log_" prefix, like log_file, log_file_out or similar?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3741#issuecomment-1921450975
You are receiving this because you are sub