Date   

Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

You CAN, but if you configure Analog_Bridge for YSF that is how it will startup. After that lets say you want to change reflectors, there is where dvswitch.sh would come in. Another example would be if you want to raise or lower the audio level without restarting AB, you could use dvswitch.sh to do it.

 Steve

On 12/26/19 6:56 PM, ve6gcd@... wrote:
Thanks Steve,

Does that mean I can insert a startup macro for the USRP node via rpt.conf so it will run dvswitch.sh in YSF mode?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Thanks Steve,

Does that mean I can insert a startup macro for the USRP node via rpt.conf so it will run dvswitch.sh in YSF mode?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

No it does not. dvswitch.sh is used to send commands to a running AB. You can run it with ./dvswitch.sh to see the list of available commands. dvswitch.sh can be used in scripts or ASL commands.

Steve

On 12/26/19 5:57 PM, ve6gcd@... wrote:
Hi Steve,

Just one more question before the reinstall, does Analog_Bridge run dvswitch.sh automatically at startup?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Hi Steve,

Just one more question before the reinstall, does Analog_Bridge run dvswitch.sh automatically at startup?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

I really have to update the system builder script.
Here are a few things you should do.
We post the latest code for the DVSwitch programs in github before the make it to the apt repository.
For Analog Bridge the repo is at <https://github.com/DVSwitch/Analog_Bridge>
I suggest you get the executable for your system from the bin directory
There have been some changes to the .ini file take a look at those.
There are newer macro files and a script that will help you control a running system. it is dvswitch.sh

For MMDVM_Bridge the repo is at <https://github.com/DVSwitch/MMDVM_Bridge
Get the updated executable from the bin directory.

If all you are planning to run is YSF, I suggest you turn off the other modes and mode networks in MMDVM_Bridge.ini

Hope this helps,
73, Steve N4IRS

On 12/26/19 5:36 PM, ve6gcd@... wrote:
Hi Steve,

Analog_Bridge in my computer was installed using DVSwitch-System-Builder.

Do I need to set anything under the MACROS section (to set the mode)? Anyway, below is the config of my setup.

===================================================================================
; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 1                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 35103                          ; Transmit TLV frames to partner on this port
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3026120                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 302612001                          ; ID of source repeater
txTg = 3026120                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)
[MACROS]
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
; For example using macro "5678" above would look like:
; *5678#9876
; Which would invoke:
; echo 9876
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
;address = 127.0.0.1                   ; IP address of AMBEServer
;rxPort = 2460                         ; Port of AMBEServer
 address = /dev/ttyUSB0              ; Device of DV3000U on this machine
 baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
 serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer
===================================================================================


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Hi Steve,

Analog_Bridge in my computer was installed using DVSwitch-System-Builder.

Do I need to set anything under the MACROS section (to set the mode)? Anyway, below is the config of my setup.

===================================================================================
; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 1                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 35103                          ; Transmit TLV frames to partner on this port
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3026120                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 302612001                          ; ID of source repeater
txTg = 3026120                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)
[MACROS]
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
; For example using macro "5678" above would look like:
; *5678#9876
; Which would invoke:
; echo 9876
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
;address = 127.0.0.1                   ; IP address of AMBEServer
;rxPort = 2460                         ; Port of AMBEServer
 address = /dev/ttyUSB0              ; Device of DV3000U on this machine
 baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
 serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer
===================================================================================


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

Geoffrey,
Can you post your Analog_Bridge.ini so we can start there?

Steve N4IRS

On 12/26/19 2:50 PM, ve6gcd@... wrote:
Happy New Year Everyone,

I am trying to bridge ASL directly to YSF/FCS. We are trying to avoid conflict with Brandmeister requirements at the moment which is why we are considering to bridge ASL and FCS directly. During my initial setup it appears Analog_Bridge is rejecting the AMBE72 packets received from YSFGateway. Upon checking the logs, I noticed that the mode keeps being set to "DMR" even if AMBE_MODE has been set to "YSFN". I am currently running Debian Linux on amd64 hardware for this setup.

Geoffrey VE6GCD  


ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Happy New Year Everyone,

I am trying to bridge ASL directly to YSF/FCS. We are trying to avoid conflict with Brandmeister requirements at the moment which is why we are considering to bridge ASL and FCS directly. During my initial setup it appears Analog_Bridge is rejecting the AMBE72 packets received from YSFGateway. Upon checking the logs, I noticed that the mode keeps being set to "DMR" even if AMBE_MODE has been set to "YSFN". I am currently running Debian Linux on amd64 hardware for this setup.

Geoffrey VE6GCD  


Re: setting up MMDVM_Bridge and Analog_Bridge #analog_bridge #mmdvm_bridge

ve6gcd@...
 

Hi Steve,

