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: Allstar to DMR ID
The DMR IDs for repeaters are 6 digit, we are up to 5 digits. Our
node numbers do not fit within the DMR ID system.
toggle quoted messageShow quoted text
There are some possibilities that could be explored. The big issue is that when a user radio displays a DMR ID it is the transmitting station, not the repeater. For ASL that data is not available. The best we can do is to get the node number of the ASL node originating the transmission. As it happens, Mike and I started a conversation just today about a method to transmit ASL node data with each transmission. Stay tuned. 73, Steve N4IRS
On 01/08/2018 07:07 PM, David KE6UPI
wrote:
|
|
|
|
Re: Allstar to DMR ID
David KE6UPI
It would be nice to register a DMR ID for the ASL node. i.e. ASL 2060 Then a DMR user could lookup the node number. David KE6UPI -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Jan 3, 2018 at 7:39 PM, Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Bridging AllStarLink to other modes.
Could not agree more . I had to do a couple of conferences to get some acceptance about the idea of a Bridge between DMR and Analog Allstar .... Even after that , there is still some mumbling about the implementation . My answer is that DMR fans can surely spare 1 TG amongst the thousand there is on the system. Analog Bridge is only using the CALL HOME TG ( Repeater DMR ID ) . I installed 2 systems , one in my region that is lets say "accepted" ... Another in a region that did not bother to explain the concept ..... All hell broke loose ..... Ham radio programmers and more technically oriented colaborators are not very good at selling their approach . More at ease in getting the job done. Get out and speak to club meetings and to on the air gathering . It's part of selling the amazing work that is being done by all of you .....
Not enough words to express my thanks to all you guys who made it all happen.....
Richard VE2DJE Le 06/01/2018 à 13:09, Peter M0NWI a
écrit :
Hi Steve,
|
|
|
|
Re: Bridging AllStarLink to other modes.
Peter M0NWI
Hi Steve,
Couldn't agree more, in the UK our Ham licence actually says for educational purposes, and it's something us Amateurs have always done, including bending commercial systems to our needs be that a retuned ex Police radio to operate 2m or DMR networks. In the UK on the hubNet, Peter G7RPG has used DVSwitch to link in DMR from BM into AllStar and it works well, and expands the reach to others, a worthwhile thing. 73, Peter Sent from Outlook From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 05 January 2018 20:45:34 To: DVSwitch@groups.io Subject: [DVSwitch] Bridging AllStarLink to other modes. I was forwarded a post from Doug WA3DSP concerning interconnection to
other services/modes on the HAMVOIP list. I have seen in the past that Doug considers himself the guardian of all good audio and AllStarLink. That is open to discussion. I think this needs to be addressed in the community. Great audio quality is a hallmark of AllStarLink and no one wants to compromise that. Another feature that singles out AllStarLink is flexibility. People have done some amazing things with AllStarLink. There are nodes and hubs that control what type of traffic pass through the node or hub. There are quite a few nodes and hubs that welcome experimentation. Connecting a foreign mode or service to a AllStarLink node is never a good idea without prior discussion. One of the many features of AllStarLink that drew me in over 10 years ago, was the ability to add features and devices. One very important fact is that it is open source. Well, at least the official AllStarLink distribution is. Channel drivers are available for EchoLink, D-Star, TLB and USRP. If it's not there, it can be added. AllStarLink welcomes people to add to and modify the open source available in github. If you have an idea, bring it up, submit a pull request and let's see how it fits. People are going to extend the capabilities of AllStarLink, that is a given. Those extensions may not be to everyone's liking. Under the banner of DVSwitch, a few of us have been building tools for bridging between different voice networks. One of those is AllStarLink. It does not matter if the purpose of the bridge is to expose analog users to the capabilities of a digital network or to display the capabilities of AllStarLink to a group of digital voice users that are not aware of a large network of open source analog nodes. There are quite a few hams that do not know about AllStarLink. This gives them a taste. I'm pretty sure every one of the digital voice radios in use support analog. Do we really want to display a negative attitude to other communities? I can tell you that not everyone on the digital voice networks want to see a bridge to analog. They don't want "those noisy analog signals" on their network. This is not a discussion of which voice mode is better. Nor is it about how to make digital voice sound better. I tell people building bridges the same thing, Don't just drop a analog bridge onto a digital channel without discussion first. One digital network I have seen is reporting over 10K calls per hour. (That might be a interesting stat to collect for AllStarLink) Bridging networks is not the purpose of AllStarLink and I would rather not see discussions of various networks on the AllStarLink user list. There are other places for that. The open source nature of AllStarLink lends itself to extension. Just be aware what you are doing and who it will effect. 73, Steve N4IRS
|
|
|
|
Re: Allstar USRP host
Mike,
toggle quoted messageShow quoted text
What error do you get? What is in the log? Do you have the USRP node in the node stanza? Steve
On 01/05/2018 09:46 PM, Mike
Swiatkowski via Groups.Io wrote:
I'm having problems connecting my allstar USRP nodes (i.e node number that interfaces to analog_bridge) to other USRP nodes. I have no problem connecting the USRP to a URIx hardware node. But, I cannot do it the other way around, like hardware URIx to USRP. So, does anyone have any idea why I am having this problem of not being able to connect my USRP nodes to anything but a physical hardware node (like a URIx interface) and how I can fix it?
|
|
|
|
Allstar USRP host
Mike, AA9VI
I'm having problems connecting my allstar USRP nodes (i.e node number that interfaces to analog_bridge) to other USRP nodes. I have no problem connecting the USRP to a URIx hardware node. But, I cannot do it the other way around, like hardware URIx to USRP. So, does anyone have any idea why I am having this problem of not being able to connect my USRP nodes to anything but a physical hardware node (like a URIx interface) and how I can fix it?
Mike, AA9VI
|
|
|
|
Bridging AllStarLink to other modes.
I was forwarded a post from Doug WA3DSP concerning interconnection to other services/modes on the HAMVOIP list. I have seen in the past that Doug considers himself the guardian of all good audio and AllStarLink. That is open to discussion. I think this needs to be addressed in the community. Great audio quality is a hallmark of AllStarLink and no one wants to compromise that. Another feature that singles out AllStarLink is flexibility. People have done some amazing things with AllStarLink. There are nodes and hubs that control what type of traffic pass through the node or hub. There are quite a few nodes and hubs that welcome experimentation. Connecting a foreign mode or service to a AllStarLink node is never a good idea without prior discussion.
One of the many features of AllStarLink that drew me in over 10 years ago, was the ability to add features and devices. One very important fact is that it is open source. Well, at least the official AllStarLink distribution is. Channel drivers are available for EchoLink, D-Star, TLB and USRP. If it's not there, it can be added. AllStarLink welcomes people to add to and modify the open source available in github. If you have an idea, bring it up, submit a pull request and let's see how it fits. People are going to extend the capabilities of AllStarLink, that is a given. Those extensions may not be to everyone's liking. Under the banner of DVSwitch, a few of us have been building tools for bridging between different voice networks. One of those is AllStarLink. It does not matter if the purpose of the bridge is to expose analog users to the capabilities of a digital network or to display the capabilities of AllStarLink to a group of digital voice users that are not aware of a large network of open source analog nodes. There are quite a few hams that do not know about AllStarLink. This gives them a taste. I'm pretty sure every one of the digital voice radios in use support analog. Do we really want to display a negative attitude to other communities? I can tell you that not everyone on the digital voice networks want to see a bridge to analog. They don't want "those noisy analog signals" on their network. This is not a discussion of which voice mode is better. Nor is it about how to make digital voice sound better. I tell people building bridges the same thing, Don't just drop a analog bridge onto a digital channel without discussion first. One digital network I have seen is reporting over 10K calls per hour. (That might be a interesting stat to collect for AllStarLink) Bridging networks is not the purpose of AllStarLink and I would rather not see discussions of various networks on the AllStarLink user list. There are other places for that. The open source nature of AllStarLink lends itself to extension. Just be aware what you are doing and who it will effect. 73, Steve N4IRS
|
|
|
|
Re: Allstar to DMR ID
David,
toggle quoted messageShow quoted text
I usually my own radio id. My wife is a ham so I have been known to use hers. Steve
On 01/03/2018 10:25 PM, David wrote:
Hi
|
|
|
|
Allstar to DMR ID
David
Hi
What is everyone running for a ID from analog when you do a allstar to dmr bridge. 0 was giving me troubles on my radio.
|
|
|
|
Re: Analog_Bridge Allstar Link Guidance
David
After digging threw GitHub I found hb_bridge. It is all working for me now.
On Jan 3, 2018 6:40 PM, "David" <david@...> wrote:
|
|
|
|
Re: Analog_Bridge Allstar Link Guidance
David
I redownloaded everything and now that part is working. I have Analog_bridge running right I think. Do I run hblink.py or hb_bridge_all.py? I do have some things in hblink.cfg. When I connect to the allstar node from another analog_bridge does show my ptt on and off. Thanks for the help.
On Tue, Jan 2, 2018 at 8:46 PM, Steve N4IRS <szingman@...> wrote: David,
|
|
|
|
Re: Analog_Bridge Allstar Link Guidance
David,
Just to verify, which Analog_Bridge are you running? For the Pi should be Analog_Bridge.ARM. You can rename it to just Analog_Bridge. Also, please post your Analog_bridge.ini 73, Steve N4IRS
|
|
|
|
Re: Analog_Bridge Allstar Link Guidance
David
I am just starting this part. The test with the dongle works. I go to start Analog_bridge and it get all they way down to starting serial for the dongle and I get a Segmentation fault error.
ps Running on a pi3
|
|
|
|
Re: confbridge.py and TG Bridge state change fun
JJ Cummings
Of course I have not had the time to get to this, hopefully sometime in the next few weeks I can sit down and look at it unless Mike has already done so?
On Thu, Nov 9, 2017 at 7:31 AM, JJ Cummings <cummingsj@...> wrote:
|
|
|
|
Re: OT Help
Corey Dean N3FE <n3fe@...>
Ok well if there anything you guys ever need, just let me know. I can help you with connections from 3102, 3103, or 3108....
toggle quoted messageShow quoted text
Corey N3FE Sent from my iPhone
On Dec 29, 2017, at 7:01 PM, Cort N0MJS <n0mjs@...> wrote:
|
|
|
|
Re: OT Help
Cort N0MJS <n0mjs@...>
apparently nothing – false alarm from what I hear.
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|
|
|
Re: OT Help
Corey Dean N3FE <n3fe@...>
I will need to look into this later as I am now t home but my smart Ptt links on 3102 are working fine.
toggle quoted messageShow quoted text
I need to know the talkgroup and login I’d number you are using for the smart Ptt connection to investigate. Sent from my iPhone
On Dec 29, 2017, at 6:07 PM, Cort N0MJS <n0mjs@...> wrote:
|
|
|
|
Re: OT Help
Corey Dean N3FE <n3fe@...>
He is an admin, Mark owns the master 3108 and I own 3102 but we have a team that manages them.
toggle quoted messageShow quoted text
Sent from my iPhone
On Dec 29, 2017, at 2:33 PM, Peter M0NWI <peter-martin@...> wrote:
|
|
|
|
Re: OT Help
Corey Dean N3FE <n3fe@...>
What do you guys need help with? I am a master admin for 3108.
toggle quoted messageShow quoted text
Sent from my iPhone
On Dec 29, 2017, at 6:09 PM, Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: OT Help
Sorry guys, I'm flat on my back sick Sent via smoke signal (Verizon)
On Dec 29, 2017 6:07 PM, Cort N0MJS <n0mjs@...> wrote:
|
|
|
