################################################
# ambe_audio configuration file.
################################################
# DEFAULTS - General settings. These values are
# inherited in each subsequent section (defined by section value).
[DEFAULTS]
debug = False # Debug output for each VOICE frame
outToFile = False # Write each AMBE frame to a file called ambe.bin
outToUDP = True # Send each AMBE frame to the _sock object (turn on/off DMRGateway operation)
gateway = 127.0.0.1 # IP address of DMRGateway app
toGatewayPort = 31000 # Port DMRGateway is listening on for AMBE frames to decode
remoteControlPort = 31002 # Port that ambe_audio is listening on for remote control commands
fromGatewayPort = 31003 # Port to listen on for AMBE frames to transmit to all peers
gatewayDmrId = 2342425 # id to use when transmitting from the gateway
tgFilter = 23525 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway
txTg = 23525 # TG to use for all frames received from DMRGateway -> IPSC
txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
#
# The section setting defines the current section to use. By default, the ‘ENABLED’ section in dmrlink.cfg is used.
# Any values in the named section override the values from the DEFAULTS section. For example, if the BM section
# has a value for gatewayDmrId it would override the value above. Only one section should be set here. Think
# of this as an easy way to switch between several different configurations with a single line.
#
section = BM # Use BM section values
# section = Sandbox # Use SANDBOX section values
[BM] # BrandMeister
tgFilter = 23525 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway
txTg = 23525 # TG to use for all frames received from DMRGateway -> IPSC
txTs = 1 # Slot to use for frames received from DMRGateway -> IPSC
Post your ambe_audio.cfg
On 04/10/2017 07:20 PM, Peter wrote:
Been doing a bit more experimenting with this, something weird is going on. My source ID is 2342425 and the destination ID should be TG234525 But, see attached, any ideas? Peter On 06/04/2017 13:23, Steve Zingman wrote:As peter has mentioned, Mike and I have been working on updating ambe_audio to work with the current version of DMRlink. Right now traffic from ASL is passing to DMR without error. Mike has a capture of the latest error when passing traffic from DMR to analog. Due to the nature of DMRlink, we have to squash a bug and move on to the next. This does take time. Stay tuned. 73, Steve N4IRS _______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital