[Gelöst]Detected alarm on channel 22: Red Alarm

[VOIPdani]

Hallo Forum!

Grad ist mir bei meinem * folgende Fehlermeldung aufgefallen:

Mar 20 08:40:12 VERBOSE[11614] logger.c:     -- Called g1/0042337xxxxx
Mar 20 08:40:16 WARNING[11614] chan_zap.c: [B]Detected alarm on channel 22: Red Alarm[/B]
Mar 20 08:40:16 WARNING[9393] chan_zap.c: [B]Detected alarm on channel 23: Red Alarm[/B]
Mar 20 08:40:16 WARNING[9393] chan_zap.c: Unable to disable echo cancellation on channel 23
Mar 20 08:40:16 NOTICE[9392] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
Mar 20 08:40:16 WARNING[9392] chan_zap.c: No D-channels available!  Using Primary channel 24 as D-channel anyway!
Mar 20 08:40:16 NOTICE[9392] chan_zap.c: pri_shutdown
Mar 20 08:40:16 VERBOSE[11614] logger.c:     -- Hungup 'Zap/22-1'
Mar 20 08:40:16 VERBOSE[11614] logger.c:   == No one is available to answer at this time (1:0/0/0)
Mar 20 08:40:16 NOTICE[9393] chan_zap.c: Alarm cleared on channel 22
Mar 20 08:40:16 NOTICE[9393] chan_zap.c: Alarm cleared on channel 23
Mar 20 08:40:16 NOTICE[9392] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
Mar 20 08:40:16 VERBOSE[11614] logger.c:     -- Executing Hangup("Zap/8-1", "") in new stack
Mar 20 08:40:16 VERBOSE[11614] logger.c:   == Spawn extension (ISDN-IN-KAPSCH, 004233776747, 3) exited non-zero on 'Zap/8-1'
Mar 20 08:40:16 VERBOSE[11614] logger.c:     -- Hungup 'Zap/8-1'
Mar 20 08:40:27 VERBOSE[9387] logger.c:     -- Accepting overlap voice call from '21' to '<unspecified>' on channel 0/2, span 3
Mar 20 08:40:27 VERBOSE[11631] logger.c:     -- Starting simple switch on 'Zap/8-1'
Mar 20 08:40:31 VERBOSE[11631] logger.c:     -- Executing SetCallerID("Zap/8-1", "72363xxxxx") in new stack
Mar 20 08:40:31 VERBOSE[11631] logger.c:     -- Executing Dial("Zap/8-1", "Zap/g1/0042337xxxxx") in new stack
Mar 20 08:40:31 VERBOSE[11631] logger.c:     -- Requested transfer capability: 0x00 - SPEECH
Mar 20 08:40:31 VERBOSE[11631] logger.c:     -- Called g1/0042337xxxxx
Mar 20 08:40:34 VERBOSE[11615] logger.c:     -- SIP/RiTa-3657 answered Zap/2-1
Mar 20 08:40:35 WARNING[11631] chan_zap.c: Detected alarm on channel 22: Red Alarm
Mar 20 08:40:35 VERBOSE[11631] logger.c:     -- Hungup 'Zap/22-1'
Mar 20 08:40:35 VERBOSE[11631] logger.c:   == No one is available to answer at this time (1:0/0/0)
Mar 20 08:40:35 WARNING[9393] chan_zap.c: Detected alarm on channel 23: Red Alarm
Mar 20 08:40:35 WARNING[9393] chan_zap.c: Unable to disable echo cancellation on channel 23
Mar 20 08:40:35 NOTICE[9393] chan_zap.c: Alarm cleared on channel 22
Mar 20 08:40:35 NOTICE[9393] chan_zap.c: Alarm cleared on channel 23
Mar 20 08:40:35 NOTICE[9392] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
Mar 20 08:40:35 WARNING[9392] chan_zap.c: No D-channels available!  Using Primary channel 24 as D-channel anyway!
Mar 20 08:40:35 NOTICE[9392] chan_zap.c: pri_shutdown
Mar 20 08:40:35 NOTICE[9392] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
Mar 20 08:40:35 VERBOSE[11631] logger.c:     -- Executing Hangup("Zap/8-1", "") in new stack

Kann mir jemand sagen was diese Fehlermeldung bedeuted?

Hier auch noch meine zapata.conf:

[channels]
language=de
switchtype = euroisdn
pridialplan = unknown
prilocaldialplan = national
nationalprefix = 0
internationalprefix = 00
overlapdial = yes

; TE mode ... fuer ISDN Amtsleitungen
context=ISDN-IN-AMT
group = 1
signalling = bri_cpe
echocancel = yes
; S/T port 1, 2, 8
channel => 1-2
channel => 4-5
channel => 22-23

pridialplan = local
prilocaldialplan = unknown

; NT mode ... fuer Kapsch als Slave
context=ISDN-IN-KAPSCH
group = 2
signalling = bri_net
echocancel = no
echocancelwhenbridged = no
; S/T port 3, 4, 5, 6, 7
channel => 7-8
channel => 10-11
channel => 13-14
channel => 16-17
channel => 19-20

PS: Ich hoffe meine octoBRI ist nicht defekt?!

lg Dani

 

[Maik]

Evtl. hat das Kabel nen Wackler oder du hast es mal kurz rausgezogen. Kannst es ja mal mit nem anderen probieren.

 

[VOIPdani]

Problem behoben

Evtl. hat das Kabel nen Wackler oder du hast es mal kurz rausgezogen. Kannst es ja mal mit nem anderen probieren.

Du hast recht, das Kabel war tatsächlich die Fehlerquelle. Danke für deine schnelle Antwort.

lg Dani