Date   

Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

The ircddbgateway log will indicate the nature of any issues, if you post it here, if so.



On 30/12/19 11:16 am, Ed W8VT wrote:
Thanks Adrian. Now that I know the registration looks OK, we'll do some more experimentation.

Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Ed W8VT
 

Thanks Adrian. Now that I know the registration looks OK, we'll do some more experimentation.

Really appreciate the assistance.

Ed W8VT


Re: DSTAR Registration Questions

Adrian Fewster <vk4tux@...>
 

Ed your current status at USTRUST is ;

W8VT sync_mng Table Records (3 entries)
target_cs last_mod_time mod_date reg_date pc_hostname arearp_cs user_cs regist_rp_cs pc_ipaddr del_flg
W8VT 2019-12-24 18:44:03 2019-12-24 18:44:03.506387 2019-12-24 18:44:03.506387
REGIST A W8VT REGIST 0.0.0.0 OK
W8VT B 2019-12-24 22:28:10 2019-12-24 22:28:09.60761 2019-12-24 21:16:29.941764
REGIST A W8VT REGIST 0.0.0.0 DELETED
W8VT Z 2019-12-11 17:55:18 2019-12-11 17:55:18.179014 2019-12-11 17:55:18.179014 ACCESSPOINT W8VT Z W8VT REGIST 0.0.0.0 OK
W8VT unsync_mng table records (1 entries)
target_cs receive_time mod_date reg_date blacklist_flg
W8VT 1970-01-01 00:00:00 2019-12-11 17:55:18.179014 2019-12-11 17:55:18.179014 OK
W8VT sync_rip Table Records (1 entries)
user_cs regist_rp_cs last_mod_time mod_date reg_date start_ipaddr del_flg
W8VT REGIST 2019-12-11 17:22:05 2019-12-11 17:22:04.964139 2019-12-11 17:22:04.964139 10.209.79.8 OK
Mon Dec 30 01:00:48 UTC 2019


which means you can use W8VT  or W8VT###Z for dplus login in ircddbgateway config ;

<snip>

dplusEnabled=1
dplusMaxDongles=5
dplusLogin=W8VT

<snip>


In the USTRUST synced user list sent to Reflectors and gateways , and the Dplus database ;

[W8VT    ] [REGIST A]
[W8VT   Z] [W8VT   Z]

You exist, so you should be able to login to any dplus reflector or gateway with the dplus host file.

Adrian .. vk4tux





On 30/12/19 10:50 am, Ed W8VT wrote:
Would appreciate it if a DSTAR guru could answer a few questions about DSTAR registration. Do have my analog bridge at least working with DCS reflectors at this point.
Knew very little about DSTAR when I started this project. Had no idea there were all these multiple systems and registration. Thought I went through all the procedures to register but obviously have missed and / or screwed up something.
Queried my call on these sites:
https://wb1gof.dstargateway.org/cgi-bin/dstar-regcheck?callsign=W8VT
http://dstar.info/query.html
Not quite sure what it all means.

What a complex and convoluted system! HELP!

Ed W8VT
Old, confused and befuddled


DSTAR Registration Questions

Ed W8VT
 

Would appreciate it if a DSTAR guru could answer a few questions about DSTAR registration. Do have my analog bridge at least working with DCS reflectors at this point.
Knew very little about DSTAR when I started this project. Had no idea there were all these multiple systems and registration. Thought I went through all the procedures to register but obviously have missed and / or screwed up something.
Queried my call on these sites:
https://wb1gof.dstargateway.org/cgi-bin/dstar-regcheck?callsign=W8VT
http://dstar.info/query.html
Not quite sure what it all means.

What a complex and convoluted system! HELP!

Ed W8VT
Old, confused and befuddled


Re: Image needed

Vicente Segovia Gonzalez
 

