[asterisk-r2] Urgente seize timeout

[Anton Krall]

Latest wanpipe being? 3.5.8 or 3.5.8.7 cause 3.5.8.7 is broken...



From: Moises Silva <moises.silva at gmail.com>
Reply-To: <asterisk-r2 at lists.digium.com>
Date: Thu, 3 Dec 2009 22:38:21 -0500
To: <orvux at orvux.net>, <asterisk-r2 at lists.digium.com>
Subject: Re: [asterisk-r2] Urgente seize timeout

try latests wanpipe.

On Thu, Dec 3, 2009 at 10:36 PM, OrvUx <orvux at orvux.net> wrote:
>   
> These are my versions:
> 
> Asterisk 1.4.24.1
> OpenR2 version: 1.1.0, revision: exported
> Zaptel 1.4.12.1
> Wanpipe 3.4.1
> Sangoma A102
> 
> This is the Call log:
> 
> [10:24:02:912] [Thread: 3050707856] [Chan 7] - Call started at Thu Dec  3
> 10:24:02 2009 on chan 7
> [10:24:02:912] [Thread: 3050707856] [Chan 7] - CAS Tx >> [SEIZE] 0x00
> [10:24:02:912] [Thread: 3050707856] [Chan 7] - CAS Raw Tx >> 0x01
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - Attempting to cancel timer
> timer 2
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - timer id 2 found, cancelling it
> now
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - calling timer callback
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - Seize Timeout Expired!
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - Protocol error. Reason = Seize
> Timeout, R2 State = Seize Transmitted, MF state = MF Engine Off, MF Group =
> Forward MF init, CAS = 0x08
> DNIS = 6641238176, ANI = 018000266845, MF = 0x20
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - Attempting to cancel timer
> timer 0
> [10:24:10:931] [Thread: 3050707856] [Chan 7] - Cannot cancel timer 0
> 
> 
> after rebooting wanpipe and asterisk all works fine again...
> 
> Thanks.
> 
> 
> L.I. Orvil Juarez
> IT Manager
> J&A Consulting
> http://www.jacons.net
>  Linux and Asterisk Consulting in Tijuana, B.C.
> 
> On Thu, 2009-12-03 at 19:21 -0500, Moises Silva wrote:
>>  On Thu, Dec 3, 2009 at 2:27 PM, OrvUx <orvux at orvux.net> wrote:
>>  
>>>  Hi guys, sorry for my question but, what happened with this problem? Mr.
>>> Anton Krall did you resolved it? I have a server with the same problem, i
>>> will appreciate if you can post your solution.
>>>  
>>>  
>>>  
>>  
>>  
>>  There is no easy answer, sometimes this is a problem with the other end not
>> replying, sometimes it seems the drivers or the card misses bit changes.
>> Which Asterisk, openr2, card and drivers do you use?
>>  
>>  
>>  -- 
>>  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
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-r2



-- 
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


_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-r2 mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-r2

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20091204/a453f5ef/attachment-0001.htm