-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Totaro wrote:
> Matt Riddell wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Steve Totaro wrote:
>>
>>> Matt Riddell wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Schall wrote:
>
Matt Riddell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Steve Totaro wrote:
>
>> Matt Riddell wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Rob Schall wrote:
>>>
>>>
We've experienced the same problem twice now in the past month. Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Totaro wrote:
> Matt Riddell wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Rob Schall wrote:
>>
>>> We've experienced the same problem twice now in the past month. The
>>> asterisk pid stops responding. We aren't able to con
Matt Riddell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Rob Schall wrote:
>
>> We've experienced the same problem twice now in the past month. The
>> asterisk pid stops responding. We aren't able to connect to the CLI and
>> all calls are dropped. The lots are pretty bare as we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Schall wrote:
> We've experienced the same problem twice now in the past month. The
> asterisk pid stops responding. We aren't able to connect to the CLI and
> all calls are dropped. The lots are pretty bare as well.
> Asterisk 1.2.13-r1
Unfortuna
We've experienced the same problem twice now in the past month. The
asterisk pid stops responding. We aren't able to connect to the CLI and
all calls are dropped. The lots are pretty bare as well.
This is the message log:
Oct 24 09:12:35 WARNING[20711] channel.c: Avoided initial deadlock for
'0x84