Hi Daniel,
due to other internal patches, the line number are a bit different. The issue seems located at the point where the patch was applied:
--- a/modules/tm/t_reply.c +++ b/modules/tm/t_reply.c @@ -1965,8 +1965,10 @@ enum rps relay_reply( struct cell *t, st if (SEND_PR_BUFFER( uas_rb, buf, res_len ) >= 0){ if (unlikely(!totag_retr && has_tran_tmcbs(t, TMCB_RESPONSE_OUT))){ LOCK_REPLIES( t ); - run_trans_callbacks_with_buf( TMCB_RESPONSE_OUT, uas_rb, t->uas.request, - relayed_msg, relayed_code); + if(relayed_msg->REPLY_STATUS==uas_rb->activ_type) { + run_trans_callbacks_with_buf( TMCB_RESPONSE_OUT, uas_rb, t->uas.request, + relayed_msg, relayed_code); + } UNLOCK_REPLIES( t ); } if (unlikely(has_tran_tmcbs(t, TMCB_RESPONSE_SENT))){
Thanks Marco
On 11/10/2017 08:41 AM, Daniel-Constantin Mierla wrote:
Hello,
can you run list command in gdb to see the code? Because I am not sure what is exactly at that line in your version with the patch.
Cheers, Daniel
On 09.11.17 18:10, Marco Capetta wrote:
I applied the patch but kamailio crashes with the following error:
(gdb) bt full #0 0x00007f8af1e9b9ae in relay_reply (t=t@entry=0x7f8a29c05868, p_msg=p_msg@entry=0xffffffffffffffff, branch=branch@entry=0, msg_status=<optimized out>, cancel_data=cancel_data@entry=0x7ffd92443570, do_put_on_wait=do_put_on_wait@entry=0) at t_reply.c:1968 relay = 0 [...]
-- Daniel-Constantin Mierla www.twitter.com/miconda --www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 13-15, 2017, in Berlin -www.asipto.com Kamailio World Conference -www.kamailioworld.com
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users