Joe, Interesting that webproxy was not running when it was showing with netstat. As far as upgrading nodejs, you might look at: <https://github.com/nodesource/distributions> curl

Okay...problem (finally) solved. Turns out that the problem was (probably) not related to changing the dashboard web port. Documenting my experience so that others may benefit. Steve, your

Patrick, Which TOT are you adjusting? Are you adjusting the TOT on the USRP node or the ASL TX? The TOT controls the TX not the RX. Just a thought. Steve

Is lightttpd running? systemctl status lighttpd and/or ps ax | grep lighttpd

Agreed, why bother? If what you are trying to do is create a private DMR TG, you can use HBlink to create a DMR Master. Insert it where you have internet on your diagram.

Please post your tune string.

Make sure you have done a update / upgrade. and retest.

Hi, A minor observation on the DVSwitch Dashboard. I have noticed that the “DMR Master” information keeps disappearing. Everything is still working as expected and DVSwitch is connected to the DMR

This is what I see on server.dvswitch.org when I set lighttpd to port 88: tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 14654/node tcp

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

Hi Folks, Is it possible to have a private connection using MMDV/Analog_Bridge ? Analog HT1 <> AllStar1 <> Analog_Bridge <> MMDVM_Bridge <> [Internet] <> MMDV_Bridge <> Analog_Bridge <> AllStar2 <>

On the non working node, try systemctl restart webproxy. Check netstat Look at /var/log/dvswitch/webroxy

On the two working DVSwitch installations, netstat -tnap shows the following line: tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1376/node Which is, I assume, the RX

What does netstat -tnap show as root? Sent via smoke signal (AT&T)

Okay. Changed it to port 8888. No difference in the RX Monitor problem.

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

Personally, I selected port 88 (after looking at the raw page and noticing that port 8080 was mentioned for RX Monitor) to avoid the obvious conflict there. Also made sure nothing else was grabbing

Is it possible to PUSH the user definable dropdown macro commands on DVSM? If not possible to Push these, can the defaults be changed somehow? -- Derek G4WXN

That works, but when I drop the transmission, the voice announcement "Linked to 4440" repeats, cutting off the first few seconds of incoming signals. -- Derek G4WXN

Hi everybody! May I have some infos and instructions to develope a multi access function on my DVSwitch Server? Thank You for help!