[arm-allstar] ARM-allstar Digest, Vol 90, Issue 16
Jeff Karpinski
jeff at 3d0g.net
Sat Nov 20 13:17:56 EST 2021
Yeah, I thoroughly tested all those. The pseudo device doesn't honor any of those settings.
> On Nov 20, 2021, at 9:22 AM, Patrick Perdue via ARM-allstar <arm-allstar at hamvoip.org> wrote:
>
> I haven't done this in a long time, but at least with ASL, it is possible to set the local and foreign telemetry separately, so, for example, if someone connects to your repeater directly, you'll hear about it, but not if someone connects to the hub node your repeater is connected to. This may be a reasonable compromise depending on what you're doing.
>
> NOTE: I haven't tried this with HamVOIP and don't remember how to do it off-hand.
>
> cop 33, 34 and 35 change the behavior of local telemetry, while 36 through 39 change the behavior of foreign link telemetry.
>
> So, for example, cop 33 and cop 37 together should, in theory, enable local telemetry and disable foreign link local output path telemetry.
>
> YMMV. Posted without warranty, expressed or implied, etc. blah blah.
>
> On 11/20/2021 9:48 AM, "Jeff Karpinski via ARM-allstar" wrote:
>> duplex = 3 and holdofftelem = 0 made no difference. Only (suboptimal) solution was to disable telemetry at the endpoints.
>>
>>> On Nov 19, 2021, at 8:31 PM, Steve L via ARM-allstar <arm-allstar at hamvoip.org> wrote:
>>>
>>> Try;
>>> duplex = 3
>>>
>>> On Fri, Nov 19, 2021, 9:01 PM "Jeff Karpinski via ARM-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>>> Node in question is a radioless hub running on a VPS. I'll try changing
>>>> holdofftelem but that's rather counter-intuitive.
>>>>
>>>> I'm pretty sure Patrick got it right and this is a limitation of the ASL
>>>> pseudo node.
>>>>
>>>>> On Nov 19, 2021, at 7:27 PM, Mark VE3JMR via ARM-allstar <
>>>> arm-allstar at hamvoip.org> wrote:
>>>>> Jeff;
>>>>>
>>>>> The answer in your question: "Majority of the members (and repeaters)
>>>>> are running HamVoIP with zero issues."
>>>>>
>>>>> Try changing holdofftelem to 0.
>>>>>
>>>>> Also, is your install on an RPi? Do you use the n node only as an
>>>>> Allstar node or also as the repeater's controller?
>>>>>
>>>>> -------------------------------------
>>>>> Message: 2
>>>>> Date: Fri, 19 Nov 2021 11:54:00 -0700
>>>>> From: Jeff Karpinski <jeff at 3d0g.net>
>>>>> To: ARM Allstar <arm-allstar at hamvoip.org>
>>>>> Subject: [arm-allstar] Radioless hub telemetry
>>>>> Message-ID: <8753CA16-E911-49B5-A53D-8D81CBB421FF at 3d0g.net>
>>>>> Content-Type: text/plain; charset=us-ascii
>>>>>
>>>>> Apologies in advance for talking about AllStarLink but I'm hoping some
>>>>> of you have crossed this bridge before.
>>>>>
>>>>> We've got a VPS based hub node, (running AllStarLink, obviously) that's
>>>>> used to aggregate connections from our repeaters. We also allow members
>>>>> to link their own personal nodes to the hub. Majority of the members
>>>>> (and repeaters) are running HamVoIP with zero issues.
>>>>>
>>>>> Problem is, for the life of me, I cannot get the hub to shut up. It
>>>>> voice announces every single connect and disconnect into it back out to
>>>>> all nodes. As AllStar's popularity has grown in the club, the number of
>>>>> nodes has exploded and it's hugely annoying to the repeater users
>>>>> hearing connect / disconnect messages constantly.
>>>>>
>>>>> Soo, anyone been down this path before? Here's the pertinent bits from
>>>>> the hub rpt.conf. I could also post the whole damn thing to pasebin if
>>>>> it helps.
>>>>>
>>>>> duplex = 2
>>>>> linktolink = no
>>>>> hangtime = 0
>>>>> althangtime = 0
>>>>> telemdefault = 0
>>>>> holdofftelem = 1
>>>>> telemdefault = 0
>>>>> telemdynamic = 0
>>>>> nounkeyct = 1
>>>>> ; idrecording = |ie
>>>>> ; idtalkover = |ie
>>>>>
>>>>> 73 75 de VE3JMR
>>>>> Mark
>>>>> Port Colborne, Ontario
>>>>> CANADA
>>>>> https://www.qrz.com/db/VE3JMR
>>>>> Allstar Node# 53132 [1]
>>>>> Echolink Node# 736666
>>>>>
>>>>> LIFE has an expiry date.
>>>>> <if trumpet=%true then exit function>
>>>>>
>>>>> Links:
>>>>> ------
>>>>> [1] http://stats.allstarlink.org/stats/53132
>>>>> _______________________________________________
>>>>>
>>>>> 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/4 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/4 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/4 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/4 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/4 web page - http://hamvoip.org
More information about the ARM-allstar
mailing list