Date   

Re: TGWhiteList on DVSwitch

IZ1XBB - Pier Paolo
 

Dear Steve,
i'm very sorry for the delay. 
I'm a sysop of an Italian Cluster, called D2ALP (TG222055). I have installed the DVSwitch on a VPS Server with the Analog Reflector in order to permit the multiuser function. All the sysops of this cluster want to fix only this TG (222055) on the server and inhibit the others TG's.
What I have to do? Any idea?

Other question...Actually, the DVS Dashboard is available?

waiting your kindly response.

73 IZ1XBB

Pier Paolo 


Re: DVSwitch YSF

Nick
 

Thanks Steve, its back to the drawing board for me...  Suggestions welcome.
Regards
Nick


Re: DVSwitch YSF

Brett KB5YZB
 

Ernie and Nick, my YSF was working a few weeks ago. No longer and nothing changed. Ernie, is your YSF DVS working?

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Nick via groups.io
Sent: Wednesday, May 11, 2022 11:53 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DVSwitch YSF

 

Hi Ernie,

Yes, it is connected to the private node to ASL. This is why I'm scratching my head. Its an external YSF Refelctor.


Re: DVSwitch YSF

Steve N4IRS
 

Nick,
In your configuration, you have to think of DVSwitch Server as a "hotspot" your AllStar node is the client or radio.
You can connect from AllStar to DMR or you can connect from AllStar to YSF or you can connect from AllStar to NXDN
You can not ADD a YSF connection to a existing AllStar to DMR.

Not that it can't be done, just not your current configuration.

Steve N4IRS
 

On 5/11/22 13:52, Nick via groups.io wrote:
Hi Ernie,

Yes, it is connected to the private node to ASL. This is why I'm scratching my head. Its an external YSF Refelctor.


Re: DVSwitch YSF

Nick
 

Hi Ernie,

Yes, it is connected to the private node to ASL. This is why I'm scratching my head. Its an external YSF Refelctor.


Re: Static Talk Groups on IPSC2 DMR+ Server

GB7NR Support
 

Hi Mike, you do a few options here. You can connect to VKDMR and add an options line and connect direct to the the originating network. You can also connect to IPSC2-FreeSTAR or any IPSC2 for that matter and connect to TG505 as a static. Example ..

DMR Network]
Enable=1
Address=185.169.252.213
Port=55555
Jitter=360
Local=62032
Password=PASSWORD
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
Options=TS1_1=505;TS2_1=23416;
Slot1=0
Slot2=1
Debug=0

This will give you static TG505 & TG23416. Again you can do this on any IPSC2 master. :). The key here is TS1_1=505;

You don’t need add any reflector options at this point either.

Shane
M0VUB


audio files

IK7VXC Mike
 

Hi, I was wondering where the audio files are located. You know the voice that says "connected to ..." in Dstar. And is it possible to edit them?

Thank you

IK7VXC Mike


Re: DVSwitch YSF

 

If you are connected to Ysf network.  It does not go out on Dmr.
It will go out on ASL if you have connected your private node 1999 to ASL Node. Have been caught out myself, forgot that I had restarted the system.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Nick via groups.io <nwebb45@...>
Sent: Wednesday, May 11, 2022 5:09:45 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DVSwitch YSF
 
MMDVM_Bridge.ini

[General]
Callsign=M6KKW
Id=234471666
Timeout=180
Duplex=0
 
[Info]
RXFrequency=222940000
TXFrequency=224940000
Power=1
Latitude=50.795723
Longitude=--0.679109
Height=10
Location=Sussex, England
Description=MMDVM_Bridge
URL=https://www.qrz.com/db/m6kkw
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=B
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=1
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=prime.tgif.network
Port=62031
Jitter=750
Local=62032
Password=Blanked
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=84.9.168.216
GatewayPort=42002
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: DVSwitch YSF

Nick
 

MMDVM_Bridge.ini

[General]
Callsign=M6KKW
Id=234471666
Timeout=180
Duplex=0
 
