Module: kamailio
Branch: 5.8
Commit: 1928af8f90ebf02f610c0904bc3d24a00aaedb81
URL:
https://github.com/kamailio/kamailio/commit/1928af8f90ebf02f610c0904bc3d24a00aaedb81
Author: Juha Heinanen
Committer: Juha Heinanen
Date: 2024-03-12T07:54:50+02:00
core: set null-terminated char for modparam (ba
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/3350#issuecomment-1989878796
You are receiving this because yo
Closed #3682 as not planned.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3682#event-12082289531
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Dev
Module: kamailio
Branch: 5.8
Commit: c229e11ba39da40cadaecd1b6aa3ae153e014bb1
URL:
https://github.com/kamailio/kamailio/commit/c229e11ba39da40cadaecd1b6aa3ae153e014bb1
Author: Sergey Safarov
Committer: Sergey Safarov
Date: 2024-03-12T04:22:53+02:00
pkg/kamailio/obs: packaged README.file_out
(
route[REGFWD] {
xlog("L_INFO", "---");
$uac_req(method) = "REGISTER";
$uac_req(ruri) = "sip:" + $avp(domain) + ":" + 'PBX_UDP_PORT';
$uac_req(furi) = "sip:" + $avp(extension) + "@" + $avp(domain);
$uac_req(turi) = "si
Module: kamailio
Branch: master
Commit: 4dc37aee853bbcf9d7fdb96245b76aaa8dfa2930
URL:
https://github.com/kamailio/kamailio/commit/4dc37aee853bbcf9d7fdb96245b76aaa8dfa2930
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-03-11T20:56:37+01:00
core: set null-termina
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
>From description I understand that only Via is removed for REGISTER (and
>PUBLISH). The Contact stays the same, in that case Path still has to be used
>in order to get the traffic back to topos-instance. Also, the incoming Path
>headers are kept. Is it right?
--
Reply to this email directly
Not sure I got exactly the kind of function you look for. One that still takes
the Identity header value and verifies only the signature, with the key
provided as parameter? Or the key has to be takes from the Identity header
parameter? Maybe you can give the function prototype (or the list of p
### 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 par
- more clear documentation for the new ds_is_from_list flags