[asterisk-r2] Problem with Parse zapata.conf

Tue Jan 13 09:07:29 CST 2009

Hi Moises ...

Thanks .. I understood wrong the guide in the part

"... will be applied to (just like zapata.conf or chan_dahdi.conf)"

But, thanks for your answer.

Now everything is clear to me.

Moises Silva escreveu:
> Eduardo,
>
> The section you are reading in the guide is about r2test.conf, the
> configuration used by the r2test program that is included with the
> library, not the configuration of Asterisk. Having said that, most
> concepts apply to the Asterisk chan_zap or chan_dahdi configuration as
> well, but the parsing of the file is certainly not the same, the
> parsing of r2test.conf is more simplistic.
>
> Now, regarding your question. The only limitation for Asterisk 1.2 and
> 1.4 is that for each comma or new channel => parameter, new internal
> R2 structure is created and this is limited to something around 32.
> Therefore, if you put
>
> channel=>1,2,3,4,5 ..... up to 32 you will run out of r2 structures.
>
> the same if you put
>
> channel=>1
> channel=>2
> channel=>3
> channel=>4
> .
> .
> .
> channel=>32
>
> However, is just a waste of space, as long as you group together the
> channels that can be grouped, I doubt you will ever run out of R2
> internal structures. As far as the R2 support is concerned, the
> following is exactly the same:
>
> channel=>1-5,9,17-31
>
> and
>
> channel=>1-5
> channel=>9
> channel=>17-31
>
> In both situations will create three R2 internal structures.
>
> Moy
>
> On Tue, Jan 13, 2009 at 8:06 AM, Eduardo Lobo Blanco
> <eduardo at spacecom.com.br> wrote:
>   
>> Hi ...
>>
>> I was reading the openr2 guide, and there i found this:
>>
>> "The "channel" parameter *must* be in the format "x-y" to specify the
>> range of channels for
>> which the previous configuration parameters will be applied to (just
>> like zapata.conf or
>> chan_dahdi.conf). If you just need 1 channel you must specify it like
>> "channel=1-1" (yeah, it
>> sucks but is the way currently works, patches accepted)."
>>
>> So, if i need to configure the channels not sequencially .. like channel
>> 1-5 then channel 9 , then channel 17-31
>>
>> what the best way to use in zapata.conf ??
>>
>> channel => 1-5,9-9,17-31
>>
>> or withou the commas like
>>
>> channel => 1-5
>> channel => 9-9
>> channel => 17-31
>>
>> I'm asking that because i'm developing an interface that will generate
>> the zapata.conf,
>> then it will be up to client to determine what channels to use.
>>
>> Thank's again !!
>>
>>
>>
>>
>> Eduardo Lobo Blanco escreveu:
>>     
>>> Ok Moises...
>>>
>>> Thanks for your answer !!
>>>
>>> Moises Silva escreveu:
>>>
>>>       
>>>> This is a known limitation that I haven't had the time to fix for 1.2
>>>> and 1.4. Only the patch for 1.6 or the 1.6 branch works well with such
>>>> configuration.
>>>>
>>>> Moy
>>>>
>>>> On Mon, Jan 12, 2009 at 1:59 PM, Eduardo Lobo Blanco
>>>> <eduardo at spacecom.com.br> wrote:
>>>>
>>>>
>>>>         
>>>>> 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
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> --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
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - http://www.avg.com
>>>> Version: 8.0.176 / Virus Database: 270.10.6/1888 - Release Date: 1/12/2009 7:04 AM
>>>>
>>>>
>>>>
>>>>         
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.10.6/1888 - Release Date: 1/12/2009 7:04 AM
>>>
>>>
>>>       
>> --
>> Abraços ...
>>
>> Eduardo Lobo Blanco
>> Spacecom Tecnologia e Comunicações LTDA.
>> eduardo at spacecom.com.br
>>
>>
>> _______________________________________________
>> --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
>>
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.176 / Virus Database: 270.10.6/1891 - Release Date: 1/13/2009 8:17 AM
>
>   

-- 
Abraços ...

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