[Info]
RXFrequency=222940000
TXFrequency=224940000
Power=1
Latitude=50.795723
Longitude=--0.679109
Height=10
Location=Sussex, England
Description=MMDVM_Bridge
URL=https://www.qrz.com/db/m6kkw
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=B
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=1
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=prime.tgif.network
Port=62031
Jitter=750
Local=62032
Password=Blanked
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress=84.9.168.216
GatewayPort=42002
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: DVSwitch YSF

Brett KB5YZB
 

I think I’m having the same issue. I wonder if this DV server is having issues?

 

KB5YZB

 

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Nick via groups.io
Sent: Wednesday, May 11, 2022 8:24 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] DVSwitch YSF

 

Hi,
I have installed Allstarlink Beta 2.00 on a Vultr server.
DMR to ASL (and vice versa) is perfect.
YSF is showing on the DVS dashboard when keyed up, but not transfering to DMR or ASL.
I've been through the forum.. I have tried swapping the ports, but to no avail.
Help would be appreciated.
Thanks in advance..


DVSwitch YSF

Nick
 

Hi,
I have installed Allstarlink Beta 2.00 on a Vultr server.
DMR to ASL (and vice versa) is perfect.
YSF is showing on the DVS dashboard when keyed up, but not transfering to DMR or ASL.
I've been through the forum.. I have tried swapping the ports, but to no avail.
Help would be appreciated.
Thanks in advance..


Tools to unpack and repack the .img file

IK7VXC Mike
 

Hi, 
can someone please recommend the right tools to unpack and later rapack the DVSwitch server .img file?

Thank you
Mike IK7VXC


Re: Static Talk Groups on IPSC2 DMR+ Server

Mike Kilsby
 

Hi Steve, many thanks for the below info.
Had totally missed the .ini edit within the Server Menu.

DMR Network]
Enable=0
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ seehttps://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
Options=
Slot1=0
Slot2=1
Debug=0

I followed the instructions as per above and added the Option line data as required and removed the # sign.
I also changed the enable=1 (which is the default) to 0 as per above and could not connect to the VK Hotspot Server. Changing back to 1 and could connect all ok but no Options string appeared on the server.

Maybe there has been some changes or it is our VK-DMR Hotspot IPSC2 Server?

many thanks for your help. Cheers Mike


Re: Disconnection after 45 seconds

Steve N4IRS
 

Just a comment,
It looks to me like HamVoIP is diverging away from normal AllStarLink operation. I'm becoming concerned. I'm not saying the changes don't have value. It's just becoming a problem dealing with all the things that need to be changed to work properly with HV: 
requirecalltoken (The next version of DVSwitch Mobile will deal with this. Among quite a few added features)
phonesendlinks
propagate_dtmf
propagate_phonedtmf
remote_dtmf_allowed
COP, 25 removed
COP, 26 removed
Remote base

For DVSwitch,
73, N4IRS
 

On 5/9/2022 6:31 PM, Kk6qms wrote:
45sec disconnect on ASL can be caused by "remote base" setting and hamvoip version.
https://community.allstarlink.org/t/iaxrpt-disconnects-after-45-seconds/18082/24

"The problem with node 49562 is that it’s setup as a “remote base” in the allstarlink portal. Here is the nodelist info:

49562=radio@...:4549/49562,74.132.115.111,y

The original remote base mode isn’t supported in HamVoIP, since no IAX2 link messages get sent when enabled as a “remote base.” HamVoIP requires link message (aka: heartbeats) at least every 45 seconds.

The simple solution is to just turn off the “remote base” mode by setting: “Is node a remote base station” to “No” in the allstarlink.org 1, “Node settings” section list.

73, David K4FXC"




Re: Disconnection after 45 seconds

Kk6qms
 

45sec disconnect on ASL can be caused by "remote base" setting and hamvoip version.
https://community.allstarlink.org/t/iaxrpt-disconnects-after-45-seconds/18082/24

"The problem with node 49562 is that it’s setup as a “remote base” in the allstarlink portal. Here is the nodelist info:

49562=radio@...:4549/49562,74.132.115.111,y

The original remote base mode isn’t supported in HamVoIP, since no IAX2 link messages get sent when enabled as a “remote base.” HamVoIP requires link message (aka: heartbeats) at least every 45 seconds.

The simple solution is to just turn off the “remote base” mode by setting: “Is node a remote base station” to “No” in the allstarlink.org 1, “Node settings” section list.

73, David K4FXC"



Re: Static Talk Groups on IPSC2 DMR+ Server

Steve N4IRS
 

[DMR Network]
Enable=0
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

On 5/9/22 22:40, Mike Kilsby wrote:
Hi Group Members, I am looking for some info/help?

I have set up a DVSwitch Server and use the Android DVSM app to control the server.

I was wondering if it is possible to set up static TG’s when DMR mode is set to DMR+.
I often use the VK DMR Hotspot server which is IPSC2.
If you key say TG 505 it will remain on for the 15 mins or so then drop off.
With BrandMeister one can set Static TG’s via Self Care.
When using a Pi-Star server Statics can be set in “Options”

Can the DMR+ ini files? be configured to allow “options” like Pi-Star?

Any info or suggestions as to who can help greatly appreciated.

Best 73 Mike
VK4MY QLD Australia.


Static Talk Groups on IPSC2 DMR+ Server

Mike Kilsby
 

Hi Group Members, I am looking for some info/help?

I have set up a DVSwitch Server and use the Android DVSM app to control the server.

I was wondering if it is possible to set up static TG’s when DMR mode is set to DMR+.
I often use the VK DMR Hotspot server which is IPSC2.
If you key say TG 505 it will remain on for the 15 mins or so then drop off.
With BrandMeister one can set Static TG’s via Self Care.
When using a Pi-Star server Statics can be set in “Options”

Can the DMR+ ini files? be configured to allow “options” like Pi-Star?

Any info or suggestions as to who can help greatly appreciated.

Best 73 Mike
VK4MY QLD Australia.


Re: Dockerize DV-Switch-Server + ASL

Jeff Lehman, N8ACL
 

As long as it would be part of the base os image for the container, or if It could be added, I don't think so, but that is why I was hoping to see Shan'e sdocker file to see how he was doing that.... that was probably pert of my downfall.


On 5/9/22 21:35, Steve N4IRS wrote:
So,
installing AllStar on a AMD64 host can be as simple as apt install allstar. The AllStar that is installed is a binary. For DAHDI that is another matter due to dkms. Does dkms have a problem in a container?

On 5/9/22 21:27, Tony Langdon wrote:
It would be nice, but I suspect (and the evidence still appears to show this) that running ASL in a Docker container is a pipe dream.  The closest one can get it seems is installing ASL on the host and running everything else in Docker containers.  Still relatively straightforward to maintain, backup and recover, because ASL keeps its configs in one place, and you can install it from an apt repository.

And having all other components in containers is a no brainer, they lend themselves to it.  I've had no issues running DVSwitch components under Docker.  Docker also tidies up the networking a bit.  Don't have to expose all ports to the host, only those that need to talk to the outside world.

On 10/5/22 11:00 am, Jeff Lehman, N8ACL via groups.io wrote:

I would love for it to fully run ASL. Here's why it was something I was looking into at one point.

1) it would make for some easy deployement in datacenters that run Docker

2) being able to deploy mulitple installs quickly and easily

2a) Disaster recovery would be so much easier. Since Docker containers are ephemeral by nature, just by backing p the data, you can have an ASL system back up and running in minutes. That is why as much of my personal infrastructure and microservices in my homelab run docker. I can completly wipe a drive and have everything back in 15 minutes versus the hours it would take to install and configure and import all the data. Load the OS, install Docker, copy data, bring the docker containers up and bam... everything is back.

3) ( and this is just purly selfish on my part) I don't run any radio enabled nodes. So I have a box dedicated to ASL that if I could run it on docker, I would be able to use this box for something else. Yes I know i could run it on a pi, but again... I would have a pi dedicated to running ASL that I could use for other projects.

4) and why not :) we have the technology.... ;)

On 5/9/22 15:26, Steve N4IRS wrote:
Depending on what you want the containerized AllStar to do, we may be able to do it with a IAX bridge.

