Welcome to DVSwitch
Purpose
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
Re: DVSwitch Dashboard - DMR Master Information
Make sure you have done a update / upgrade. and retest.
toggle quoted messageShow quoted text
On 12/9/20 7:31 AM, g8ptn@...
wrote:
|
|
DVSwitch Dashboard - DMR Master Information
g8ptn@...
Hi, I have noticed that the “DMR Master” information keeps disappearing. Everything is still working as expected and DVSwitch is connected to the DMR server. Switching between servers in the “dvs” control panel restores the dialog information.
PS. Keep up the great work on DVSwitch. Even using the software vocoder, for DMR the audio on both transmit and receive is excellent. Regards, Dave (G8PTN)
Hardware:
|
|
Re: DVSwitch Dashboard Web Port
This is what I see on server.dvswitch.org when I set lighttpd to
port 88:
toggle quoted messageShow quoted text
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 14654/node tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 20288/lighttpd
On 12/9/20 8:27 AM, Joe, WB3IHY wrote:
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.
|
|
Re: MMDVM to MMDVM connections ?
Patrick Perdue
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 mad, on
a public network. Not sure how private calls work with DVSwitch,
not something I've ever cared to try. That, or set up an HBlink or some other DMR master server somewhere and directly connect to that. It's very common, especially on Brandmeister, for people to make
group calls on personal ID's to connect, I've noticed.
On 12/9/2020 5:47 PM, Gerry Filby wrote:
Hi Folks,
|
|
MMDVM to MMDVM connections ?
Gerry Filby
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 <> HT2 ("Why bother ?" - what's the point of going through the digital mode - just go AllStar to AllStar ?) Or would one have to use a temporary Talk Group ? Best, Gerry. W6WNG
|
|
Re: DVSwitch Dashboard Web Port
On the non working node, try systemctl restart webproxy. Check netstat Look at /var/log/dvswitch/webroxy
From: Joe, WB3IHY
Sent: Wednesday, December 9, 2020 1:06 PM To: main@dvswitch.groups.io Subject: Re: [DVSwitch] DVSwitch Dashboard Web Port
On the two working DVSwitch installations, netstat -tnap shows the following line:
|
|
Re: DVSwitch Dashboard Web Port
Joe, WB3IHY
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 Monitor doing its thing. On the one where I switched lighttpd to port 8888, there is nothing listed with port 8080 anywhere. Is that what you're looking for or do you need me to post the entire output? If the latter, then I'd need to (ahem) redact a few things in it for security reasons, HI HI. On the one where I switched the lighttpd port, there is nothing with port 8080 listed.
|
|
Re: DVSwitch Dashboard Web Port
What does netstat -tnap show as root?
Sent via smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Joe, WB3IHY <groupsdotio@...>
Sent: Wednesday, December 9, 2020 9:02:54 AM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] DVSwitch Dashboard Web Port Okay. Changed it to port 8888. No difference in the RX Monitor problem.
|
|
Re: DVSwitch Dashboard Web Port
Joe, WB3IHY
Okay. Changed it to port 8888. No difference in the RX Monitor problem.
|
|
Re: DVSwitch Dashboard Web Port
That port is in the privileged range. Please use a port number > 1000
|
|
Re: DVSwitch Dashboard Web Port
Joe, WB3IHY
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 port 8080 on the machine.
|
|
Can client macros commands be pushed to the client.
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?
|
|
Re: Using DVSwitch to access DMR+/Phoenix
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
|
|
DVSwitch Server Multi Access
Hi everybody! May I have some infos and instructions to develope a multi access function on my DVSwitch Server?
|
|
Re: digital transmit overtime
Patrick Perdue
Hi Steve:
Thanks. Yeah, I thought it should work the same as any other channel driver, so I changed it to a ridiculously low number (10000), and transmissions over 10 seconds across the bridge still passed after rpt reload, at least from digital to analog. I didn't test in the other direction.
|
|
Re: digital transmit overtime
Patrick,
toggle quoted messageShow quoted text
AllStar should treat traffic coming from AB just like any other channel driver. I will try to test when I get a chance. I'm on the road for the next few day, so it will be the weekend before I can play. Steve N4IRS
On 12/9/20 5:38 AM, Patrick Perdue wrote:
Hi:
|
|
digital transmit overtime
Patrick Perdue
Hi:
I'm trying to find a way to limit transmission time from digital to analog. Lately, I've had users experimenting with Peanut and BlueDV continuously transmitting for long periods of time without realizing it. totime in rpt.conf on the node's stanza seems to have no effect, and I can't find a way to do this from DVSwitch itself. What am I missing?
|
|
Re: DVSwitch Dashboard Web Port
All done! Now is all OK! Thank you for the help!!!
|
|
Re: Adding P25 to existing YSF and DMR bridge
Gary, KE8O
Steve,
Last night when I tested the P25Gateway was one of the services I forgot to start. In all of my previous attempts it was running. It is set to startup on 27715 my P25 reflector #. I'm using privateP25Host.txt to define my P25Reflector (attached). Tonight I tested again with the GW started and I'm seeing activity in my terminal windows for MB, AB, and AB2. I've attached the logs from each of those terminal windows. I also included my P25Reflector log, and my P25GW ini. There has to be something I'm overlooking. Thank you !
|
|
Re: DVSwitch Dashboard Web Port
What port did you move the dashboard to? RX Monitor uses port 8080.
toggle quoted messageShow quoted text
Steve N4IRS
On 12/8/20 7:07 PM, Joe, WB3IHY wrote:
Would changing the port have any repercussions, such as causing the RX Monitor button to malfunction?
|
|