Date   

Start DVSwitch in DStar

G4WXN@...
 

DVSwitch always starts up in DMR.

I would like to start it up in DStar, but am struggling to find the correct file to configure?


Re: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

Steve N4IRS
 

Good to hear.

On 12/1/2020 9:19 AM, G4WXN@... wrote:
Thanks Steve
all seems ok now.


Re: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

G4WXN@...
 

Thanks Steve
all seems ok now.


Re: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

Steve N4IRS
 

OK,
The message means that Analog_Bridge can not find your ID in it's database.
From the command line as root (sudo -s) do this:

/opt/MMDVM_Bridge/dvswitch.sh lookup 2352421
Does it return your ID callsign and name?

grep 2352421 /var/lib/dvswitch/subscriber_ids.csv
Does it return your ID, callsign, and name?

If either one is no
/usr/local/sbin/DVSM_Update.sh

Restart Analog_Bridge
systemctl trestart analog_bridge

Check the log for the error.

Steve N4IRS


On 12/1/2020 8:37 AM, G4WXN@... wrote:
Here it is
--------------------------------
; 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 = 2                            ; 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)
transferRootDir = /tmp ; Export database files to USRP partner
 
; General vocoder setup information
decoderFallBack = false               ; 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 = 42025                         ; 31103 Transmit TLV frames to partner on this port
rxPort = 41025                          ; 31100 Listen for TLV frames from partner on this port
ambeMode = DMR                          ; 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 =2352421                   ; ID to use when transmitting from Analog_Bridge
repeaterID =235242102                   ; ID of source repeater
txTg = 9                                ; 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 = 169.254.42.42                   ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 46001                          ; Transmit USRP frames on this port
rxPort = 46001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 6                      ; Gain (in db) of the AGC filter
usrpAgc = -20,10,100   ; Set the agc threshold (db), slope (db) and decay (ms)
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 = 2471                         ; 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: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

G4WXN@...
 

Here it is
--------------------------------
; 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 = 2                            ; 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)
transferRootDir = /tmp ; Export database files to USRP partner
 
; General vocoder setup information
decoderFallBack = false               ; 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 = 42025                         ; 31103 Transmit TLV frames to partner on this port
rxPort = 41025                          ; 31100 Listen for TLV frames from partner on this port
ambeMode = DMR                          ; 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 =2352421                   ; ID to use when transmitting from Analog_Bridge
repeaterID =235242102                   ; ID of source repeater
txTg = 9                                ; 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 = 169.254.42.42                   ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 46001                          ; Transmit USRP frames on this port
rxPort = 46001                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 6                      ; Gain (in db) of the AGC filter
usrpAgc = -20,10,100   ; Set the agc threshold (db), slope (db) and decay (ms)
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 = 2471                         ; 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: Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

Steve N4IRS
 

Please post your AB.ini file.

Steve N4IRS

On 12/1/20 5:21 AM, G4WXN@... wrote:
The following message is showing in AB.
Could someone tell me what this means, and how to fix it.

"Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net
ile.  Please correct this."


Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net ile.

G4WXN@...
 

The following message is showing in AB.
Could someone tell me what this means, and how to fix it.

"Your gatewayDmrId nnnnnnn is NOT in the subscriber f .net
ile.  Please correct this."


Re: BransMeister Self care password for a DVSwitch

@AndrewVK2HAC
 

you should use the Selfcare password you set up on BM for your USer ID.


Re: Coming to a browser near you

@AndrewVK2HAC
 

Mike,
thanks for the detailed update. Look forward to using it when released.


Re: Coming to a browser near you

Mike Zingman - N4IRR
 

Status Report:
I now have a manageable list of items to finish for an alpha release.  The items are divided into Server, and Client with most of the work done for both.  Client needs some "configuration" support, and the server needs some more edge case development.  The last few days have been all client side, but today was a lot more server side.

For an overview the client is a little different than Mobile and pyUC in that it does not communicate with AB directly.  This was initially because the HTML client uses websockets and rather than add that as in interface to AB, a server was created.  The server is implemented in Nodejs and was an outgrowth of the work for the dashboard RX Monitor.  Now the server has grown in several ways which I will document as I get closer to release.

As far as features, hUC is starting out as a peer to pyUC in UI and capabilities.  It will evolve over time.

Finally, the server, HTML and config files will need to be packaged and system services will be set up.


Re: ASL <-> D-Star <-> xlxd

va3dxv
 

Yeah I thought I'd be clever and change the ircddbgateway ports (./Common/DStarDefines.h) and recompile but that just confused it, now seems to try to make the outgoing connections on those ports.


Re: ASL <-> D-Star <-> xlxd

 

I don't think so, because they are D-STAR protocol ports, which are
fixed (DPlus, DExtra, etc). 

xlxd:
udp        0      0 103.4.234.160:8880     
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10002    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:30001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:30051    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:10100    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:42000    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:20001    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:12345    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:12346    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:40000    
0.0.0.0:*                           4607/xlxd
udp        0      0 103.4.234.160:62030    
0.0.0.0:*                           4607/xlxd

ircDDBgateway
udp        0      0 127.0.0.1:20001        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20002        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20003        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20004        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20005        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20006        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 127.0.0.1:20007        
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 10.43.21.136:20010     
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:40000          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30001          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30002          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30003          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30004          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30005          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30006          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30007          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30051          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30052          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30053          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30054          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30055          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30056          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30057          
0.0.0.0:*                           3484/ircddbgatewayd
udp        0      0 0.0.0.0:30062          
0.0.0.0:*                           3484/ircddbgatewayd

On 1/12/20 11:44 am, Steve N4IRS wrote:
Should be able to move one of the ports.

