UA(192.168.0.11) received 183, find Record-Route(36.140.122.12)
then send ACK to 36.140.122.12(Kamialio public ip) not 192.168.0.2(kamailio internal ip), so Kamailio can't receive ACK.
this is my config，192.168.0.11 -> Kamailio -> Other SBC(public ip)
function ksr_request_route()
if KSR.is_INVITE() then
KSR.rr.record_route();
KSR.nathelper.fix_nated_contact()
end
end
This question has been bothering me for a long time, help me
[cid:d1ec74be-1c33-406e-80d5-68663d1cd21f]
[cid:bda00d0d-e6e6-4dc9-9462-141ad42b09b8]
Hi All,
I use kamailio In front of Asterisk and kamailio needs to refresh registrations periodically towards Asterisk to ensure the availability of users from Asterisk side.
I use uac module and call uac_req_send() for sending REGISTER requests.
I set $uac_req(evroute)=1
The event_route[uac:reply] is called fine, but in kamailio logs I see the next lines:
CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring
After some time, kamailio has crashed.
CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) – ignoring
CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34
ALERT: <core> [main.c:774]: handle_sigs(): child process 1407950 exited by a signal 6
Any idea that is it a bug or I use something wrong in config?
Thanks in advance!
Péter Barabás
*Hello,*
I am running kamailio-5.3.4 on one of my setup and I intend to use the
crypto module in the same.
I wanted to understand the following details when the module is used:
I understand it uses the AES algorithm, is that correct?
Does it use AES 128, 192 or 256 bit algorithms?
Does it use CBC or ECB mode for AES?
The 5.3 version does not have an parameter for init-vector, so does
kamailio use any init vector internally in this case?
When i compared the encrypted text that kamailio produces and the ones
available online, they were producing different outputs even when same
shared secret was used. Hence asking for more clarification
PS: Upgrading kamailio is my very last option as this is one af an old
setup which only needs this feature without much changes.
Thanks for any valuable response.
*-- Jayesh*
Hello,
In reference to this issue https://github.com/kamailio/kamailio/issues/3081 I've been advised to set http_reply_parse to "no" which I did (and it is the default value anyways).
# grep http_reply_parse /etc/kamailio/kamailio.cfg
http_reply_parse=no
After setting this, I still get these parsing errors:
{ "idx": 23, "pid": 102, "level": "ERROR", "module": "core", "file": "core/parser/msg_parser.c", "line": 748, "function": "parse_msg", "logprefix": "", "message": "ERROR: parse_msg: message=<HTTP/1.1 100 Continue\r\n\r\nHTTP/1.1 200 OK\r\ndate: Wed, 26 Jul 2023 16:43:19 GMT\r\ncontent-length: 224\r\ncontent-type: text/plain; charset=utf-8\r\n\r\n{\"result\": {\"ruri\":\"\",\"fU\":\"\",\"tU\":\"\",\"privacy\":\"\",\"identity\":\"\",\"error\":{\"code\":0,\"message\":\"\"},\"mb\":\"\",\"Headers\":null,\"encrypted\":\"\",\"sipsScheme\":\"\",\"attestation\":\"\",\"authUser\":\"\",\"authPassword\":\"\",\"disableStirShaken\":\"\"}}>" }
Is there anything that I am missing beyond setting that parameter?
Thank you,
Alexandru
