<HTML dir=ltr><HEAD><TITLE>Re: [OpenSIPS-Users] timeout on "100 Trying"</TITLE>
<META content="text/html; charset=unicode" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18943"></HEAD>
<BODY>
<DIV dir=ltr id=idOWAReplyText82392>
<DIV dir=ltr><FONT color=#000000 size=2 face=Verdana>thank you, how do we control set the timeout value between INVITE and 100 ?</FONT></DIV>
<DIV dir=ltr><FONT color=#000000 size=2 face=Verdana></FONT> </DIV>
<DIV dir=ltr><FONT size=2 face=Verdana>I suppose that once it is reached the failure_route block will be triggered</FONT></DIV>
<DIV dir=ltr><FONT size=2 face=Verdana></FONT> </DIV>
<DIV dir=ltr><FONT color=#000000 size=2><FONT face=Verdana> # uncomment the following lines if you want to redirect the failed<BR> # calls to a different new destination<BR> ##if (t_check_status("486|408")) {<BR> ## sethostport("192.168.2.100:5060");<BR> ## # do not set the missed call flag again<BR> ## t_relay();<BR> ##}<BR></FONT></DIV></FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> users-bounces@lists.opensips.org on behalf of Iņaki Baz Castillo<BR><B>Sent:</B> Tue 31/08/2010 1:34 PM<BR><B>To:</B> OpenSIPS users mailling list<BR><B>Subject:</B> Re: [OpenSIPS-Users] timeout on "100 Trying"<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>2010/8/31 Julien Chavanton <jc@atlastelecom.com>:<BR>> Hi, we have a core switch that can reroute calls on timeout, it is using<BR>> timeout on "100 Trying"<BR>><BR>> I was thinking opensips could wait for "100 Trying" comming from the remote<BR>> switch :<BR>><BR>><BR>> UA1 -INVITE-> P1<BR>> P1 -INVITE-> UA2<BR>> P1 <--100--- UA2<BR>> UA1 <--100--- P1<BR>><BR>><BR>> From t_relay doc<BR>> 0x01 - do not generate an 100 trying provisional reply when building the<BR>> transaction. By default one is generated. Useful if you already pushed an<BR>> stateless 100 reply from script.<BR>><BR>> Will Opensips forward 100 Trying ?<BR><BR>Never. 100 response is always hop-by-hop rather than end-to-end so it<BR>MUST be always generated by each node without waiting a response from<BR>downstream.<BR><BR>You can avoid OpenSIPS sending the mandatory 100 Trying but it will<BR>cause INVITE retransmissions from the core switch. It's much better<BR>and common the following solution:<BR><BR>- UA1 (core switch) sends INVITE to OpenSIPS.<BR><BR>- OpenSIPS replies the mandatory 100 Trying.<BR><BR>- OpenSIPS routes the call to UA2.<BR><BR>- Let's imagine UA2 is down so there is no reply.<BR><BR>- OpenSIPS then acts on failure_route (the winning response is a local<BR>generated 408 Timeout) and sends a response (maybe 408, 503 depending<BR>on UA1 failover implementation) to UA1.<BR><BR>- UA1 receives such response (i.e 408) and reroutes the call.<BR><BR><BR>--<BR>Iņaki Baz Castillo<BR><ibc@aliax.net><BR><BR>_______________________________________________<BR>Users mailing list<BR>Users@lists.opensips.org<BR><A href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</A><BR></FONT></P></DIV></BODY></HTML>