Date   

Re: Output callsigns to variable or CSV file

Steve N4IRS
 

From what program are you trying to get data from?

On 2/2/2020 12:24 PM, Jaenulton@... wrote:
I am working on a script that will log a timestamps and callsign to a text file. I can't figure out how to get the callsign of the station that is broadcasting. Setting it as a variable for use in bash would be really cool, but at this point I would even be happy with a one liner writing it to a TMP .txt file.

Could anyone suggest how to get the callsign from the command line when the RX begins?


Output callsigns to variable or CSV file

Jaenulton@...
 

I am working on a script that will log a timestamps and callsign to a text file. I can't figure out how to get the callsign of the station that is broadcasting. Setting it as a variable for use in bash would be really cool, but at this point I would even be happy with a one liner writing it to a TMP .txt file.

Could anyone suggest how to get the callsign from the command line when the RX begins?


Re: EA5GVK with Zumspot AMBE Server...

ve6gcd@...
 

In addition, additional network changes might be required depending on where you will use DVSwitch mobile.

If the Ambe Server is installed in the house, and you want to use DVSwitch mobile from outside, then you probably need to set up port forwarding in your router for the unit.


Re: EA5GVK with Zumspot AMBE Server...

ve6gcd@...
 

I also tried MD380emu before but I prefer the Zum Ambe Server as the audio conversion to DMR is like night and day between the two.

However, when I used it for YSF I noticed some popping sound in between transmissions. This does not happen when on DMR mode.

I do not believe that this is hardware related. Please note that the Zum Ambe Board was only introduced recently, so probably the Analog_Bridge software needs to be modified for YSF to work well on the new hardware.  

Thus, in the meantime I use Zum Ambe Server for DMR. And for YSF, I configured Analog_Bridge to use ThumbDV on serial mode.   


Re: EA5GVK with Zumspot AMBE Server...

Adam Liette
 

Ok. I didn't know about that part of analog_bridge.ini. What I'm aiming for is to use the AMBE board rather than md380emu and be able to use the DV-Switch mobile app. It was my understanding that using an AMBE device would allow it to work better on D-Star, etc.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of ve6gcd@... <ve6gcd@...>
Sent: Saturday, February 1, 2020 10:27:54 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] EA5GVK with Zumspot AMBE Server...
 
Can you tell me what do you want to do with it on the Pi?

I used the Zum Ambeboard as vocoder hardware for Analog_Bridge. So upon inserting the configured SD card (Ambe Server mode with IP address 192.168.1.230 and port 2460) to the Zum Ambeboard, I plugged the Ethernet data cable to the unit then powered it on. Afterwards, I configured the Analog_Bridge.ini with the following lines:

[DV3000]
address = 192.168.1.230                ; 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 = false                                    ; Use serial=true for direct connect or serial=false for AMBEServer  


Re: EA5GVK with Zumspot AMBE Server...

ve6gcd@...
 

Can you tell me what do you want to do with it on the Pi?

I used the Zum Ambeboard as vocoder hardware for Analog_Bridge. So upon inserting the configured SD card (Ambe Server mode with IP address 192.168.1.230 and port 2460) to the Zum Ambeboard, I plugged the Ethernet data cable to the unit then powered it on. Afterwards, I configured the Analog_Bridge.ini with the following lines:

[DV3000]
address = 192.168.1.230                ; 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 = false                                    ; Use serial=true for direct connect or serial=false for AMBEServer  


Re: EA5GVK with Zumspot AMBE Server...

Adam Liette
 

I had that part done, but I wasn't sure if there was anything special to do on the Pi. I selected the AMBE device, etc, but wasn't getting anywhere on DMR or other modes.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of ve6gcd@... <ve6gcd@...>
Sent: Saturday, February 1, 2020 5:26:03 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] EA5GVK with Zumspot AMBE Server...
 
I setup one before, you just need to set it up using the configurator in the Zum website. Afterwards you just copy the created file to the included SD card, insert it to the ambeboard and you should be good to go


Re: EA5GVK with Zumspot AMBE Server...

ve6gcd@...
 

I setup one before, you just need to set it up using the configurator in the Zum website. Afterwards you just copy the created file to the included SD card, insert it to the ambeboard and you should be good to go


EA5GVK with Zumspot AMBE Server...

Adam Liette
 

 

Hello all. I’ve seen references to using the various AMBE thumb sticks, but has anyone used the Zumspot AMBE server with their installation of EA5GVK’s image? I have the Zumspot device that works either via the network or USB, but didn’t have any luck when I tried it.

 

Thanks,

Adam, W8FLH

 


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

dvlink
dvlink

El jue., 30 ene. 2020 23:38, Jay <jay.n4nqy@...> escribió:
What is the login and password for V8 Virtual machine? 


--

jb   N4NQY


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Jay
 

What is the login and password for V8 Virtual machine? 


--

jb   N4NQY


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

AND.... That was easy. working like a champ.


Re: MMDMV_Bridge password

Steve N4IRS
 

