On Mon, 23 Oct 2006, Klaus Darilion wrote:
> Hi!
>
> This weekend we had a problem with our Asterisk Box which ran flawlessly for
> nearly 4 weeks. The Asterisk server sits between the PSTN and a Siemens PBX
> and bridges 2 BRI lines. No calls, not incoming, not outgoing. The admin
> rebooted the
Hi Klaus.
I'm not sure about the timer expiry meaning,
but you could use the xlog command (usually found
in /usr/lib/eicon/divas)
Just run it as root indicating which span (1..4)
you want to trace:
./xlog -c 2
that shoud show you layer 1 & layer 2
dump
Alberto.
Klaus Darilion ha scritto:
Hi
Hi!
This weekend we had a problem with our Asterisk Box which ran flawlessly
for nearly 4 weeks. The Asterisk server sits between the PSTN and a
Siemens PBX and bridges 2 BRI lines. No calls, not incoming, not
outgoing. The admin rebooted the Dell Box and then everything worked
fine again.
On Mon, 2004-07-12 at 23:53, Andreas Bayer wrote:
> Hi,
>
> i have a debian-system with the asterisk 1:0.9-1 packages and chan-capi
> 0.3.1-2 installed.
>
> My chan-capi seems to be out-of-order.
>
> Capi and I4l work in general.
> I can use isdnlog and capi4hylafax.
> Using chan_modem_i4l with
Hi,
i have a debian-system with the asterisk 1:0.9-1 packages and chan-capi
0.3.1-2 installed.
My chan-capi seems to be out-of-order.
Capi and I4l work in general.
I can use isdnlog and capi4hylafax.
Using chan_modem_i4l with the sam context work fine too.
But no incoming calls are answered by
