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: "Node 1998" message when connected to the node
Wow, you really did not see the vertical row of the numbers 1999?
toggle quoted messageShow quoted text
Sent by smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Bryan <kf1d@...>
Sent: Saturday, January 29, 2022 11:27:01 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] "Node 1998" message when connected to the node Hi Mike,
Yes, that removed the automated announcement of "Node 1998" when connecting. Now, it connects without any announcement. Thanks. So the only issue that I have now, is no data showing up in the Status page on the app. Bryan
|
|
|
|
Re: "Node 1998" message when connected to the node
Bryan
Hi Mike,
Yes, I agree. I wouldn't expect my node number to show up in the Status page. I connected my node to another node and the other node's information doesn't show up in the status page. I seem to recall, that with my old node, I would connect to East Coast Reflector and the status page would display all the callsigns and nodes utilizing that reflector. However, with this latest build, nothing is displayed. Thanks, Bryan
|
|
|
|
Re: "Node 1998" message when connected to the node
If you are connected to 53450
I don't think it shows in the list, it should show what is connected to "it"/53450 It is not connected to itself.
|
|
|
|
Re: "Node 1998" message when connected to the node
Bryan
Hi Mike,
Yes, that removed the automated announcement of "Node 1998" when connecting. Now, it connects without any announcement. Thanks. So the only issue that I have now, is no data showing up in the Status page on the app. Bryan
|
|
|
|
Re: "Node 1998" message when connected to the node
try it like this....
[android-iaxrpt] ;;; Stanza is the context from iax.conf exten => 53450,1,Answer exten => 53450,n,Set(CALLERID(num)=0) exten => 53450,n,Rpt,53450|P|${CALLERID(name)} ;;; The "CallerID" from IAXRpt
|
|
|
|
Re: "Node 1998" message when connected to the node
Bryan
Hi Steve,
I compared your stanza text with my stanza text in the message directly below your message and it looks the same. With that text, I still get the "1998" and also no information on the status page. Thanks, Bryan
|
|
|
|
Re: "Node 1998" message when connected to the node
extensions.conf
On 1/29/22 22:29, Bryan wrote:
Hi Steve and Dave,
|
|
|
|
Re: "Node 1998" message when connected to the node
Bryan
Hi Steve and Dave,
I fixed the "NOCID" showing up in the allstarlink node information webpage. That is no longer an issue. Currently everything is working fine. I can connect to my node and other nodes fine. But I still have these two issues: 1. I still get the automated announcement "Node 1998" message when I initially connect to my node. 2. I noticed that the Status page on the app does not show any connections. I remember, on my last node, when I connected to East Coast Reflector, I would see all the connections on the status page. Now it is blank. I am running the node with the latest system updates. See below for the stanzas. Again, everything is working ok, but I just have these odd issues. iax.conf [KF1D] ; The stanza is the Username from the phone app
type=friend
context=android-iaxrpt
host=dynamic
auth=md5
secret=****; PASSWORD
disallow=all
allow=ulaw
transfer=no
calltokenoptional=0.0.0.0/0.0.0.0
requirecalltoken=no
Thanks,extensions.conf [android-iaxrpt] ;;; Stanza is the context from iax.conf
exten => 53450,1,Answer
exten => 53450,n,Playback,rpt/node
exten => 53450,n,Playback,digits/1
exten => 53450,n,Playback,digits/9
exten => 53450,n,Playback,digits/9
exten => 53450,n,Playback,digits/8
exten => 53450,n,Set(CALLERID(num)=0)
exten => 53450,n,Rpt,53450|P|${CALLERID(name)} ;;; The "CallerID" from IAXRpt
Bryan
|
|
|
|
Re: Pi-star for a RX only?
You might try a usrp connection to a node config'd with the same. Probably have to see pistar folks for that usrp on their side. That is how we get DVS to ASL. Anyway, that's my only idea.
On 1/29/2022 1:36 PM, Steve KC1AWV
wrote:
I know that this is a bit off-topic for the board, so Steve please forgive me, but this has me thinking.
|
|
|
|
Re: Pi-star for a RX only?
I know that this is a bit off-topic for the board, so Steve please forgive me, but this has me thinking.
As a thought experiment: I wouldn't use Pi-Star. I would create my own install of MMDVM and MMDVM_HS. Configure MMDVM to work as normally, but use something like iptables to block incoming UDP packets from the network. This may result in what you want - a 'hotspot' that hears, but can't talk. I say not to use Pi-Star only because there's a lot of overhead for functions that are being purposely broken for this application. Pi-Star also has auto-update features that can cause your desired config to change without notice. -Steve KC1AWV
|
|
|
|
New Subgroup
With the increase of HamVoIP questions and answers since I created the installer for HamVoIP, I have decided to create a subgroup. <https://dvswitch.groups.io/g/HamVoiP> Please as HamVoIP specific questions in that subgroup.
Steve N4IRS
|
|
|
|
Re: Allstar node 50281 and dvswitch
Jimmy, I do not see a way that installing DVSwitch Server on another card could corrupt a system on your main card. I suggest you look at your asterisk log to see why it's not starting. Steve N4IRS
On 1/29/22 12:02, Jimmy wrote:
|
|
|
|
Re: Pi-star for a RX only?
toggle quoted messageShow quoted text
On 1/29/22 13:03, chris wrote:
Hello everyone,
|
|
|
|
Pi-star for a RX only?
chris
Hello everyone,
I would like to set one of my hotspots to RX only. I have a slight null on my repeater system to the southeast about 15 miles out how ever the TX of the repeater is very good and using a mobile there is no issues. I would like to use a hot spot as a RX only solution for HT's. We have a hot spot on top a building currently in the area with the null, the tested has shown it works very well as a satellite receiver. The problem is the hotspot still transmits and we would avoid this all together. Yes, we can change the offset on the TX side to +20000 and we would not hear the TX but this isn't correct because it's still TX-ing just on a diffrent freq. Is there anyway to rewrite the code for RX only?
|
|
|
|
Re: DVSwitch HAMVOIP
#dvs
John EA5JAV/M0JCA
Hi Steve, I promised I would double-check the IAX password step again, started from another clean image and did it again following your instructions that were spot on, I have one observation which may be of interest, all working perfectly (Allstar via IAX2, DMR, P25 etc on USRP) using DVSwitch, however what’s interesting is that in DVSM I have my callsign EA5JAV in the [Username] field and in the [Password] field have my correct Password that I chose previously when setting up as per instructions and everything works perfectly, I happened to check /etc/asterisk/iax.conf, the stanza for [EA5JAV] had a blank password, so it hasn’t picked it up when going through the setup menu, another interesting thing is that as the password is blank, I can enter anything in DVSM password field and it connects and works. I’ve manually changed iax.conf and replaced the blank password to have the correct one, and all good now. Apart from that everything else fine, thanks again Steve
|
|
|
|
Allstar node 50281 and dvswitch
Jimmy
Hi
|
|
|
|
Simplex repeater?
Rob KA2PBT <pabutusa@...>
Has anyone ever constructed a simplex repeater? Something like a "parrot" but actually connected to a radio?
I'm not looking to connect to any network. Just a free standing node that grabs the voice packets and then sends them back out. Not an ideal situation but something that could be setup to extend range for a project or event. Regards, --> Rob, KA2PBT
|
|
|
|
Re: DVSwitch HAMVOIP
#dvs
John EA5JAV/M0JCA
I'll take a backup and retry that Steve, ty
|
|
|
|
Re: DVSwitch HAMVOIP
#dvs
John EA5JAV/M0JCA
Ps. also edited manager.conf so I can use application "Node Remote" to change/disconnect Allstar nodes, and can confirm that node remote working too
|
|
|
|
Re: DVSwitch HAMVOIP
#dvs
Glad it's working. When you ran the first time setup you should
have been asked for a IAX password. It should have inserted that
password into iax.conf You can run option 3 again and after the
reboot, you can walk through the settings and see/set the IAX
password.
On 1/28/22 16:53, John-EA5JAV wrote:
Hi Steve, well all I can say is a huge THANK-YOU, with the exception of the tri colour LED which I will speak to Peter about, everything is now working and tested on DVSwitch.
|
|
|