I would login to selfcare and set the password. I believe BM wants people to move away from passw0rd so you may want to choose a unique password.

Steve N4IRS

On 1/29/2020 3:31 AM, Phil VK3VB wrote:
Greetings.

I have had a DMR-P25 DVSWITCH running succesfully for a few months.

About a week ago the brandmeister connection dropped off and I am seeing

M: 2020-01-29 06:31:49.848 DMR, Closing DMR Network
M: 2020-01-29 06:31:49.850 DMR, Opening DMR Network
E: 2020-01-29 06:31:59.909 DMR, Login to the master has failed, retrying network
 ...
M: 2020-01-29 06:31:59.911 DMR, Closing DMR Network
M: 2020-01-29 06:31:59.912 DMR, Opening DMR Network
E: 2020-01-29 06:32:09.968 DMR, Login to the master has failed, retrying network

I am told the password is incorrect, but nothing has changed and it is set to "passw0rd" in the MMDVM_Bridge.ini, which is correct for the master.

Any way to capture the connection request string that is being sent so I can see if something weird is going on?

thanks

Phil VK3VB



MMDMV_Bridge password

Phil VK3VB
 

Greetings.

I have had a DMR-P25 DVSWITCH running succesfully for a few months.

About a week ago the brandmeister connection dropped off and I am seeing

M: 2020-01-29 06:31:49.848 DMR, Closing DMR Network
M: 2020-01-29 06:31:49.850 DMR, Opening DMR Network
E: 2020-01-29 06:31:59.909 DMR, Login to the master has failed, retrying network
 ...
M: 2020-01-29 06:31:59.911 DMR, Closing DMR Network
M: 2020-01-29 06:31:59.912 DMR, Opening DMR Network
E: 2020-01-29 06:32:09.968 DMR, Login to the master has failed, retrying network

I am told the password is incorrect, but nothing has changed and it is set to "passw0rd" in the MMDVM_Bridge.ini, which is correct for the master.

Any way to capture the connection request string that is being sent so I can see if something weird is going on?

thanks

Phil VK3VB


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Correct

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Bill N2WNS <n2wns.radio@...>
Sent: Wednesday, January 29, 2020 7:27:47 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] MMDVM_Bridge not sending to NXDNGateway
 
AH... So no analog bridge for this since no transcoding?


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

AH... So no analog bridge for this since no transcoding?


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

As I said,
Cross connect TX to RX and RX to TX

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31015                  ; Port to send AMBE TLV frames to (export)
RXPort = 31014                  ; Port to listen on (import)


