2013-12-15 11:05:34 -05:00
|
|
|
# DMRLink SAMPLE CONFIGURATION FILE
|
|
|
|
#
|
2013-10-12 12:21:00 -04:00
|
|
|
# Rename to dmrlink.cfg and add your information
|
2013-12-15 11:05:34 -05:00
|
|
|
# # GLOBAL CONFIGURATION ITEMS
|
|
|
|
# There are no global options at this time
|
|
|
|
#
|
|
|
|
[GLOBAL]
|
2013-12-22 17:16:10 -05:00
|
|
|
PATH: /absolute/path/to/DMRlink
|
2013-12-15 11:05:34 -05:00
|
|
|
|
|
|
|
|
|
|
|
# STDOUT REPORTING CONFIG
|
|
|
|
# Enabling "REPORT_PEERS" will cause a print-out of the peers in each
|
2014-08-15 09:39:51 -04:00
|
|
|
# IPSC each time the periodic reporting loop runs, that perios is
|
|
|
|
# specifiec by "REPORT_INTERVAL" in seconds. Likewise, the
|
2013-12-15 11:05:34 -05:00
|
|
|
# additional features listed will cause that list to either include
|
|
|
|
# or not include MODE and/or SERVICE FLAG details.
|
|
|
|
#
|
|
|
|
[REPORTS]
|
2013-12-22 17:23:42 -05:00
|
|
|
REPORT_PEERS: 0
|
2014-08-15 09:39:51 -04:00
|
|
|
REPORT_INTERVAL: 60
|
2013-12-15 11:05:34 -05:00
|
|
|
PEER_REPORT_INC_MODE: 0
|
|
|
|
PEER_REPORT_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. LOG_HANDERLS may be any of the
|
|
|
|
# following, please, no spaces in the list if you use several:
|
|
|
|
# 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: /tmp/dmrlink.log
|
2013-12-22 17:26:17 -05:00
|
|
|
LOG_HANDLERS: console
|
|
|
|
LOG_LEVEL: CRITICAL
|
2014-09-05 08:50:49 -04:00
|
|
|
LOG_NAME: DMRlink
|
2013-12-15 11:05:34 -05:00
|
|
|
|
|
|
|
|
|
|
|
# CONFIGURATION FOR IPSC NETWORKS
|
2014-01-02 12:16:23 -05:00
|
|
|
# Please read these closely - catastrophic results could result by setting
|
|
|
|
# certain flags for things DMRlink cannot do.
|
2013-10-12 12:21:00 -04:00
|
|
|
#
|
2013-12-15 11:05:34 -05:00
|
|
|
# [NAME] The name you want to use to identify the IPSC instance (use
|
|
|
|
# something better than "IPSC1"...)
|
2013-10-12 12:21:00 -04:00
|
|
|
# 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
|
2014-10-31 11:30:18 -04:00
|
|
|
# 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.
|
2013-10-12 12:21:00 -04:00
|
|
|
# PORT: This is the UDP source port for DMRLink to use for this
|
|
|
|
# IPSC network, must be unique!!!
|
2014-01-02 12:16:23 -05:00
|
|
|
# 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
|
2014-09-18 19:54:26 -04:00
|
|
|
# MASTER_PEER: True if DMRlink will be the master, False if we're a peer
|
2013-10-12 12:21:00 -04:00
|
|
|
# AUTH_ENABLED: Do we use authenticated IPSC?
|
|
|
|
# AUTH_KEY: The Authentication key (up to 40 hex characters)
|
2014-05-15 18:17:54 -04:00
|
|
|
# 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)
|
2013-10-12 12:21:00 -04:00
|
|
|
#
|
|
|
|
# ...Repeat the block for each IPSC network to join.
|
2013-12-15 11:05:34 -05:00
|
|
|
#
|
2013-10-12 12:08:06 -04:00
|
|
|
|
2014-01-02 12:16:23 -05:00
|
|
|
[IPSC1]
|
2013-10-12 12:08:06 -04:00
|
|
|
ENABLED: True
|
2014-01-02 12:16:23 -05:00
|
|
|
RADIO_ID: 12345
|
2014-10-31 11:30:18 -04:00
|
|
|
IP: 4.3.2.1
|
2014-01-02 12:16:23 -05:00
|
|
|
PORT: 50000
|
2013-10-12 12:08:06 -04:00
|
|
|
ALIVE_TIMER: 5
|
2014-01-02 12:16:23 -05:00
|
|
|
MAX_MISSED: 20
|
2014-10-31 11:30:18 -04:00
|
|
|
PEER_OPER: True
|
|
|
|
IPSC_MODE: DIGITAL
|
2013-10-12 12:08:06 -04:00
|
|
|
TS1_LINK: True
|
|
|
|
TS2_LINK: True
|
2014-10-31 11:30:18 -04:00
|
|
|
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: True
|
2014-01-02 12:16:23 -05:00
|
|
|
AUTH_KEY: 1A2B3C
|
|
|
|
MASTER_IP: 1.2.3.4
|
|
|
|
MASTER_PORT: 50000
|