El vie., 27 dic. 2019 a las 19:02, Brett KB5YZB via Groups.Io (<Brett.williams=sss.gov@groups.io>) escribió:
DV switch friends, I just upgraded from x86 CentOS to a PI 3. I installed hamviop however I want to have ALLstar/Echolink/DMR/Yeasu on one pi. Friend who is helping me install the bridges said to install the DV switch image instead of Hamvoip to make all this work. I looked for the link for an image (can't find) before sending this....sorry I'm sure its out there in DV switch land. Is there an image for all the above?

Thanks for the help!!!!

Brett
KB5YZB


Re: Hytera DMR Gateway

EA5GVK Joaquin
 

I have tried the hytera gw with the dmrgateway. AND IT WORKS PERFECTLY TO CONNECT TO BRANDMEISTER AND DMR +
BUT HBLINK HAS PROBLEMS:
If the TG of the HBLINK, in turn is linked to other systems, for example to an XLX, the audio in the direction of the HBLINK to XLX does not come out. However, in the sense of XLX to HBLINK, yes.
That is

HYTERA-GW -> DMRGATEWAY -> HBLINK - TGLINK TO XLX -> DOES NOT WORK.

AND HOWEVER TO THE CONTRARY IF

HBLINK-TG LINK TO XLX -> DMRGATEWAY -> HYTERA-GW -> WORK PERFECTLY.

CAN SOMEBODY HELP ME.


Re: ASL to YSF Question

Adrian Fewster <vk4tux@...>
 

It just disables the port = 0 instead of the address, various gateway connections with disabled local ports should not affect each other.

I just find the method produces the least debug complaints.

On 28/12/19 7:55 am, Eric Dayrit wrote:
Adrian,
Quick question? this local address/ port setup will not interfere to each other if I have 4 MMDVM Bridge instances running in one box?
Thanks, Eric


Re: ASL to YSF Question

Eric-K6KWB
 

Adrian,
Quick question? this local address/ port setup will not interfere to each other if I have 4 MMDVM Bridge instances running in one box?
Thanks, Eric


Re: ASL to YSF Question

Eric-K6KWB
 

thanks Adrian, noted.


Re: ASL to YSF Question

Adrian Fewster <vk4tux@...>
 

mmdvm_bridge.ini


I use ;


[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=0
GatewayAddress= ip or dns of your YSFreflector
GatewayPort=42000 port of your reflector
Debug=0

On 28/12/19 5:34 am, Eric Dayrit wrote:
mmdvm_bridge.ini
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress= ip or dns of your YSFreflector
GatewayPort=42000 port of your reflector
Debug=0


Re: ASL to YSF Question

Eric-K6KWB
 

Hello Tito,
you can try this:

mmdvm_bridge.ini
[System Fusion Network]
Enable=1
LocalAddress=0
LocalPort=3200
GatewayAddress= ip or dns of your YSFreflector
GatewayPort=42000 port of your reflector
Debug=0
 
DVSwitch.ini
[YSF]
Address = 127.0.0.1 
TXPort = 35100 to AB.ini RXport
RXPort = 35103  from AB.ini TXport
FallbackID = 1234567 your id
ExportTG = 9 
Slot = 2
 
AB.ini
[AMBE_AUDIO]
address = 127.0.0.1                  
txPort = 35103                        
rxPort = 35100                          
ambeMode = YSFN                           
minTxTimeMS = 2500     


Re: Image needed

Eric-K6KWB
 

Hi Brett,
For ASL - http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/  
install asl image first then download DVSwitch system builder.

For DVSwitch - https://github.com/DVSwitch/DVSwitch-System-Builder

If this is not what your looking for, I'm pretty sure someone will guide you.
best regards,
Eric


ASL to YSF Question

Tito Lopez - YN1OB
 

Hello Folks, I have a question...
I have two VMs on two different hosts.
One One I am running ASL<->YFSN
on the other  I am running a YSF Reflector.
What I would like to do is connect the ASL-YSFN to that YSF Reflector.
Where or which of  the .ini files I need to configure to make the magic happen.
 i am building a DMR free system, Nothing wrong with DMR but YSF is my favorite flavor. 

73's
W3DAW
YN1OB


Image needed

Brett KB5YZB
 

DV switch friends, I just upgraded from x86 CentOS to a PI 3. I installed hamviop however I want to have ALLstar/Echolink/DMR/Yeasu on one pi. Friend who is helping me install the bridges said to install the DV switch image instead of Hamvoip to make all this work. I looked for the link for an image (can't find) before sending this....sorry I'm sure its out there in DV switch land. Is there an image for all the above?

Thanks for the help!!!!

Brett
KB5YZB


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

You CAN, but if you configure Analog_Bridge for YSF that is how it will startup. After that lets say you want to change reflectors, there is where dvswitch.sh would come in. Another example would be if you want to raise or lower the audio level without restarting AB, you could use dvswitch.sh to do it.

 Steve

On 12/26/19 6:56 PM, ve6gcd@... wrote:
Thanks Steve,

Does that mean I can insert a startup macro for the USRP node via rpt.conf so it will run dvswitch.sh in YSF mode?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Thanks Steve,

Does that mean I can insert a startup macro for the USRP node via rpt.conf so it will run dvswitch.sh in YSF mode?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

No it does not. dvswitch.sh is used to send commands to a running AB. You can run it with ./dvswitch.sh to see the list of available commands. dvswitch.sh can be used in scripts or ASL commands.

Steve

On 12/26/19 5:57 PM, ve6gcd@... wrote:
Hi Steve,

Just one more question before the reinstall, does Analog_Bridge run dvswitch.sh automatically at startup?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Hi Steve,

Just one more question before the reinstall, does Analog_Bridge run dvswitch.sh automatically at startup?

73,
Geoffrey VE6GCD


Re: ASL Briddge to YSF/FCS #analog_bridge

Steve N4IRS
 

I really have to update the system builder script.
Here are a few things you should do.
We post the latest code for the DVSwitch programs in github before the make it to the apt repository.
For Analog Bridge the repo is at <https://github.com/DVSwitch/Analog_Bridge>
I suggest you get the executable for your system from the bin directory
There have been some changes to the .ini file take a look at those.
There are newer macro files and a script that will help you control a running system. it is dvswitch.sh

For MMDVM_Bridge the repo is at <https://github.com/DVSwitch/MMDVM_Bridge
Get the updated executable from the bin directory.

If all you are planning to run is YSF, I suggest you turn off the other modes and mode networks in MMDVM_Bridge.ini

Hope this helps,
73, Steve N4IRS

On 12/26/19 5:36 PM, ve6gcd@... wrote:
Hi Steve,

Analog_Bridge in my computer was installed using DVSwitch-System-Builder.

Do I need to set anything under the MACROS section (to set the mode)? Anyway, below is the config of my setup.

===================================================================================
; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 1                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 35103                          ; Transmit TLV frames to partner on this port
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3026120                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 302612001                          ; ID of source repeater
txTg = 3026120                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[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                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)
[MACROS]
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
; For example using macro "5678" above would look like:
; *5678#9876
; Which would invoke:
; echo 9876
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
;address = 127.0.0.1                   ; IP address of AMBEServer
;rxPort = 2460                         ; Port of AMBEServer
 address = /dev/ttyUSB0              ; Device of DV3000U on this machine
 baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
 serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer
===================================================================================


Re: ASL Briddge to YSF/FCS #analog_bridge

ve6gcd@...
 

Hi Steve,

Analog_Bridge in my computer was installed using DVSwitch-System-Builder.

Do I need to set anything under the MACROS section (to set the mode)? Anyway, below is the config of my setup.

===================================================================================
; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; Analog_Bridge supports include files. More on this later...
include = dvsm.macro
; include = asl.macro
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 1                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 35103                          ; Transmit TLV frames to partner on this port
rxPort = 35100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 3026120                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 302612001                          ; ID of source repeater
txTg = 3026120                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames
; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[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                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)
[MACROS]
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
; For example using macro "5678" above would look like:
; *5678#9876
; Which would invoke:
; echo 9876
; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
;address = 127.0.0.1                   ; IP address of AMBEServer
;rxPort = 2460                         ; Port of AMBEServer
 address = /dev/ttyUSB0              ; Device of DV3000U on this machine
 baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
 serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer
===================================================================================

4321 - 4340 of 9925