Problem still exists in 5.8.2. Can this issue be re-opened?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3851#issuecomment-2173430421
You are receiving this because you are subscribed to this thread.
Message ID:
Is there any indication if this is a functional problem, or just a case of
logging that should be reduced - I'm trying to gauge if I should hold off
before upgrading.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3851#issuecomment-2118838919
### Description
Calling functions from the `dialplan` module in 5.8 (`dp_translate()`,
`dp_match()`) results in the following line being logged:
```
WARNING: [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called
from dialplan: dp_db.c: pcre2_free(206)
```
Is this a functional
Issue auto marked marked as "stale", but the provided fix works.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3784#issuecomment-2101844186
You are receiving this because you are subscribed to this thread.
Message ID:
My guess is that md5 would be sufficient. It's still odd feeling that CRC32
wasn't getting sufficient randomization against the actual Call-Ids I was
receiving. Anything requiring OpenSSL and actual cryptographic-quality
algorithms seems overkill, though.
--
Reply to this email directly or
I don't think macro replacement works inside of strings. I believe you should
be able to achieve what you want using
[#!defexp](https://github.com/kamailio/kamailio-wiki/blob/main/docs/cookbooks/5.7.x/core.md#defexp),
as the examples in the core documentation are nearly identical to your
Confirmed that this is working. Will it get ported to 5.8 or will it be the
next `major.minor` release?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3784#issuecomment-2022908007
You are receiving this because you are subscribed to this
Is it possible to use the same logic for downloading (and caching) of the key
as the `secsipid_check` function:
> If the keyPath parameter is empty, the function is downloading the key using
> the URL from "info" parameter of the sIdentity, using the value of "timeout"
> parameter to limit the
Ah - I see the function takes three arguments. The third argument only has "A"
as an allowed value?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3784#issuecomment-2009659271
You are receiving this because you are subscribed to this thread.
Sorry for the delayed reply - I had a few small issues compiling, but kamailio
then fails to start with secsipid_verify() not found:
During startup:
```
0(1) ERROR: [core/cfg.y:3870]: yyparse(): cfg. parser: failed to find
command secsipid_verify (params 2)
```
Versions:
```
### Description
Carrierroute's CRC32 algorithm over call_id tends to produce poor call
distribution under real world examples. Having 4 records for a given
carrier/domain combo (assuming no flags, mask, or scan_prefix) and a
probability of `0.25` using a hash source of `call_id` I observed
I'll give the JWT module a peek. Lack of caching is maybe an issue (but can be
'farmed out' to something else for caching purposes).
Perhaps this would be better considered as an error with the existing
`secsipid_check()` function in that it will only validate `shaken` passport
types, and the
### Description
Currently secsipid has a method to sign arbitrary (json) data
(`secsipid_sign`), however it has no converse method to check the signature.
Currently, an attempt to check a `div` signature for example will yield a
`-303` error (`SIPHdrInfo`). Rather than trying to have full
I'll try to get around to this. It was pretty simple to test if memory serves.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3064#issuecomment-1867686329
You are receiving this because you are subscribed to this thread.
Message ID:
### Description
I came across the following while trying to serialize SQL data to xavp
(`sql_xquery()`) and then serializing the result to htable using
`xavp_params_implode()`. One of the data columns has a type of `BIGINT`. The
resulting string had neither the key nor value.
I recognize
Thank you. I think I'll be able to test tomorrow.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3620#issuecomment-1786078674
You are receiving this because you are subscribed to this thread.
Message ID:
### Description
Add a function `secsipid_sign_privkey(sheaders, spaypload, keyData)` that
accepts a pseudovariable with the PEM data analagous to the difference between
the following functions:
- `secsipid_build_identity(origTN, destTN, attest, origID, x5u, keyPath)`
-
This appears to be occurring in 5.6, 5.7, and devel- branch as well. Simple
example config:
```
#!KAMAILIO
loadmodule "pv"
loadmodule "tm"
loadmodule "xlog"
route {
xinfo("[$rm $ci-$cs] Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n");
t_send_reply("404", "Not Found");
exit;
}
Thank you. I'll try to create a testing situation around this.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3318#issuecomment-1372373543
You are receiving this because you are subscribed to this thread.
Message ID:
I'm calling them separately because there's no function to call them together.
;)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3318#issuecomment-1366809182
You are receiving this because you are subscribed to this thread.
Message ID:
### Description
The permissions module has two reload RPC commands, `permissions.addressReload`
which reloads the `address` table, and `permissions.trustedReload`, which
reloads the `trusted` table.
The module parameter `reload_delta` exists to prevent concurrent reloading of a
single table:
> The Alpine automatic build does not work now. Required refactoring after
> Docker Hub closed the CI-builds on the free accounts. A thing required to
> write an automatic Alpine build using GitHub actions.
>
> Let's write alpine automatic builds during the next mouth. If this does not
>
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
### Description
Issues building `PYTHON` module on Alpine Linux due to [sunsetting of
Python2](https://www.python.org/doc/sunset-python-2/). The `python2` package
(apk) has been removed from the current Alpine linux. The APKBUILD file in the
current Kamailio branches includes build settings
It's the same result with a double quoted "1".
`if (uac_auth("1")) {`
The error message looks like it can't find the command with this signature.
```
0(24044) ERROR: [core/cfg.y:3536]: yyparse(): cfg. parser: failed to
find command uac_auth (params 1)
0(24044) CRITICAL: [core/cfg.y:3677]:
### Description
According to the documentation for the UAC module, the `uac_reg` command can
accept an optional argument to use the pre-calculated HA1 format:
```
4.7. uac_auth([mode])
This function can be called only from failure route and will build the
authentication response header and
Config, Log, and SIP messaging attached. The config file is simplified as much
as I could for the purpose of reproducing this issue.
[kamailio_5.4.3.log](https://github.com/kamailio/kamailio/files/5978808/kamailio_5.4.3.log)
### Description
CSeq fails to increment on CANCEL in v5.4.3. Possible regression of problem
fixed in issue #918. Not reproducible in v5.3.8, nor in v5.5 nightly debian
package.
_Note: I have another (production) system running v.5.4.1 that does not
exhibit this behavior, so it's possible
Closed #2517.
--
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/2517#event-3895127332___
Kamailio (SER) - Development Mailing List
Thank you for the clarification. I think that's enough to close the ticket.
It's not "as *I* expect," but it's easier to change my expectations to the
existing behavior than to expect the world to revolve around me.
--
You are receiving this because you are subscribed to this thread.
Reply
Is my problem with the use of the negation operator? Or should I be calling
the function in the condition instead of assigning to a variable and then
evaluating the variable?
```
$vn(alias_found) = alias_db_lookup("DbAliases");
if ( !$vn(alias_found) ) {
## I would expect this to execute
### Description
alias_db_lookup is returning `-1` if result is not found. The documentation
says "The function returns TRUE if R-URI is alias and it was replaced by user's
SIP uri." The implication is that it should return FALSE if that is not the
case. Sample code:
```
$vn(init_ruri) =
Pre-Submission Checklist
!-- Go over all points below, and after creating the PR, tick all the
checkboxes that apply --
!-- All points should be verified, otherwise, read the CONTRIBUTING
guidelines from above--
!-- If youre unsure about any of these, dont hesitate to ask on
sr-dev mailing
### Description
Use of acronym "HF" (header field) in the REGISTRAR is a bit obscure. It
probably makes sense to experienced Kamailio admins, but it's not immediately
apparent to beginners. Since there is little gained by using the acronym in
this document it would be more friendly to use
**tl;dr:** This is a minor bug report for Kamailio, and regarding access to
SQL Azure, I'd be happy to finance an Azure SQL database for testing if desired.
The issue is about _assumed_ behavior within the DB_UNIXODBC module.
The behavior in Azure SQL that is atypical, because trying to
I'm able to connect, the bug report here is more about the errors being written
to the kamailio log.
I'm also experiencing hangs, and hadn't considered that this could be from the
ODBC connection, so I'll look into this.
You indicate that you're working around this by proxying your query
### Description
Using DB_UNIXODBC with an Azure SQL database works, however when starting
Kamailio, errors are shown for :
```
26(80403) ERROR: db_unixodbc [connection.c:219]: db_unixodbc_extract_error():
unixodbc:SQLDriverConnect=01000:3:5701:[Microsoft][ODBC Driver 17 for SQL
Server][SQL
37 matches
Mail list logo