Date   

Re: Rpi3 Bridge

Justin Morris
 

Appreciate it, That got it going, kind of. Analog is passing to dmr fine. audio needs adjusting but works. dmr to analog only causes a kerchunk to come though. watching MMDVM_Bridge it seems to be seeing the whole transmission. 


Re: Analog_Bridge.ini

Steve N4IRS
 

Jeff,
You can't run USRP and Simple USB in the same node stanza at the same time. Each node stanza has a unique rxchannel.
It should look something like this:

[1999]
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

duplex = 0          ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

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 from connected nodes
                    ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0    ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0    ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no     ; disables forcing physical half-duplex operation of main repeater while
                    ; still keeping half-duplex semantics (optional)

nounkeyct = 1       ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000     ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie   ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie    ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

[1998]
rxchannel = SimpleUSB/usb_1998    ; SimpleUSB


Same box, no problem. Same node stanza, problem.

Steve


On 5/31/2018 9:30 AM, Jeff Carrier wrote:
Steve, 

You mentioned something yesterday that created a question in my mind.  You said USRP and SimpleUSB can't run together on the same box.  I'm assuming that has something to do with those two channel drivers in asterisk.  My install seems to be fine less the complaints about "digital sounding audio" but I'm running Analog_Bridge, MMDVM_Bridge and P25Gateway on the same Pi as an allstar node with URIx connected running DSP.  It seems fine but does this have the potential to cause erratic behavior?

On Thu, May 31, 2018 at 7:20 AM Steve N4IRS <szingman@...> wrote:
We are working to simplify and standardize the configuration files across all the Partner programs. Analog_Bridge.ini is one of the oldest and needs a little facelift to better match the other partners. Though some of the parameter names are changing, the old names will be supported for a while. If you are still using the older names, you will get a warning in the Analog_Bridge log. Your configuration will continue to operate as before. I have bolded the changes parameters Here is the updated Analog_Bridge.ini:

; 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.


; 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 = ./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 = 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 = 31003                          ; Transmit TLV frames to partner on this port
rxPort = 31000                          ; 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 = 2000                      ; 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 = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; 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 = 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
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; 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: Analog_Bridge.ini

Jeff Carrier
 

Steve, 

You mentioned something yesterday that created a question in my mind.  You said USRP and SimpleUSB can't run together on the same box.  I'm assuming that has something to do with those two channel drivers in asterisk.  My install seems to be fine less the complaints about "digital sounding audio" but I'm running Analog_Bridge, MMDVM_Bridge and P25Gateway on the same Pi as an allstar node with URIx connected running DSP.  It seems fine but does this have the potential to cause erratic behavior?

On Thu, May 31, 2018 at 7:20 AM Steve N4IRS <szingman@...> wrote:
We are working to simplify and standardize the configuration files across all the Partner programs. Analog_Bridge.ini is one of the oldest and needs a little facelift to better match the other partners. Though some of the parameter names are changing, the old names will be supported for a while. If you are still using the older names, you will get a warning in the Analog_Bridge log. Your configuration will continue to operate as before. I have bolded the changes parameters Here is the updated Analog_Bridge.ini:

; 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.


; 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 = ./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 = 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 = 31003                          ; Transmit TLV frames to partner on this port
rxPort = 31000                          ; 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 = 2000                      ; 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 = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; 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 = 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
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; 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



Analog_Bridge.ini

Steve N4IRS
 

We are working to simplify and standardize the configuration files across all the Partner programs. Analog_Bridge.ini is one of the oldest and needs a little facelift to better match the other partners. Though some of the parameter names are changing, the old names will be supported for a while. If you are still using the older names, you will get a warning in the Analog_Bridge log. Your configuration will continue to operate as before. I have bolded the changes parameters Here is the updated Analog_Bridge.ini:

; 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.


; 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 = ./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 = 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 = 31003                          ; Transmit TLV frames to partner on this port
rxPort = 31000                          ; 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 = 2000                      ; 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 = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; 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 = 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
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; 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: Rpi3 Bridge

Steve N4IRS
 

In Analog_Bridge.ini Do not use the same ID for both gatewayDmrId  and repeaterID
I suggest the gatewayDmrId should be your 7 digit DMR ID

Run MMDVM_Bridge MMDVM_Bridge.ini in /opt/MMDVM_Bridge. This is what logs into BM. See what the output is.

Steve

On 5/31/2018 8:55 AM, kc5mmw@... wrote:
Could you help me find what is broken? I can connect to my other node from asl. I do not see the id's i chose in my brandmiester hotspot list

; 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.
 
; General Section describes settings for Analog_Bridge itself.
;   For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 
; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the server
 
; Audio devices are normally not needed when in gateway service.  These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null           ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null            ; Only used for dongle mode
 
; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = false                   ; Use app as just a fancy dongle for DMR
useVox = false                          ; If using dongle mode (useMicrophone), enable VOX
voxDecay = 2                            ; Hang time in seconds
voxTrigger = 200                        ; Value to trip PTT (0-32767)
 
; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 310502480                ; ID to use when transmitting from Analog_Bridge
repeaterID = 310502480                  ; ID of source repeater
txTg = 31055                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received 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 toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -10                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.25                          ; Gain factor of audio from ASL (0.0-1.0)
 
; 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]
server = 127.0.0.1                      ; IP address of AMBEServer
port = 2460                             ; Port of AMBEServer
; server = /dev/ttyUSB0                 ; Device of DV3000U on this machine
; port = 460800                         ; Baud rate of the dongle
; serial = true                         ; Use serial (DV3000U) or IP
[General]
Callsign=KC5MMW
Id=310502480
Timeout=180
Duplex=0
ModeHang=0
RFModeHang=0
NetModeHang=0
Display=None
Daemon=0
 