Steve N4IRS

On 5/9/22 15:22, Jeff Lehman, N8ACL via groups.io wrote:
I would love to see your docker file and how you are doing it. I know I struggled with it for a while. I would love to be able to run Allstar in a dockerized environment. Suggestion: get dvswitch/ analog reflector running in its own container so that people can have the option of running those separate. So you can run dvs server, ar and asl in multiple containers


On May 9, 2022, at 10:52, GB7NR Support <support@...> wrote:



Ok.. After some head banging.. and staying up til stupid o’clock I managed to get ASL to work in docker. Infact with some magic I managed to get the two components working that have been causing us all problems. Using the right kernels and OS is key to this. ASL have already attempted to do this but the Dockerfile just does’t work. Why do we need to compile from source when it’s already compiled ! Isn’t that what repo’s are for? Or maybe I’m missing somthing ? I’m no docker guru but love testing this out! :)

anyway I’m going to do some testing later, I’ve created a container with ASL on it fully compiled. I can ssh into it from root so I can see what’s going on. If you can compile from source on debian Buster on the host, why is a container so different? One has to simplify this. If I can get this to work the the DV-Switch element (MMDVM_Bridge etc etc will be a peice of cake to add in docker. Will keep you posted 

Shane 
M0VUB



-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Dockerize DV-Switch-Server + ASL

Steve N4IRS
 

So,
installing AllStar on a AMD64 host can be as simple as apt install allstar. The AllStar that is installed is a binary. For DAHDI that is another matter due to dkms. Does dkms have a problem in a container?

On 5/9/22 21:27, Tony Langdon wrote:
It would be nice, but I suspect (and the evidence still appears to show this) that running ASL in a Docker container is a pipe dream.  The closest one can get it seems is installing ASL on the host and running everything else in Docker containers.  Still relatively straightforward to maintain, backup and recover, because ASL keeps its configs in one place, and you can install it from an apt repository.

And having all other components in containers is a no brainer, they lend themselves to it.  I've had no issues running DVSwitch components under Docker.  Docker also tidies up the networking a bit.  Don't have to expose all ports to the host, only those that need to talk to the outside world.

On 10/5/22 11:00 am, Jeff Lehman, N8ACL via groups.io wrote:

I would love for it to fully run ASL. Here's why it was something I was looking into at one point.

1) it would make for some easy deployement in datacenters that run Docker

2) being able to deploy mulitple installs quickly and easily

2a) Disaster recovery would be so much easier. Since Docker containers are ephemeral by nature, just by backing p the data, you can have an ASL system back up and running in minutes. That is why as much of my personal infrastructure and microservices in my homelab run docker. I can completly wipe a drive and have everything back in 15 minutes versus the hours it would take to install and configure and import all the data. Load the OS, install Docker, copy data, bring the docker containers up and bam... everything is back.

3) ( and this is just purly selfish on my part) I don't run any radio enabled nodes. So I have a box dedicated to ASL that if I could run it on docker, I would be able to use this box for something else. Yes I know i could run it on a pi, but again... I would have a pi dedicated to running ASL that I could use for other projects.

4) and why not :) we have the technology.... ;)

On 5/9/22 15:26, Steve N4IRS wrote:
Depending on what you want the containerized AllStar to do, we may be able to do it with a IAX bridge.

Steve N4IRS

On 5/9/22 15:22, Jeff Lehman, N8ACL via groups.io wrote:
I would love to see your docker file and how you are doing it. I know I struggled with it for a while. I would love to be able to run Allstar in a dockerized environment. Suggestion: get dvswitch/ analog reflector running in its own container so that people can have the option of running those separate. So you can run dvs server, ar and asl in multiple containers


On May 9, 2022, at 10:52, GB7NR Support <support@...> wrote:



Ok.. After some head banging.. and staying up til stupid o’clock I managed to get ASL to work in docker. Infact with some magic I managed to get the two components working that have been causing us all problems. Using the right kernels and OS is key to this. ASL have already attempted to do this but the Dockerfile just does’t work. Why do we need to compile from source when it’s already compiled ! Isn’t that what repo’s are for? Or maybe I’m missing somthing ? I’m no docker guru but love testing this out! :)