[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31014                  ; Port to send AMBE TLV frames to (export)
RXPort = 31015                  ; Port to listen on (import)

On 1/28/20 9:11 PM, Bill N2WNS wrote:
This is a DMR<->NXDN. I wasn't sure if the MD380 server was needed, so I put it in there anyway. I read it wasn't needed for DMR/NXDN/YSF but I intend on added P25 to the Mix at some point and believed it would be needed then. I mapped out all my ports on paper before putting this in place.

Here is my DVSwtich config :

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31015                  ; Port to send AMBE TLV frames to (export)
RXPort = 31014                  ; Port to listen on (import)
Slot = 2                        ; Export slot


[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31017                  ; Port to send AMBE TLV frames to (export)
RXPort = 31016                  ; Port to listen on (import)
FallbackID = 34000            ; In case we can not find a valid DMR id in the da                                                                                               tabase, export this one
NXDNFallbackID  = 34000         ; Use this ID when the input DMR ID is not found                                                                                                in the database
Translate = 31360=31360           ; Translate NXDN TG < -- > DMR TG (bidirection                                                                                               al)
Slot = 2                        ; Export slot


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

This is a DMR<->NXDN. I wasn't sure if the MD380 server was needed, so I put it in there anyway. I read it wasn't needed for DMR/NXDN/YSF but I intend on added P25 to the Mix at some point and believed it would be needed then. I mapped out all my ports on paper before putting this in place.

Here is my DVSwtich config :

[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31015                  ; Port to send AMBE TLV frames to (export)
RXPort = 31014                  ; Port to listen on (import)
Slot = 2                        ; Export slot


[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31017                  ; Port to send AMBE TLV frames to (export)
RXPort = 31016                  ; Port to listen on (import)
FallbackID = 34000            ; In case we can not find a valid DMR id in the da                                                                                               tabase, export this one
NXDNFallbackID  = 34000         ; Use this ID when the input DMR ID is not found                                                                                                in the database
Translate = 31360=31360           ; Translate NXDN TG < -- > DMR TG (bidirection                                                                                               al)
Slot = 2                        ; Export slot


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Bill,
I'm a little confused. This is a DMR to NXDN bridge? I believe it is based on your first message. You don't need a transcoder to bridge DMR <-> NXDN Here is the flow diagram.

DMR Network <-> MMDVM_Bridge <-> NXDNGateway <-> NXDN Network.

That's it. One copy of MMDVM_Bridge with NXDN and DMR enabled in MMDVM_Bridge.ini
What you want to do is "cross connect" DMR to NXDN in DVSwitch.ini By cross connect, I mean TX Port to RX Port and RX Port to TX Port.

Steve N4IRS

On 1/28/20 8:37 PM, Bill N2WNS wrote:
So in troubleshooting, I came in from the NXDN side and and was able to hit MMDVM_Bridge:

M: 2020-01-29 00:52:16.252 NXDN, received network transmission from N2WNS to TG 31360
M: 2020-01-29 00:52:16.761 DMR, TX state = ON
I: 2020-01-29 00:52:16.761 DMR, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
M: 2020-01-29 00:52:19.529 NXDN, received network end of transmission, 3.4 seconds
M: 2020-01-29 00:52:19.534 DMR, TX state = OFF, DMR frame count was 55 frames

But there was nothing on the DMR side. This tells me there is something a miss in the RTP traffic. Below are my two analog bridges:

DMR<->Analog:

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

; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = False                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2473        ; 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 = 31014                          ; Transmit TLV frames to partner on this port
rxPort = 31015                          ; 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 = 3101883                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310998                          ; ID of source repeater
txTg = 31660                                ; 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 = 32013                          ; Transmit USRP frames on this port
rxPort = 34013                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

[MACROS]

; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute

; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter

; For example using macro "5678" above would look like:
; *5678#9876

; Which would invoke:
; echo 9876

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                   ; IP address of AMBEServer
rxPort = 2460                         ; Port of AMBEServer
; address = /dev/ttyUSB0              ; Device of DV3000U on this machine
; baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
; serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer


Analog<->NXDN:

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

; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2473        ; 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 = 31016                          ; Transmit TLV frames to partner on this port
rxPort = 31017                          ; Listen for TLV frames from partner on this port
ambeMode = NXDN                          ; 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 = 3101883                         ; ID to use when transmitting from Analog_Bridge
repeaterID = 310998                          ; ID of source repeater
txTg = 31660                                ; 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 = 34013                          ; Transmit USRP frames on this port
rxPort = 32013                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

[MACROS]

; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute

; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter

; For example using macro "5678" above would look like:
; *5678#9876

; Which would invoke:
; echo 9876

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                   ; IP address of AMBEServer
rxPort = 2460                         ; Port of AMBEServer
; address = /dev/ttyUSB0              ; Device of DV3000U on this machine
; baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
; serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer

I'm running one instance of the MD380 server.

Am I missing something here?


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

So in troubleshooting, I came in from the NXDN side and and was able to hit MMDVM_Bridge:

M: 2020-01-29 00:52:16.252 NXDN, received network transmission from N2WNS to TG 31360
M: 2020-01-29 00:52:16.761 DMR, TX state = ON
I: 2020-01-29 00:52:16.761 DMR, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
M: 2020-01-29 00:52:19.529 NXDN, received network end of transmission, 3.4 seconds
M: 2020-01-29 00:52:19.534 DMR, TX state = OFF, DMR frame count was 55 frames

But there was nothing on the DMR side. This tells me there is something a miss in the RTP traffic. Below are my two analog bridges:

DMR<->Analog:

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

; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = False                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2473        ; 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 = 31014                          ; Transmit TLV frames to partner on this port
rxPort = 31015                          ; 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 = 3101883                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310998                          ; ID of source repeater
txTg = 31660                                ; 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 = 32013                          ; Transmit USRP frames on this port
rxPort = 34013                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

[MACROS]

; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute

; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter

; For example using macro "5678" above would look like:
; *5678#9876

; Which would invoke:
; echo 9876

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                   ; IP address of AMBEServer
rxPort = 2460                         ; Port of AMBEServer
; address = /dev/ttyUSB0              ; Device of DV3000U on this machine
; baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
; serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer


Analog<->NXDN:

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

; General vocoder setup information
decoderFallBack = true                  ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2473        ; 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 = 31016                          ; Transmit TLV frames to partner on this port
rxPort = 31017                          ; Listen for TLV frames from partner on this port
ambeMode = NXDN                          ; 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 = 3101883                         ; ID to use when transmitting from Analog_Bridge
repeaterID = 310998                          ; ID of source repeater
txTg = 31660                                ; 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 = 34013                          ; Transmit USRP frames on this port
rxPort = 32013                          ; Listen for USRP frames on this port
usrpAudio = AUDIO_UNITY                 ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
usrpGain = 1.10                         ; Gain (in db) of the AGC filter
tlvAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
tlvGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

[MACROS]

; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute

; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter

; For example using macro "5678" above would look like:
; *5678#9876

; Which would invoke:
; echo 9876

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                   ; IP address of AMBEServer
rxPort = 2460                         ; Port of AMBEServer
; address = /dev/ttyUSB0              ; Device of DV3000U on this machine
; baud = 460800                       ; Baud rate of the dongle (230400 or 460800)
; serial = true                       ; Use serial=true for direct connect or serial=false for AMBEServer

I'm running one instance of the MD380 server.

Am I missing something here?

3761 - 3780 of 9579