Hi Alex,

We have a similar issue (slightly complex) as it involves sip parallel forking.

The issue is that failure_route[] occurs when all sip forked are exhausted even though "302 Moved Temporarily" has been responded back by one of the SIP endpoint quite quickly.

So, we wish to handle 302 onreply_route[] as it is received quite promptly but as you pointed out Kamailio doesn’t let us set the contact header or append_to_reply.

Please can you suggest me is there any way out we can change the sip contact when using sip parallel forking.

Many Thanks

Regards
Muhammad Adil M Zaka

-----Original Message-----
From: sr-users <sr-users-bounces@lists.kamailio.org> On Behalf Of Alex Balashov
Sent: 16 January 2020 22:32
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] Trouble with 302 Redirect

Try doing this in a failure_route[]; onreply_route[] isn't really meant to transform replies, just to passively observe or drop them.

Also, you'll want to use append_to_reply():

   https://kamailio.org/docs/modules/5.3.x/modules/textops.html#textops.f.append_to_reply

Note that the conditions that give rise to the invocation of a failure_route are broader and somewhat more abstract than any given SIP reply -- e.g. transaction reply timeouts. So, you would want to structure your failure_route like this:

   failure_route[REDIRECT_HANDLE] {
      if(t_is_canceled())
         exit;

      if(t_branch_timeout()) {
         # Handle the timeout case...

	 exit;
      }

      # Use $T_rpl to access reply code ($rs) and reply reason if needed
      # ($rs), per:
      #
      # https://www.kamailio.org/wiki/cookbooks/5.3.x/pseudovariables#t_rpl_pv

      if($T_rpl($rs) == 486) {
         append_to_reply("Contact: <sip:...>\r\n");
         t_reply("302", "Moved Temporarily");
	 exit;
      }

      # Some other case.
   }

-- Alex

On Thu, Jan 16, 2020 at 03:54:54PM -0500, Jim Leahy wrote: