2
# /etc/dahdi/genconf_parameters
4
# This file contains parameters that affect the
5
# dahdi_genconf configuration generator.
8
# * A comment from '#' to end of line
9
# * Blank lines ignored
10
# * Whitespace at end of line trimmed
11
# * Single valued items:
12
# key <whitespace...> value
13
# * List valued items:
15
# <whitespace...>value1
16
# <whitespace...>value2
20
# When generating extensions for chan_dahdi.conf or users.conf etc: the
21
# extension number will be channel_number+base_exten . The default is:
24
# Make FXS (analog phones) extensions answer immediately (sets
25
# 'immediate = yes' for them in chan_dahdi.conf). Don't enable this before
26
# you're read documentation about this option.
29
# For FXS (analog phones) - use KS or LS? ks is the only method for
30
# Asterisk to provide disconnect supervision and thus it would normally
31
# be preferred and is the default.
34
# For FXO (analog lines) - use KS or LS? KS is the default and is
35
# normally the better choice as it allows detecting hang-ups on many
39
# Set tone zone values. This is used for playing tones (busy, dial-tone
40
# and such). The default is 'us'. This sets the value for both loadzone
41
# and defaultzone in system.conf .
44
# The dialplan context into which to send trunks in chan_dahdi.conf or
45
# users.conf. The default value is:
46
#context_lines from-pstn
48
# The dialplan context into which to send extensions in chan_dahdi.conf or
49
# users.conf. The default value is:
50
#context_phones from-internal
52
# Two extra contexts for the input ports and output ports of an
53
# Astribank. Default values are:
54
#context_input astbank-input
55
#context_output astbank-output
57
# A group to put all analog phones in. By default 0, so you can dial to
58
# the 'first phone available' using Dahdi/g5 .
61
# A group in which to put all the channels belonging to some trunk.
62
# Thus you can dial through "some trunk" using Dahdi/G0/NUMBER
65
# Channels of digital trunk of span N are also added to group 10+N (that
66
# is: 14 for channels of span 4).
68
# Do we want to use PtP ('bri') or PtMP ('bri_ptmp') for BRI? PtMP
69
# allows connecting several CPE devices on the same network device
70
# (several BRI phones on the same line, kind of like several analog
71
# phones on the same analog line). However it is generally brings
72
# unnecessary complexity for a pbx-pbx connection. It is still the
73
# default as this is normally what you get for a BRI PSTN connection.
76
# If this option is set (that is: not remmed-out), BRI NT ports will
77
# also be set as overlap. This is useful if you want to connect ISDN
81
# The echo canceler to use. If you have a hardware echo canceler, just
82
# leave it be, as this one won't be used anyway.
84
# The default is mg2, but it may change in the future. E.g: a packager
85
# that bundles a better echo canceler may set it as the default, or
86
# dahdi_genconf will scan for the "best" echo canceler.
90
#echo_can none # to avoid echo canceler altogether
93
# 'yes' - forces BRI cards to use 'hardhdlc' signalling.
94
# 'no' - forces BRI cards to use 'dchan' (an alias for 'fcshdlc').
95
# It is usefull only for dahdi with the bristuff patch.
97
# If it is left out or set to 'auto':
98
# * Information supplied by the driver is used to decide:
99
# - Currently implemented for Astribanks.
100
# - Taken from /sys/bus/xpds/drivers/bri/dchan_hardhdlc.
101
# * Without this info, falls back to 'hardhdlc'.
104
# For MFC/R2 Support: 'R2' will make E1 spans CAS and with the
105
# 'r2_idle_bits' bit in system.conf . It will also make dahdi_genconf default
106
# to generating the channels of this card in unicall.conf rather than in
107
# chan_dahdi.conf . The meaning of this may be extended somehow to support
108
# R2 through openr2/chan_dahdi later on.
109
#pri_connection_type R2
112
# pri_termtype contains a list of settings:
113
# Currently the only setting is for TE or NT (the default is TE). This
114
# sets two different but normally related configuration items:
116
# A TE span will have *_cpe signalling in Asterisk and will also get
117
# timing from the remote party.
119
# A NT span will have *_new signalling in Asterisk and will provide
120
# timing to the remote party.
122
# pri_termtype is a list if span specs and configuration (TE/NT) for
123
# them. The first spec that matches is used. The matching is of perl
124
# regular expressions, but with '*' and '?' have their meaning from
125
# basic regular expressions.