Dstar requires callsigns. Your metadata did not resolve to a call. Bad lookup? Empty database?

The error message is returned by your Allstar Node when issuing a RptStatus. Most likely it is because you have misconfigured your node number in Analog_Reflector.json or manager.conf on the Allstar s

The dashboard does log file scraping and if I remember, the solution is to set your STFU log to replace the MMDVM log. I could be wrong though.

Or you do the easy thing: change the file name/path in the ini file to your own custom named csv file.

Change "Screen Scale"

Yes, many routers have problems with "hairpin" routes. https://en.wikipedia.org/wiki/Hairpinning

Do not use SSID, just 7 digit DMR ID

I will look into it.

However, it IS a known issue that ircddbgateway can runaway and use 100%cpu.

This is just an informational message. The message is a result of adding a new event type to several of the modes. Please ignore it. I will fix the message in the next release.

Try this: https://dvswitch.groups.io/g/Mobile/message/969

Did you select USRP ?

So I can reproduce you issue, please tell me the OS version by running uname -a and reporting the results. All tests I have done with FF have worked, so I want to see if I broke something recently.

I had issues with mine, describes here: https://dvswitch.groups.io/g/Mobile/message/1341 What firmware version are you using?

All python code is open source. The pyaudio module witten in C /C++ is on git. Sorry I do not have the link on hand. When pyaudio was written ALSA was the standard audio subsystem. But many distros ha

Mike, Your original question was can I change CALLSIGN / DVSW to something else. Well, No, your callsign is a required field in the protocol and most networks verify that it is valid and allowed. The

Ralf, The new Analog_Reflector will fill this need. However, tell me more about your pool. Did you write a proxy? Does it have a list of available ports? Does it spawn new AB instances on demand? Mike

Jeff, Apple (being the control freaks that they are) specifically cripple any other browser than Safari. I have tested on Chrome and have found that the web audio implementation is broken (on purpose)

That port is in the privileged range. Please use a port number > 1000

Status Report: I now have a manageable list of items to finish for an alpha release. The items are divided into Server, and Client with most of the work done for both. Client needs some "configuration