Can you tell me how to configure ASL direct bridge to YSF we are currently avoiding conflict with DMR/Brandmeister regulations at the moment. I tried it and keeps noticing in the debug that mode being set to DMR even when ambe_mode is YSFN.

73,
Geoffrey VE6GCD 


Re: Need help getting DV Switch to change DMR Talk Groups #analog_bridge

Ted Lawrence
 

Yes, Thanks for responding Steve.  Yes, running DVSwitch on Raspberry Pi bridge between DMR and AllStar.  I had set static TG 315136 set on BrandMeister and change it to static TG 315135. BrandMeister kept resetting and reporting 315136 as static.  After a period I finally realized, that BransMister was looking for a clear TG 4000 from the bridge hotspot after I made the static change.  I could not issue that command from the ASL/DMR Bridge.  However, BrandMeister cleared the TG 315136 after the period timeout.  So all works as it should now.

Ted KD4EG


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Ken, K6EFJ
 

Thanks Adrian and everyone that helped me find where to change language to english. Turns out there are 4 locations that had the file I needed to modify. Three were just extras that had been saved in a folder called LinuxExtras and the one I actually needed to modify at  path= /usr/local/etc/opendv/ircddbgatway

I now have Dstar voice in english,  Merry Christmas
Ken Smith K6EFJ 


Re: Hytera DMR Gateway

Marco IW0RED
 

Hi Joaquin, I don't have one raspberry 3 (it is too old) but only one
raspberry 3+ that doesn't run debian Jessie.
Do you have the source code of the hytera gw mmdvm software?
I'm sorry but I don't use the mmdvm to xlx bridge.
73 Marco IW0RED.
Happy New Year.

On Wed, Dec 25, 2019 at 11:06 AM EA5GVK Joaquin <ea5gvk@gmail.com> wrote:

Hi Marco, it is version linux.
I have running hytera gw mmdvm, perfect.
the connection to the XLX by mmdvm, the audio is cut, in the direction of the XLX to the Repeater Hytera rd625 PERFECT.
BUT IN SENSE REPEATER TO XLX, THE AUDIO IS CUTTED TWO SECONDS TO BEGIN.
CAN YOU HELP OR GUIDE ME?
thanks.
Happy New Year.
PD: Firmware rd625 hytera A9.00.10.100.iM
--
Marco Brunozzi

Tel. +14152360004
Cel. +393483343274
Skype: marco.brunozzi
Twitter: marcobrunozzi
---------------------------------------


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Adrian Fewster <vk4tux@...>
 

Looks like these came from the redundant DL5DI Opendv repository, instead of G4KLX repository then.

Those long paths there, adding the opendv user from previous wx2.8 version were silly.

The G4KLX repo provides much easier customisation and latest developments ;

https://github.com/g4klx/ircDDBGateway/blob/master/Makefile

ifeq ($(TARGET), opendv)

export DATADIR := "/usr/share/opendv"

export LOGDIR := "/var/log/opendv"

export CONFDIR := "/etc"

export BINDIR := "/usr/sbin"

else

export DATADIR := "/usr/share/ircddbgateway"

export LOGDIR := "/var/log"

export CONFDIR := "/etc"

export BINDIR := "/usr/bin"

endif


https://github.com/g4klx/ircDDBGateway


On 25/12/19 8:48 pm, ea7jcl@... wrote:
Hi group

path = /usr/local/etc/opendv/ircddbgateway

Merry Christmas


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

SP2ONG Waldek
 


Maybe someone will need this description to configure ircddbgateway

http://www.dvmega.co.uk/manual/ircDDBGateway-ENG.pdf

Merry Christmas


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

ea7jcl@...
 

Hi group

path = /usr/local/etc/opendv/ircddbgateway

Merry Christmas


Re: Hytera DMR Gateway

EA5GVK Joaquin
 

Hi Marco, it is version linux.
I have running hytera gw mmdvm, perfect.
the connection to the XLX by mmdvm, the audio is cut, in the direction of the XLX to the Repeater Hytera rd625 PERFECT.
BUT IN SENSE REPEATER TO XLX, THE AUDIO IS CUTTED TWO SECONDS TO BEGIN.
CAN YOU HELP OR GUIDE ME?
thanks.
Happy New Year.
PD: Firmware rd625 hytera A9.00.10.100.iM


Re: ASL to DMR change TG with DTMF?

sigmazgfx@...
 

No worries. I figured it out.
Thanks again guys, this is great!

I still need to slip in the commands to keep allison off the dmr node. And I still need to kick on the d-star side too. 
It'll be awesome to have ASL, DMR, D-Star and analog in the car. (Very happy) 

73 de W2JON


Re: 1 Way Audio (XLX DMR to ASL)

Michael KD5DFB
 

