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: ASL <> DMR <> YSF inquiry?
#mmdvm_bridge
Asl<>AB<>MB<>Hblink3<>MB<>YSFReflector
|
|
|
|
ASL <> DMR <> YSF inquiry?
#mmdvm_bridge
andrew delgado
Hello!
how can i do this setup? ASL <> DMR <> YSF what are the tools do i need? i was able to setup ASL <> DMR now how can i add YSF reflector to have it ASL<>DMR <> YSF? what tools to i need? Thanks! Andrew
|
|
|
|
D-Star info from G4LKX
This message contains important information that I want disseminated far and wide please.
I have been approached by the people who run aprs.fi and REF001/REF030 (not the same people) about problems being caused by hotspots. This is down to usage and I hope that people will act on this information: 1. APRS, it is important that when configuring your hotspot, that you ensure that the suffix used for accessing aprs.fi is unique. For example if you use more than one hotspot, then ensure that for every mode and for every hotspot, the aprs.fi access callsign is unique. This is usually done by specifying a unique suffix to the callsign used by the hotspot. If more than one hotspot attempts to access aprs.fi with the same callsign+suffix combination, the first one is thrown off, and the new one connects. In the meantime the original one tries to connect and throw the new one off. This can happen multiple times per second, and is causing problems for them. Please, please, please, look at your configurations and if you have a duplicate, change one of them. 2. REF001/REF030, apparently the network load on these D-Star reflectors is now very high due to the number of hotspots connecting and staying connected. Could you please consider changing your gateway configuration so that you disconnect after a certain period of inactivity (this means local RF activity) so that they aren't overloaded. I know we like to listen out for activity, but we must also realise that D-Star popular reflectors const money to run, and that includes network and processor usage. A quick look at their dashboards will reveal the problem, they're huge. Jonathan G4KLX
|
|
|
|
Re: #analog_bridge #analog_bridge
#analog_bridge
toggle quoted messageShow quoted text
On 4/19/20 7:41 AM, Philippe wrote:
Help me to make working the application tx and Rx
|
|
|
|
#analog_bridge #analog_bridge
#analog_bridge
Help me to make working the application tx and Rx
|
|
|
|
Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
Josep
Ea3abn@... Enviado desde mi dispositivo Samsung -------- Mensaje original -------- De: EA5GVK Joaquin <ea5gvk@...> Fecha: 18/04/2020 11:52 (GMT+01:00) Para: main@DVSwitch.groups.io Asunto: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR. DVLINK V9 IS HERE. INCLUDES NEW DVSWITCH, SINGLE USER AND MULTIUSER WITH AMBE PHYSICAL SERVER, HBLINK IMPROVED, AND A GREAT NEW "HOTSPOTS" SINGLE AND MULTIUSER TO HAVE YOUR DMOS, HOTSPOT, MMDVM REPEATERS IN THE SAME IMAGE. (Thanks to the great work of my friend EA7JCL&EA5GVK) LINK INFO & DOWNLOAD: http://ea5gvk-dmr.zigor.es/2020/04/18/aqui-os-presento-a-dvlink-v9-con-muchas-novedades/ .REMEMBER THE DVLINK PHILOSOPHY IS TO HELP THE AMATEUR RADIO OPERATOR TO APPROACH DIGITAL RADIO WITH GUARANTEES FOR HIM AND THE DIGITAL NETWORKS AND NOT THE CONTRARY. DVLINK USES THIRD-PARTY SOFTWARE WITHOUT MODIFICATION AND WITH ORIGINAL CONFIGURATIONS OF ITS CREATORS. - SUPPORT IN SPANISH, WE ARE WORKING FOR ENGLISH AND FRENCH LANGUAGES. TECHNICAL SUPPORT WITH TELEGRAM GROUP JOIN: https://t.me/joinchat/AveYRFJCxSbhKbI2ti1_Og Thanks to the DVSwitch and HBLINK team, without your software, we would be sadder. Thanks to Steve, Cort and all the DVSwitch and HBLINK team, for your great work.
|
|
|
|
Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.
EA5GVK Joaquin
DVLINK V9 IS HERE.
INCLUDES NEW DVSWITCH, SINGLE USER AND MULTIUSER WITH AMBE PHYSICAL SERVER, HBLINK IMPROVED, AND A GREAT NEW "HOTSPOTS" SINGLE AND MULTIUSER TO HAVE YOUR DMOS, HOTSPOT, MMDVM REPEATERS IN THE SAME IMAGE. (Thanks to the great work of my friend EA7JCL&EA5GVK) LINK INFO & DOWNLOAD: http://ea5gvk-dmr.zigor.es/2020/04/18/aqui-os-presento-a-dvlink-v9-con-muchas-novedades/ .REMEMBER THE DVLINK PHILOSOPHY IS TO HELP THE AMATEUR RADIO OPERATOR TO APPROACH DIGITAL RADIO WITH GUARANTEES FOR HIM AND THE DIGITAL NETWORKS AND NOT THE CONTRARY. DVLINK USES THIRD-PARTY SOFTWARE WITHOUT MODIFICATION AND WITH ORIGINAL CONFIGURATIONS OF ITS CREATORS. - SUPPORT IN SPANISH, WE ARE WORKING FOR ENGLISH AND FRENCH LANGUAGES. TECHNICAL SUPPORT WITH TELEGRAM GROUP JOIN: https://t.me/joinchat/AveYRFJCxSbhKbI2ti1_Og Thanks to the DVSwitch and HBLINK team, without your software, we would be sadder. Thanks to Steve, Cort and all the DVSwitch and HBLINK team, for your great work.
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Uli
Yes that was me yesterday on your Reflector testing.
Can you post you MMDVM_Bridge.ini and your DVSwitch.ini so that I can compare it to mine? Maybe that gives a hint where the problem lies. Uli
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Tito Lopez - YN1OB
Ah so you are the one that is connected to the reflector. Cool. So it works fine. The problem is on my end.
On Fri, Apr 17, 2020 at 10:11 AM Uli <g90@...> wrote: @Tito: I have put your YSF Reflector IP into my MMDVM_Bridge.ini file rebooted and did a few tests. It works fine, I get audio in both directions.
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Uli
@Tito: I have put your YSF Reflector IP into my MMDVM_Bridge.ini file rebooted and did a few tests. It works fine, I get audio in both directions.
Did you open up in your router port 42000 UDP pointing to the IP of your RPI with the MMDVM_Bridge running on it? Uli
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Uli
@Tito: Did you open up all necessary ports on your router? That was one of my problems in the first place that prevented the connection
Try to run something like tail -f /var/log/mmdvm/MMDVM_Bridge-2020-04-17.log (replace the date with the current date) to display a live log and check what is going on Now take a DMR HT and a C4fm HT key up and check whats shown in the livelog @Steve: I have no clue why the DVSwitch system builder did not work. It might have been a user rights problem or it did not like the raspbian stretch lite, but I don´t know for sure. When I have time, I´ll give it another try. Uli
|
|
|
|
#analog_bridge Problem with Analogbridge on Orangepi
#analog_bridge
Kim-Benjamin Lütkemeier
Hello,
I downloaded vom Github the aktual arm64 version. but on the Debian is only 2.28 running. /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./Analog_Bridge.arm64) AnalogBridge# ldd --version ldd (Debian GLIBC 2.28-10) 2.28 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper. it is possible to change ist and upload a version that work with 2.28? 73, do1kbl
|
|
|
|
#dmrlink
#dmrlink
Hi all
I have my dvswitch USRP working fine on DMR TG however not much luck with linking my TG to asterisk allstar node can anyone please help ??
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
What program are you running to build the bridge? I need that log
with traffic in both directions.
toggle quoted messageShow quoted text
<https://dvswitch.groups.io/g/main/wiki/Bridge-DMR-to-YSF-Narrow> <https://dvswitch.groups.io/g/main/wiki/Help%21>
On 4/16/20 5:44 PM, Tito Lopez wrote:
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Tito Lopez - YN1OB
So what is it that you need?
On Thu, Apr 16, 2020 at 12:52 PM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Can you have several instances of Dvswicth running in different folders with the dvswitch.sh?
ea7jcl@...
I think function getABInfoFileName is the key.
Cheers.
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Analog_Bridge is not used in a DMR to YSFn bridge.
toggle quoted messageShow quoted text
On 4/16/2020 2:38 PM, Tito Lopez wrote:
Here is my Analog_Bridge Log
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Tito Lopez - YN1OB
Here is my Analog_Bridge Log
I: 2020-04-16 18:30:52.292 Analog_Bridge is starting
M: 2020-04-16 18:30:52.294 Setting [MACROS] DMR -> /opt/Analog_Bridge/dvswitch.sh mode DMR
M: 2020-04-16 18:30:52.294 Setting [MACROS] DSTAR -> /opt/Analog_Bridge/dvswitch.sh mode DSTAR
M: 2020-04-16 18:30:52.294 Setting [MACROS] NXDN -> /opt/Analog_Bridge/dvswitch.sh mode NXDN
M: 2020-04-16 18:30:52.294 Setting [MACROS] P25 -> /opt/Analog_Bridge/dvswitch.sh mode P25
M: 2020-04-16 18:30:52.294 Setting [MACROS] YSF -> /opt/Analog_Bridge/dvswitch.sh mode YSF
M: 2020-04-16 18:30:52.294 Setting [MACROS] dbupdate -> /opt/Analog_Bridge/dvswitch.sh collectProcessPushDataFiles
M: 2020-04-16 18:30:52.294 Setting [MACROS] 9876 -> /opt/Analog_Bridge/parrot.sh
M: 2020-04-16 18:30:52.294 Setting [] include -> dvsm.macro
M: 2020-04-16 18:30:52.294 Setting [GENERAL] logLevel -> 2
M: 2020-04-16 18:30:52.294 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2020-04-16 18:30:52.294 Setting [GENERAL] exportMetadata -> true
M: 2020-04-16 18:30:52.294 Setting [GENERAL] decoderFallBack -> true
M: 2020-04-16 18:30:52.294 Setting [GENERAL] useEmulator -> true
M: 2020-04-16 18:30:52.294 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] address -> 127.0.0.1
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] txPort -> 31103
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] rxPort -> 31100
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] ambeMode -> DMR
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] minTxTimeMS -> 2500
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] gatewayDmrId -> 7101003
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] repeaterID -> 710100306
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] txTg -> 710411
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] txTs -> 2
M: 2020-04-16 18:30:52.294 Setting [AMBE_AUDIO] colorCode -> 1
M: 2020-04-16 18:30:52.294 Setting [USRP] address -> 127.0.0.1
M: 2020-04-16 18:30:52.294 Setting [USRP] txPort -> 32001
M: 2020-04-16 18:30:52.294 Setting [USRP] rxPort -> 34001
M: 2020-04-16 18:30:52.294 Setting [USRP] usrpAudio -> AUDIO_USE_GAIN
M: 2020-04-16 18:30:52.294 Setting [USRP] usrpGain -> .8
M: 2020-04-16 18:30:52.294 Setting [USRP] tlvAudio -> AUDIO_USE_GAIN
M: 2020-04-16 18:30:52.294 Setting [USRP] tlvGain -> 0.25
M: 2020-04-16 18:30:52.294 Setting [DV3000] address -> 127.0.0.1
M: 2020-04-16 18:30:52.294 Setting [DV3000] rxPort -> 2460
I: 2020-04-16 18:30:52.294 Open UDP listener on 127.0.0.1:31100
I: 2020-04-16 18:30:52.294 Open USRP on 127.0.0.1:32001
M: 2020-04-16 18:30:52.294 Connecting to DV3000 hardware......
W: 2020-04-16 18:30:53.325 DV3000 not found at 127.0.0.1:2460
I: 2020-04-16 18:30:53.326 Subscriber IDs loaded: 0
I: 2020-04-16 18:30:53.326 Default extended metadata <7101003>
I: 2020-04-16 18:30:53.326 Connecting to emulator on host 127.0.0.1:2470
W: 2020-04-16 18:30:53.326 Using software MBE decoder version 1.2.3
W: 2020-04-16 18:30:53.326 Using software OP25 IMBE/AMBE vocoder
I: 2020-04-16 18:30:53.326 Connected to USRP 127.0.0.1:32001
I: 2020-04-16 18:30:53.326 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2020-04-16 18:30:53.327 Starting USRP --> Analog_Bridge (encoder) -> TLV thread
==================================================================================== MMDVM_Bridge Log I: 2020-04-16 18:30:52.278 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2020-04-16 18:30:52.278 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-04-16 18:30:52.278 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-04-16 18:30:52.278 This software is for use on amateur radio networks only,
I: 2020-04-16 18:30:52.278 it is to be used for educational purposes only. Its use on
I: 2020-04-16 18:30:52.278 commercial networks is strictly prohibited.
I: 2020-04-16 18:30:52.278 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-04-16 18:30:52.278 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-04-16 18:30:52.278 Built 14:23:56 Nov 11 2019 (GitID #9dae1ac)
I: 2020-04-16 18:30:52.278 General Parameters
I: 2020-04-16 18:30:52.278 Callsign: YN1OB
I: 2020-04-16 18:30:52.278 Id: 710100306
I: 2020-04-16 18:30:52.278 Duplex: no
I: 2020-04-16 18:30:52.278 Timeout: 180s
I: 2020-04-16 18:30:52.278 D-Star: disabled
I: 2020-04-16 18:30:52.278 DMR: enabled
I: 2020-04-16 18:30:52.278 YSF: enabled
I: 2020-04-16 18:30:52.278 P25: disabled
I: 2020-04-16 18:30:52.278 NXDN: disabled
I: 2020-04-16 18:30:52.278 Modem Parameters
I: 2020-04-16 18:30:52.278 Port: /dev/null
I: 2020-04-16 18:30:52.278 RX Invert: no
I: 2020-04-16 18:30:52.278 TX Invert: no
I: 2020-04-16 18:30:52.278 PTT Invert: no
I: 2020-04-16 18:30:52.278 TX Delay: 100ms
I: 2020-04-16 18:30:52.278 RX Offset: 0Hz
I: 2020-04-16 18:30:52.278 TX Offset: 0Hz
I: 2020-04-16 18:30:52.278 RX DC Offset: 0
I: 2020-04-16 18:30:52.278 TX DC Offset: 0
I: 2020-04-16 18:30:52.278 RF Level: 100.0%
I: 2020-04-16 18:30:52.278 DMR Delay: 0 (0.0ms)
I: 2020-04-16 18:30:52.278 RX Level: 50.0%
I: 2020-04-16 18:30:52.278 CW Id TX Level: 50.0%
I: 2020-04-16 18:30:52.278 D-Star TX Level: 50.0%
I: 2020-04-16 18:30:52.278 DMR TX Level: 50.0%
I: 2020-04-16 18:30:52.278 YSF TX Level: 50.0%
I: 2020-04-16 18:30:52.278 P25 TX Level: 50.0%
I: 2020-04-16 18:30:52.278 NXDN TX Level: 50.0%
I: 2020-04-16 18:30:52.278 RX Frequency: 222340000Hz (222340000Hz)
I: 2020-04-16 18:30:52.278 TX Frequency: 224940000Hz (224940000Hz)
M: 2020-04-16 18:30:52.279 Opening the MMDVM
I: 2020-04-16 18:30:52.279 Display Parameters
I: 2020-04-16 18:30:52.279 Type:
I: 2020-04-16 18:30:52.279 DMR Network Parameters
I: 2020-04-16 18:30:52.279 Address: 74.91.118.251 ;3103.repeater.net
I: 2020-04-16 18:30:52.279 Port: 62031
I: 2020-04-16 18:30:52.279 Local: 62032
I: 2020-04-16 18:30:52.279 Jitter: 360ms
I: 2020-04-16 18:30:52.279 Slot 1: disabled
I: 2020-04-16 18:30:52.279 Slot 2: enabled
I: 2020-04-16 18:30:52.279 Mode Hang: 3s
I: 2020-04-16 18:30:52.279 Info Parameters
I: 2020-04-16 18:30:52.279 Callsign: YN1OB
I: 2020-04-16 18:30:52.279 RX Frequency: 222340000Hz
I: 2020-04-16 18:30:52.279 TX Frequency: 224940000Hz
I: 2020-04-16 18:30:52.279 Power: 1W
I: 2020-04-16 18:30:52.279 Latitude: 41.733299deg N
I: 2020-04-16 18:30:52.279 Longitude: -50.399899deg E
I: 2020-04-16 18:30:52.279 Height: 0m
I: 2020-04-16 18:30:52.279 Location: "Iceberg, North Atlantic"
I: 2020-04-16 18:30:52.279 Description: "MMDVM_Bridge"
I: 2020-04-16 18:30:52.279 URL: "https://groups.io/g/DVSwitch"
M: 2020-04-16 18:30:52.279 DMR, Opening DMR Network
I: 2020-04-16 18:30:52.279 System Fusion Network Parameters
I: 2020-04-16 18:30:52.279 Local Address: 0
I: 2020-04-16 18:30:52.279 Local Port: 3200
I: 2020-04-16 18:30:52.279 Gateway Address: 149.248.2.133
I: 2020-04-16 18:30:52.279 Gateway Port: 42000
I: 2020-04-16 18:30:52.279 Mode Hang: 3s
M: 2020-04-16 18:30:52.279 Opening YSF network connection
I: 2020-04-16 18:30:52.279 RSSI
I: 2020-04-16 18:30:52.279 Mapping File: RSSI.dat
W: 2020-04-16 18:30:52.279 Cannot open the RSSI data file - RSSI.dat
I: 2020-04-16 18:30:52.280 DMR Id Lookups
I: 2020-04-16 18:30:52.280 File: /var/lib/mmdvm/DMRIds.dat
I: 2020-04-16 18:30:52.280 Reload: 24 hours
I: 2020-04-16 18:30:52.589 Loaded 161717 Ids to the DMR callsign lookup table
I: 2020-04-16 18:30:52.589 DMR RF Parameters
I: 2020-04-16 18:30:52.589 Id: 710100306
I: 2020-04-16 18:30:52.589 Color Code: 1
I: 2020-04-16 18:30:52.589 Self Only: no
I: 2020-04-16 18:30:52.589 Embedded LC Only: yes
I: 2020-04-16 18:30:52.589 Dump Talker Alias Data: no
I: 2020-04-16 18:30:52.589 Prefixes: 0
I: 2020-04-16 18:30:52.589 Call Hang: 3s
I: 2020-04-16 18:30:52.589 TX Hang: 3s
I: 2020-04-16 18:30:52.589 Mode Hang: 10s
M: 2020-04-16 18:30:52.589 DMR, Opening INI file: DVSwitch.ini
I: 2020-04-16 18:30:52.589 Started the DMR Id lookup reload thread
M: 2020-04-16 18:30:52.590 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-04-16 18:30:52.590 DMR, Setting [DMR] TXPort -> 31100
M: 2020-04-16 18:30:52.590 DMR, Setting [DMR] RXPort -> 31103
M: 2020-04-16 18:30:52.590 DMR, Setting [DMR] Slot -> 2
M: 2020-04-16 18:30:52.590 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103. Result = 1
I: 2020-04-16 18:30:52.590 YSF RF Parameters
I: 2020-04-16 18:30:52.590 Low Deviation: no
I: 2020-04-16 18:30:52.590 Remote Gateway: no
I: 2020-04-16 18:30:52.590 Self Only: no
I: 2020-04-16 18:30:52.590 DSQ: no
I: 2020-04-16 18:30:52.590 Mode Hang: 10s
M: 2020-04-16 18:30:52.590 YSF, Opening INI file: DVSwitch.ini
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] TXPort -> 31103
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] RXPort -> 31100
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] FallbackID -> 3128973
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] ExportTG -> 710411
M: 2020-04-16 18:30:52.590 YSF, Setting [YSF] Slot -> 2
M: 2020-04-16 18:30:52.590 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100. Result = 1
M: 2020-04-16 18:30:52.590 MMDVM_Bridge-20191105_V1.4.1 is running
M: 2020-04-16 18:31:02.635 DMR, Logged into the master successfully
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
I don't know about anyone else, but it's a little hard to
troubleshoot without seeing the logs.
toggle quoted messageShow quoted text
On 4/16/2020 12:56 PM, Tito Lopez
wrote:
Yep I did that just that rebuilt everything a few days ago, I still get no Audio from DMR <--->YSF Reflector. I see traffic but just that
|
|
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
Tito Lopez - YN1OB
Yep I did that just that rebuilt everything a few days ago, I still get no Audio from DMR <--->YSF Reflector. I see traffic but just that
|
|
|