On 11/30/20 7:42 PM, Tony Langdon wrote:
On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
  ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
 From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.




--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: ASL <-> D-Star <-> xlxd

Steve N4IRS
 

Should be able to move one of the ports.

On 11/30/20 7:42 PM, Tony Langdon wrote:
On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.


Re: ASL <-> D-Star <-> xlxd

 

On 1/12/20 8:53 am, Steve N4IRS wrote:
It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <->
MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I
assume it can.
From memory, they both listen on the same ports.  I had to move
ircDDBGateway off the host I was running xlxd on in my setup.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Coming to a browser near you

Steve N4IRS
 

It's moving along. Should be some time this year.

On 11/30/20 6:58 PM, newsletters@... wrote:
Mike,
when do you estimate a Beta product?

Thanks


Re: Coming to a browser near you

@AndrewVK2HAC
 

Mike,
when do you estimate a Beta product?

Thanks


Re: ASL <-> D-Star <-> xlxd

Steve N4IRS
 

It would be:
 ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> ircDDBGateway <-> xlxd

I don't know if ircDDBGateway and XLX can exist on the same machine. I assume it can.

Steve N4IRS

On 11/30/20 4:20 PM, va3dxv wrote:
Hello everyone. Is there much D-Star activity in the group? I've got a working xlxd reflector set up I use for a DStar group. Running on the same server, I have a working AllStar simplex radio node with Analog_Bridge and MMDVM_Bridge.

I'd like to bridge the ASL node into xlxd, in D-Star mode. So in theory, it goes like this: ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> xlxd

However I can only get MMDVM_Bridge to connect to xlxd if I use [DMR Network] in MMDVM_Bridge.ini. If I try using [D-Star Network], xlxd sees DPlus packets but it doesn't retransmit anything, and doesn't show the connection. Audio is messed up in DMR mode anyways, even though A_B says on start up it's using the hardware codec.

I could maybe insert ircDDBGateway between M_B and xlxd but it doesn't look like they can easily coexist on the same host.

Can MMDVM_Bridge connect to xlxd in DPlus or another DStar mode? I don't want to have to go analog->dmr->dstar, I'd rather just do analog->dstar. Wondering if anyone on here is doing this and how they went about it. Thank You


Re: Dashboard Time

David Aitcheson KB3EFS
 

Steve N4IRS,

Could the "America" one be referencing South America and the "US" one is referencing North America?

73
Dave
KB3EFS



On 11/30/20 3:33 PM, Steve N4IRS wrote:
I can't tell you the difference between the 2. I use US and the time zone. It works. Why? Some day I'll Google it. No duh. ;)

On 11/30/2020 3:31 PM, Chuck wrote:

Thanks, Steve, that did it.  Needed to select US vs America.  Duhhh!

 

73,

Chuck

KE5RAD

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Monday, November 30, 2020 1:19 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Dashboard Time

 

[Edited Message Follows]

Try setting to US / Central in raspi-config

On 11/30/2020 1:36 PM, Chuck wrote:

Where?

Chuck

On November 30, 2020 12:33:13 PM CST, Mike KB8JNM <groupio@...> wrote:

Daylight savings flag ?

On 11/30/2020 1:27 PM, ke5rad@... wrote:

How can I adjust the time on the DVSwitch Dashboard running on my Raspberry Pi?  Mine is an hour fast.  I looked at the .ini files and saw nothing related to time zone and I  set America Chicago in raspi-config but no joy.  Suggestions??
--
73,
Chuck
KE5RAD




ASL <-> D-Star <-> xlxd

va3dxv
 

Hello everyone. Is there much D-Star activity in the group? I've got a working xlxd reflector set up I use for a DStar group. Running on the same server, I have a working AllStar simplex radio node with Analog_Bridge and MMDVM_Bridge.

I'd like to bridge the ASL node into xlxd, in D-Star mode. So in theory, it goes like this: ASL <-> Analog_Bridge <-> (DStar, using hardware USB chip) <-> MMDVM_Bridge <-> xlxd

However I can only get MMDVM_Bridge to connect to xlxd if I use [DMR Network] in MMDVM_Bridge.ini. If I try using [D-Star Network], xlxd sees DPlus packets but it doesn't retransmit anything, and doesn't show the connection. Audio is messed up in DMR mode anyways, even though A_B says on start up it's using the hardware codec.

I could maybe insert ircDDBGateway between M_B and xlxd but it doesn't look like they can easily coexist on the same host.

Can MMDVM_Bridge connect to xlxd in DPlus or another DStar mode? I don't want to have to go analog->dmr->dstar, I'd rather just do analog->dstar. Wondering if anyone on here is doing this and how they went about it. Thank You


Re: Dashboard Time

Steve N4IRS
 

I can't tell you the difference between the 2. I use US and the time zone. It works. Why? Some day I'll Google it. No duh. ;)

On 11/30/2020 3:31 PM, Chuck wrote:

Thanks, Steve, that did it.  Needed to select US vs America.  Duhhh!

 

73,

Chuck

KE5RAD

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Monday, November 30, 2020 1:19 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Dashboard Time

 

[Edited Message Follows]

Try setting to US / Central in raspi-config

On 11/30/2020 1:36 PM, Chuck wrote:

Where?

Chuck

On November 30, 2020 12:33:13 PM CST, Mike KB8JNM <groupio@...> wrote:

Daylight savings flag ?

On 11/30/2020 1:27 PM, ke5rad@... wrote:

How can I adjust the time on the DVSwitch Dashboard running on my Raspberry Pi?  Mine is an hour fast.  I looked at the .ini files and saw nothing related to time zone and I  set America Chicago in raspi-config but no joy.  Suggestions??
--
73,
Chuck
KE5RAD


721 - 740 of 8313