I’ve not done anything to the HB_Bridge branch of HBlink – hbmonitor will not work with it. If you’re using DMRlink, use the DMRmonitor that goes with it. HBlink’s master branch is getting

Bill, Cort may chime. I don't know if HBmonitor will work with the HB_Bridge branch (sure do need to merge that in...) Your post does raise a question, are you saying Hytera can talk to

I'm currently running the HB_Bridge branch of HBlink along with the IPSC_Bridge version of DMRlink to make my Hytera repeater talk to a C-Bridge. Knowing it's not supported, I would like to use

On the surface, this sounds like a internet bandwidth issue/cpu bandwidth issue or perhaps some form of dropped packets in the stream. Or even a combination. But, don't be to quick to make

This sounds like something (port#'s) in the file changed and not realized until the reboot. Check the port data between ambe audio and analog bridge and then from there to mmdvm bridge. OR Follow

Well, it sounds like you have your bridge on a public node. Hard to have 'selective control' that way. Think of it a bit backwards. I have dmr tg 91 set-up on 29999 for the last several months. It's

I have md380-emu running too on my pi3, dmr to ASL audio is OK, but ASL to DMR , there are a lot of DMR stations complain that my audio is like a robot. Any optimization can be done?

Jeff, The logs are there to help in troubleshooting. Since your problem is ASL -> DMR, consider the following diagram: ASL -> Analog_Bridge -> MMDVM_Bridge -> BrandMeister When traffic

Running Allstarlink (ASL) with Analog_Bridge , md380-emu and MMDVM_Bridge...... Got it up and running last night, had a qso from allstar to dmr and DMR back to allstar with "PERFECT" audio

yeah, i knew about that one, but i cant guarantee that the connecting station will connect in monitor mode :)

If I understand your question right ... Just connect to your DMR Bridged node in RX (*2xxxx) ...mike/kb8jnm

I have a working DMR to Allstar setup (thanks for the help!). I have a friend of mine who wants to listen in to the monday night papa system roundtable through my allstar node. Is there a quick and

This comes from the old phone patch protocol: “star-up, pound-down” But, with Allstar, you can configure this to be whatever you want in rpt.conf cop, 6 is the function to key up the

Hi, Thanks very much for the info! I never heard it was # before. The info I've seen and a couple of youtube videos say *99 is a TX toggle. Well thanks for clearing that up! -Steve W7RD

As Paul correctly pointed out, it is # to drop the tx But, I'm wondering where you had got the idea it was 99 again, You are not the first to have that assumption. Did you read this somewhere ? I'm

You should have an unkey command by default I believe its #

Hi, I've set up about 10 DMR to Allstar bridges. This may be more of an Allstar issue than DVSwitch. Anyhow, when I key with *99 on the phone portal (or IAX client) it works great ... audio comes

You can add 1999 to allmon private nodes file. Steve

Afternoon all, After the install of the ASL-DMR bridge where do I name 1999 to what it is, for when it shows up in allmon2 Thank you for reading. Joe G7kdz

Dan, I believe it has been said, If you have issues with the server, Use any other one that works well for you. So , it's worth a try if you are having issues. But re-check periodically as things