hello all
we have seen some cores on the same server like this one
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f02297a0537 in __GI_abort () at abort.c:79
#2 0x55caeb47dc3d in qm_debug_check_frag (qm=0x7f00aba53000,
f=0x7f019c02c760, file=0x7f0222
### 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)`
- `secsipid_build_identity_
hello,
i have tried with a friend recently, im unsure if it's the proper place to talk
about it, but it's one of the rare forums with a category focused about
SIP/VoIP.
here it is :
gigaset c530ip, i guess it's among the most solt model from the last decade,
from that manufacturer.
on frenchy
@nchaigne commented on this pull request.
On src/modules/http_client/doc/http_client_admin.xml:
Typos : "paramters", "cirtificates"
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3619#pullrequestreview-1701397662
You are receiving this because
The behaviour is actually documented:
"The HTTP connection will be defined using default values in modparam's **above
the definition of the httpcon** in the configuration file."
But this can easily be overlooked. I also had trouble understanding why my
configuration did not work initially.
It's
- Inform that the order of the parameters is important when httpcon is loaded
first
Pre-Submission Checklist