I know that this is a bit off-topic for the board, so Steve please forgive me, but this has me thinking. As a thought experiment: I wouldn't use Pi-Star. I would create my own install of MMDVM and MMD

Ok, so the only issue I see at this point is with Analog_Bridge. It's not aware of M17 as a digital mode and does not know how to send frames to M17Gateway. I suppose we'll have to wait until Analog_B

Tony, my thoughts exactly. A path between two points should be made as simple as possible. I was unaware of the Codec2 server. This should make things a whole lot easier. M17Gateway exists as a 'beta'

As of now, there is only one known path to get M17 to ASL, and that is to use M172DMR. nostar MMDVM_CM fork: https://github.com/nostar/MMDVM_CM Using M172DMR, you can cross-mode M17 to a DMR talkgroup

Skyler, I'm sorry that your experience with M17 hasn't been as stellar as some may expect. Please, understand that the protocol is still very much in its infancy, and there are many people working on

DISREGARD Bad metadata. My fault.

Apologies if I'm waking a solved thread, but I seem to be having the same issue. Inbound DStar works on Allstar, but transmitting from Allstar doesn't seem to work. I: 2020-05-04 21:03:51.186 Analog_B

DMRGateway is not required. I have made a note in my old doc that reflects this. I will be creating a new doc that should be available after the holidays. Steve KC1AWV

> The accompanying readme file says user:repeater, pw:allstarlink, consistent with other ASL rpi versions. Then, either the README is incorrect, or the image is incorrect. I'd ask whoever wrote the RE

A quick Google search for Beaglebone Black AllStarLink provided a document with this information: The login username is root and the PW is root I also assume this is the hamvoip distribution? If so, y

If you're talking the Xelatec (xipar) IAXRPT dispatch console, I don't think so. It's closed source as well, so a separate Windows client would be needed to build in the USRP functions I believe.

Sometimes, I like to live in the past. Here's the logs from XLX and MB Jul 1 2019 build - still no connection to module I --- XLX log --- Oct 3 14:02:41 xlx740 xlxd: DMRmmdvm connect packet from KC1AW

#mmdvm_bridge

Testing now, but no connect to module with MB. I'm including the HBL log lines for comparison as well. Version issue? Maybe my MB is older... --- HBlink connect to XLX --- Oct 3 12:23:56 xlx740 xlxd:

#mmdvm_bridge

Not with that configuration, the one you pasted is for DMRGateway. This is what I used for MB: [DMR Network] Enable=1 Address=[ip address of xlx server] Port=62030 Jitter=360 Local=62031 Password=pass

#mmdvm_bridge

Try en_US

Sorry Steve, I can feel the frustration. I have tested with the Options line, and nothing happens on the XLX side. root@test:/opt/MMDVM_Bridge_2# ./MMDVM_Bridge MMDVM_Bridge.ini I: 2019-10-02 18:50:28

#mmdvm_bridge

I see what you're getting at, Ken. I wonder if anyone has tried G722 on ASL? I think I have a desk phone that supports it, maybe I can try it out and see what happens.

> Then why do you quote DMRGateway config # for Module = D ? That was my mistake, I was looking fast through my docs and made the mistake of quoting the wrong part.

#mmdvm_bridge

I think the config file on GitHub is a carry over from a previous version. From what I know, adding the Module line to the DMR Network stanza should connect you to a module when established. There's n

#mmdvm_bridge

Wait, I see the confusion. Even I get a little mixed up here. I was reading the DMRGateway config. Oops. Try this for MB: [DMR Network] Enable=1 Address=[xlx server ip] Port=62030 Jitter=360 Local=620

#mmdvm_bridge