Date   

Re: DVMEGA

Steve N4IRS
 

I was going to answer that but held off. No, you can not install DVSwitch Server (easily) on HAMVOIP. For now, your best bet is either 2 Pi or a RPi3.

On 1/1/21 9:55 AM, N4UPC - Scott via groups.io wrote:
Thanks Steve!  Would it be better to install the HamVOIP version of AllStar and then install the DVSwitch software?


Re: DVMEGA

N4UPC - Scott
 

Thanks Steve!  Would it be better to install the HamVOIP version of AllStar and then install the DVSwitch software?


Re: DVMEGA

Steve N4IRS
 

Scott,
Yes, you can install DVSwitch Server with the DVstick30 on the Raspberry Pi 4 by following the DVSwitch Installation and User Guide v1.61 document.
Adding AllStar becomes a problem on that system. ASL 1.01 does not run on a Raspberry Pi 4. I can tell you that AllStar for the Raspberry Pi 4 is being worked on.

Steve N4IRS

On 1/1/21 8:57 AM, N4UPC - Scott via groups.io wrote:
If I follow the "DVSwitch Installation and User Guide v1.61.pdf" and put DVSwitch on a RasPi 4 (4GB) can I use the DVstick30 on the RasPi?  Also, what's the best way to also get AllStar on the RasPi?  Thanks!


DVMEGA

N4UPC - Scott
 

If I follow the "DVSwitch Installation and User Guide v1.61.pdf" and put DVSwitch on a RasPi 4 (4GB) can I use the DVstick30 on the RasPi?  Also, what's the best way to also get AllStar on the RasPi?  Thanks!


Re: One Way Traffic ASL to YSF

Steve N4IRS
 

There are not too many people running remote separated AllStar / DVSwitch. Most port issues are within a bridge. It's always RX to TX, TX to RX
Glad to hear you got it working. I'm good on sleep, pretty much 11 PM to 5 AM 7 days a week.

Steve N4IRS

On 1/1/21 8:40 AM, Jay wrote:
Duh, light goes on.  They each have to point to the other.  So ASL Node address points to the remote DVSwitch and the DVSwitch's USRP address points to ASL. 

I kept trying to do one or the other,  thinking if ASL was sending to the DVSwitch Address/Port, then it was also fetching from the same Address (DVSwitch), therefore only one of the two servers really needed to know the actual address of the other.  Changed both and it works.

As I read the forum posts, I am really thinking that there are others who are stuck on the same problem.  

Thank you very much.  I have been struggling with this for a couple weeks, ever since I moved to an off-site server for the DVSwitch application.   

73 and get some sleep.....
--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 

Duh, light goes on.  They each have to point to the other.  So ASL Node address points to the remote DVSwitch and the DVSwitch's USRP address points to ASL. 

I kept trying to do one or the other,  thinking if ASL was sending to the DVSwitch Address/Port, then it was also fetching from the same Address (DVSwitch), therefore only one of the two servers really needed to know the actual address of the other.  Changed both and it works.

As I read the forum posts, I am really thinking that there are others who are stuck on the same problem.  

Thank you very much.  I have been struggling with this for a couple weeks, ever since I moved to an off-site server for the DVSwitch application.   

73 and get some sleep.....
--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Steve N4IRS
 

Analog_Bridge:

[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                 ; Digital -> Analog (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_USE_AGC)
usrpGain = 1.10                         ; Gain factor when usrpAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)
usrpAGC = -20,10,100                    ; Set the agc threshold (db), slope (db) and decay (ms)
tlvAudio = AUDIO_UNITY                  ; Analog -> Digital (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor when tlvAudio = AUDIO_USE_GAIN (0.0 to 5.0) (1.0 = AUDIO_UNITY)


AllStar

rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                    ; 127.0.0.1 = IP of the target application
                    ; 34001 = UDP port the target application is listening on
                    ; 32001 = UDP port ASL is listening on


On 12/31/20 11:39 PM, Jay wrote:
Also, the DVSwitch Server is hosted in the Cloud, so am I confused on where the DVSwitch Server IP needs to go?

Hanging it up for the evening.  Start again in the morn.



--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 

Also, the DVSwitch Server is hosted in the Cloud, so am I confused on where the DVSwitch Server IP needs to go?

Hanging it up for the evening.  Start again in the morn.



--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 

tlvAudio is correct.  Cut and paste issue
--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 

Ok, had not gone there.  I see the logic.  So I really need a static IP for the Allstar node to insure it does not change.  I can do that.

I assumed that ASL's rpt.conf file should point to the IP address of the DVSWitch Server (off premise).  AB was hearing traffic coming from ASL just fine so I "assumed" that if AB was sending traffic to its local port that was where ASL was getting it from (since ASL knew where to send traffic?).  It sounds like ASL should always send and receive to 127.0.0.1 and AB needs the address of the ASL Node to fetch and send traffic.

[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32004                          ; Transmit USRP frames on this port
rxPort = 34004                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.00                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITYNNN               ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

[1994]                                  ; YSF
rxchannel = USRP/23.94.xxx.118:34004:32004  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 23.94.xxx.118 = IP of the DVSwitch Server
                                        ; 34004 = UDP port the target application is listening on
                                        ; 32004 = UDP port ASL is listening on
duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but$
hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0
holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or $
                                        ; except when an ID needs to be done and there is a signal comi$
telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!$
telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with$
linktolink = no                         ; disables forcing physical half-duplex operation of main repea$
                                        ; still keeping half-duplex semantics (optional)
nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.
tx_timeout = 180000                     ; transmit time-out time (in ms) (optional, default 3 minutes 1$
idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/no$
idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org$
connpgm=/usr/local/sbin/supermon/smlogger 1  ; use this line for Supermon
discpgm=/usr/local/sbin/supermon/smlogger 0  ; use this line for Supermon
--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Steve N4IRS
 

Jay,
AB should be sending to the IP of the AllStar node not 127.0.0.1 You can post the USRP section and the rxchannel so we can check it.

On 12/31/20 10:11 PM, Jay wrote:
My USRP stanza in AB.ini is exactly the default.

I have my YSF on Private Node 1994 and the rpt.conf for node 1994 is the default layout with the exception that it points my Cloud Server (I have tried it with a local server also).  The  appropriate field is:   rxchannel = 23.94.xxx.118:34004:32004 

Netstat -umap shows the Cloud Server's AB is sending to 127.0.0.1:32004.  Netstat on the Allstar box shows Asterisk listening on 32004.  I can send audio from Asterisk all the way through to the YSF Reflector.  Audio from the YSF Reflector seems to get all the way back to the AB side of the DVSwitch Server, which is supposed to be outputting on 32004.

I have bee struggling with the thought that I have a port issue.  I opened 30000- 39000.  No difference.  I put the Asterisk box in the DMZ.  No change.

I set up a ASL to DMR Private Node changing the ports to 34003 and 32003.  Exact same results.  I of course edited the AB.ini and MB.ini files appropriately for ports and mode, and I am running 2 copies of md380-emu.

I see only only odd think and it should not make a difference, but when AB is seeing incoming traffic to pass to ASL, it shows "Begin TX: src=1234567 rpt=0 dst=1234 slot=2 call=W4ABC", where W4ABC is the call of the transmitting station.

I have run out of ideas, unless Asterisk does not like those ports. and is ignoring them, but as Netstat shows, it does open them.

jb  N4NQY
--


--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 


I will mention that I have tried all of the Duplex setting on both the Main Asterisk node and the Private Nodes with no success and only the Private Node I am testing is connected to the main node while testing

--

jb   N4NQY


Re: One Way Traffic ASL to YSF

Jay
 

My USRP stanza in AB.ini is exactly the default.

I have my YSF on Private Node 1994 and the rpt.conf for node 1994 is the default layout with the exception that it points my Cloud Server (I have tried it with a local server also).  The  appropriate field is:   rxchannel = 23.94.xxx.118:34004:32004 

Netstat -umap shows the Cloud Server's AB is sending to 127.0.0.1:32004.  Netstat on the Allstar box shows Asterisk listening on 32004.  I can send audio from Asterisk all the way through to the YSF Reflector.  Audio from the YSF Reflector seems to get all the way back to the AB side of the DVSwitch Server, which is supposed to be outputting on 32004.

I have bee struggling with the thought that I have a port issue.  I opened 30000- 39000.  No difference.  I put the Asterisk box in the DMZ.  No change.

I set up a ASL to DMR Private Node changing the ports to 34003 and 32003.  Exact same results.  I of course edited the AB.ini and MB.ini files appropriately for ports and mode, and I am running 2 copies of md380-emu.

I see only only odd think and it should not make a difference, but when AB is seeing incoming traffic to pass to ASL, it shows "Begin TX: src=1234567 rpt=0 dst=1234 slot=2 call=W4ABC", where W4ABC is the call of the transmitting station.

I have run out of ideas, unless Asterisk does not like those ports. and is ignoring them, but as Netstat shows, it does open them.

jb  N4NQY
--


--

jb   N4NQY


Re: Interface Icom D-Star repeater to DVSwitch?

lloyd Duck
 

You can setup the ICom D-Star repeater and use Centos 7 and make it a G3 gateway (new stuff) or use Pi-Star image and use a raspberry pi for the gateway. 

Lloyd, W5LND



On Dec 31, 2020, at 3:20 PM, Jim Kusznir <jim@...> wrote:

Hello:

I'm probably off-base here, but hopefully someone can point me in the right direction...

I have an Icom D-Star DV repeater (eg, ID-RP4000V and ID-RP2C).  The gateway software (which apparently requires Centos 5!) seems to not have been updated in a decade or so....But I'm not finding any other instructions on how to enable this perfectly good hardware to participate in a D-Star network.

Can a component of DV Switch provide the IP interface that the controller is looking for to allow this RF system to be fully D-Star enabled (connected)?  If not, is there another project or direction I should look before trying to build a Centos 5 VM and find the ancient versions of software that the Icom CD that shipped with the repeater requires?

I greatly appreciate your help!
Thanks!
--Jim, K7LL


Re: Interface Icom D-Star repeater to DVSwitch?

David Ranch
 


Hello Jim,

Icom's G2 gateway software was based on Centos5 but their newer G3 gateway software uses Centos7.  Here is a URL that might help answer some of your questions:

   https://dstar.info/

It's worth mentioning that I understand that Icom has a new G4 software stack in Beta.  I think it's been in Beta for a while now and I have no idea when they might release it.  There is also a question around Centos's charter change around Centos 8 vs. Centos Stream but we'll have to see what comes of that.

--David
KI6ZHD



On 12/31/2020 01:20 PM, Jim Kusznir wrote:
Hello:

I'm probably off-base here, but hopefully someone can point me in the right direction...

I have an Icom D-Star DV repeater (eg, ID-RP4000V and ID-RP2C).  The gateway software (which apparently requires Centos 5!) seems to not have been updated in a decade or so....But I'm not finding any other instructions on how to enable this perfectly good hardware to participate in a D-Star network.

Can a component of DV Switch provide the IP interface that the controller is looking for to allow this RF system to be fully D-Star enabled (connected)?  If not, is there another project or direction I should look before trying to build a Centos 5 VM and find the ancient versions of software that the Icom CD that shipped with the repeater requires?

I greatly appreciate your help!
Thanks!
--Jim, K7LL


Re: DV Switch Server

Steve Siesel [K4KSA]
 

Ok sounds good! I was just looking to be ready, but if all the parts are not out yet I will have to wait! In my system I do have two instances of AB and MB running. The other instance takes another TG and sends it to Broadcastify.

Thanks again for your help, I was just trying have everything I need.

Steve


On Thu, Dec 31, 2020 at 5:00 PM Steve N4IRS <szingman@...> wrote:
Steve,
Since you already have AB and MB installed, "adding" DVSwitch Server would pretty much be the same thing at this time. It pretty much comes down to you have one Analog_Bridge. That AB can service ASL or the clients (Android, Python) Once we release the Analog_Reflector and the HTML client, that changes, a little. With Analog_Reflector, Android, Python, HTML and ASL can share that Analog_Bridge. The operative word he is share. You can't have ASL routed to DMR while you talk on NXDN, You still have one AB. You can have ASL, Android and HTML all connected to the same digital network (and TG) at the same time.

Hope this helps,
Steve N4IRS  

On 12/31/20 4:50 PM, Steve Siesel [K4KSA] wrote:

I want to add DVSwitch Server to my system.

 

Currently I have ASL along with Analog Bridge and MMDVM Bridge in one Raspberry Pi. Can I add DV Switch Server in here as well? Once installed would DVSwitch Server handle the ASL<>DMR that is currently being handled now along with using the Android app and other products that are coming? Would I get the DVSwitch-System-Builder from GitHub to accomplish this?

 

I also noticed the complete image for DVSwitch as well, but want to know if by using DVSwitch-System-Builder it would work on my existing Raspberry Pi.

 

 

Thank You and Have a good New Year!

 

Steve

K4KSA

 

 



Re: DV Switch Server

Steve N4IRS
 

Steve,
Since you already have AB and MB installed, "adding" DVSwitch Server would pretty much be the same thing at this time. It pretty much comes down to you have one Analog_Bridge. That AB can service ASL or the clients (Android, Python) Once we release the Analog_Reflector and the HTML client, that changes, a little. With Analog_Reflector, Android, Python, HTML and ASL can share that Analog_Bridge. The operative word he is share. You can't have ASL routed to DMR while you talk on NXDN, You still have one AB. You can have ASL, Android and HTML all connected to the same digital network (and TG) at the same time.

Hope this helps,
Steve N4IRS  

On 12/31/20 4:50 PM, Steve Siesel [K4KSA] wrote:

I want to add DVSwitch Server to my system.

 

Currently I have ASL along with Analog Bridge and MMDVM Bridge in one Raspberry Pi. Can I add DV Switch Server in here as well? Once installed would DVSwitch Server handle the ASL<>DMR that is currently being handled now along with using the Android app and other products that are coming? Would I get the DVSwitch-System-Builder from GitHub to accomplish this?

 

I also noticed the complete image for DVSwitch as well, but want to know if by using DVSwitch-System-Builder it would work on my existing Raspberry Pi.

 

 

Thank You and Have a good New Year!

 

Steve

K4KSA

 

 



DV Switch Server

Steve Siesel [K4KSA]
 

I want to add DVSwitch Server to my system.

 

Currently I have ASL along with Analog Bridge and MMDVM Bridge in one Raspberry Pi. Can I add DV Switch Server in here as well? Once installed would DVSwitch Server handle the ASL<>DMR that is currently being handled now along with using the Android app and other products that are coming? Would I get the DVSwitch-System-Builder from GitHub to accomplish this?

 

I also noticed the complete image for DVSwitch as well, but want to know if by using DVSwitch-System-Builder it would work on my existing Raspberry Pi.

 

 

Thank You and Have a good New Year!

 

Steve

K4KSA

 

 


Re: Interface Icom D-Star repeater to DVSwitch?

Jeff Lehman, N8ACL
 

Hi Jim!

So it’s been a while since I dinked with a d-star machine, but I can at least tell you “from what I remember”. It does require Centos, but with the updates to ircddbgateway, you MAY be able to update to a newer version of Centos. However, to be able to handle the registrations and user database, I believe you still need to have the gateway installed on the computer running everything. Now here is where I also get into i don’t know. I don’t remember if ircddbgateway is what handled that or not. I don’t believe so. There may be an updated version of the old registration gateway software that may be able to be used, but that would take some research. But I do know that that piece was needed for the user database and registering the repeater on the network. 

Your mileage may vary at this point. Like I said it’s been since d-star first made its appearance that I messed with it. So updates may have been put out,  it I have not followed it in a while. 

Jeff


On Dec 31, 2020, at 16:28, Steve N4IRS <szingman@...> wrote:

 Jim,
Let me start with, I don't have a clue. That being said, if anything MAYBE you can use the installation of ircDDBGateway on DVSwitch Server as a way to access the network. I would suggest researching Icom repeater and ircDDBGateway. Maybe someone has more info.

Steve N4IRS

On 12/31/20 4:20 PM, Jim Kusznir wrote:
Hello:

I'm probably off-base here, but hopefully someone can point me in the right direction...

I have an Icom D-Star DV repeater (eg, ID-RP4000V and ID-RP2C).  The gateway software (which apparently requires Centos 5!) seems to not have been updated in a decade or so....But I'm not finding any other instructions on how to enable this perfectly good hardware to participate in a D-Star network.

Can a component of DV Switch provide the IP interface that the controller is looking for to allow this RF system to be fully D-Star enabled (connected)?  If not, is there another project or direction I should look before trying to build a Centos 5 VM and find the ancient versions of software that the Icom CD that shipped with the repeater requires?

I greatly appreciate your help!
Thanks!
--Jim, K7LL


Re: Interface Icom D-Star repeater to DVSwitch?

Steve N4IRS
 

Jim,
Let me start with, I don't have a clue. That being said, if anything MAYBE you can use the installation of ircDDBGateway on DVSwitch Server as a way to access the network. I would suggest researching Icom repeater and ircDDBGateway. Maybe someone has more info.

Steve N4IRS

On 12/31/20 4:20 PM, Jim Kusznir wrote:
Hello:

I'm probably off-base here, but hopefully someone can point me in the right direction...

I have an Icom D-Star DV repeater (eg, ID-RP4000V and ID-RP2C).  The gateway software (which apparently requires Centos 5!) seems to not have been updated in a decade or so....But I'm not finding any other instructions on how to enable this perfectly good hardware to participate in a D-Star network.

Can a component of DV Switch provide the IP interface that the controller is looking for to allow this RF system to be fully D-Star enabled (connected)?  If not, is there another project or direction I should look before trying to build a Centos 5 VM and find the ancient versions of software that the Icom CD that shipped with the repeater requires?

I greatly appreciate your help!
Thanks!
--Jim, K7LL

1841 - 1860 of 9907