Sure, but I'm currently going through two of them to get from Allstar to DStar. I'm just wondering if there's a way to drop one of them out and still maintain metadata. I could directly connect A_B an

I'm not great at writing out flows. My setup currently doesn't use ircDDBGateway, since that's all handled at the XLX reflector end. So, it goes like this. Allstar <-> AB <-> HBLink <-> MB <-> XLXD (D

OK, so things are pretty much as I thought they were. Just wanted to make sure I wasn't missing anything should I decide to redesign this system. I'll probably keep things as-is for now, then add anot

You only need to change the password=passw0rd line in the [DMR Network] stanza of MMDVM_Bridge.ini for any DVSwitch instance, replacing it with the hotspot security password you've set up on the Brand

As I understand it, you can set up a private P25 reflector which is available to anyone who uses the pi-star host files, thus, no need to link to a public reflector. This is what I plan to do. I will

Yes, that's what I was referring to. I don't know what the process is for having your reflector listed, only that it can be done.

Hi: I'm sure this has been brought up before. I have a system using DVSwitch, which involves an XLX reflector. Currently, the XLX module to which DVSwitch is connected is also configured as an autolin

Hi: I'm trying to find a way to limit transmission time from digital to analog. Lately, I've had users experimenting with Peanut and BlueDV continuously transmitting for long periods of time without r

Hi Steve: Thanks. Yeah, I thought it should work the same as any other channel driver, so I changed it to a ridiculously low number (10000), and transmissions over 10 seconds across the bridge still p

The cheap and easy solution would be to just use a personal CCS7 ID as a group call for all participants (not exactly private), or just anything that isn't being used and won't make people mad, on a p

I’m adjusting it on the USRP node. For now, I wrote a cheap shell script that is called only when the USRP node is keying towards ASL, which sleeps for a while, mutes both TLV and USRP. Then another s

A couple of things: In my experience, requesting an XLX interlink to your reflector from a Brandmeister master server works pretty well. They would prefer you do it that way or use OpenBridge. In my s

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.

Definitely looking forward to this, especially if you can do something like referencing the Allstarlink node database and matching to ID's, if they exist. Of course, there is a lot of room for error,

Make sure the lines starting with idrecording and idtalkover are either commented out or don't exist in /etc/asterisk/rpt.conf under the stanza for the node where your DMR bridge lives. You may also w

#analog_bridge #mmdvm_bridge

Just comment the line out entirely. It isn't needed. Not even a dit.

#analog_bridge #mmdvm_bridge

No, it definitely won't even try to send an ID if that line is commented out, so there's really no point in having it there in the first place on a USRP bridge.

#analog_bridge #mmdvm_bridge

And I can tell you from experience, having done it on four different bridges, that it doesn't do anything at all if idrecording and idtalkover aren't defined. I originally used your example because I

#analog_bridge #mmdvm_bridge

That's just a default example which was never changed to something useful by whoever installed that node.

#analog_bridge #mmdvm_bridge

Yes, that is the example string used in HamVoIP, which generates a GSM file on the node setup script.

#analog_bridge #mmdvm_bridge