[asterisk-r2] suddenly system has become unstable

[Moises Silva]

>
> [13:51:00:864] [Thread: 28011424] [Chan 9] - Seize Timeout Expired!
> [13:51:00:875] [Thread: 28011424] [Chan 9] - Protocol error. Reason = Seize
> Timeout, R2 State = Seize Transmitted, MF state = MF Engine Off, MF Group =
> Forwa
> rd MF init, CAS = 0x08
> DNIS = 55739176, ANI = 216, MF = 0x20
>

Do you have incoming calls at all?
As I said before, seize time out is the same as if a SIP interface sends an
INVITE and never gets a reply, the only difference here is that the INVITE
is a CAS signal sent through the E1, we send the CAS signal but never get a
reply, either because is not getting into the card or because the card or
driver is not reporting the response (or not sending the CAS signal at all).

I suggest you to contact Sangoma technical support, they should be able to
help with the CAS signaling troublesooting. Particularly, what I think we
would need is a system that can no longer make calls, DONT restart wanpipe,
and then we can see if the cas signaling is not being sent or received.


-- 
Moises Silva
Software Developer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090805/184e8038/attachment.htm