[asterisk-r2] Problem with Parse zapata.conf

Mon Jan 12 12:59:28 CST 2009

Hello list,

I'm having a problem with zapata.conf when i'm configuring the channels.

I have two E1 using asterisk 1.4.22, zaptel 1.4.12.1

I would like to use this sintax in zapata.conf:

channel => 
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31

channel => 
32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62

but when i start the asterisk, the log file show me:

[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
1: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
2: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
3: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
4: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
5: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
6: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
7: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
8: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
9: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
10: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
11: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
12: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
13: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
14: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
15: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
17: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
18: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
19: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
20: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
21: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
22: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
23: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
24: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
25: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
26: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
27: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
28: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
29: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
30: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
31: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
32: Red Alarm
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
33: Red Alarm
[Jan 12 16:48:30] ERROR[15135] chan_dahdi.c: No more R2 links available!.
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Cannot get another R2 
DAHDI context!
[Jan 12 16:48:30] WARNING[15135] chan_dahdi.c: Detected alarm on channel 
34: Red Alarm

The Red Alarm is not the problem because my link is really down..
the problem is the 3 last messages ... this messages apears to all the 
rest of the channels, for channels 34 until 62.
in asterisk the command "mfcr2 show channels" show me channel 1 to 33.

But. when i change the sintax in zapata.conf for something like

channel => 1-15,17-31
channel => 32-46,48-62

its work normally ..

I tried some others sintax, and some time it's works and sometime it's 
not ..

Does any onde know if it there is a correction for that ?

-- 
Abraços ...

Eduardo Lobo Blanco
Spacecom Tecnologia e Comunicações LTDA.
eduardo at spacecom.com.br