[Allstar Digital] DMRGateway / DMRGui / DMRLink /ambe_audio / DV3000u /PiDV
Steve Zingman
szingman at msgstor.com
Mon Apr 10 19:32:51 EDT 2017
OK,
I'm confused too.
On 04/10/2017 07:30 PM, Peter wrote:
>
> # DMRLink SAMPLE CONFIGURATION FILE
> #
> # Rename to dmrlink.cfg and add your information
> #
> # minor tweaks to match install for use by DMRGateway
> # N4IRS
> #
> #
>
> # GLOBAL CONFIGURATION ITEMS
> #
> [GLOBAL]
> PATH: /opt/dmrlink/
>
>
> # NETWORK REPORTING CONFIGURATION
> # Enabling "REPORT_NETWORKS" will cause a reporting action for
> # IPSC each time the periodic reporting loop runs, that period is
> # specifiec by "REPORT_INTERVAL" in seconds. Possible values
> # for "REPORT_NETWORKS" are:
> # PICKLE - a Python pickle file of the network's data structure
> # (JSON DOES NOT WORK RNIGHT NOW) JSON - a JSON file of the
> network's data structure
> # (REDIS DOES NOT WORK RIGHT NOW) REDIS - send JSON format data
> structure to a local|remote
> # redis server
> # PRINT - a pretty print (STDOUT) of the data structure
> # "PRINT_PEERS_INC_MODE" - Boolean to include mode bits
> # "PRINT_PEERS_INC_FLAGS" - Boolean to include flag bits
> #
> # PRINT is the odd man out because it sends prettily formatted stuff
> # to STDOUT. The others send the internal data structure of the IPSC
> # instance and let some program on the other end sort it out.
> #
> # REPORT_INTERVAL - Seconds between reports
> # REPORT_PATH - Absolute path save data (pickle and json)
> #
> [REPORTS]
> REPORT_NETWORKS:
> REPORT_INTERVAL: 60
> REPORT_PATH:
> PRINT_PEERS_INC_MODE: 0
> PRINT_PEERS_INC_FLAGS: 0
>
>
> # SYSTEM LOGGER CONFIGURAITON
> # This allows the logger to be configured without chaning the individual
> # python logger stuff in dmrlink.py. LOG_FILE should be a complete
> # path/filename for *your* system -- use /dev/null for non-file
> handlers.
> # LOG_HANDERLS may be any of the following, please, no spaces in the
> # list if you use several:
> # null
> # console
> # console-timed
> # file
> # file-timed
> # syslog
> # LOG_LEVEL may be any of the standard syslog logging levels, though
> # as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
> # used.
> #
> [LOGGER]
> LOG_FILE: /var/log/dmrlink/dmrlink.log
> LOG_HANDLERS: console
> LOG_LEVEL: DEBUG
> LOG_NAME: DMRlink
>
>
> # DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES
> # Ok, not the TGID, there's no master list I know of to download
> # This is intended as a facility for other applcations built on top of
> # DMRlink to use, and will NOT be used in DMRlink directly.
> # STALE_DAYS is the number of days since the last download before we
> # download again. Don't be an ass and change this to less than a few days.
> [ALIASES]
> TRY_DOWNLOAD: True
> PATH: ../
> PEER_FILE: peer_ids.csv
> SUBSCRIBER_FILE: subscriber_ids.csv
> TGID_FILE: talkgroup_ids.csv
> PEER_URL:
> http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?table=repeaters&format=csv&header=0
> SUBSCRIBER_URL:
> http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?table=users&format=csv&header=0
> STALE_DAYS: 7
>
>
> # CONFIGURATION FOR IPSC NETWORKS
> # Please read these closely - catastrophic results could result by setting
> # certain flags for things DMRlink cannot do.
> #
> # [NAME] The name you want to use to identify the IPSC
> instance (use
> # something better than "IPSC1"...)
> # ENABLED: Should we communiate with this network? Handy if
> you need to
> # shut one down but don't want to lose the config
> # RADIO_ID: This is the radio ID that DMRLink should use to
> communicate
> # IP: This is the local IPv4 address to listen on. It
> may be left
> # blank if you do not need or wish to specify. It is
> mostly
> # useful when DMRlink uses multiple interfaces to
> serve as an
> # application gatway/proxy from private and/or VPN
> networks
> # to the real world.
> # PORT: This is the UDP source port for DMRLink to use for
> this
> # PSC network, must be unique!!!
> # ALIVE_TIMER: Seconds between keep-alive transmissions
> # MAX_MISSED: How many missed keep-alives before we remove a peer
> # PEER_OPER: This signals the master and peers whether or not
> we are
> # operational. True is the only thing that makes sense.
> # IPSC_MODE: May be 'DIGITAL', 'ANALOG', or 'NONE'. Digital is
> really the
> # only thing that makes sense.
> # TSx_LINK: Is this time slot linked?
> # CSBK_CALL: Should be False, we cannot process these, but may
> be useful
> # for debugging.
> # RCM: Repeater Call Monitoring - don't unable unless you
> plan to
> # actually use it, this craetes extra network traffic.
> # CON_APP: Third Party Console App - exactly what DMRlink is,
> should
> # be set to True.
> # XNL_CALL: Can cause problems if not set to False, DMRlink
> does not
> # process XCMP/XNL calls.
> # XNL_MASTER: Obviously, should also be False, see XNL_CALL.
> # DATA_CALL: Process data calls. True if you want to process
> data calls
> # VOICE_CALL: Process voice calls. True if you want to process
> voice calls
> # MASTER_PEER: True if DMRlink will be the master, False if we're
> a peer
> # AUTH_ENABLED: Do we use authenticated IPSC?
> # AUTH_KEY: The Authentication key (up to 40 hex characters)
> # MASTER_IP: IP address of the IPSC master (ignored if DMRlink
> is the master)
> # MASTER_PORT: UDP port of the IPSC master (ignored if DMRlinkn
> is the master)
> # GROUP_HANGTIME: Group hangtime, per DMR configuration
> #
> # ...Repeat the block for each IPSC network to join.
> #
>
> [BM]
> ENABLED: True
> RADIO_ID: 2342425
> IP:
> PORT: 50000
> ALIVE_TIMER: 5
> MAX_MISSED: 20
> PEER_OPER: True
> IPSC_MODE: DIGITAL
> TS1_LINK: True
> TS2_LINK: True
> CSBK_CALL: False
> RCM: True
> CON_APP: True
> XNL_CALL: False
> XNL_MASTER: False
> DATA_CALL: True
> VOICE_CALL: True
> MASTER_PEER: False
> AUTH_ENABLED: False
> AUTH_KEY: 1A2B3C
> MASTER_IP: 91.121.101.163
> MASTER_PORT: 55001
> GROUP_HANGTIME: 5
>
>
> [SAMPLE_MASTER]
> ENABLED: False
> RADIO_ID: 54321
> IP: 192.168.1.1
> PORT: 50000
> ALIVE_TIMER: 5
> MAX_MISSED: 20
> PEER_OPER: True
> IPSC_MODE: DIGITAL
> TS1_LINK: True
> TS2_LINK: True
> CSBK_CALL: False
> RCM: True
> CON_APP: True
> XNL_CALL: False
> XNL_MASTER: False
> DATA_CALL: True
> VOICE_CALL: True
> MASTER_PEER: True
> AUTH_ENABLED: True
> AUTH_KEY: 1A2B3C
> # Below not used for a Master
> # MASTER_IP: 1.2.3.4
> # MASTER_PORT: 50000
> GROUP_HANGTIME: 5
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 11/04/2017 00:28, Steve Zingman wrote:
>> Post your dmrlink.cfg
>>
>> On 04/10/2017 07:26 PM, Peter wrote:
>>>
>>> ################################################
>>> # 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
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 11/04/2017 00:22, Steve Zingman wrote:
>>>> 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 at lists.keekles.org
>>>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Allstar-Digital mailing list
>>>>> Allstar-Digital at lists.keekles.org
>>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Allstar-Digital mailing list
>>>> Allstar-Digital at lists.keekles.org
>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>
>>>
>>>
>>> _______________________________________________
>>> Allstar-Digital mailing list
>>> Allstar-Digital at lists.keekles.org
>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>
>>
>>
>> _______________________________________________
>> Allstar-Digital mailing list
>> Allstar-Digital at lists.keekles.org
>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
>
> _______________________________________________
> Allstar-Digital mailing list
> Allstar-Digital at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20170410/89b5d7bf/attachment.html>
More information about the Allstar-Digital
mailing list