Figured it out.

uname -a
Linux mmdvm 4.9.0-7-amd64 #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13) x86_64 GNU/Linux
cd /tmp
wget https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.amd64
cp /tmp/MMDVM_Bridge.amd64 /opt/MMDVM_Bridge2/MMDVM_Bridge
MMDVM_Bridge version 20191105_V1.4.1 git #9dae1ac

I will test audio this afternoon when I have all my portable radios :-)


Re: 1 Way Audio (XLX DMR to ASL)

Michael KD5DFB
 

Steve,

Thank you for the quick response!

I am not 100% sure which one to use. Here is my lscpu

use MMDVM_Bridge.i386??

root@mmdvm:/opt/HBlink# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 61
Model name:            Virtual CPU a7769a6388d5
Stepping:              2
CPU MHz:               2394.438
BogoMIPS:              4788.87
Hypervisor vendor:     KVM
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              4096K
L3 cache:              16384K
NUMA node0 CPU(s):     0
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single kaiser fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat


Re: 1 Way Audio (XLX DMR to ASL)

Steve N4IRS
 

Michael,
I think your one way audio issue may be solved by using the most current MMDVM_Bridge in github at <https://github.com/DVSwitch/MMDVM_Bridge/tree/master/bin>

On 12/24/19 11:57 AM, Michael KD5DFB wrote:
I am trying to bridge from our c-bridge to my xlx reflector and I am experiencing the same 1 way audio.

cbridge<>IPSC_Bridge<>HB_Bridge<>MMDVM-Bridge<>XLX

The audio works from XLX to DMR but NOT the other way.

I tried the following and thought it would be an easier setup but I keep getting the following error. I am looking for the most efficient way

cbridge<>IPSC_Bridge<>HB_Bridge<>XLX

root@mmdvm:/opt/HBlink# python HB_Bridge.py
load config file config.file
DEBUG 2019-12-24 10:48:20,863 Logging system started, anything from here on gets logged
INFO 2019-12-24 10:48:20,864 ID ALIAS MAPPER: 'peer_ids.json' is current, not downloaded
INFO 2019-12-24 10:48:20,864 ID ALIAS MAPPER: 'subscriber_ids.json' is current, not downloaded
INFO 2019-12-24 10:48:21,315 HBlink 'HB_Bridge.py' (c) 2017 Mike Zingman N4IRR, N0MJS - SYSTEM STARTING...
INFO 2019-12-24 10:48:21,315 Version 20170620
DEBUG 2019-12-24 10:48:21,317 (MASTER-1) Master maintenance loop started
DEBUG 2019-12-24 10:48:21,317 MASTER instance created: MASTER-1, <__main__.HB_BRIDGE instance at 0x7f96dc141cf8>
ERROR 2019-12-24 10:48:21,318 Uncaught exception
Traceback (most recent call last):
  File "HB_Bridge.py", line 243, in <module>
    systems[system] = HB_BRIDGE(system, CONFIG, logger)
  File "HB_Bridge.py", line 101, in __init__
    self.hb_ambe = AMBE_HB(self, _name, _config, _logger, self._ambeRxPort)
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 381, in __init__
    AMBE_BASE.__init__(self, _parent, _name, _config, _logger, _port)
  File "/usr/local/lib/python2.7/dist-packages/dmr_utils/ambe_bridge.py", line 187, in __init__
    self.udp_port = reactor.listenUDP(self._ambeRxPort, UDP_IMPORT(self.import_datagramReceived))
  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 369, in listenUDP
    p.startListening()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 178, in startListening
    self._bindSocket()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/udp.py", line 198, in _bindSocket
    raise error.CannotListenError(self.interface, self.port, le)
CannotListenError: Couldn't listen on any:36100: [Errno 98] Address already in use.
root@mmdvm:/opt/HBlink#

I can just run python hblink.py and it works fine. I don't understand why I am getting the CannotListenError: Couldn't listen on any:36100: [Errno 98] Address already in use.

No other process is using port 36100

Also, what option do I need to put in under OPTIONS: to connect to module A?

hblink.cfg
[XLX 827]
MODE: CLIENT
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP:
PORT: 50006
MASTER_IP: xlx.kd5dfb.net   
MASTER_PORT: 62030
PASSPHRASE: passw0rd
CALLSIGN: KD5DFB
RADIO_ID: 3148242
RX_FREQ: 222340000
TX_FREQ: 223940000
TX_POWER: 25
COLORCODE: 1
SLOTS: 3
LATITUDE: 41.7333
LONGITUDE: -50.3999
HEIGHT: 75
LOCATION: Iceberg, USA
DESCRIPTION: HBlink repeater
URL: https://groups.io/g/DVSwitch
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 5
OPTIONS: 4001

4301 - 4320 of 9891