Reply to this email directly or view it on GitHub.
Hi, Kamailio server is raising an internal error when recieves an "INVITE" request. I've increased the debug level value in kamailio config file but I cannot get further information. Some times it works with exactly the same configuration so I can't figure out what is wrong.
I attached below the few lines related with the internal error among the huge debug messages:
DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fe070bedb68, callback type 2, id 0 entered
12(13521) DEBUG: acc [acc_logic.c:644]: tmcb_func(): acc callback called for t(0x7fe070bedb68) event type 2, reply code 500
12(13521) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=12 global id=12 T end=0x7fe070bedb68
12(13521) DEBUG: tm [t_reply.c:2217]: reply_received(): DEBUG: reply_received: org. status uas=180, uac[0]=100 local=0 is_invite=1)
12(13521) DEBUG: <core> [mem/f_malloc.c:432]: fm_malloc(): fm_malloc(0x7fe070970000, 1423) called from tm: t_msgbuilder.c: build_local_reparse(369)
12(13521) DEBUG: <core> [mem/f_malloc.c:507]: fm_malloc(): fm_malloc(0x7fe070970000, 1424) returns address 0x7fe070c02c28
12(13521) DEBUG: <core> [mem/f_malloc.c:576]: fm_free(): fm_free(0x7fe070970000, 0x7fe070c02c28), called from tm: t_reply.c: reply_received(2271)
12(13521) DEBUG: <core> [mem/f_malloc.c:595]: fm_free(): fm_free: freeing block alloc'ed from tm: t_msgbuilder.c: build_local_reparse(369)
12(13521) DEBUG: <script>: incoming reply
12(13521) DEBUG: tm [t_reply.c:1311]: t_should_relay_response(): ->>>>>>>>> T_code=180, new_code=500
12(13521) DEBUG: tm [t_reply.c:1829]: relay_reply(): DEBUG: relay_reply: branch=0, save=1, relay=-1 icode=0
( ... )
DEBUG: <core> [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status):
12(13521) DEBUG: <core> [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0>
12(13521) DEBUG: <core> [parser/msg_parser.c:637]: parse_msg(): status: <500>
12(13521) DEBUG: <core> [parser/msg_parser.c:639]: parse_msg(): reason: <Internal Server Error>
—
Reply to this email directly or view it on GitHub.