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: Hbmonitor full work. Perfectly
Hello
can you help me ?
What is your configuration? INFO:root:Initiating Connection to Server.
INFO:root:Connected.
INFO:root:Resetting reconnection delay
INFO:root:Lost connection. Reason: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
]
|
|
Hbmonitor error message
INFO:root:Initiating Connection to Server.
INFO:root:Connected.
INFO:root:Resetting reconnection delay
INFO:root:Lost connection. Reason: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
|
|
Re: HBBridge setting up more then one link between the two
Corey Dean N3FE <n3fe@...>
Somewhere on your system you are using one of those ports already. That is why it will not start. Corey n3fe
On Tue, Aug 14, 2018 at 12:34 AM KB5PBM <rob297@...> wrote:
|
|
Re: HBBridge setting up more then one link between the two
KB5PBM
with config of ################################################ [DEFAULTS] [IPSCBRIDGE1] [IPSCBRIDGE2]
[RULES] #[DEFAULTS] [IPSCBRIDGE1] [IPSCBRIDGE2]
[RULES] [IPSCBRIDGE2]
|
|
Re: HBBridge setting up more then one link between the two
Cort N0MJS <n0mjs@...>
What is the error?
toggle quoted messageShow quoted text
On Aug 13, 2018, at 7:20 PM, KB5PBM <rob297@...> wrote:
|
|
HBBridge setting up more then one link between the two
KB5PBM
Currently I have IPSC_Bridge configured as below. And two masters configured in dmrlink.cfg master 1 and 2. IPSC_Bridge works fine. However when I try the same with HBBridge i get an error. Is HBBridge able to do the same? To get around this I am running two instances of HBBridge. Needed more timeslots to my C-bridge. Its over kill I know. But easier to exec at startup.
[DEFAULTS] gateway = 127.0.0.1 # IP address of Partner Application (HB_Bridge, Analog_Bridge) fromGatewayPort = 34100 # Port IPSC_Bridge is listening on for data (IPSC_Bridge <--- Partner) toGatewayPort = 34103 # Port Partner is listening on for data (IPSC_Bridge ---> Partner) [MASTER] gateway = 127.0.0.1 # IP address of Partner Application (HB_Bridge, Analog_Bridge) fromGatewayPort = 39400 # Port IPSC_Bridge is listening on for data (IPSC_Bridge <--- Partner) toGatewayPort = 39403 # Port Partner is listening on for data (IPSC_Bridge ---> Partner) [MASTER1] gateway = 127.0.0.1 # IP address of Partner Application (HB_Bridge, Analog_Bridge) fromGatewayPort = 39100 # Port IPSC_Bridge is listening on for data (IPSC_Bridge <--- Partner) toGatewayPort = 39103 # Port Partner is listening on for data (IPSC_Bridge ---> Partner)
|
|
Re: Analog_Bridge gain
I had the same issue I went to positive 10 or 15 with another station listening and that seemed right to us. Your milage could vary. Acg gain for to ASL. Set the other to use acg. Unity means no adjustment I believe.
On Sun, Aug 12, 2018, 1:47 PM Dennis Ramos <m0tfg@...> wrote: hello guys, i just wonder if you can help me to increase my dmr audio going to allstarlink. it is a little bit low.
|
|
Re: Analog_Bridge gain
hey Dennis...use your dmr radio to connect to my ASL - DMR bridge so I can hear your audio DMR on my Allstar node...or I guess you can connect your Allstar node and use you bridge to talk to your node while you are connected to me. My bridge TG is 42555. Mark
On Sun, Aug 12, 2018 at 9:47 PM, Dennis Ramos <m0tfg@...> wrote: hello guys, i just wonder if you can help me to increase my dmr audio going to allstarlink. it is a little bit low.
|
|
Re: Analog_Bridge gain
Dennis Ramos
hello guys, i just wonder if you can help me to increase my dmr audio going to allstarlink. it is a little bit low.
my existing setting are this; default [USRP] server = 127.0.0.1 ; IP address of Allstar/Asterisk toASLPort = 32001 ; Analog_Bridge <-- ASL fromASLPort = 34001 ; Analog_Bridge --> ASL aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN) agcGain = -20 ; Gain (in db) of the AGC filter dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF) dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0) actually i would like to understand those unity, use agc and use gain setting, and the gain levels in db. what are those for. many thanks in advance de dennis/m0tfg
|
|
Re: No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
On Sun, Aug 12, 2018 at 11:21 AM, JJ Cummings wrote:
Box, not boat... yay iThing autospell bahahaha Great it works!
I had a firewall installed on my root.
Have the port 62031 now released.
And I had in the reg_alc.py
PERMIT confused DENY
Thank you very much
I think I have to do an English course Hi Hi
73 Juergen
|
|
Re: No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
JJ Cummings
Box, not boat... yay iThing autospell bahahaha
toggle quoted messageShow quoted text
Sent from the iRoad
On Aug 12, 2018, at 12:10, JJ Cummings <cummingsj@...> wrote:
|
|
Re: No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
JJ Cummings
So it doesn’t look like anything is connecting to it... I’d verify firewall/connectivity etc( basic network troubleshooting)... are you running a firewall on the boat running hblink?... when a connection attempt is made it will be clear in the log.
toggle quoted messageShow quoted text
Sent from the iRoad
On Aug 12, 2018, at 12:06, Jürgen Clemenz <j.clemenz@...> wrote:
|
|
Re: No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
On Sun, Aug 12, 2018 at 08:54 AM, JJ Cummings wrote:
Set your log level to debug and retry, you will see when clients connect... or if you don’t see you know there is still something misconfigured with ports/network/firewall etc....This is only Displayed here DEBUG 2018-08-12 20:04:26,321 Logging system started, anything from here on gets logged
INFO 2018-08-12 20:04:26,322 Registration ACL file found, importing entries. This will take about 1.5 seconds per 1 million IDs
INFO 2018-08-12 20:04:26,322 Registration ACL loaded: action "DENY" for 4 registration IDs
INFO 2018-08-12 20:04:26,322 HBlink TCP reporting server configured
DEBUG 2018-08-12 20:04:26,323 Periodic reporting loop started
INFO 2018-08-12 20:04:26,323 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2018-08-12 20:04:26,324 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:26,324 MASTER instance created: MASTER-1, <__main__.HBSYSTEM instance at 0x7ff47731a5a8>
DEBUG 2018-08-12 20:04:31,326 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:36,326 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:41,328 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:46,326 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:51,327 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:04:56,328 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:01,327 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:06,327 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:11,326 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:16,328 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:21,326 (MASTER-1) Master maintenance loop started
DEBUG 2018-08-12 20:05:26,326 Periodic reporting loop started
DEBUG 2018-08-12 20:05:26,326 (MASTER-1) Master maintenance loop started
73
|
|
Re: No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
JJ Cummings
Set your log level to debug and retry, you will see when clients connect... or if you don’t see you know there is still something misconfigured with ports/network/firewall etc....
toggle quoted messageShow quoted text
Sent from the iRoad
On Aug 12, 2018, at 08:08, Jürgen Clemenz <j.clemenz@...> wrote:
|
|
Re: HBLink Parrot Settings
EA5GVK Joaquin
can you send me the configuration files so that the master works in slot 2 tg 9990?
thank you very much.
|
|
No Voice connection between 2 MMDVM (Pi-Star Software) Hotspots
Hello
Thanks for the help that has already been given to me. You are a great team :-)
After I changed the port to 62031 there are no error messages in the Pi-Star protocol.
I have 2 MMDVM hotspots connected to Hblink Master.
But unfortunately no voice arrives.
1. MMDVM hotspot DO5VH <----------------->2. MMDVM Hotspot DH9YAP . The log of pi-star DO5VH and Dh9yap is attached !! Is no status shown when starting Hblink?
for example
HOTspot ... connect
in the Status
This logfile is empty Also this log is empty : LOG_FILE: /tmp/hblink.log here still my Hblink master cfg: [GLOBAL]
PATH: ./
PING_TIME: 5
MAX_MISSED: 3
[REPORTS]
REPORT: False
REPORT_INTERVAL: 60
REPORT_PORT: 4321
REPORT_CLIENTS: 127.0.0.1
[LOGGER]
LOG_FILE: /tmp/hblink.log
LOG_HANDLERS: console-timed
LOG_LEVEL: INFO
LOG_NAME: HBlink
[ALIASES]
TRY_DOWNLOAD: True
PATH: ./
PEER_FILE: peer_ids.csv
SUBSCRIBER_FILE: subscriber_ids.csv
TGID_FILE: talkgroup_ids.csv
PEER_URL: https://ham-digital.org/status/rptrs.csv
SUBSCRIBER_URL: https://ham-digital.org/status/users.csv
STALE_DAYS: 7
# EXPORT AMBE DATA
# This is for exporting AMBE audio frames to an an "external" process for
# decoding or other nefarious actions.
[AMBE]
EXPORT_IP: 127.0.0.1
EXPORT_PORT: 1234
[MASTER-1]
MODE: MASTER
ENABLED: True
REPEAT: True
EXPORT_AMBE: False
IP:
PORT: 62031
PASSPHRASE: funknetz.nrw
GROUP_HANGTIME: 5
Maybe a port problem ? 73 :-) Juergen
|
|
Re: Master maintenance loop started
On Thu, Aug 9, 2018 at 03:46 PM, Steve N4IRS wrote:
62031 Hello
it seems to work :-)
Here is the log from the pi-star:
I have the port 62031 registered. Is the timeout from the master correct or does it still have to change a setting in the hblink.cfg? 73 Juergen Starting logging, please wait... M: 2018-08-10 11:16:33.121 DMR Slot 2, received RF voice header from DH9YAP to TG ALL M: 2018-08-10 11:16:35.822 DMR Slot 2, received RF end of voice transmission, 2.5 seconds, BER: 0.3%, RSSI: -47/-47/-47 dBm E: 2018-08-10 11:16:54.780 DMR, Connection to the master has timed out, retrying connection M: 2018-08-10 11:16:54.781 DMR, Closing DMR Network M: 2018-08-10 11:16:54.781 DMR, Opening DMR Network M: 2018-08-10 11:17:11.560 DMR Slot 2, received RF voice header from DH9YAP to TG ALL M: 2018-08-10 11:17:16.780 DMR Slot 2, received RF end of voice transmission, 5.0 seconds, BER: 0.5%, RSSI: -47/-47/-47 dBm E: 2018-08-10 11:18:04.908 DMR, Connection to the master has timed out, retrying connection M: 2018-08-10 11:18:04.908 DMR, Closing DMR Network M: 2018-08-10 11:18:04.909 DMR, Opening DMR Network M: 2018-08-10 11:19:14.841 DMR Slot 2, received RF voice header from DH9YAP to TG ALL E: 2018-08-10 11:19:15.026 DMR, Connection to the master has timed out, retrying connection M: 2018-08-10 11:19:15.027 DMR, Closing DMR Network M: 2018-08-10 11:19:15.027 DMR, Opening DMR Network M: 2018-08-10 11:19:21.863 DMR Slot 2, received RF end of voice transmission, 6.8 seconds, BER: 0.4%, RSSI: -47/-47/-47 dBm M: 2018-08-10 11:19:34.584 DMR Slot 2, received RF voice header from DH9YAP to TG ALL M: 2018-08-10 11:19:40.524 DMR Slot 2, received RF end of voice transmission, 5.8 seconds, BER: 0.5%, RSSI: -47/-47/-47 dBm E: 2018-08-10 11:20:25.165 DMR, Connection to the master has timed out, retrying connection M: 2018-08-10 11:20:25.165 DMR, Closing DMR Network M: 2018-08-10 11:20:25.165 DMR, Opening DMR Network
|
|
Re: HBlink "socket_address" Branch
Jose - EA5SW
Tested the sockek branch:
hb_link runs OK for me. Connects to some systems, as peer and some peers connect to masters. hb_confbridge links also all at the moment OK hb_parrot don't work as master.. some errors, I tried to figure to change the config but no luck. To be continued...
|
|
Re: Master maintenance loop started
So,
toggle quoted messageShow quoted text
HBlink is listening on port 5400. See Albert's message about the Pi-Star firewall. I suggest you test on port 62031 since it is not firewalled. Steve n4IRS
On 08/09/2018 06:17 PM, Jürgen Clemenz
wrote:
On Thu, Aug 9, 2018 at 11:32 AM, Steve N4IRS wrote:
|
|
Re: Master maintenance loop started
Albert Lawson
Pi-Star has an inbound and outbound firewall configured by default that could be affecting it's ability to connect. Have you looked at those settings by chance...???
73's
Albert/WB7AWL
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Jürgen Clemenz <j.clemenz@...>
Sent: Thursday, August 9, 2018 10:30 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] Master maintenance loop started Maybe you can try to connect my master.
Address: 213.202.228.66
Port 5400
Password: funknetz.nrw
|
|