[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=C
SelfOnly=0
AckReply=1
AckTime=750
ErrorReply=1
RemoteGateway=0
ModeHang=0
 
[DMR]
Enable=1
Beacons=0
BeaconInterval=60
BeaconDuration=3
ColorCode=1
SelfOnly=0
EmbeddedLCOnly=1
DumpTAData=0
CallHang=0
TXHang=0
ModeHang=0
 
[System Fusion]
Enable=0
LowDeviation=0
SelfOnly=0
RemoteGateway=0
ModeHang=0
 
[P25]
Enable=0
NAC=293
SelfOnly=0
OverrideUIDCheck=0
RemoteGateway=0
ModeHang=0
 
[NXDN]
Enable=0
RAN=1
SelfOnly=0
RemoteGateway=0
ModeHang=0
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
ModeHang=0
Debug=0
 
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
ModeHang=0
Debug=0
 
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=42000
ModeHang=0
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
ModeHang=0
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
ModeHang=0
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: Rpi3 Bridge

Justin Morris
 

Could you help me find what is broken? I can connect to my other node from asl. I do not see the id's i chose in my brandmiester hotspot list

; 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.
 
; General Section describes settings for Analog_Bridge itself.
;   For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
 
; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data
 
; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                      ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the server
 
; Audio devices are normally not needed when in gateway service.  These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null           ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null            ; Only used for dongle mode
 
; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = false                   ; Use app as just a fancy dongle for DMR
useVox = false                          ; If using dongle mode (useMicrophone), enable VOX
voxDecay = 2                            ; Hang time in seconds
voxTrigger = 200                        ; Value to trip PTT (0-32767)
 
; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay
gatewayDmrId = 310502480                ; ID to use when transmitting from Analog_Bridge
repeaterID = 310502480                  ; ID of source repeater
txTg = 31055                            ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames received 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 toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -10                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.25                          ; Gain factor of audio from ASL (0.0-1.0)
 
; 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]
server = 127.0.0.1                      ; IP address of AMBEServer
port = 2460                             ; Port of AMBEServer
; server = /dev/ttyUSB0                 ; Device of DV3000U on this machine
; port = 460800                         ; Baud rate of the dongle
; serial = true                         ; Use serial (DV3000U) or IP
[General]
Callsign=KC5MMW
Id=310502480
Timeout=180
Duplex=0
ModeHang=0
RFModeHang=0
NetModeHang=0
Display=None
Daemon=0
 
