<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=RU link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span lang=EN-US>Hello.<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>I&#8217;m thinking about modifying chan_iax2.c
to allow N (2 or 3) unreplied pokes before reporting peer as unreachable. Are
there any objections against such an approach?<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US>The problem I&#8217;m trying to solve if
constant flooding of console with output like:<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:25:57] NOTICE[2659]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 62<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:26:27] NOTICE[2655]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 52<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:27:31] NOTICE[2656]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 52<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:28:01] NOTICE[2655]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 51<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:29:05] NOTICE[2656]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 51<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:29:35] NOTICE[2658]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 55<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:30:39] NOTICE[2653]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 55<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:31:09] NOTICE[2655]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 58<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:32:13] NOTICE[2656]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 58<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:32:43] NOTICE[2662]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 61<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:33:47] NOTICE[2658]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 61<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:35:37] NOTICE[2660]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 53<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:36:41] NOTICE[2659]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 53<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:37:11] NOTICE[2660]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 52<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:38:15] NOTICE[2659]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 52<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:38:45] NOTICE[2656]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 55<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:39:49] NOTICE[2661]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 55<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:40:19] NOTICE[2655]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 56<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:41:23] NOTICE[2655]:
chan_iax2.c:8467 __iax2_poke_noanswer: Peer '1002' is now UNREACHABLE! Time: 56<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>[Oct&nbsp; 3 00:41:53] NOTICE[2653]:
chan_iax2.c:7578 socket_process: Peer '1002' is now REACHABLE! Time: 56<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US>I have IAX2 clients connecting over VPN and
there is a packet loss about 7% for them so some packets are actually lost. I
suppose that as soon as single poke packet is lost, asterisk reports
unreachable peer. Although just a single additional poke would reveal the fact
that peer is alive.<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US>Regards,<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US>Dmitry Andrianov<o:p></o:p></span></p>

</div>

</body>

</html>