Hello James,
thanks for the follow up.
If you found a mitigation for the issue, please create a pull-request on our github tracker for it. Then it can be better analysed and also merged after review.
Cheers,
Henning
-----Original Message----- From: James Morrison via sr-users sr-users@lists.kamailio.org Sent: Mittwoch, 26. Februar 2025 08:02 To: sr-users@lists.kamailio.org Cc: James Morrison stinktohighheaven@gmail.com Subject: [SR-Users] Re: REG_MAR_REPLY never get executed
Finally I found the issue. In ims_auth module > cxdx_mar.c > async_cdp_callback function, within the done label, there is a call to t_continue function that should find the transaction and execute the callback for ims_www_challenge (REG_MAR_REPLY route), tmb.t_continue(data-
tindex, data->tlabel, data->act);
however because the transaction is already put on wait by calling put_on_wait(trans); inside _reply_light function in tm module, the transaction is in terminated phase and that's the reason why the callback is never executed. Strangely, for SAR requests, instead of t_continue, t_continue_skip_timer function is called t_continue_skip_timer: tmb.t_continue_skip_timer(data->tindex, data->tlabel, data->act);
That effectively ignores the transaction state, and calls the respective callback function. I checked the newer version and didn't find any change in the function calls.
I used t_continue_skip_timer for MAR request and everything worked as expected. Can I use the t_continue_skip_timer instead of t_continue for MAR requests too without any concern? Is there any side effect? what about unreleased transactions and memory leak? __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- sr- users@lists.kamailio.org To unsubscribe send an email to sr-users- leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender!