[asterisk-r2] Dahdi configuraion / error

Tue Sep 1 08:31:46 CDT 2009

Hi Joao, good morning

An alarm is a response to an error on the E1 line or framing. Three of
the conditions that cause alarms are loss of frame alignment (LFA),
loss of multi-frame alignment (LFMA), and loss of signal (LOS).

The LFA condition, also called an out-of-frame (OOF) condition, and
LFMA condition occur when there are errors in the incoming framing
pattern. The number of bit errors that provokes the condition depends
on the framing format. The LOS condition occurs when no pulses have
been detected on the line for between 100 to 250 bit times. This is
the highest state alarm where nothing is detected on the line. The LOS
may occur when a cable is not plugged in or the far end equipment,
which is the source of the signal, is out of service.

The alarm indication signal (AIS) and remote alarm indication (RAI)
alarms are responses to the LOS, LFA, and LFMA conditions. The RAI
alarm is transmitted on LFA, LFMA, or LOS. RAI will be transmitted
back to the far end that is transmitting frames in error. The AIS
condition is a response to error conditions also. The AIS response is
an unframed all 1's pattern on the line to the remote host. It is used
to tell the far end it is still alive.

AIS is the blue alarm, RAI is the yellow alarm. A red alarm that can
occur after a LFA has existed for 2.5 seconds. It is cleared after the
LFA has been clear for at least one second.

On Tue, Sep 1, 2009 at 10:17 AM, Joao Gomes
Pereira<gomespereira at startel.pt> wrote:
>
> Hello
> I just updated the kernel, dahdi-linux and dahdi-tools
> Im also using now asterisk 1.4.26.1
>
> And im still with a red light (not RED/YELLOW anymore):
>
> [root at catumbela ~]# /etc/rc.d/init.d/dahdi status
> ### Span  1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) HDB3/ RED
>

Red Alarm is a hardware problem

> Here is my config:
> /etc/dahdi/system.conf ------------------------------
>
> loadzone = us
> defaultzone=us
>
> span=1,1,0,cas,hdb3
> cas=1-15:1101
> dchan=16
> cas=17-31:1101
>
>
> Sep  1 13:56:14 catumbela kernel: TE4XXP: Span 1 configured for CAS/HDB3
> Sep  1 13:56:14 catumbela kernel: wct4xxp: Setting yellow alarm on span 1
>
> here is dmesg:
>
> [root at catumbela ~]# dmesg
> ...
> TE4XXP: Span 1 configured for CAS/HDB3
> timing source auto card 0!
> wct4xxp: Setting yellow alarm on span 1
> SPAN 1: Primary Sync Source
>
> Could this be a configuration issue or a hardware problem?
>
>
> Thanks
> regards
> Joao Pereira
>
>
> --
> StarTel - A Rede Livre
> Joao Gomes Pereira
> www.startel.pt
> +351 304500650
> sip: gomespereira at startel.pt
>
> _______________________________________________
> --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
>

-- 
Alexandre C Alencar (Skarmeth)
http://blog.alexandrealencar.net/
http://www.alexandrealencar.net/
http://people.debian-ce.org/skarmeth/