<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><tt>Por lo que se observa en el tracer estaria cambiando internamente de 00(forced release) a 11 (señal clearback) y lo esta procesando como señal clear-back en lugar de forced-release.<br><br>Habria que investigar si contempla la señal de forced-release.<br><br><br>Saludos Alberto<br><br>[09:27:46:839] [Thread: 140326316050176] [Chan 10] - <b>Bits
changed</b> from <b>0x00 to 0x0C</b></tt><tt><br>
</tt><br><br><br>--- El <b>mié 7-nov-12, Diego G. Perez <i><diegoperez891@gmail.com></i></b> escribió:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: Diego G. Perez <diegoperez891@gmail.com><br>Asunto: Re: [asterisk-r2] Protocol error. Reason = Invalid CAS<br>Para: asterisk-r2@lists.digium.com<br>Fecha: miércoles, 7 de noviembre de 2012, 14:55<br><br><div id="yiv1945600946">
<div>
Buenos dias.<br>
<br>
Disculpen la demora, les comento que sigo con el mismo problema.<br>
La llamadas se establecen perfectamente y NO SE CORTAN. El error lo
veo aleatoriamente en dos escenarios diferentes:<br>
<br>
a) La llamada finaliza con: <br>
<br>
.......<br>
<tt>[09:24:56:369] [Thread: 140326108309248] [Chan 10] - Cannot
cancel timer 0</tt><tt><br>
</tt><tt>[09:24:56:369] [Thread: 140326108309248] [Chan 10] - <b>CAS
Tx >> [CLEAR FORWARD</b>] 0x08</tt><tt><br>
</tt><tt>[09:24:56:369] [Thread: 140326108309248] [Chan 10] - CAS
Raw Tx >> 0x09</tt><tt><br>
</tt><tt>[09:24:56:759] [Thread: 140326316050176] [Chan 10] - Bits
changed from 0x04 to 0x00</tt><tt><br>
</tt><tt>[09:24:56:759] [Thread: 140326316050176] [Chan 10] - <b>CAS
Rx << [FORCED RELEASE]</b> 0x00</tt><tt><br>
</tt><tt>[09:27:46:839] [Thread: 140326316050176] [Chan 10] - Bits
changed from 0x00 to 0x0C</tt><tt><br>
</tt><tt>[09:27:46:839] [Thread: 140326316050176] [Chan 10] - CAS Rx
<< [0x0C] 0x0C</tt><tt><br>
</tt><tt>[09:27:46:839] [Thread: 140326316050176] [Chan 10] -
Protocol error. Reason = Invalid CAS, R2 State = Clear Back After
Clear Forward Received, MF state = MF Engine Off, MF Group =
Forwa$</tt><tt><br>
</tt><tt>DNIS = 4447100, ANI = 11701, MF = 0x20</tt><tt><br>
</tt><tt>[09:27:46:839] [Thread: 140326316050176] [Chan 10] -
Attempting to cancel timer timer 0</tt><tt><br>
</tt><tt>[09:27:46:839] [Thread: 140326316050176] [Chan 10] - Cannot
cancel timer 0</tt><br>
<br>
b) La llamada finaliza correctamente:<br>
<br>
...........<br>
<tt>[14:24:22:254] [Thread: 140064051861248] [Chan 9] - Cannot
cancel timer 0</tt><tt><br>
</tt><tt>[14:24:22:254] [Thread: 140064051861248] [Chan 9] - <b>CAS
Tx >> [CLEAR FORWARD]</b> 0x08</tt><tt><br>
</tt><tt>[14:24:22:254] [Thread: 140064051861248] [Chan 9] - CAS Raw
Tx >> 0x09</tt><tt><br>
</tt><tt>[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Bits
changed from 0x04 to 0x08</tt><tt><br>
</tt><tt>[14:24:22:610] [Thread: 140064099895040] [Chan 9] - <b>CAS
Rx << [IDLE]</b> 0x08</tt><tt><br>
</tt><tt>[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Call
ended</tt><tt><br>
</tt><tt>[14:24:22:610] [Thread: 140064099895040] [Chan 9] -
Attempting to cancel timer timer 0</tt><tt><br>
</tt><tt>[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Cannot
cancel timer 0</tt><br>
<br>
Y después recibo un archivo backward:<br>
<tt><br>
</tt><tt>[14:24:22:796] [Thread: 140064099895040] [Chan 9] - Call
started at Wed Nov 7 14:24:22 2012 on chan 9 [openr2 version
1.3.2, revision exportado]</tt><tt><br>
</tt><tt>[14:24:22:796] [Thread: 140064099895040] [Chan 9] -
Initialized R2 MF detector</tt><tt><br>
</tt><tt>[14:24:22:796] [Thread: 140064099895040] [Chan 9] - CAS Tx
>> [SEIZE ACK] 0x0C</tt><tt><br>
</tt><tt>[14:24:22:796] [Thread: 140064099895040] [Chan 9] - CAS Raw
Tx >> 0x0D</tt><tt><br>
</tt><tt>[14:27:12:862] [Thread: 140064099895040] [Chan 9] - Bits
changed from 0x00 to 0x0C</tt><tt><br>
</tt><tt>[14:27:12:862] [Thread: 140064099895040] [Chan 9] - CAS Rx
<< [0x0C] 0x0C</tt><tt><br>
</tt><tt>[14:27:12:862] [Thread: 140064099895040] [Chan 9] -
Protocol error. Reason = Invalid CAS, R2 State = Seize ACK
Transmitted, MF state = Seize ACK Transmitted, MF Group = Backward
MF init$</tt><tt><br>
</tt><tt>DNIS = , ANI = , MF = 0x20</tt><tt><br>
</tt><tt>[14:27:12:862] [Thread: 140064099895040] [Chan 9] -
Attempting to cancel timer timer 0</tt><tt><br>
</tt><tt>[14:27:12:862] [Thread: 140064099895040] [Chan 9] - Cannot
cancel timer 0</tt><br>
<br>
Hice las siguientes pruebas:<br>
<br>
- Probé con los siguientes parámetros en chan_dahdi como me comentó<b>
</b><span class="yiv1945600946gmail_sendername">Ivan Paes José</span>:<br>
<br>
mfcr2_metering_pulse_timeout=500 ó <br>
timer.cas_persistance_check=100<br>
<br>
Siguió igual.<br>
<br>
- Instalé irqbalance y veo en /proc/interrupts que se están
balanceando en dos CPU.<br>
<br>
La placa esta compartiendo IRQ con otros dispositivos.<br>
De que manera puedo asignar un único IRQ para la placa?<br>
<br>
El dahdi_test me sigue dando bien: <b>Average: 99.998258%</b><br>
<br>
Que otra cosa puedo probar?<br>
<br>
En este momento estoy esperando respuesta de telefónica para que
hagamos algunas pruebas.<br>
<br>
Muchas Gracias,<br>
<br>
Diego<br>
<br>
</div>
</div><br>-----Adjunto en línea a continuación-----<br><br><div class="plainMail">--<br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br><br>asterisk-r2 mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-r2" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-r2</a></div></blockquote></td></tr></table>