I was just reminded that many of the DMARC TGs are available on DMR+ which MMDVM_Bridge will connect to. I would check if the TGs you want are available on DMR+ Steve N4IRS On

Thank you. Yes looks like I was making the assumption that DV4Mini, had a vocoder, but doesn't. What I need is a USB vocoder widget like the THUMBDV or equivalent.

See this: <https://dvswitch.groups.io/g/main/files/IPSC_AB_ASL.txt> <https://dvswitch.groups.io/g/allstarlink/files/ASL%20to%20DMR%20Bridge.pdf> Instead of MMDVM_Bridge you will

Jeff, I have an older ASL-DMR bridge running with a DV3000 running with access to two cbridge connections (since 2015). As long as I maintain full quieting access to my allstarlink node, there will

You will probably want to do a separate asl node from your bm connection. From past experience bm would prefer you not bridging networks. So you may want to setup a separate public asl node to connect

Tom, The connection to a c-Bridge would be through IPSC_Bridge rather then MMDVM_Bridge. It would look like this for ASL: ASL <-> Analog_Bridge <-> IPSC_Bridge <-> c-Bridge.

Can a DMR-allstar bridge connect to a DMR-MARC cbridge? I've been seeing only Brandmeister connection info. Thanks, Tom / K5TRA

Yes, a hardware vocoder is preferred. The question is about a DV4 Mini. Different device. DV4 Mini radio not usable with DVSwitch.

I've been using a ThumbDV and it's working quite well. Nice, clear audio. Is it worlds better than the MD380 emulator? Nah. But it's good.

I recently started to use DVSwitch with Allstar and just tried to set up a Bluetooth headset to work mobile with, having seen the option in the settings. What I was not expecting was the 'Not yet

One other thing I did work out, well at least for the image I am using on the Rpi. I had to change directory before running the pushfile cd /opt/Analog_Bridge then ./dvswitch.sh pushfile

Yes I worked out that it was a syntax error, many thanks.

Thanks Steve. Interestingly, when I comment either the file pointer or the complete stanza, this still shows up in the log... "Started the DMR Id lookup reload thread" Perhaps a more ideal situation

Use pushFile, I was looking at the function name not the command name.

One reason I can see is for logging. Easier to lookup a callsign then a DMR ID when debugging. That being said Comment out the file pointer for DMR ID lookup in MB.ini Steve N4IRS

I'm running an MMDVM Bridge instance as part of an Asterisk <--> HBlink connector. I cannot think of any reason why I'd need MMDVM Bridge to lookup DMR IDs in either direction for this purpose. So,

This is what the "developers" sent: - Create your reflector list (a text file) in /tmp called DSTAR_node_list.txt - The file is a list of reflectors and human readable names:

Why not just post the info here? Sent via smoke signal (AT&T)

I would stay far far away from the dv4mini stuff but that is just my personal opinion!

Firstly like to point out that I am a noob when it comes to DVSwitch so please be kind. I am currently using DVswitch on a Rpi as the server and a tablet PC. I am getting OK audio reports on DMR,