[arm-allstar] Whitelist 1 node - Same Server?

Doug Crompton wa3dsp at gmail.com
Fri Apr 5 14:46:47 EDT 2019


Yes,  OK you need to select  context=radio-secure  in the radio stanza of
iax.conf.  I did not see that mentioned in your original message. Keep in
mind that if anyone wants to do this that messing with the config files can
really break things! Make backups before you make any changes so you can go
back!

There is also only one white or black list database so the way it is
structured now you can't have a different white list for different nodes or
a different blacklist for different nodes on the same server.

In reality doing this all in the extensions file is a better way to do it
as long as you are aware of its limitations BUT we are not advocating
changing this except in special cases where you really want to specifically
allow or deny an incoming node by local node number on a server. I think
this is a special case.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Fri, Apr 5, 2019 at 2:21 PM Doug Crompton <wa3dsp at gmail.com> wrote:

> I don't think this will work since iax,conf directly calls the white,
> black, or radio context depending on the users desire. ALL traffic would
> then go through the one selected. The decision is made before it gets to
> the extensions file.
>
> [radio]
> type=user
> disallow=all
> allow=g726aal2
> allow=ilbc
> allow=ulaw
> ;allow=gsm
> codecpriority=host
> ; **** Select one and only one of the next three lines ****
> ;context=radio-secure
> context=blacklist
> ;context=whitelist
> transfer=no
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Fri, Apr 5, 2019 at 11:04 AM "David McGough via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>>
>>
>> Sean,
>>
>> Yes, fairly easy to do.  In your extensions.conf file,
>> you've got a [radio-secure] stanza that looks something like this. Note
>> that the 23455, 23456 and 23457 are 3 nodes on the same box:
>>
>>
>> [radio-secure]
>> exten => 23455,1,rpt,23455|X
>> exten => 23456,1,rpt,23456|X
>> exten => 23457,1,rpt,23457|X
>>
>>
>> Change this to be something like this, where node 23456 goes through the
>> "whitelist":
>>
>> [radio-secure]
>> exten => 23455,1,rpt,23455|X
>> exten => 23456,1,Goto(whitelist|s|1)
>> exten => 23457,1,rpt,23457|X
>>
>>
>> [whitelist]
>> exten => s,1,NoOp(${CALLERID(num)})
>> exten => s,n,NoOp(${IAXPEER(CURRENTCHANNEL)})
>> exten => s,n,GotoIf($["${IAXPEER(CURRENTCHANNEL)}" =
>> "127.0.0.1"]?radio-secure,${EXTEN},1)  ;permit local IPs
>> exten =>
>> s,n,GotoIf($[${DB_EXISTS(whitelist/${CALLERID(num)})}]?radio-secure,${EXTEN},1)
>> exten => s,n,Hangup
>>
>>
>>
>> I HAVEN'T ACTUALLY TRIED THIS! So, my syntax may not be quite perfect!
>> I'll try it later today, if someone else doesn't beat me to it....But,
>> this is the basic idea.
>>
>>
>> 73, David KB4FXC
>>
>>
>>
>>
>> On Fri, 5 Apr 2019, "Sean McCarthy via ARM-allstar" wrote:
>>
>> > Should have clearly stated, the server has 2 nodes, I would like a
>> > whitelist on only one of those nodes.
>> >
>> > Thanks,
>> > Sean
>> >
>> > On Fri, Apr 5, 2019 at 9:19 AM Sean McCarthy <smccarthy61 at gmail.com>
>> wrote:
>> >
>> > > Is there any way to set up iax.conf and extensions.conf for a
>> whitelist
>> > > that only affects one node on the same server?
>> > >
>> > > Thanks,
>> > > Sean
>> > >
>> > _______________________________________________
>> >
>> > ARM-allstar mailing list
>> > ARM-allstar at hamvoip.org
>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> >
>> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> >
>>
>> _______________________________________________
>>
>> ARM-allstar mailing list
>> ARM-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>


More information about the ARM-allstar mailing list