| 1 |
# |
| 2 |
# /etc/dahdi/genconf_parameters |
| 3 |
# |
| 4 |
# This file contains parameters that affect the |
| 5 |
# dahdi_genconf configuration generator. |
| 6 |
# |
| 7 |
# Syntax: |
| 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: |
| 14 |
# key |
| 15 |
# <whitespace...>value1 |
| 16 |
# <whitespace...>value2 |
| 17 |
# ... |
| 18 |
# |
| 19 |
|
| 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: |
| 22 |
#base_exten 4000 |
| 23 |
# |
| 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. |
| 27 |
#fxs_immediate yes |
| 28 |
# |
| 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. |
| 32 |
#fxs_default_start ls |
| 33 |
# |
| 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 |
| 36 |
# lines. |
| 37 |
#fxo_default_start ls |
| 38 |
|
| 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 . |
| 42 |
#lc_country il |
| 43 |
|
| 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 |
| 47 |
# |
| 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 |
| 51 |
# |
| 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 |
| 56 |
|
| 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 . |
| 59 |
#group_phones 5 |
| 60 |
# |
| 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 |
| 63 |
#group_lines 0 |
| 64 |
|
| 65 |
# Channels of digital trunk of span N are also added to group 10+N (that |
| 66 |
# is: 14 for channels of span 4). |
| 67 |
|
| 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. |
| 74 |
#bri_sig_style bri |
| 75 |
# |
| 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 |
| 78 |
# phones. |
| 79 |
#brint_overlap |
| 80 |
|
| 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. |
| 83 |
# |
| 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. |
| 87 |
# |
| 88 |
#echo_can hpec |
| 89 |
#echo_can oslec |
| 90 |
#echo_can none # to avoid echo canceler altogether |
| 91 |
|
| 92 |
# bri_hardhdlc: |
| 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. |
| 96 |
# |
| 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'. |
| 102 |
#bri_hardhdlc auto |
| 103 |
|
| 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 |
| 110 |
#pri_connection_type CAS |
| 111 |
# |
| 112 |
# Explicitly set the idle bits for E1 CAS (Sample value is the default): |
| 113 |
#r2_idle_bits 1101 |
| 114 |
# |
| 115 |
# Set T1 framing type to d4 instead of esf: |
| 116 |
#tdm_framing d4 |
| 117 |
# |
| 118 |
# Use E&M on CAS (default is FXS/FXO). If set, E1 spans will be used as |
| 119 |
# E&M-E1 and T1 will use the requested type: |
| 120 |
#em_signalling em |
| 121 |
#em_signalling em_w |
| 122 |
#em_signalling featd |
| 123 |
#em_signalling featdtmf |
| 124 |
#em_signalling featdtmf_ta |
| 125 |
#em_signalling featb |
| 126 |
#em_signalling fgccama |
| 127 |
#em_signalling fgccamamf |
| 128 |
# |
| 129 |
# pri_termtype contains a list of settings: |
| 130 |
# Currently the only setting is for TE or NT (the default is TE). This |
| 131 |
# sets two different but normally related configuration items: |
| 132 |
# |
| 133 |
# A TE span will have *_cpe signalling in Asterisk and will also get |
| 134 |
# timing from the remote party. |
| 135 |
# |
| 136 |
# A NT span will have *_new signalling in Asterisk and will provide |
| 137 |
# timing to the remote party. |
| 138 |
# |
| 139 |
# pri_termtype is a list if span specs and configuration (TE/NT) for |
| 140 |
# them. The first spec that matches is used. The matching is of perl |
| 141 |
# regular expressions, but with '*' and '?' have their meaning from |
| 142 |
# basic regular expressions. |
| 143 |
#pri_termtype |
| 144 |
# SPAN/2 NT |
| 145 |
# SPAN/4 NT |
| 146 |
# |
| 147 |
#pri_termtype |
| 148 |
# SPAN/* NT |
| 149 |
# |
| 150 |
# Astribanks can be matched by span and also by their: |
| 151 |
# LABEL + XPD number: |
| 152 |
# this is burned into the Astribank and won't change |
| 153 |
# if it's connected via different USB port/hub |
| 154 |
# CONNECTOR + XPD number: |
| 155 |
# The USB path to which the Astribank is connected. |
| 156 |
# Replacing an Astribank and connecting to the same USB port/hub |
| 157 |
# would not change this property. However, any change in USB |
| 158 |
# wiring (e.g: adding another hub) may alter this. |
| 159 |
# NUM (XBUS number) + XPD number: |
| 160 |
# The XBUS number. This is not stable and may even change |
| 161 |
# between boots. |
| 162 |
# |
| 163 |
#pri_termtype |
| 164 |
# LABEL/usb:INT01216/XPD-0[123] NT |
| 165 |
# LABEL/usb:INT00375/XPD-0[123] NT |
| 166 |
# CONNECTOR/@usb-0000:00:1d.7-1/XPD-0[123] NT |
| 167 |
# CONNECTOR/@usb-0000:00:1d.7-2/XPD-0[123] NT |
| 168 |
# NUM/XBUS-01/XPD-0[123] NT |
| 169 |
# NUM/XBUS-03/XPD-0[123] NT |