[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch
 
[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24
 
[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=C
SelfOnly=0
AckReply=1
AckTime=750
ErrorReply=1
RemoteGateway=0
ModeHang=0
 
[DMR]
Enable=1
Beacons=0
BeaconInterval=60
BeaconDuration=3
ColorCode=1
SelfOnly=0
EmbeddedLCOnly=1
DumpTAData=0
CallHang=0
TXHang=0
ModeHang=0
 
[System Fusion]
Enable=0
LowDeviation=0
SelfOnly=0
RemoteGateway=0
ModeHang=0
 
[P25]
Enable=0
NAC=293
SelfOnly=0
OverrideUIDCheck=0
RemoteGateway=0
ModeHang=0
 
[NXDN]
Enable=0
RAN=1
SelfOnly=0
RemoteGateway=0
ModeHang=0
Id=12345
 
[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
ModeHang=0
Debug=0
 
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
ModeHang=0
Debug=0
 
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=42000
ModeHang=0
Debug=0
 
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
ModeHang=0
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
ModeHang=0
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020
 


Re: Rpi3 Bridge

Steve N4IRS
 

That is a leftover from a older version and will be removed. It is done by ASL during install.

Steve

On 5/31/2018 7:54 AM, kc5mmw@... wrote:
Could someone elaborate on the line in Analog_Bridge.ini that says "for RPI, don"t forget to modprobe sns_pcm_oss to get the devices populated"
How do I do this? 


Rpi3 Bridge

Justin Morris
 

Could someone elaborate on the line in Analog_Bridge.ini that says "for RPI, don"t forget to modprobe sns_pcm_oss to get the devices populated"
How do I do this? 


Re: DMR to AllStar Bridge - Private Call to DMR ID without a TG?

Lito - WI6Y
 

Hi Corey,

This is the excerpt:

Address=3103.repeater.net
Port=62031
Jitter=750
Local=62032
Password=passw0rd

As you can see, it is passw0rd. It does connect for a bit but then it disconnects and generates that message.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Corey Dean N3FE <n3fe@...>
Sent: Wednesday, May 30, 2018 2:42 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?
 
You have the wrong password in the config for connecting to the master.  It should be passw0rd


On May 30, 2018, at 4:26 PM, Roselito de los Reyes <Tolitski@...> wrote:

Hi Steve,

I am getting these messages from my MMDVM_bridge log.

M: 2018-05-30 20:17:45.579 DMR, TX state = ON
I: 2018-05-30 20:17:45.579 DMR, Begin TX: src=1107374 rpt=110737480 dst=5152 slot=2 cc=1 metadata=WI6Y
M: 2018-05-30 20:17:47.601 DMR, TX state = OFF
M: 2018-05-30 20:18:01.693 DMR Slot 2, received network voice header from KQ6RC to TG 5152
M: 2018-05-30 20:18:02.468 DMR Talker Alias (Data Format 1, Received 6/6 char): 'KQ6RC '
M: 2018-05-30 20:18:07.986 DMR Slot 2, received network end of voice transmission, 6.3 seconds, 0% packet loss, BER: 0.0%
W: 2018-05-30 20:18:17.332 DMR, Login to the master has failed, retrying login ...
E: 2018-05-30 20:19:17.332 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-30 20:19:17.332 DMR, Closing DMR Network
M: 2018-05-30 20:19:17.332 DMR, Opening DMR Network
D: 2018-05-30 20:19:27.337 DMR, Sending authorisation
D: 2018-05-30 20:19:27.342 DMR, Sending configuration
M: 2018-05-30 20:19:27.347 DMR, Logged into the master successfully
M: 2018-05-30 20:19:32.315 DMR Slot 2, received network voice header from AF6YU to TG 5152

Why am I getting these messages ? Am I doing something wrong? or is 3103 just congested?

Also, I noticed that sometimes the TA coming from YSF->DMR Mike's call sign (N4IRR) would come up as the default ID..  Where is that located in the config file?

Thanks

Lito

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of WillieB <will@...>
Sent: Friday, May 25, 2018 5:15 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?
 
Hi Steve, no problem. The only difference was the MMDVM_Bridge.ini had 3113756 instead of 311375690. I tried that just now and I could hear myself on hoseline, so I knew that part was working.

So I tried from my radio as a private call and no luck. But then I changed it to a group call and BAM! Working perfectly. Now it even shows up under my Brandmeister self care as a new hotspot 311375690, so I can have separate static TGs than my ZUMspot.

Thanks so much for your help Steve and Jeff, and others that replied. Have a great long weekend!

Will
KE4IAJ

On Fri, May 25, 2018 at 7:40 PM, Steve N4IRS <szingman@...> wrote:
Will,
I tested the config below, but only from ASL to DMR. I do not have 3112138 programmed in my radio. I used the BM last heard and hoseline to verify audio.
Can you show me your config in the same format?

MMDVM_Bridge.ini
[General]
Callsign=N4IRS
Id=311213890

Analog_Bridge.ini
gatewayDmrId = 3112138
repeaterID = 311213890
txTg = 3112138
txTs = 2
colorCode = 1



On 05/25/2018 07:21 PM, WillieB wrote:
Dell PowerEdge C1100
Virtual Machine on ESXi 5.1
Fresh install of Debian 9.4 (no GUI)
4 cores
4GB RAM
500GB HDD

On Fri, May 25, 2018 at 7:09 PM, Steve N4IRS <szingman@...> wrote:
Will,
What hardware are you running the bridge on?

On 05/25/2018 04:56 PM, WillieB wrote:

Well I’m using a ZUMspot connecting through Brandmeister I think, so yes…

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 4:55 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

If you're not connecting to brandmeister then it really doesn't matter I guess.  I assumed you were intending to connect there.  I didn't mean to throw a wrench in the conversation.

 

On Fri, May 25, 2018 at 2:48 PM, WillieB <will@...> wrote:

Steve => I tried that and I also tried the gatewayDmrId as the repeaterID just for grins. Neither worked. I don’t seem to be getting anywhere, but I greatly appreciate the time you guys have been taking to reply. Maybe I need to read some more about TGs. See further explanation below if there’s any confusion on what exactly I’m trying to accomplish.

 

Jeff => Hmm, I’m not sure why I would need a repeater ID just for a DVswitch bridge? If I use a TG in txTg then it works fine. It just won’t allow me to specify a DMR ID in the txTg field.

 

I’ll explain a bit further. The whole reason I’m trying to do this is to allow my HT to make a private or group call to the DMR ID used on the DVswitch bridge and be connected to my AllStar node. Then I can connect my bridged AllStar node to any other AllStar or Echolink node while using my ZUMspot as a DMR hotspot. So this allows me to have DMR, Echolink, and AllStar functionality using 1 hotspot. This works great when I use a TG, the only problem is I’m transmitting on the TG and the communication is only between my HT and the connected AllStar node.

 

Let me give an example. On Tuesday nights at 8:00pm there’s an AllStar Technical net (DMR is discussed frequently) I want to connect to on AllStar node 45221. So what I would do is use my AllStar bridge node 46690 and connect it to 45221. So at that point when the net is taking place on 45221 I will be able to hear it and transmit to it on my HT via DMR ID 3113756. This works great when I bridge my AllStar node 46690 to our local talkgroup, but the only problem is I don’t want it to occupy the talk group. This is why I’m trying to setup a bridge to my DMR ID 3113756 that’s on my HT instead of using a TG. Maybe that clears things up if there is any confusion on what I’m trying to accomplish.

 

If it’s not possible with DVswitch then maybe there are some kind of unused or private TGs I can use if I can’t get DMR IDs to work? Or maybe create my own TG? Guess I need to read more on how TGs work.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 3:37 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

DMR Repeater ID's are typically 6 digits long and they identify the repeater and can therefore be used as a talkgroup

 

A DMR user ID is 7 digits and must be unique as it "generally" translates to an IP address in the DMR system.

 

If you have not already requested a DMR repeater ID I'm thinking you'd need to do that.

 

my 2 cents

 

On Fri, May 25, 2018 at 1:30 PM, WillieB <will@...> wrote:

Right, I understand those definitions. I set it up like this:

 

gatewayDmrId = 3110229 <= DMR ID for KE4IAJ (ID that shows on all DMR radios when the direct is AllStar => DMR.)

repeaterID = 311022901 <= DMR ID above + 01

txTg = 3113756 <= DMR ID for KE4IAJ

 

In a reply from in this same thread you stated “My point is that you can use DMRID as a TG. I do it all the time for testing.”. Wouldn’t this mean that I can use a DMR ID for the txTg? If not then how can I use a DMR ID as a TG?

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 3:21 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

gatewayDmrId is the ID that ALL analog stations will present to BrandMeister it should be a user ID (7 digits)
repeaterID is the repeater that BM thinks the analog traffic is coming from.
txTg is the Talk Group that a analog user will transmit on.

Steve

On 5/25/2018 3:16 PM, WillieB wrote:

Well I tested a private call, my DMR ID to a friend’s DMR ID, both of us with an HT behind a hotspot and it worked perfect. I could call him and he could call me. Then I tested some more with my bridge using 3113756 for both the gatewayDmrId and for txTg. It didn’t work in either direction. I could PTT on my HT and not hear anything on AllStar, and I could transmit on AllStar and not hear anything on my HT.

 

In the meantime I received my other new DMR ID so I tested with it as well. See settings below for Analog_Bridge.ini, but unfortunately nothing is working, same results. 3110229 is my new ID and 311356 is my older one. I’m I setting this up correctly? If I set the contact to TG9 like Steve suggested then how do I specify to call my other DMR ID? I’m quite confused still on how to set this up as a bridge from my ASL node to my HT. Are there any kind of pseudo talkgroups or something similar? Any other ideas?

 

gatewayDmrId = 3110229                  ; ID to use when transmitting from Analog_Bridge

repeaterID = 311022901                  ; ID of source repeater

txTg = 3113756                          ; TG to use for all frames received from Analog_Bridge -> xx_Bridge

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of WillieB
Sent: Friday, May 25, 2018 1:13 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

It doesn’t matter to me if it’s a group or private call. I’ll play around with different settings and see what works.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 12:13 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Hmmm,
A private call? Interesting idea. Then maybe put the TG back to 9? I'll have to think/play with this idea...

On 5/25/2018 11:42 AM, WillieB wrote:

It’s working fine with a TG, but doesn’t seem to be working by me changing the txTg field to my 3113756 DMR ID and rebooting the bridge. I’m sure I’m just doing something wrong. As a test on my HT I did a manual private call to 3113756 and I don’t hear anything on the AllStar node. And when I key the AllStar node nothing happens on my HT. When I look in Brandmeister self-care, it’s showing an Auto Static group of 3113756 which I believe is correct. I’ve attached logs to the email which may help. I’m open for suggestions.

 

73

Will, KE4IAJ

TARG AEC

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:28 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

You should be able to put your current DMRID in, you wont need a second ID.

On 5/25/2018 9:25 AM, WillieB wrote:

Thanks Steve,

 

I’ve always argued the point to my teachers is that it depends on what definition of “sound” that you use lol. I have requested an additional DMR ID waiting for approval. Once it is approved I’ll test using it. My guess is that I just put the DMR ID in the txTg field in place of the TG in the Analog_Bridge.ini file.

 

If that doesn’t work I’ll wait on the example documentation for the HBlink.

 

Will

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:00 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Will,
A couple of comments here. Tying up a TG is a relative thing.  Almost like if a tree falls in a forest and there is no one there to hear it, does it make a sound. My point is that you can use DMRID as a TG. I do it all the time for testing. Another way to solve the issue is to setup hblink as a server or master. Point your MMDVM_bridge at it and point you HS at it. You now have a private connection between MMDVM_Bridge and your ZUMspot.

We are working on the documentation now and a example of that type of config is planned. HBlink is pretty easy to setup.

Steve

On 5/25/2018 8:47 AM, WillieB wrote:

Hello group,

 

I have searched and haven’t found anything so hopefully you guys can point me in the right direction. First of all many many thanks to Steve and anyone else involved for these programs and applications!

 

I am using dvswitch with analog_bridge, mmdvm_bridge, and md380-emu to create a DMR to AllStar bridge. I have it working (Many thanks to KV4S (Russell)) fine bridging to a DMR talkgroup. My question is, can I bridge an AllStar node directly to a DMR user ID without a talkgroup? I guess this would be a private call? What I’m trying to accomplish here is to allow me to use my ZUMspot to connect to AllStar nodes through the bridge, but without tying up an entire talkgroup. Thanks in advance.

 

 

73

Will, KE4IAJ

TARG AEC

 

 

 

 

 

 

 

 






Re: DMR to AllStar Bridge - Private Call to DMR ID without a TG?

Corey Dean N3FE <n3fe@...>
 

You have the wrong password in the config for connecting to the master.  It should be passw0rd


On May 30, 2018, at 4:26 PM, Roselito de los Reyes <Tolitski@...> wrote:

Hi Steve,

I am getting these messages from my MMDVM_bridge log.

M: 2018-05-30 20:17:45.579 DMR, TX state = ON
I: 2018-05-30 20:17:45.579 DMR, Begin TX: src=1107374 rpt=110737480 dst=5152 slot=2 cc=1 metadata=WI6Y
M: 2018-05-30 20:17:47.601 DMR, TX state = OFF
M: 2018-05-30 20:18:01.693 DMR Slot 2, received network voice header from KQ6RC to TG 5152
M: 2018-05-30 20:18:02.468 DMR Talker Alias (Data Format 1, Received 6/6 char): 'KQ6RC '
M: 2018-05-30 20:18:07.986 DMR Slot 2, received network end of voice transmission, 6.3 seconds, 0% packet loss, BER: 0.0%
W: 2018-05-30 20:18:17.332 DMR, Login to the master has failed, retrying login ...
E: 2018-05-30 20:19:17.332 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-30 20:19:17.332 DMR, Closing DMR Network
M: 2018-05-30 20:19:17.332 DMR, Opening DMR Network
D: 2018-05-30 20:19:27.337 DMR, Sending authorisation
D: 2018-05-30 20:19:27.342 DMR, Sending configuration
M: 2018-05-30 20:19:27.347 DMR, Logged into the master successfully
M: 2018-05-30 20:19:32.315 DMR Slot 2, received network voice header from AF6YU to TG 5152

Why am I getting these messages ? Am I doing something wrong? or is 3103 just congested?

Also, I noticed that sometimes the TA coming from YSF->DMR Mike's call sign (N4IRR) would come up as the default ID..  Where is that located in the config file?

Thanks

Lito

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of WillieB <will@...>
Sent: Friday, May 25, 2018 5:15 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?
 
Hi Steve, no problem. The only difference was the MMDVM_Bridge.ini had 3113756 instead of 311375690. I tried that just now and I could hear myself on hoseline, so I knew that part was working.

So I tried from my radio as a private call and no luck. But then I changed it to a group call and BAM! Working perfectly. Now it even shows up under my Brandmeister self care as a new hotspot 311375690, so I can have separate static TGs than my ZUMspot.

Thanks so much for your help Steve and Jeff, and others that replied. Have a great long weekend!

Will
KE4IAJ

On Fri, May 25, 2018 at 7:40 PM, Steve N4IRS <szingman@...> wrote:
Will,
I tested the config below, but only from ASL to DMR. I do not have 3112138 programmed in my radio. I used the BM last heard and hoseline to verify audio.
Can you show me your config in the same format?

MMDVM_Bridge.ini
[General]
Callsign=N4IRS
Id=311213890

Analog_Bridge.ini
gatewayDmrId = 3112138
repeaterID = 311213890
txTg = 3112138
txTs = 2
colorCode = 1



On 05/25/2018 07:21 PM, WillieB wrote:
Dell PowerEdge C1100
Virtual Machine on ESXi 5.1
Fresh install of Debian 9.4 (no GUI)
4 cores
4GB RAM
500GB HDD

On Fri, May 25, 2018 at 7:09 PM, Steve N4IRS <szingman@...> wrote:
Will,
What hardware are you running the bridge on?

On 05/25/2018 04:56 PM, WillieB wrote:

Well I’m using a ZUMspot connecting through Brandmeister I think, so yes…

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 4:55 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

If you're not connecting to brandmeister then it really doesn't matter I guess.  I assumed you were intending to connect there.  I didn't mean to throw a wrench in the conversation.

 

On Fri, May 25, 2018 at 2:48 PM, WillieB <will@...> wrote:

Steve => I tried that and I also tried the gatewayDmrId as the repeaterID just for grins. Neither worked. I don’t seem to be getting anywhere, but I greatly appreciate the time you guys have been taking to reply. Maybe I need to read some more about TGs. See further explanation below if there’s any confusion on what exactly I’m trying to accomplish.

 

Jeff => Hmm, I’m not sure why I would need a repeater ID just for a DVswitch bridge? If I use a TG in txTg then it works fine. It just won’t allow me to specify a DMR ID in the txTg field.

 

I’ll explain a bit further. The whole reason I’m trying to do this is to allow my HT to make a private or group call to the DMR ID used on the DVswitch bridge and be connected to my AllStar node. Then I can connect my bridged AllStar node to any other AllStar or Echolink node while using my ZUMspot as a DMR hotspot. So this allows me to have DMR, Echolink, and AllStar functionality using 1 hotspot. This works great when I use a TG, the only problem is I’m transmitting on the TG and the communication is only between my HT and the connected AllStar node.

 

Let me give an example. On Tuesday nights at 8:00pm there’s an AllStar Technical net (DMR is discussed frequently) I want to connect to on AllStar node 45221. So what I would do is use my AllStar bridge node 46690 and connect it to 45221. So at that point when the net is taking place on 45221 I will be able to hear it and transmit to it on my HT via DMR ID 3113756. This works great when I bridge my AllStar node 46690 to our local talkgroup, but the only problem is I don’t want it to occupy the talk group. This is why I’m trying to setup a bridge to my DMR ID 3113756 that’s on my HT instead of using a TG. Maybe that clears things up if there is any confusion on what I’m trying to accomplish.

 

If it’s not possible with DVswitch then maybe there are some kind of unused or private TGs I can use if I can’t get DMR IDs to work? Or maybe create my own TG? Guess I need to read more on how TGs work.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 3:37 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

DMR Repeater ID's are typically 6 digits long and they identify the repeater and can therefore be used as a talkgroup

 

A DMR user ID is 7 digits and must be unique as it "generally" translates to an IP address in the DMR system.

 

If you have not already requested a DMR repeater ID I'm thinking you'd need to do that.

 

my 2 cents

 

On Fri, May 25, 2018 at 1:30 PM, WillieB <will@...> wrote:

Right, I understand those definitions. I set it up like this:

 

gatewayDmrId = 3110229 <= DMR ID for KE4IAJ (ID that shows on all DMR radios when the direct is AllStar => DMR.)

repeaterID = 311022901 <= DMR ID above + 01

txTg = 3113756 <= DMR ID for KE4IAJ

 

In a reply from in this same thread you stated “My point is that you can use DMRID as a TG. I do it all the time for testing.”. Wouldn’t this mean that I can use a DMR ID for the txTg? If not then how can I use a DMR ID as a TG?

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 3:21 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

gatewayDmrId is the ID that ALL analog stations will present to BrandMeister it should be a user ID (7 digits)
repeaterID is the repeater that BM thinks the analog traffic is coming from.
txTg is the Talk Group that a analog user will transmit on.

Steve

On 5/25/2018 3:16 PM, WillieB wrote:

Well I tested a private call, my DMR ID to a friend’s DMR ID, both of us with an HT behind a hotspot and it worked perfect. I could call him and he could call me. Then I tested some more with my bridge using 3113756 for both the gatewayDmrId and for txTg. It didn’t work in either direction. I could PTT on my HT and not hear anything on AllStar, and I could transmit on AllStar and not hear anything on my HT.

 

In the meantime I received my other new DMR ID so I tested with it as well. See settings below for Analog_Bridge.ini, but unfortunately nothing is working, same results. 3110229 is my new ID and 311356 is my older one. I’m I setting this up correctly? If I set the contact to TG9 like Steve suggested then how do I specify to call my other DMR ID? I’m quite confused still on how to set this up as a bridge from my ASL node to my HT. Are there any kind of pseudo talkgroups or something similar? Any other ideas?

 

gatewayDmrId = 3110229                  ; ID to use when transmitting from Analog_Bridge

repeaterID = 311022901                  ; ID of source repeater

txTg = 3113756                          ; TG to use for all frames received from Analog_Bridge -> xx_Bridge

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of WillieB
Sent: Friday, May 25, 2018 1:13 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

It doesn’t matter to me if it’s a group or private call. I’ll play around with different settings and see what works.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 12:13 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Hmmm,
A private call? Interesting idea. Then maybe put the TG back to 9? I'll have to think/play with this idea...

On 5/25/2018 11:42 AM, WillieB wrote:

It’s working fine with a TG, but doesn’t seem to be working by me changing the txTg field to my 3113756 DMR ID and rebooting the bridge. I’m sure I’m just doing something wrong. As a test on my HT I did a manual private call to 3113756 and I don’t hear anything on the AllStar node. And when I key the AllStar node nothing happens on my HT. When I look in Brandmeister self-care, it’s showing an Auto Static group of 3113756 which I believe is correct. I’ve attached logs to the email which may help. I’m open for suggestions.

 

73

Will, KE4IAJ

TARG AEC

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:28 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

You should be able to put your current DMRID in, you wont need a second ID.

On 5/25/2018 9:25 AM, WillieB wrote:

Thanks Steve,

 

I’ve always argued the point to my teachers is that it depends on what definition of “sound” that you use lol. I have requested an additional DMR ID waiting for approval. Once it is approved I’ll test using it. My guess is that I just put the DMR ID in the txTg field in place of the TG in the Analog_Bridge.ini file.

 

If that doesn’t work I’ll wait on the example documentation for the HBlink.

 

Will

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:00 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Will,
A couple of comments here. Tying up a TG is a relative thing.  Almost like if a tree falls in a forest and there is no one there to hear it, does it make a sound. My point is that you can use DMRID as a TG. I do it all the time for testing. Another way to solve the issue is to setup hblink as a server or master. Point your MMDVM_bridge at it and point you HS at it. You now have a private connection between MMDVM_Bridge and your ZUMspot.

We are working on the documentation now and a example of that type of config is planned. HBlink is pretty easy to setup.

Steve

On 5/25/2018 8:47 AM, WillieB wrote:

Hello group,

 

I have searched and haven’t found anything so hopefully you guys can point me in the right direction. First of all many many thanks to Steve and anyone else involved for these programs and applications!

 

I am using dvswitch with analog_bridge, mmdvm_bridge, and md380-emu to create a DMR to AllStar bridge. I have it working (Many thanks to KV4S (Russell)) fine bridging to a DMR talkgroup. My question is, can I bridge an AllStar node directly to a DMR user ID without a talkgroup? I guess this would be a private call? What I’m trying to accomplish here is to allow me to use my ZUMspot to connect to AllStar nodes through the bridge, but without tying up an entire talkgroup. Thanks in advance.

 

 

73

Will, KE4IAJ

TARG AEC

 

 

 

 

 

 

 

 






Re: DMR to AllStar Bridge - Private Call to DMR ID without a TG?

Lito - WI6Y
 

Hi Steve,

I am getting these messages from my MMDVM_bridge log.

M: 2018-05-30 20:17:45.579 DMR, TX state = ON
I: 2018-05-30 20:17:45.579 DMR, Begin TX: src=1107374 rpt=110737480 dst=5152 slot=2 cc=1 metadata=WI6Y
M: 2018-05-30 20:17:47.601 DMR, TX state = OFF
M: 2018-05-30 20:18:01.693 DMR Slot 2, received network voice header from KQ6RC to TG 5152
M: 2018-05-30 20:18:02.468 DMR Talker Alias (Data Format 1, Received 6/6 char): 'KQ6RC '
M: 2018-05-30 20:18:07.986 DMR Slot 2, received network end of voice transmission, 6.3 seconds, 0% packet loss, BER: 0.0%
W: 2018-05-30 20:18:17.332 DMR, Login to the master has failed, retrying login ...
E: 2018-05-30 20:19:17.332 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-30 20:19:17.332 DMR, Closing DMR Network
M: 2018-05-30 20:19:17.332 DMR, Opening DMR Network
D: 2018-05-30 20:19:27.337 DMR, Sending authorisation
D: 2018-05-30 20:19:27.342 DMR, Sending configuration
M: 2018-05-30 20:19:27.347 DMR, Logged into the master successfully
M: 2018-05-30 20:19:32.315 DMR Slot 2, received network voice header from AF6YU to TG 5152

Why am I getting these messages ? Am I doing something wrong? or is 3103 just congested?

Also, I noticed that sometimes the TA coming from YSF->DMR Mike's call sign (N4IRR) would come up as the default ID..  Where is that located in the config file?

Thanks

Lito


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of WillieB <will@...>
Sent: Friday, May 25, 2018 5:15 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?
 
Hi Steve, no problem. The only difference was the MMDVM_Bridge.ini had 3113756 instead of 311375690. I tried that just now and I could hear myself on hoseline, so I knew that part was working.

So I tried from my radio as a private call and no luck. But then I changed it to a group call and BAM! Working perfectly. Now it even shows up under my Brandmeister self care as a new hotspot 311375690, so I can have separate static TGs than my ZUMspot.

Thanks so much for your help Steve and Jeff, and others that replied. Have a great long weekend!

Will
KE4IAJ

On Fri, May 25, 2018 at 7:40 PM, Steve N4IRS <szingman@...> wrote:
Will,
I tested the config below, but only from ASL to DMR. I do not have 3112138 programmed in my radio. I used the BM last heard and hoseline to verify audio.
Can you show me your config in the same format?

MMDVM_Bridge.ini
[General]
Callsign=N4IRS
Id=311213890

Analog_Bridge.ini
gatewayDmrId = 3112138
repeaterID = 311213890
txTg = 3112138
txTs = 2
colorCode = 1



On 05/25/2018 07:21 PM, WillieB wrote:
Dell PowerEdge C1100
Virtual Machine on ESXi 5.1
Fresh install of Debian 9.4 (no GUI)
4 cores
4GB RAM
500GB HDD

On Fri, May 25, 2018 at 7:09 PM, Steve N4IRS <szingman@...> wrote:
Will,
What hardware are you running the bridge on?

On 05/25/2018 04:56 PM, WillieB wrote:

Well I’m using a ZUMspot connecting through Brandmeister I think, so yes…

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 4:55 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

If you're not connecting to brandmeister then it really doesn't matter I guess.  I assumed you were intending to connect there.  I didn't mean to throw a wrench in the conversation.

 

On Fri, May 25, 2018 at 2:48 PM, WillieB <will@...> wrote:

Steve => I tried that and I also tried the gatewayDmrId as the repeaterID just for grins. Neither worked. I don’t seem to be getting anywhere, but I greatly appreciate the time you guys have been taking to reply. Maybe I need to read some more about TGs. See further explanation below if there’s any confusion on what exactly I’m trying to accomplish.

 

Jeff => Hmm, I’m not sure why I would need a repeater ID just for a DVswitch bridge? If I use a TG in txTg then it works fine. It just won’t allow me to specify a DMR ID in the txTg field.

 

I’ll explain a bit further. The whole reason I’m trying to do this is to allow my HT to make a private or group call to the DMR ID used on the DVswitch bridge and be connected to my AllStar node. Then I can connect my bridged AllStar node to any other AllStar or Echolink node while using my ZUMspot as a DMR hotspot. So this allows me to have DMR, Echolink, and AllStar functionality using 1 hotspot. This works great when I use a TG, the only problem is I’m transmitting on the TG and the communication is only between my HT and the connected AllStar node.

 

Let me give an example. On Tuesday nights at 8:00pm there’s an AllStar Technical net (DMR is discussed frequently) I want to connect to on AllStar node 45221. So what I would do is use my AllStar bridge node 46690 and connect it to 45221. So at that point when the net is taking place on 45221 I will be able to hear it and transmit to it on my HT via DMR ID 3113756. This works great when I bridge my AllStar node 46690 to our local talkgroup, but the only problem is I don’t want it to occupy the talk group. This is why I’m trying to setup a bridge to my DMR ID 3113756 that’s on my HT instead of using a TG. Maybe that clears things up if there is any confusion on what I’m trying to accomplish.

 

If it’s not possible with DVswitch then maybe there are some kind of unused or private TGs I can use if I can’t get DMR IDs to work? Or maybe create my own TG? Guess I need to read more on how TGs work.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Jeff Carrier
Sent: Friday, May 25, 2018 3:37 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

DMR Repeater ID's are typically 6 digits long and they identify the repeater and can therefore be used as a talkgroup

 

A DMR user ID is 7 digits and must be unique as it "generally" translates to an IP address in the DMR system.

 

If you have not already requested a DMR repeater ID I'm thinking you'd need to do that.

 

my 2 cents

 

On Fri, May 25, 2018 at 1:30 PM, WillieB <will@...> wrote:

Right, I understand those definitions. I set it up like this:

 

gatewayDmrId = 3110229 <= DMR ID for KE4IAJ (ID that shows on all DMR radios when the direct is AllStar => DMR.)

repeaterID = 311022901 <= DMR ID above + 01

txTg = 3113756 <= DMR ID for KE4IAJ

 

In a reply from in this same thread you stated “My point is that you can use DMRID as a TG. I do it all the time for testing.”. Wouldn’t this mean that I can use a DMR ID for the txTg? If not then how can I use a DMR ID as a TG?

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 3:21 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

gatewayDmrId is the ID that ALL analog stations will present to BrandMeister it should be a user ID (7 digits)
repeaterID is the repeater that BM thinks the analog traffic is coming from.
txTg is the Talk Group that a analog user will transmit on.

Steve

On 5/25/2018 3:16 PM, WillieB wrote:

Well I tested a private call, my DMR ID to a friend’s DMR ID, both of us with an HT behind a hotspot and it worked perfect. I could call him and he could call me. Then I tested some more with my bridge using 3113756 for both the gatewayDmrId and for txTg. It didn’t work in either direction. I could PTT on my HT and not hear anything on AllStar, and I could transmit on AllStar and not hear anything on my HT.

 

In the meantime I received my other new DMR ID so I tested with it as well. See settings below for Analog_Bridge.ini, but unfortunately nothing is working, same results. 3110229 is my new ID and 311356 is my older one. I’m I setting this up correctly? If I set the contact to TG9 like Steve suggested then how do I specify to call my other DMR ID? I’m quite confused still on how to set this up as a bridge from my ASL node to my HT. Are there any kind of pseudo talkgroups or something similar? Any other ideas?

 

gatewayDmrId = 3110229                  ; ID to use when transmitting from Analog_Bridge

repeaterID = 311022901                  ; ID of source repeater

txTg = 3113756                          ; TG to use for all frames received from Analog_Bridge -> xx_Bridge

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of WillieB
Sent: Friday, May 25, 2018 1:13 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

It doesn’t matter to me if it’s a group or private call. I’ll play around with different settings and see what works.

 

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 12:13 PM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Hmmm,
A private call? Interesting idea. Then maybe put the TG back to 9? I'll have to think/play with this idea...

On 5/25/2018 11:42 AM, WillieB wrote:

It’s working fine with a TG, but doesn’t seem to be working by me changing the txTg field to my 3113756 DMR ID and rebooting the bridge. I’m sure I’m just doing something wrong. As a test on my HT I did a manual private call to 3113756 and I don’t hear anything on the AllStar node. And when I key the AllStar node nothing happens on my HT. When I look in Brandmeister self-care, it’s showing an Auto Static group of 3113756 which I believe is correct. I’ve attached logs to the email which may help. I’m open for suggestions.

 

73

Will, KE4IAJ

TARG AEC

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:28 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

You should be able to put your current DMRID in, you wont need a second ID.

On 5/25/2018 9:25 AM, WillieB wrote:

Thanks Steve,

 

I’ve always argued the point to my teachers is that it depends on what definition of “sound” that you use lol. I have requested an additional DMR ID waiting for approval. Once it is approved I’ll test using it. My guess is that I just put the DMR ID in the txTg field in place of the TG in the Analog_Bridge.ini file.

 

If that doesn’t work I’ll wait on the example documentation for the HBlink.

 

Will

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Friday, May 25, 2018 9:00 AM
To:
main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR to AllStar Bridge - Private Call to DMR ID without a TG?

 

Will,
A couple of comments here. Tying up a TG is a relative thing.  Almost like if a tree falls in a forest and there is no one there to hear it, does it make a sound. My point is that you can use DMRID as a TG. I do it all the time for testing. Another way to solve the issue is to setup hblink as a server or master. Point your MMDVM_bridge at it and point you HS at it. You now have a private connection between MMDVM_Bridge and your ZUMspot.

We are working on the documentation now and a example of that type of config is planned. HBlink is pretty easy to setup.

Steve

On 5/25/2018 8:47 AM, WillieB wrote:

Hello group,

 

I have searched and haven’t found anything so hopefully you guys can point me in the right direction. First of all many many thanks to Steve and anyone else involved for these programs and applications!

 

I am using dvswitch with analog_bridge, mmdvm_bridge, and md380-emu to create a DMR to AllStar bridge. I have it working (Many thanks to KV4S (Russell)) fine bridging to a DMR talkgroup. My question is, can I bridge an AllStar node directly to a DMR user ID without a talkgroup? I guess this would be a private call? What I’m trying to accomplish here is to allow me to use my ZUMspot to connect to AllStar nodes through the bridge, but without tying up an entire talkgroup. Thanks in advance.

 

 

73

Will, KE4IAJ

TARG AEC

 

 

 

 

 

 

 

 






Re: Updated DVSwitch repository available

WillieB <will@...>
 

I tuned my audio last night and ended up with the settings below. First I connected the my bridged node to a local repeater node and equalized the audio listening on DMR and Analog. Once the DMR receive audio was adjusted I then connected my bridged node to 3009999 (Echolink Test Server) and adjusted the audio coming back. Not a perfect science but audio sounds really good in both directions now.

 

aslAudio = AUDIO_USE_AGC

agcGain = -10

dmrAudio = AUDIO_USE_GAIN

dmrGain = 0.50

 

 

73

Will, KE4IAJ

TARG AEC

 

 

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Wednesday, May 30, 2018 1:08 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Updated DVSwitch repository available

 

Peter,
Use:
dmrAudio = AUDIO_USE_GAIN                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 2                                                   ; Gain factor of audio from ASL (0.0-1.0)

This is multiply by 2. If still too low raise by 1 until you get it where you want it. 3.5 is a acceptable number.

Mike and I have been talking about tweaking these defaults.

Steve

On 5/30/2018 12:58 PM, Peter Buckley via Groups.Io wrote:

Thanks Steve,

 

Please make a suggestion as your schedule allows.

 

Symptom needing help:  low volume audio coming back in from DMR side to Allstar side.

My current  Analog_Bridge.ini is below.  Original entries marked with a  #  (updated entries right below those lines)

Steve - I made the adjustments based on an earlier email (to the group) from you.

Q.)  How best to include the DMR Audio going into the Allstar side.

73s  -pete  N0ECT

 

 

[USRP]

server = 127.0.0.1                      ; IP address of Allstar/Asterisk

toASLPort = 32001                       ; Analog_Bridge <-- ASL

fromASLPort = 34001                     ; Analog_Bridge --> ASL

#  aslAudio = AUDIO_UNITY               ; Original Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)

aslAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)

# agcGain = -20                         ; Original  Gain (in db) of the AGC filter

agcGain = .5                            ; Gain (in db) of the AGC filter

dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)

dmrGain = 0.65                          ; Gain factor of audio from ASL (0.0-1.0)

#  dmrGain = 0.35                       ; Original  Gain factor of audio from ASL (0.0-1.0)

 

On Sunday, May 20, 2018 7:23 PM, Steve N4IRS <szingman@...> wrote:

 

I have some updates to make to to the programs, meta packages and config files. We are changing some of the defaults to point to the test reflectors. There are a few minor updates to the programs. 
Mike and I have been working on the documentation and example configs. I'll be updating the wiki with some of the samples.

73, Steve N4IRS

 

 


Re: DMR to ASL audio level

Peter Buckley
 

Thanks Steve,

That DMR Audio increase tip - worked perfectly.  The DMR side came up (what I needed) to get the analog listeners (Allstar) up to a good level.
Our assigned BM/TG 31085   is connected to an old Analog Repeater system that covers most of western Colorado - Vail, Aspen, Glenwood Springs and Grand Junction.
73s  pete  N0ECT


On Wednesday, May 30, 2018 11:07 AM, Steve N4IRS <szingman@...> wrote:


Peter,
Use:
dmrAudio = AUDIO_USE_GAIN                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 2                                                   ; Gain factor of audio from ASL (0.0-1.0)

This is multiply by 2. If still too low raise by 1 until you get it where you want it. 3.5 is a acceptable number.

Mike and I have been talking about tweaking these defaults.

Steve


On 5/30/2018 12:58 PM, Peter Buckley via Groups.Io wrote:
Thanks Steve,

Please make a suggestion as your schedule allows.

Symptom needing help:  low volume audio coming back in from DMR side to Allstar side.
My current  Analog_Bridge.ini is below.  Original entries marked with a  #  (updated entries right below those lines)
Steve - I made the adjustments based on an earlier email (to the group) from you.
Q.)  How best to include the DMR Audio going into the Allstar side.
73s  -pete  N0ECT


