<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0"></p>
<div>
<div>Hi Moises, thanks for your answer,</div>
<div><br>
</div>
<div>The issue is that with another PBX the calls have no problem, all are handled correctly, therefore the provider argues that a problem is the new PBX. </div>
<div><span style="font-size: 12pt;">However, I have already tried with the persistence check, and the release signal really persists for about 160ms.</span><br>
</div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div><span style="font-size: 12pt;">Regards, Ezequiel </span></div>
</div>
<br>
<p></p>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>De:</b> asterisk-r2-bounces@lists.digium.com <asterisk-r2-bounces@lists.digium.com> en nombre de Moises Silva <moises.silva@gmail.com><br>
<b>Enviado:</b> viernes, 16 de marzo de 2018 10:56 a.m.<br>
<b>Para:</b> asterisk-r2@lists.digium.com<br>
<b>Asunto:</b> Re: [asterisk-r2] Incoming calls hangs randomly prior R2 exchange</font>
<div> </div>
</div>
<div>
<div dir="ltr"><br>
<div class="x_gmail_extra">
<div class="x_gmail_quote">On Thu, Mar 15, 2018 at 3:40 PM, Ezequiel Quadri <span dir="ltr">
<<a href="mailto:ezequiel_quadri@hotmail.com" target="_blank" id="LPlnk331940" previewremoved="true">ezequiel_quadri@hotmail.com</a>></span> wrote:<br>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div dir="ltr">
<div id="x_gmail-m_-3760767879806140442divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<p style="margin-top:0px; margin-bottom:0px"></p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">OpenR2 call files:<br>
</p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px"></p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px"><br>
</p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px"></p>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:236] [Thread: 140405976749824] [Chan 4] - Call started at Tue Mar 13 12:22:03 2018 on chan 4 [openr2 version 1.3.3, revision (release)]</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:236] [Thread: 140405976749824] [Chan 4] - Initialized R2 MF detector</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:236] [Thread: 140405976749824] [Chan 4] - CAS Tx >> [SEIZE ACK] 0x0C</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:236] [Thread: 140405976749824] [Chan 4] - CAS Raw Tx >> 0x0D</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Bits changed from 0x00 to 0x08</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - CAS Rx << [CLEAR FORWARD] 0x08</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Far end disconnected. Reason: Normal Clearing</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Call ended</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Attempting to cancel timer timer 0</div>
<div style="font-size:16px; font-family:Calibri,Helvetica,sans-serif">[12:22:03:277] [Thread: 140405976749824] [Chan 4] - Cannot cancel timer 0</div>
<p></p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px"><br>
</p>
<p style="font-family:Calibri,Helvetica,sans-serif; font-size:16px"></p>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:236] [Thread: 140405976241920] [Chan 5] - Call started at Tue Mar 13 12:22:03 2018 on chan 5 [openr2 version 1.3.3, revision (release)]</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:236] [Thread: 140405976241920] [Chan 5] - Initialized R2 MF detector</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:236] [Thread: 140405976241920] [Chan 5] - CAS Tx >> [SEIZE ACK] 0x0C</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:236] [Thread: 140405976241920] [Chan 5] - CAS Raw Tx >> 0x0D</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Bits changed from 0x00 to 0x08</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - CAS Rx << [CLEAR FORWARD] 0x08</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Far end disconnected. Reason: Normal Clearing</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Call ended</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Attempting to cancel timer timer 0</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:16px">[12:22:03:277] [Thread: 140405976241920] [Chan 5] - Cannot cancel timer 0</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>I think you should try contacting your telco as this seems like an issue upstream. Having said that, you may try to fix it by using 'timers.cas_persistence_check=100' in the advanced protocol file (r2proto.conf). This helps clearing 'false positives' with
CAS signals that are short-lived (e.g less than 100ms).</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>