Browse code

modules/tm: no reason to reset KR on continuation of async requests - maybe before continuing, a reply has been sent, request forwarded, etc...

Jason Penton authored on 30/01/2015 12:53:18
Showing 1 changed files
... ...
@@ -221,7 +221,7 @@ int t_continue(unsigned int hash_index, unsigned int label,
221 221
 			Not a huge problem, fr timer will fire, but CANCEL
222 222
 			will not be sent. last_received will be set to 408. */
223 223
 
224
-		reset_kr();
224
+//		reset_kr();
225 225
 
226 226
 		/* fake the request and the environment, like in failure_route */
227 227
 		if (!fake_req(&faked_req, t->uas.request, 0 /* extra flags */, uac)) {