[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
#  aslAudio = AUDIO_UNITY               ; Original Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
aslAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
# agcGain = -20                         ; Original  Gain (in db) of the AGC filter
agcGain = .5                            ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.65                          ; Gain factor of audio from ASL (0.0-1.0)
#  dmrGain = 0.35                       ; Original  Gain factor of audio from ASL (0.0-1.0)


On Sunday, May 20, 2018 7:23 PM, Steve N4IRS <szingman@...> wrote:


I have some updates to make to to the programs, meta packages and config files. We are changing some of the defaults to point to the test reflectors. There are a few minor updates to the programs. 
Mike and I have been working on the documentation and example configs. I'll be updating the wiki with some of the samples.

73, Steve N4IRS






Re: DMR to ASL audio level

Steve N4IRS
 

Peter,
Use:
dmrAudio = AUDIO_USE_GAIN                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 2                                                   ; Gain factor of audio from ASL (0.0-1.0)

This is multiply by 2. If still too low raise by 1 until you get it where you want it. 3.5 is a acceptable number.

Mike and I have been talking about tweaking these defaults.

Steve


On 5/30/2018 12:58 PM, Peter Buckley via Groups.Io wrote:
Thanks Steve,

Please make a suggestion as your schedule allows.

Symptom needing help:  low volume audio coming back in from DMR side to Allstar side.
My current  Analog_Bridge.ini is below.  Original entries marked with a  #  (updated entries right below those lines)
Steve - I made the adjustments based on an earlier email (to the group) from you.
Q.)  How best to include the DMR Audio going into the Allstar side.
73s  -pete  N0ECT


