Date   

Re: Interface Icom D-Star repeater to DVSwitch?

Jim Kusznir
 

Thank you, this is just the type of answer I was hoping for!

I'll give pi-star a try!  With luck, the W7YH icom repeater that has been off the network for about 5 years will be back online soon!

--Jim, K7LL


Re: Where the heck is hUC?

EA5GVK Joaquin
 

Happy new year. great news. Thanks Steve


El vie, 1 ene 2021 a las 18:38, Steve N4IRS (<szingman@...>) escribió:
Happy new year to all!
Just a quick update, The HTML Client (hUC) and the Analog_Reflector have gone into beta test as of today. The beta team will now start trying to break it and comment on features etc. I do not have a time frame as to when this goes to full release. We will need to package it for installation and document how to install, manage and use.

73, Steve N4IRS


Re: Where the heck is hUC?

Steve N4IRS
 

Happy new year to all!
Just a quick update, The HTML Client (hUC) and the Analog_Reflector have gone into beta test as of today. The beta team will now start trying to break it and comment on features etc. I do not have a time frame as to when this goes to full release. We will need to package it for installation and document how to install, manage and use.

73, Steve N4IRS


Re: DVMEGA

Steve N4IRS
 

Setup with the ASL 1.01 image. Follow the readme to pin the kernel and headers. Once you have ASL configured the way you want it, you can add DVSwitch Server with:
As root:
cd /tmp
wget http://dvswitch.org/buster
chmod +x buster
./buster
apt-get install dvswitch-server

Follow this to setup DVSwitch Server <http://www.dvswitch.org/DVSwitch_install.pdf>

Steve N4IRS

On 1/1/21 10:57 AM, N4UPC - Scott via groups.io wrote:
Okay Steve. Thanks again.  I've got a RasPi 3A+ that I can try.  What is the best way to go about this?


Re: DVMEGA

N4UPC - Scott
 

Okay Steve. Thanks again.  I've got a RasPi 3A+ that I can try.  What is the best way to go about this?


Re: Interface Icom D-Star repeater to DVSwitch?

Steve N4IRS
 

Unless Pi-Star ha modified ircDDBGateway, the version of ircDDBGateway should be the same. Of course, you will have to edit the ircDDBGateway config by hand. /etc/ircddbgateway

On 1/1/21 10:23 AM, Ken KE2N via groups.io wrote:
With Pi Star, you can specify repeater type 1 in the gateway configure and it will talk to an ID RP2C repeater controller and any attached ICOM DSTAR repeater(s).   I run that here on 2 meters. 

So if DVS has the same gateway software as Pi Star (?) it might work. So the question is: Does the DVS DSTAR Gateway support repeater type 1 (meaning the RP2C interface)?

This is of interest to me since (maybe) I could replace my Pi Star gateway with DVS and its DSTAR Gateway and then have bridging options in the same box.

Ken


Re: Interface Icom D-Star repeater to DVSwitch?

Ken KE2N
 

With Pi Star, you can specify repeater type 1 in the gateway configure and it will talk to an ID RP2C repeater controller and any attached ICOM DSTAR repeater(s).   I run that here on 2 meters. 

So if DVS has the same gateway software as Pi Star (?) it might work. So the question is: Does the DVS DSTAR Gateway support repeater type 1 (meaning the RP2C interface)?

This is of interest to me since (maybe) I could replace my Pi Star gateway with DVS and its DSTAR Gateway and then have bridging options in the same box.

Ken


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

1701 - 1720 of 9774