<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi,<br>
<br>
The failure route is correct and you have to arm it before sending
out the request via the request route (before the t_relay()) with
t_on_failure("MANAGE_FAILURE")<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
OpenSIPS Summit May 2017 Amsterdam
<a class="moz-txt-link-freetext" href="http://www.opensips.org/events/Summit-2017Amsterdam.html">http://www.opensips.org/events/Summit-2017Amsterdam.html</a>
</pre>
<div class="moz-cite-prefix">On 05/01/2017 04:22 AM,
<a class="moz-txt-link-abbreviated" href="mailto:volga629@networklab.ca">volga629@networklab.ca</a> wrote:<br>
</div>
<blockquote cite="mid:1493601764.3540.2@smtp.networklab.ca"
type="cite">Hello Bogdan,
<div>I created fail route </div>
<div><br>
</div>
<div>failure_route[MANAGE_FAILURE] {</div>
<div> if (t_check_status("408")) {</div>
<div> append_branch();</div>
<div> route(DISPATCH);</div>
<div> }</div>
<div><br>
</div>
<div> if (t_was_cancelled()) {</div>
<div> exit;</div>
<div> }</div>
<div>}</div>
<div><br>
</div>
<div>How I can detect that timer expire ? On which stage in reply
need apply fail route.</div>
<div><br>
</div>
<div>volga629<br>
<br>
On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu
<a class="moz-txt-link-rfc2396E" href="mailto:bogdan@opensips.org"><bogdan@opensips.org></a> wrote:<br>
<blockquote type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<tt>Hi,<br>
<br>
OpenSIPS is generating the CANCEL due to the timeout (no
answer to the call) - see:<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout">http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout</a><br>
<br>
If you want to get a redirect to a VM, you need to use the
failure route in order to catch the 408 reply and create a
new branch to the VM server.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
OpenSIPS Summit May 2017 Amsterdam
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips.org/events/Summit-2017Amsterdam.html">http://www.opensips.org/events/Summit-2017Amsterdam.html</a>
</pre>
<div class="moz-cite-prefix">On 04/29/2017 06:28 AM, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:volga629@networklab.ca"><a class="moz-txt-link-abbreviated" href="mailto:volga629@networklab.ca">volga629@networklab.ca</a></a>
wrote:<br>
</div>
<blockquote cite="mid:1493436485.3540.1@smtp.networklab.ca"
type="cite">Hello Alex,
<div>So what it is </div>
<div><br>
</div>
<div>
<div>2017/04/28 22:12:45.455111 server_public_ip:5082
-> client_public_ip:47293</div>
<div>SIP/2.0 180 Ringing</div>
<div>Via: SIP/2.0/TCP
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293</div>
<div>Record-Route:
<sip:10.18.130.27;r2=on;lr;ftag=f30d187f;did=acf.146ecb6></div>
<div>Record-Route:
<sip:server_public_ip:5082;transport=tcp;r2=on;lr;ftag=f30d187f;did=acf.146ecb6></div>
<div>From: "volga629" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4310@sip.company.tld"><sip:4310@sip.company.tld></a>;tag=f30d187f</div>
<div>To: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4300@sip.company.tld"><sip:4300@sip.company.tld></a>;tag=ZH2mc6gFgS9Fg</div>
<div>Call-ID:
141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI</div>
<div>CSeq: 2 INVITE</div>
<div>Contact: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4300@10.18.130.26:5160;transport=udp"><sip:4300@10.18.130.26:5160;transport=udp></a></div>
<div>User-Agent: B2BUA01</div>
<div>Accept: application/sdp</div>
<div>Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE,
INFO, UPDATE, REGISTER, NOTIFY, PUBLISH, SUBSCRIBE</div>
<div>Supported: timer, path, replaces</div>
<div>Allow-Events: talk, hold, conference, presence,
as-feature-event, dialog, line-seize, call-info, sla,
include-session-description, presence.winfo,
message-summary, refer</div>
<div>Content-Length: 0</div>
<div><br>
</div>
<div><b>OPENSIPS send to PBX</b></div>
<div> </div>
<div>2017/04/28 22:13:14.639461 10.18.130.27:5060 ->
10.18.130.26:5160</div>
<div>CANCEL <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:sip:4300@sip.company.tld">sip:4300@sip.company.tld</a>
SIP/2.0</div>
<div>Via: SIP/2.0/UDP
10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0</div>
<div>From: "volga629"<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4310@sip.company.tld"><sip:4310@sip.company.tld></a>;tag=f30d187f</div>
<div>Call-ID:
141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI</div>
<div>To: <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4300@sip.company.tld"><sip:4300@sip.company.tld></a></div>
<div>CSeq: 2 CANCEL</div>
<div>Max-Forwards: 70</div>
<div>Reason: SIP;cause=480;text="NO_ANSWER"</div>
<div>User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))</div>
<div>Content-Length: 0</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>2017/04/28 22:13:14.639605 server_public_ip:5082
-> client_public_ip:47293</div>
<div>SIP/2.0 408 Request Timeout</div>
<div>Via: SIP/2.0/TCP
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293</div>
<div>To:
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:sip:4300@sip.company.tld"><sip:4300@sip.company.tld></a>;tag=c88f800b416e86b8a763b24c260500d8-3c4f</div>
<div>From: "volga629"<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:sip:4310@sip.company.tld"><sip:4310@sip.company.tld></a>;tag=f30d187f</div>
<div>Call-ID:
141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI</div>
<div>CSeq: 2 INVITE</div>
<div>Server: OpenSIPS (2.4.0-dev (x86_64/linux))</div>
<div>Content-Length: 0</div>
</div>
<div><br>
</div>
<div><br>
On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:abalashov@evaristesys.com"><a class="moz-txt-link-rfc2396E" href="mailto:abalashov@evaristesys.com"><abalashov@evaristesys.com></a></a>
wrote:<br>
<blockquote type="cite">
<div class="plaintext" style="white-space: pre-wrap;">OpenSIPS didn't hang up anything.
On April 28, 2017 10:30:08 PM EDT, <a moz-do-not-send="true" href="mailto:volga629@networklab.ca">volga629@networklab.ca</a> wrote:
<blockquote>Hello Everyone,
Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail.
What way possible fix it.
Please see attached trace.
volga629
</blockquote>
-- Alex
--
Principal, Evariste Systems LLC (<a moz-do-not-send="true" href="http://www.evaristesys.com">www.evaristesys.com</a>)
Sent from my Google Nexus.
_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>