[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
#  aslAudio = AUDIO_UNITY               ; Original Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
aslAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
# agcGain = -20                         ; Original  Gain (in db) of the AGC filter
agcGain = .5                            ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.65                          ; Gain factor of audio from ASL (0.0-1.0)
#  dmrGain = 0.35                       ; Original  Gain factor of audio from ASL (0.0-1.0)


On Sunday, May 20, 2018 7:23 PM, Steve N4IRS <szingman@...> wrote:


I have some updates to make to to the programs, meta packages and config files. We are changing some of the defaults to point to the test reflectors. There are a few minor updates to the programs. 
Mike and I have been working on the documentation and example configs. I'll be updating the wiki with some of the samples.

73, Steve N4IRS




DMR to ASL audio level

Peter Buckley
 

Thanks Steve,

Please make a suggestion as your schedule allows.

Symptom needing help:  low volume audio coming back in from DMR side to Allstar side.
My current  Analog_Bridge.ini is below.  Original entries marked with a  #  (updated entries right below those lines)
Steve - I made the adjustments based on an earlier email (to the group) from you.
Q.)  How best to include the DMR Audio going into the Allstar side.
73s  -pete  N0ECT


[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
#  aslAudio = AUDIO_UNITY               ; Original Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
aslAudio = AUDIO_USE_GAIN               ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
# agcGain = -20                         ; Original  Gain (in db) of the AGC filter
agcGain = .5                            ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.65                          ; Gain factor of audio from ASL (0.0-1.0)
#  dmrGain = 0.35                       ; Original  Gain factor of audio from ASL (0.0-1.0)


On Sunday, May 20, 2018 7:23 PM, Steve N4IRS <szingman@...> wrote:


I have some updates to make to to the programs, meta packages and config files. We are changing some of the defaults to point to the test reflectors. There are a few minor updates to the programs. 
Mike and I have been working on the documentation and example configs. I'll be updating the wiki with some of the samples.

73, Steve N4IRS



Re: A brief how to, please

Paul Nannery KC2VRJ
 

I have a low cost vps cloud at cost. Not the best but works however my OS choice is very limited. 


On Wed, May 30, 2018, 12:37 PM Steve N4IRS <szingman@...> wrote:
Happy to help. It allowed me to find and fix a issue. I'm building everything on Jessie for now so bith Jessie and Stretch are supported.

Steve

On 5/30/2018 12:35 PM, Paul Nannery KC2VRJ wrote:
Steve,

Thank you for your help it installed now to make it all play nice


Re: A brief how to, please

Steve N4IRS
 

Happy to help. It allowed me to find and fix a issue. I'm building everything on Jessie for now so bith Jessie and Stretch are supported.

Steve

On 5/30/2018 12:35 PM, Paul Nannery KC2VRJ wrote:
Steve,

Thank you for your help it installed now to make it all play nice


Re: A brief how to, please

Paul Nannery KC2VRJ
 

Steve,

Thank you for your help it installed now to make it all play nice


Re: Updated DVSwitch repository available

Steve N4IRS
 

Mike,
Analog_Bridge is one of the programs in the overall DVSwitch "family" We have enhanced Analog_Bridge and added MMDVM_Bridge, Quantar_Bridge and a few others. We are still early in testing and we are now using the Debian apt method to install. Mike and I have been working on documentation and examples.

73, Steve

On 5/30/2018 10:11 AM, Mike Swiatkowski via Groups.Io wrote:
Steve,
I may have fallen behind with the announcement so my apologies.  Is DVSwitch replacing Analog_Bridge from github since it also contains Analog_Bridge and has much more functionality?  It looks like that is where most of yours and Mike's development efforts have been concentrated lately.  I'm looking forward to trying it all out. 

Mike, AA9VI


Re: Updated DVSwitch repository available

Mike, AA9VI
 

Steve,
I may have fallen behind with the announcement so my apologies.  Is DVSwitch replacing Analog_Bridge from github since it also contains Analog_Bridge and has much more functionality?  It looks like that is where most of yours and Mike's development efforts have been concentrated lately.  I'm looking forward to trying it all out. 

Mike, AA9VI

7701 - 7720 of 9070