<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>problem with status in serial forking (maybe related to bug 48)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<P><FONT SIZE=2 FACE="Courier New">Hello, </FONT>
<BR><FONT SIZE=2 FACE="Courier New">I have a problem with serial forking and it seems the same behaviour of the bug 48:</FONT>
<BR><FONT SIZE=2 FACE="Courier New">my ser.cfg script stops the first call due to time-out (fr_inv_timer), and the status in the failure_route is 408, and then sends a call to a second destination.</FONT></P>
<P><FONT SIZE=2 FACE="Courier New">If the caller hang up the call, the status in failure-route should be 487, but I have 408 again.</FONT>
<BR><FONT SIZE=2 FACE="Courier New">The bug is declared as closed since the 0.9.5 (<A HREF="http://tracker.iptel.org/browse/SER-48">http://tracker.iptel.org/browse/SER-48</A>), where can I take the patch? </FONT>
<BR><FONT SIZE=2 FACE="Courier New">I have downloaded the version 0.9.6 from <A HREF="http://ftp.iptel.org/pub/ser/0.9.6/src/">http://ftp.iptel.org/pub/ser/0.9.6/src/</A>, but it doesn't seem to contain the patch for the bug. </FONT></P>
<P><FONT SIZE=2 FACE="Courier New">thanks</FONT>
</P>
</BODY>
</HTML><pre>**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message inerror.
**********************************************************************</pre>