[asterisk-r2] Canales que se Bloquean CLEAR BA CLEAR FO DTMFR2 CANTV Venezuela

[Moises Silva]

2013/3/5 Maycol Alvarez <maycolalvarez at gmail.com>

>  Gracias por responder, aqui envio los 10 archivos comprimidos:
> https://www.dropbox.com/sh/ghk3gnvo32lld0y/_WTqv_ImhN/mfcr2/mfcr2.zip
>
> y la salida de mfcr2 show channels:
>   84 VE      10      4        Yes       Yes              CLEAR FO SEIZE AC
>   85 VE      10      4        Yes       Yes              CLEAR FO SEIZE AC
>   86 VE      10      4        Yes       Yes              CLEAR FO CLEAR BA
>   87 VE      10      4        Yes       Yes              CLEAR FO SEIZE AC
>   88 VE      10      4        Yes       Yes              CLEAR FO ANSWER
>   89 VE      10      4        Yes       Yes              CLEAR FO CLEAR BA
>   90 VE      10      4        Yes       Yes              CLEAR FO CLEAR BA
>   91 VE      10      4        Yes       Yes              CLEAR FO SEIZE AC
>   92 VE      10      4        Yes       Yes              CLEAR FO ANSWER
>   93 VE      10      4        Yes       Yes              CLEAR FO CLEAR BA
>
>
The logs are pretty clear. The openr2 stack never receives the change in
bits from SEIZE ACK (0x0C) back to IDLE (0x08)

Some possible reasons:

1. The bits actually did not change in the line (the other end is stuck)
2. Bug in the DAHDI drivers
3. Bug in the Digium firmware/hardware
4. Bug in openr2/Asterisk

Can you confirm with "dahdi_tool" what the state of the rx bits is in one
of the channels stuck in CLEAR FO SEIZE AC ?

If the bits are 1001, it means the bits changed correctly, but the event
was not propagated due to reasons 2-4

If you have access to a Sangoma card you can try that to discard reasons 2
and 3 (at least partially).

*Moises Silva
**Manager, Software Engineering***

msilva at sangoma.com

Sangoma Technologies

100 Renfrew Drive, Suite 100, Markham, ON L3R 9R6 Canada


t.   +1 800 388 2475 (N. America)

t.   +1 905 474 1990 x128

f.   +1 905 474 9223



**<http://www.sangoma.com/contact?utm_source=signature&utm_medium=email&utm_campaign=email+signatures>

Products<http://sangoma.com/products?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Solutions<http://sangoma.com/solutions?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Events<http://sangoma.com/about_us/events?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Contact<http://www.sangoma.com/contact?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Wiki<http://wiki.sangoma.com/?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Facebook<http://www.facebook.com/pages/Sangoma-VoIP-Cards/43578453335?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
 | Twitter<http://www.twitter.com/sangoma?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>`|
| YouTube<http://www.youtube.com/sangomatechnologies?utm_source=signature&utm_medium=email&utm_campaign=email%2Bsignatures>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20130307/34a5b899/attachment.htm>