Welcome to DVSwitch
DVSwitch is a set of tools and programs related to provisioning and operating Amateur Radio digital voice networks.
Purpose
The purpose of DVSwitch is as follows:
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).
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
Our stated position is:
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.
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: STFU
Does your dmr ID match the same id in DVSwitch.ini?
Sent via smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of f0dei <f0dei@...>
Sent: Thursday, April 22, 2021 1:38:20 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] STFU More progress :
Connected but set for 208036002 in STFU in log i see 208036001 When I trig PTT nothing seems to be routed to TG20839 (listening on real repeater) I: 2021-04-22 17:33:48.164 STFU is starting I: 2021-04-22 17:33:48.164 Connecting to STFU server at address: master.bm262.de:54006 I: 2021-04-22 17:33:48.242 Successful connection to BM server at ip address: I: 2021-04-22 17:33:57.507 DMR, Begin TX: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:33:59.526 DMR, TX state = OFF, DMR frame count was 34 frames I: 2021-04-22 17:34:29.750 DMR, Remote CMD: codec=slin I: 2021-04-22 17:34:41.869 DMR, TAG_SET_INFO: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:34:41.869 DMR, Remote CMD: txTg=20839 I: 2021-04-22 17:34:47.657 DMR, Begin TX: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:34:52.017 DMR, TX state = OFF, DMR frame count was 73 frames
|
|
|
|
Re: STFU
f0dei
More progress :
Connected but set for 208036002 in STFU in log i see 208036001 When I trig PTT nothing seems to be routed to TG20839 (listening on real repeater) I: 2021-04-22 17:33:48.164 STFU is starting I: 2021-04-22 17:33:48.164 Connecting to STFU server at address: master.bm262.de:54006 I: 2021-04-22 17:33:48.242 Successful connection to BM server at ip address: I: 2021-04-22 17:33:57.507 DMR, Begin TX: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:33:59.526 DMR, TX state = OFF, DMR frame count was 34 frames I: 2021-04-22 17:34:29.750 DMR, Remote CMD: codec=slin I: 2021-04-22 17:34:41.869 DMR, TAG_SET_INFO: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:34:41.869 DMR, Remote CMD: txTg=20839 I: 2021-04-22 17:34:47.657 DMR, Begin TX: src=2080360 rpt=208036001 dst=20839 slot=2 cc=1 metadata=F0DEI I: 2021-04-22 17:34:52.017 DMR, TX state = OFF, DMR frame count was 73 frames
|
|
|
|
Re: STFU
Or:
toggle quoted messageShow quoted text
master.bm262.de
On 4/22/2021 1:17 PM, f0dei wrote:
STFU Log
|
|
|
|
Re: STFU
Use 3102.repeater.net In my experence, terminal.brandmeister.network
does not work.
toggle quoted messageShow quoted text
On 4/22/2021 1:17 PM, f0dei wrote:
STFU Log
|
|
|
|
Re: STFU
f0dei
STFU Log
I: 2021-04-22 17:14:47.524 STFU is starting I: 2021-04-22 17:14:47.525 Connecting to STFU server at address: terminal.brandmeister.network:54006 F: 2021-04-22 17:14:53.570 Error logging into BM server. Error code returned by server: -6 I: 2021-04-22 17:14:53.570 Connecting to STFU server at address: terminal.brandmeister.network:54006 F: 2021-04-22 17:15:00.180 Error logging into BM server. Error code returned by server: -6 I: 2021-04-22 17:15:00.181 Connecting to STFU server at address: terminal.brandmeister.network:54006 F: 2021-04-22 17:15:06.229 Error logging into BM server. Error code returned by server: -6
|
|
|
|
Re: STFU
f0dei
On Thu, Apr 22, 2021 at 06:41 PM, Steve N4IRS wrote:
apt updateInstalled and service is running now but seems not connected tested on 3102 IP and terminal.brandmeister.network [STFU] ; Brandmeister Open DMR Terminal (ODMRT) Protocol BMAddress = 74.91.114.19 ; Brandmeister ODMRT server address BMPort = 54006 ; Brandmeister ODMRT port BMPassword = XXXXXXX ; Your Brandmeister password Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) txPort = 36100 ; Port to send AMBE TLV frames to (export) rxPort = 36103 ; Port to listen on (import) UserID = 208036002 ; Your DMR ID + SSID TalkerAlias = F0DEI Toufik ; Max 27 characters StartTG = 20839 ; Startup talk group LogLevel = 3 ; STFU log level (0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error)
|
|
|
|
Re: STFU
Check if you have /opt/STFU. If not:
toggle quoted messageShow quoted text
apt update apt install stfu
On 4/22/2021 12:40 PM, f0dei wrote:
I think STFU is not installed, no service running or available.
|
|
|
|
Re: STFU
f0dei
I think STFU is not installed, no service running or available.
How to install STFU ?
|
|
|
|
Re: STFU
Can you show your AR and AB logs when you select the mode? Do you
have the STFU service running?
toggle quoted messageShow quoted text
On 4/22/2021 12:31 PM, f0dei wrote:
Thanks for reply,
|
|
|
|
Re: STFU
f0dei
Thanks for reply,
I can select STFU in HTML client or on my PNC380 but it's not working, Attached my json file : { "nodeName":"DVSwitch", "dmrID":"2080360", "abAddress": "127.0.0.1", "usrpTxPort": "31001", "usrpRxPort": "31001", "mobilePort": "12345", "wsPort": "443", "keyDir": "./ssl/", "siteroot": "./arRoot", "logFileName": "/var/log/dvswitch/Analog_Reflector.log", "logLevel": "2", "disallowUnknownClients": false, "brokerURL": "mqtt://localhost:1883", "rightsMask": "4", "autoMute": true, "clientDebugMode": false, "clientModes": ["Intercom", "DMR", "STFU", "DSTAR|D-Star", "NXDN", "P25", "YSF", "ASL|AllStar"], "bridges": { "asl": [ {"node" : "1999", "address" : "127.0.0.1", "rxPort" : "34001", "txPort" : "32001", "rights" : 3, "amiUserName" : $ ], "ab" : [ {"name" : "DMR", "address" : "127.0.0.1", "rxPort" : "51100", "txPort" : "51103", "rights" : 1}, {"name" : "D-Star", "address" : "127.0.0.1", "rxPort" : "52100", "txPort" : "52103", "rights" : 1}, {"name" : "NXDN", "address" : "127.0.0.1", "rxPort" : "53100", "txPort" : "53103", "rights" : 1}, {"name" : "P25", "address" : "127.0.0.1", "rxPort" : "54100", "txPort" : "54103", "rights" : 1}, {"name" : "YSF", "address" : "127.0.0.1", "rxPort" : "55100", "txPort" : "55103", "rights" : 1} ] } }
|
|
|
|
Re: STFU
Analog_Reflector.json:
toggle quoted messageShow quoted text
"clientModes": ["Intercom", "DMR", "STFU", "DSTAR|D-Star", "NXDN", "P25", "YSF", "ASL|AllStar", "M17 Bridge|M17"], dvsm.macro: [MACROS] ; Example: When a DVSM user selects the DMR mode, AB will look for the mode below and execute the script and pass the parameter. ; In this case, AB will execute the script "/opt/MMDVM_Bridge/dvswitch.sh" and pass the prarmeters of "mode DMR" to the script. DMR = /opt/MMDVM_Bridge/dvswitch.sh mode DMR DSTAR = /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR NXDN = /opt/MMDVM_Bridge/dvswitch.sh mode NXDN P25 = /opt/MMDVM_Bridge/dvswitch.sh mode P25 YSF = /opt/MMDVM_Bridge/dvswitch.sh mode YSF ASL = /opt/MMDVM_Bridge/dvswitch.sh mode ASL STFU = /opt/MMDVM_Bridge/dvswitch.sh mode STFU intercom = /opt/MMDVM_Bridge/dvswitch.sh mode INTERCOM That should be all you need. Steve N4IRS
On 4/22/2021 12:12 PM, f0dei wrote:
Hello All,
|
|
|
|
STFU
f0dei
Hello All,
Any tips how to setup STFU ? DVSWitch and Analog Reflector are already running on my VPS) and STFU section is already set in DVSWitch.ini 73 Toufik, F0DEI
|
|
|
|
Re: Fusion node lists and tune string
G4WXN@...
Steve
Once again thanks for your help. I have attached the MB and AB logs as well as the YSF Gateway log. As I mentioned before I can access the reflectors with the IP and port, and hearing traffic. -- Derek G4WXN
|
|
|
|
Re: Audio
Yes. How about a little more detail as to what you are trying to do.
toggle quoted messageShow quoted text
On 4/22/2021 8:31 AM, N4UPC - Scott via
groups.io wrote:
Is it possible to normalize the audio on the DVSwitch server?
|
|
|
|
Audio
Is it possible to normalize the audio on the DVSwitch server?
|
|
|
|
Re: Fusion node lists and tune string
Show me the AB and MB logs when you dial 857727
toggle quoted messageShow quoted text
On 4/22/21 5:56 AM,
G4WXN@... wrote:
I have attached another YSFGateway log file, and added some notes to it.
|
|
|
|
Re: Fusion node lists and tune string
G4WXN@...
I have attached another YSFGateway log file, and added some notes to it.
Linking appears to work if the dialer has IP address and port, this I do from a customised YSF node list by a long press on B.
If I enter the dialer string 857727, as you can see in the log nothing happens.
-- Derek G4WXN
|
|
|
|
Re: Fusion node lists and tune string
You now have the remote control ports defined. MB should be sending
commands to YSFGateway. SHow the AB and MB logs when you issue tune
command. Make sure you issue a mode YSF first.
toggle quoted messageShow quoted text
|
|
|
|
Re: Fusion node lists and tune string
G4WXN@...
Rebooted the Pi
-- Derek G4WXN
|
|
|
|
Re: Fusion node lists and tune string
Did you restart mmdvm_bridge?
toggle quoted messageShow quoted text
On 4/21/2021 2:11 PM,
G4WXN@... wrote:
|
|
|