[asterisk-r2] Urgente seize timeout

Wed Aug 5 00:08:05 CDT 2009

Moises

I did the tests today.... The scenario is this:
Wanpipe 3.3.15 and 3.4.2.4

On 3.4.2.4 I went into zttool and as soon as the prolems started all E1
channels seems to have gone down.. Zttool shows 1001 on RX and TX and no
calls could go in and out, the logs shows no errors regarding sangoma but on
openr2 they showd this:

chan-3-forward-1-20090804094726.call:[09:47:34:384] [Thread: 13544352] [Chan
3] - Protocol error. Reason = Seize Timeout, R2 State = Seize Transmitted,
MF state = MF Engine Off, MF Group = Forward MF init, CAS = 0x08

On all channels...

So I restart just asterisk.... Everything stayed the same..  No call could
go in and out and zttool showd rx 1001 and tx 1001

So I turned asterisk off again and then I did a wanrouter restart...
Restarted asterisk and everything was back to normal.

This leads me to believe that something between wanpipe and openr2 or
asterisk is bad...

Tonight Im going to upgrade to openr2 1.2 rc1 and wanpipe 3.5.4 to see if
this helps... Tomorrow Ill run the same tests and report back.

From: Moises Silva <moises.silva at gmail.com>
Reply-To: <asterisk-r2 at lists.digium.com>
Date: Tue, 4 Aug 2009 01:17:30 -0400
To: <asterisk-r2 at lists.digium.com>
Subject: Re: [asterisk-r2] Urgente seize timeout

the next time you see the issue, take a look at zttool or dahdi_tool, when
you select the span you will see the ABCD bits, check if the tx bits on the
channel you are trying to make a call are set to 0001 (that is a seize) and
see if the rx bits in the same channel are anything different than 1001,
that would let us know if the problem is in openr2 at all or not. I dont
think the problem is in openr2 though.

Ideally as well, I should be able to get access to the box in question when
the problem occurs. Which wanpipe driver version are you using?

Try with 3.5.4 if you are using 3.4.4, or try 3.5.4 if you are using 3.4.4,
that is, just switch the versions to see if that helps.

On Tue, Aug 4, 2009 at 1:04 AM, Anton Krall <akrall at intruder.com.mx> wrote:
> No errors regarding wanpipe on /var/log/messages
> 
> 
> 
> 
> From: Moises Silva <moises.silva at gmail.com <http://moises.silva@gmail.com> >
> Reply-To: <asterisk-r2 at lists.digium.com <http://asterisk-r2@lists.digium.com>
> >
> Date: Tue, 4 Aug 2009 00:22:31 -0400
> 
> To: <asterisk-r2 at lists.digium.com <http://asterisk-r2@lists.digium.com> >
> Subject: Re: [asterisk-r2] Urgente seize timeout
> 
> Did you try to look for errors in /var/log/messages ? if this is driver
> related you may see errors there
> 
> On Mon, Aug 3, 2009 at 11:41 PM, Anton Krall <akrall at intruder.com.mx
> <http://akrall@intruder.com.mx> > wrote:
>> The line is working... When this happens... I need to restart wanpipe and
>> asterisk and everthing is back to nromal for some time.... Weird thing is,
>> this didnt happen with openr2 and digium cards.. Started when I exchanged the
>> card for a sangoma...  And I think it is software related because after
>> restarting wanpipe and asterisk, everthing goes back to normal for some
>> time...
>> 
>> 
>> 
>> From: Moises Silva <moises.silva at gmail.com <http://moises.silva@gmail.com>
>> <http://moises.silva@gmail.com> >
>> 
>> Reply-To: <asterisk-r2 at lists.digium.com <http://asterisk-r2@lists.digium.com>
>> <http://asterisk-r2@lists.digium.com> >
>> 
>> Date: Mon, 3 Aug 2009 11:42:09 -0400
>> 
>> To: <asterisk-r2 at lists.digium.com <http://asterisk-r2@lists.digium.com>
>> <http://asterisk-r2@lists.digium.com> >
>> 
>> Subject: Re: [asterisk-r2] Urgente seize timeout
>> 
>> 
>> On Fri, Jul 31, 2009 at 3:38 PM, Anton Krall <akrall at intruder.com.mx
>> <http://akrall@intruder.com.mx>  <http://akrall@intruder.com.mx> > wrote:
>>> Ah! For got to add.. Weird thing is, its the same E1 as before, we just
>>> upgraded a digium e1 card to a sangoma one with wanpipe now... Could it be
>>> wanpipe related?
>> 
>> Should not be an issue, I have been using wanpipe since I started the
>> development of openr2 since Sangoma sent me my first boards to test. The
>> seize timeout simply means the other end did not change the ABCD bits to
>> reply our initial message, may be your rx CAS signaling is not working at all
>> or the telco disabled the line?  
>> 
>> -- 
>> 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 <http://moy@sangoma.com>
>> <http://moy@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
>> 
>> _______________________________________________
>> --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 <http://moy@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
> 
> _______________________________________________
> --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/20090805/3d0a1fc0/attachment-0001.htm 