anchor.diff:  			   created -> "Responding";
   			   forwarded -> "Forwarding response"
   		       end,
  -		logger:log(LogLevel, "~s: ~s '~p ~s'",
  -			   [LogTag, What, Status, Reason]),
  -		store_transaction_result(NewSipState, Request, Status, Reason, LogTag),
  +		logger:log(LogLevel, "~s: ~s '~p ~s'", [LogTag, What, Status, Reason]),
  +		case State#state.testing of
  +		    true -> ok;
  +		    false ->
  +			store_transaction_result(NewSipState, Request, Status, Reason, LogTag)
  +		end,
   		{ok, NewState2} = send_response(Response, SendReliably, State),
   		%% Make event out of the fact that we are sending a response
  -		ToTagUsed = sipheader:get_tag(keylist:fetch('to', Response#response.header)),
  -		L = [{to_tag, ToTagUsed}],
  -		event_final_response(State#state.branch, Created, Status, Reason, L),
  +		event_final_response(Created, NewState2, Status),
   		enter_sip_state(NewSipState, NewState2);
   	    E ->
   		logger:log(error, "~s: State machine does not allow us to send '~p ~s' in response to '~s ~s' "
  
positive.code: 	    {Status, Reason} = {Response#response.status, Response#response.reason},
  	    case State#state.sipstate of
  		completed ->
  		    logger:log(debug, "~s: Resend after ~p (response to ~s ~s): ~p ~s",
  			       [LogTag, siptimer:timeout2str(Timeout), Method, sipurl:print(URI), Status, Reason]),
  		    transportlayer:send_proxy_response(State#state.socket, State#state.response),
  		    NewTimeout = case Method of
  
negative.code: %%%
  %%% Note    : Perhaps we should generate a 500 if we don't get adopted
  %%%           in a few seconds from when we start?
  %%%
  %%% Server transaction processes are spawned automatically by the
  %%% transaction layer when new requests arrive.
  %%%
  %%% At the same time, the transaction layer also starts the request/3
  %%% function of the Yxa application running (for example
  %%% incomingproxy:request/3). The application is what RFC3261 calls a
  %%% 'Transaction User' or 'proxy core'.
  %%%
  %%% The application should 'adopt' the server transaction process, and
  %%% then tell it what response(s) to send.
  %%%
  %%% After adopting a server transaction, the application can get the
  %%% following signals from the server transaction :
  %%%
  %%%    {servertransaction_cancelled, Pid, ExtraHeaders} - the
  %%%       transaction layer has received a CANCEL matching this server
  %%%       transaction.
  %%%         Pid          = pid() of server transaction
  %%%         ExtraHeaders = list() of {Key, ValueList} tuples - headers
  %%%                        from the CANCEL request that should be
  %%%                        passed on to any downstream entitys
  %%%
  %%%    {servertransaction_terminating, Pid} - the server transaction
  %%%       is terminating.
  %%%         Pid = pid() of server transaction
  %%%
  %%%-------------------------------------------------------------------
  -module(servertransaction).
  %%-compile(export_all).
  
  -behaviour(gen_server).
  
  