[arm-allstar] Hub Node rpt.conf Configuration Questions
Mike - W5JR
w5jr.lists at gmail.com
Tue Jul 12 10:35:28 EST 2016
Andrew, I often create iax/Zoiper access to my hub nodes so that I can control/monitor them directly if needed. Think allowing telemetry on the hub (for as long as you can stand it) but not a radio node. As such, since I may be connected for long periods without activity on the channel, I've programmed IDs in beacon mode to periodically remind me that I'm connected. These obviously don't propagate down system, so they may not even be callsigns, just a representative pneumonic.
I *think* duplex still determines whether you have mix audio or first come, first heard, but I've not ever set my hubs to duplex=0.
tnx
Mike / W5JR
Alpharetta GA
> On Jul 12, 2016, at 10:03 AM, Andrew Sylthe via arm-allstar <arm-allstar at hamvoip.org> wrote:
>
> Hello Everyone,
>
> I have a working Hub Node configured as a second node on a RPi3 with the following pertinent configuration options in rpt.conf:
>
> rxchannel=dahdi/pseudo
> duplex=0
> ;idrecording=
> ;idtalkover=
>
> Does anyone happen to know if it even matters what you set duplex= as, or if you'd even need to uncomment and set the idrecording and idtalkover configuration options? I can't think of any reasons why you would need to, but am asking these questions in case I'm missing something. The Hub Node doesn't have a directly connected radio. My thoughts are, then why would you need the Hub Node to identify or provide telemetry. I tried searching Google & the mailing list archives for earlier discussions on the topic, but couldn't find anything.
>
>
> All comments are welcome, Thanks!
>
> --
> Andrew Sylthe
> KC9ONA
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160712/88bdeda3/attachment.html>
More information about the arm-allstar
mailing list