asterisk users - Nov 2008 - TE410P alarms stay RED with 1.4.22

Hi,

I tried "upgrading" from debian's 1.4.21.2 package to vanilla
1.4.22 but
then my TE410P alarms stay RED and no zap channels can be created, even
if they are correctly listed by "zap show channels". I tried adding
"dahdichanname = no" to asterisk.conf's [options] to no effect.

Going back to 1.4.21.2 brings my alarms back to OK.

This is with zaptel 1.4.12.1.

-- 
http://www.critikart.net

Bonjour Louis-David,

Asterisk envoie-t-il le signal au boitier pour le failover ?

Laurent



Le 11 nov. 08 ? 08:49, Louis-David Mitterrand <vindex+lists-asterisk-users at
apartia.or
g> a ?crit :
> Hi,
>
> I tried "upgrading" from debian's 1.4.21.2 package to vanilla
1.4.22
> but
> then my TE410P alarms stay RED and no zap channels can be created,  
> even
> if they are correctly listed by "zap show channels". I tried
adding
> "dahdichanname = no" to asterisk.conf's [options] to no
effect.
>
> Going back to 1.4.21.2 brings my alarms back to OK.
>
> This is with zaptel 1.4.12.1.
>
> -- 
> http://www.critikart.net
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

On Tue, Nov 11, 2008 at 09:49:14AM +0100, Louis-David Mitterrand
wrote:
> Hi,
> 
> I tried "upgrading" from debian's 1.4.21.2 package to vanilla
1.4.22 but
> then my TE410P alarms stay RED and no zap channels can be created, even
> if they are correctly listed by "zap show channels". I tried
adding
> "dahdichanname = no" to asterisk.conf's [options] to no
effect.
> 
> Going back to 1.4.21.2 brings my alarms back to OK.
OK false alarm here: we use an isdnguard device that needs an additional
res_watchdog.c file (bristuff patch). Once added it works.

Let's hope 1.4.22 will solve our random crashes and system resources
hogging...

-- 
http://www.critikart.net