Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2007-12-03 Thread Andres Junge
El sáb, 01-12-2007 a las 13:28 +0200, Faidon Liambotis escribió: > tags 299583 + moreinfo unreproducible > thanks > > I apologize beforehand for being so late in responding you. > Since huge progress has been made by both of our upstreams since 1.0.x, > could you test if this bug still occurs for

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2007-12-01 Thread Faidon Liambotis
tags 299583 + moreinfo unreproducible thanks I apologize beforehand for being so late in responding you. Since huge progress has been made by both of our upstreams since 1.0.x, could you test if this bug still occurs for you. I realize that you may not use asterisk at all after such a long time w

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-16 Thread Tzafrir Cohen
On Wed, Mar 16, 2005 at 05:14:25PM -0400, Andres Junge wrote: > Tzafrir Cohen wrote: > > >>I am using asterisk 1.0.5-2 and zaptel compiled from cvs (digium > >>recomendation) > >> > >> > > > >Why zaptel from CVS? I'm not sure if this combination is healthy. > > > > > > > Because I need the wc

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-16 Thread Andres Junge
Tzafrir Cohen wrote: I am using asterisk 1.0.5-2 and zaptel compiled from cvs (digium recomendation) Why zaptel from CVS? I'm not sure if this combination is healthy. Because I need the wctdm module which is not in the zaptel-source debian package. Also, in later versions the Debian pac

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-15 Thread Tzafrir Cohen
On Tue, Mar 15, 2005 at 10:10:58AM -0400, Andrés Junge wrote: > > Hi Andres, > > > >> Any idea? Maybe the unofficial patches? > > > > have you made sure ztcfg is only run once? Moreover 1.0.4-2 is obsolete > > if you use zaptel 1.0.6 and asterisk 1.0.6 with it. Yet the most likely > > to cause this

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-15 Thread Andrés Junge
> Hi Andres, > >> Any idea? Maybe the unofficial patches? > > have you made sure ztcfg is only run once? Moreover 1.0.4-2 is obsolete > if you use zaptel 1.0.6 and asterisk 1.0.6 with it. Yet the most likely > to cause this is loading the module and running ztcfg twice. > I have a E100p (1xE1) car

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-15 Thread Kilian Krause
Hi Andres, > Any idea? Maybe the unofficial patches? have you made sure ztcfg is only run once? Moreover 1.0.4-2 is obsolete if you use zaptel 1.0.6 and asterisk 1.0.6 with it. Yet the most likely to cause this is loading the module and running ztcfg twice. -- Best regards, Kilian signature.

Bug#299583: libpri1: D-Channel stop working when upgrading to 1.0.4-1 to 1.0.4-2

2005-03-14 Thread Andres Junge
Package: libpri1 Version: 1.0.4-1 Severity: normal After I have upgraded to libpri-1.0.4-1 d-channel stop working. The asterisk log showed: Mar 14 17:34:51 NOTICE[24544]: PRI got event: No more alarm (5) on Primary D-channel of span 1 Mar 14 17:34:51 WARNING[24544]: No D-channels available! Usi