I remember some discussion about sound being very choppy on the ASL Buster images a few months ago. No idea what the status of that is now. I'll try it and see what happens.

Sorry, I should clarify... I want to build a radio-less node in the sense that there is a fob with a microphone and output connected, which incorporates DVSwitch Server.

I don't mean to hijack the thread, though this is somewhat related. I know there were problems with ASL on Buster with sound in the past. Was this ever addressed, or is Buster only good as an ASL hub

Hi: I just connected my P25 reflector to ASL. Though it is part of a multi-mode system, the P25 instance of Analog_Bridge is connected directly to ASL on it's own private node to avoid transcoding lay

Also true, though I think he is just connecting his hotspot to DMR and using it to convert to C4FM, not DVSwitch for that. Again, could be wrong, and I'll shut up before I get myself into trouble, but

I could be wrong, but it doesn't sound like Frank is actually bridging to YSF, but rather is just crossmoding to DMR with a C4FM radio. That being the case, there will be no separate option for changi

Are you running USRPGain and TLVGain at unity? I've found it helps a lot to turn TLVGain down quite a bit in Analog_Bridge.ini. TLV is the gain sent from analog to digital. This will reduce the gain t

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

#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

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

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

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

#analog_bridge #mmdvm_bridge

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

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,

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.

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

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

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

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

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