[asterisk-r2] Protocol error. Reason = Invalid CAS

[Diego G. Perez]

Buenos dias.

Disculpen la demora, les comento que sigo con el mismo problema.
La llamadas se establecen perfectamente y NO SE CORTAN. El error lo veo 
aleatoriamente en dos escenarios diferentes:

a) La llamada finaliza con:

.......
[09:24:56:369] [Thread: 140326108309248] [Chan 10] - Cannot cancel timer 0
[09:24:56:369] [Thread: 140326108309248] [Chan 10] - *CAS Tx >> [CLEAR 
FORWARD*] 0x08
[09:24:56:369] [Thread: 140326108309248] [Chan 10] - CAS Raw Tx >> 0x09
[09:24:56:759] [Thread: 140326316050176] [Chan 10] - Bits changed from 
0x04 to 0x00
[09:24:56:759] [Thread: 140326316050176] [Chan 10] - *CAS Rx << [FORCED 
RELEASE]* 0x00
[09:27:46:839] [Thread: 140326316050176] [Chan 10] - Bits changed from 
0x00 to 0x0C
[09:27:46:839] [Thread: 140326316050176] [Chan 10] - CAS Rx << [0x0C] 0x0C
[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$
DNIS = 4447100, ANI = 11701, MF = 0x20
[09:27:46:839] [Thread: 140326316050176] [Chan 10] - Attempting to 
cancel timer timer 0
[09:27:46:839] [Thread: 140326316050176] [Chan 10] - Cannot cancel timer 0

b) La llamada finaliza correctamente:

...........
[14:24:22:254] [Thread: 140064051861248] [Chan 9] - Cannot cancel timer 0
[14:24:22:254] [Thread: 140064051861248] [Chan 9] - *CAS Tx >> [CLEAR 
FORWARD]* 0x08
[14:24:22:254] [Thread: 140064051861248] [Chan 9] - CAS Raw Tx >> 0x09
[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Bits changed from 
0x04 to 0x08
[14:24:22:610] [Thread: 140064099895040] [Chan 9] - *CAS Rx << [IDLE]* 0x08
[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Call ended
[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Attempting to cancel 
timer timer 0
[14:24:22:610] [Thread: 140064099895040] [Chan 9] - Cannot cancel timer 0

Y después recibo un archivo backward:

[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]
[14:24:22:796] [Thread: 140064099895040] [Chan 9] - Initialized R2 MF 
detector
[14:24:22:796] [Thread: 140064099895040] [Chan 9] - CAS Tx >> [SEIZE 
ACK] 0x0C
[14:24:22:796] [Thread: 140064099895040] [Chan 9] - CAS Raw Tx >> 0x0D
[14:27:12:862] [Thread: 140064099895040] [Chan 9] - Bits changed from 
0x00 to 0x0C
[14:27:12:862] [Thread: 140064099895040] [Chan 9] - CAS Rx << [0x0C] 0x0C
[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$
DNIS = , ANI = , MF = 0x20
[14:27:12:862] [Thread: 140064099895040] [Chan 9] - Attempting to cancel 
timer timer 0
[14:27:12:862] [Thread: 140064099895040] [Chan 9] - Cannot cancel timer 0

Hice las siguientes pruebas:

- Probé con los siguientes parámetros en chan_dahdi como me 
comentó**Ivan Paes José:

mfcr2_metering_pulse_timeout=500  ó
timer.cas_persistance_check=100

Siguió igual.

- Instalé irqbalance y veo en /proc/interrupts que se están balanceando 
en dos CPU.

La placa esta compartiendo IRQ con otros dispositivos.
De que manera puedo asignar un único IRQ para la placa?

El dahdi_test me sigue dando bien: *Average: 99.998258%*

Que otra cosa puedo probar?

En este momento estoy esperando respuesta de telefónica para que hagamos 
algunas pruebas.

Muchas Gracias,

Diego

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20121107/a90b10de/attachment.htm>