Re: Current Best-Practices for Linking with Brandmeister
Its not a hardware problem. Only 2 channels are being used. With the third not being used. That's where the problem lies. You need a pair.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Friday, December 18, 2020 3:12:06 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Current Best-Practices for Linking with Brandmeister
Though I am using DVSwitch for part of my bridge, the way I'm hosting things now is that XLXD itself is acting as a YSF reflector, compiled with changes to the source to autolink module A to the room. The YSF reflector Registry officially supports XLXD now, so I don't need to run a separate service to host YSF. Thus, MMDVM_Bridge isn't needed to make that connection. I am using HBlink connected to 4001 to bridge from XLX to both the regular and prime TGIF servers, then DVSwitch to connect that to ASL, but BM, YSF and DStar are not using DVSwitch to make any part of that connection. I have a pair of ThumbDV's connected remotely (XLXD lives on a nearby VPS, two dongles are connected to a repurposed 2011 Mac Mini running Stretch in my house) and I can go months without restarting anything.
If my home internet goes down, which rarely happens, transcoding to/from DStar is messed up until the connection is re-established, but everything else is fine. I don't have to manually do anything to make that happen.
If I do need to restart a service, say, to upgrade the DVSwitch binaries or something like that, only the connection between the digital modes and ASL is broken for the duration.
Not saying this is necessarily the best solution, but it works for me.
On 12/18/2020 8:59 AM, Ernie Gm7kbk wrote: