[App_rpt-users] Setting up a permanent radio-IP-radio setup

[Doug Kingston]

Maybe answering my own question...

Do these commands from
https://allstarlink.org/portal/dtmf_functionlist.php?node=2001 let me set
up the permanent link as I described?

*951  =>   Permanent Link Disconnect
*952  =>   Permanent Link Connect (Monitor Only)
*953  =>   Permanent Link Connect

"Permanent" Links are links that are intended to be up all the time. The
connection will be maintained constantly, unless explicitly disconnected
with the Permanent Link Disconnect function (*953). A Permanent Link can
not be disconnected with the standard Link Disconnect (*1) function.


Assuming this is the case, what other changes do I need for authentication,
etc.

My guess is:
1) add entry to [nodes] section at bottom of rpt.conf
2) put <something> in iax.conf on the destination node (not the one issuing
the commands above) to permit the calling node to access.


On Sun, Apr 30, 2017 at 1:57 PM, Doug Kingston <dpk at randomnotes.org> wrote:

> Bob,
>
> By back-to-back, I mean radio in location 1 hooked to allstar node
> (private) to IP to allstar node (also private) in location 2 to radio.  The
> idea is to connect a shadowed area to
> Both locations have internet connectivity - they just don't have radio
> connectivity.
> We want the nodes to link up automatically on startup and to attempt to
> reconnect if disconnected.
>
> You mentioned using the [nodes] but also had a reference to content in the
> iax.conf file.  Do you have an example we could use as a reference?
> I can see the sample for connecting periodically from cron in
> /etc/asterisk/local, but what if I want a permanent, reconnecting link?
>
> -Doug-
>
>
> On Sun, Apr 30, 2017 at 10:55 AM, Bob Pyke <k6ecm1 at gmail.com> wrote:
>
>> Doug,
>>
>> What do you mean, back-to-back? Is it your intent to link a group of
>> private nodes? What is your network situation? IOW, does the remote node(s)
>> have internet connectivity? Linking private nodes on the internet need to
>> know where each other ar located (think IP address). This is setup in the
>> [nodes] stanza in rpt.conf, where each <IP address>:<bindport from iax.conf>
>>
>> Thanks,
>> Bob
>> k6ecm
>> 73
>>
>> Sent from iPad
>>
>>
>> On Apr 30, 2017, at 10:04 AM, Doug Kingston <dpk at randomnotes.org> wrote:
>>
>> I am helping another ham to set up a back-to-back remote base setup to
>> help provide communication to a shaded area for a public service event.  We
>> have a working remote base setup with hamvoip.org distribution and now
>> want to hook two of these back to back.  I am helping with the Linux
>> knowledge and got the current remote base working.  I am looking for some
>> pointers about how to do this, and timing is short.  We need this running
>> in 2 weeks.  Here's his request in his own words:
>>
>>> I’ve got an event the first weekend of June that I want the linked radio
>>> system for, so that is kind of what is driving my “rush”.
>>>
>>> I would like to take the basic (final) software setup/configuration for
>>> ASC-North and archive it so we always have that foundation. (Doesn’t need
>>> to be by June 1).
>>>
>>> I would like to learn how to modify that foundation to create a
>>> different remote base. Different Asterisk Name (1998, 1997, 1996, etc.),
>>> and whatever other changes are necessary so an independent base can be
>>> established. (Doesn’t need to be by June 1).
>>>
>>> I would like to set up two Pi’s with the USB interface and radios, so
>>> they automatically, and exclusively, talk to each other. One I imagine
>>> (I’ll call the primary base) would have to broadcast it’s IP (dyndns), the
>>> other (I’ll call remote) would need to want to connect to that.  This is
>>> the need for the start of June. I have all of the needed hardware for both
>>> stations (Pi, USB interface, radio). This specific request is totally
>>> unrelated to ACS, but is in support of Special Olympics Washington Spring
>>> Games, which are being conducted June 2, 3, 4 (and will probably be on
>>> non-amateur radios/frequencies). They operate multiple venues which this
>>> year are more geographically separated than they have been in the past, and
>>> we’ll no longer be able to utilize simplex to talk between them. No
>>> reasonable repeater option is available and putting up a temporary one is
>>> all but impossible as it would have to be on JBLM someplace.
>>>
>>> Once this is set up, but not necessarily immediately, I would like to
>>> know the specific programming for these that could be changed to add
>>> another unique pair, or to add another single (remote) radio as a link to
>>> the primary base.
>>
>>
>> Any pointers would be most appreciated.  I assume this will require
>> defining some sort of default call, but I am new to asterisk.
>>
>> -Doug-, KD7DK
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit http://lists.allstarlink.org/c
>> gi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
>> the page. Enter your email address and press the "Unsubscribe or edit
>> options button"
>> You do not need a password to unsubscribe, you can do it via email
>> confirmation. If you have trouble unsubscribing, please send a message to
>> the list detailing the problem.
>>
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit http://lists.allstarlink.org/c
>> gi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
>> the page. Enter your email address and press the "Unsubscribe or edit
>> options button"
>> You do not need a password to unsubscribe, you can do it via email
>> confirmation. If you have trouble unsubscribing, please send a message to
>> the list detailing the problem.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20170430/1569c74c/attachment.html>