anyway I’m going to do some testing later, I’ve created a container with ASL on it fully compiled. I can ssh into it from root so I can see what’s going on. If you can compile from source on debian Buster on the host, why is a container so different? One has to simplify this. If I can get this to work the the DV-Switch element (MMDVM_Bridge etc etc will be a peice of cake to add in docker. Will keep you posted 

Shane 
M0VUB



-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Dockerize DV-Switch-Server + ASL

Jeff Lehman, N8ACL
 

OK good. Sometimes I ramble and think it makes sense when in reality, it makes ZERO sense.

On 5/9/22 21:31, Steve N4IRS wrote:
That covered it, thanks.

On 5/9/22 21:30, Jeff Lehman, N8ACL via groups.io wrote:

AH ok... sorry. I misunderstood.

It would need to function as a full Allstar system. Make calls, receive calls, accept connections from a multitude of different platforms (HUC/Analog reflector/An IAX or SIp client/a PBX etc).

So how I use Allstar. I run a radioless system that has multiple nodes on it. I can connect to it via a PBX (to allow multiple IP based phones for example) or via Analog Reflector for example. I then use it to call other nodes to listen to nets, etc. I also have a couple of club nodes on it to act as a "hub" system. SO I use it as a radio system without a radio.

Does that make any sense? LOL....

On 5/9/22 21:25, Steve N4IRS wrote:
Jeff,
You are telling me why you want to put AllStar in a docker. What you have not told me, is what does the AllStar need to be able to do? Call other nodes? be a hub? etc. How do you USE AllStar?

Steve

On 5/9/22 21:00, Jeff Lehman, N8ACL via groups.io wrote:

I would love for it to fully run ASL. Here's why it was something I was looking into at one point.

1) it would make for some easy deployement in datacenters that run Docker

2) being able to deploy mulitple installs quickly and easily

2a) Disaster recovery would be so much easier. Since Docker containers are ephemeral by nature, just by backing p the data, you can have an ASL system back up and running in minutes. That is why as much of my personal infrastructure and microservices in my homelab run docker. I can completly wipe a drive and have everything back in 15 minutes versus the hours it would take to install and configure and import all the data. Load the OS, install Docker, copy data, bring the docker containers up and bam... everything is back.

3) ( and this is just purly selfish on my part) I don't run any radio enabled nodes. So I have a box dedicated to ASL that if I could run it on docker, I would be able to use this box for something else. Yes I know i could run it on a pi, but again... I would have a pi dedicated to running ASL that I could use for other projects.

4) and why not :) we have the technology.... ;)

On 5/9/22 15:26, Steve N4IRS wrote:
Depending on what you want the containerized AllStar to do, we may be able to do it with a IAX bridge.

Steve N4IRS

On 5/9/22 15:22, Jeff Lehman, N8ACL via groups.io wrote:
I would love to see your docker file and how you are doing it. I know I struggled with it for a while. I would love to be able to run Allstar in a dockerized environment. Suggestion: get dvswitch/ analog reflector running in its own container so that people can have the option of running those separate. So you can run dvs server, ar and asl in multiple containers


On May 9, 2022, at 10:52, GB7NR Support <support@...> wrote:



Ok.. After some head banging.. and staying up til stupid o’clock I managed to get ASL to work in docker. Infact with some magic I managed to get the two components working that have been causing us all problems. Using the right kernels and OS is key to this. ASL have already attempted to do this but the Dockerfile just does’t work. Why do we need to compile from source when it’s already compiled ! Isn’t that what repo’s are for? Or maybe I’m missing somthing ? I’m no docker guru but love testing this out! :)

anyway I’m going to do some testing later, I’ve created a container with ASL on it fully compiled. I can ssh into it from root so I can see what’s going on. If you can compile from source on debian Buster on the host, why is a container so different? One has to simplify this. If I can get this to work the the DV-Switch element (MMDVM_Bridge etc etc will be a peice of cake to add in docker. Will keep you posted 

Shane 
M0VUB




101 - 120 of 10634