[OpenSIPS-Devel] [ opensips-Patches-2789126 ] extend tm uac functions to support tmcb release function
SourceForge.net
noreply at sourceforge.net
Fri May 8 19:17:54 CEST 2009
Patches item #2789126, was opened at 2009-05-08 13:17
Message generated for change (Tracker Item Submitted) made by john_riordan
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=2789126&group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: 1.5.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: John Riordan (john_riordan)
Assigned to: Nobody/Anonymous (nobody)
Summary: extend tm uac functions to support tmcb release function
Initial Comment:
Currently there does not appear to be a reliable way to cleanup callback parameters passed to the tm uac functions - t_request, t_request_within, etc.. This patch extends the tm uac functions to support the tmcb release function for tm callback parameter cleanup. This is based on work done earlier which added the infrastructure necessary to do proper cleanup and here we are extending the existing uac functions to use that earlier work done in...
Author: dan_pascu <dan_pascu at 689a6050-402a-0410-94f2-e92a70836424>
Date: Thu Nov 20 18:55:23 2008 +0000
Added infrastructure for tm callback parameter cleanup. Fixed memory corruption caused by invalid freeing of dialogs
git-svn-id: https://opensips.svn.sourceforge.net/svnroot/opensips/trunk@4992 689a6050-402a-0410-94f2-e92a70836424
Currently, callback parameters cannot be reliably cleaned up. For example, when using t_request to send an INVITE and the uas responds with a 200 but then the ACK(s) gets lost and the uas continues sending 200s the callback is called repeatedly with an indication that the request was completed so one is faced with either not freeing the callback parameters (leaking memory) or freeing them repeatedly (ah, umm).
Regardless, proper cleanup can best be done by utilizing the release function infrastructure.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=2789126&group_id=232389
More information about the Devel
mailing list