1ATMSIGD.CONF(4) File Formats ATMSIGD.CONF(4)
2
6 atmsigd.conf - configuration file for the ATM signaling demon
7
9 /etc/atmsigd.conf
10
12 atmsigd.conf contains configuration data for atmsigd. atmsigd reads
13 atmsigd.conf after parsing the command line options, before connecting
14 to the ATM network.
15 Configuration parameters are arranged in functional groups. In order to
17 set a parameter, the name of the group, the name of the parameter, and
18 the parameter value(s) have to be specified, e.g.
19 sig level debug
21 decreases the logging threshold for messages related to signaling to
23 the debug level. The following options are recognized:
24 debug dump path
26 Specifies the directory to which atmsigd will write status and
27 trace dumps. If tracing is not yet enabled, the trace size is
28 automatically set to a (small) default value.
29 debug level level
31 Sets the default debug level to level. level can be any of
32 debug, info, warn, error, and fatal. Only messages with the same
33 or a higher priority than the debug level are printed. Note
34 that the command-line option -d generates even more output (e.g.
35 hexdumps of all packets passing between atmsigd and the network)
36 than debug level debug.
37 debug log path
39 Specifies the file to which atmsigd writes logging messages.
40 When using the special file name syslog, messages are send to
41 the system logger instead. Log messages are written to standard
42 output if no log file is specified. Writing to standard output
43 can also be explicitly requested by using the special file name
44 stderr.
45 debug trace [number]
47 Enables tracing and optionally sets the number of entries that
48 should be kept in the trace buffer. A (small) default is used if
49 the number is omitted.
50 io level level
52 Sets the debug level for IO-related messages to level.
53 io max_rate rate
55 Sets the rate to signal if an application requests the "maxi‐
56 mum". See qos(7) for the syntax to use for expressing the rate.
57 The default maximum rate is 353207 cells/second (OC3). (Note
58 that the value of max_rate does not constrain the rates an
59 application can explicitly request.)
60 io qos qos
62 Configures the signaling VC to use the specified QOS (see qos(7)
63 for the syntax). By default, UBR at link speed is used on the
64 signaling VC.
65 io vc [itf.]vpi.vci
67 Uses the specified VC for signaling messages instead of the
68 usual 0.0.5.
69 saal level level
71 Sets the debug level for messages related to SAAL (i.e. SSCF and
72 SSCOP) to level.
73 sig level level
75 Sets the debug level for messages related to signaling (Q.2931
76 or ISP) to level.
77 sig mode mode
79 Set the mode of operation. The following modes are available:
80 user for the user side, network for the network side, and switch
81 for operation in a switch. The default behaviour is user.
82 sig uni30
84 Use UNI 3.0 signaling. If specified together with sig uni31,
85 this option sets UNI 3.1 signaling with a few backwards-compati‐
86 bility extensions.
87 sig uni31
89 Use UNI 3.1 signaling. This option can be combined with sig
90 uni30 (see above).
91 sig uni40
93 Use UNI 4.0 signaling. This option can be combined with sig
94 q.2963.1 (see below).
95 sig q.2963.1
97 Enable peak cell rate renegotiation. This option is only avail‐
98 able with UNI 4.0 signaling.
99 sig vpci vpci itf itf
101 Sets up a very simplistic type of routing. All calls with VPCI
102 values equal to or greater than vpci will be routed to itf, and
103 their VPI values will be set to the signaled VPCI minus vpci.
104 Multiple sig vpci entries can be used to support an arbitrary
105 number of interfaces. Example: with sig vpci 4 itf 1, a call
106 signaled for VPCI/VCI 0.x is routed to 0.0.x, a call signaled
107 for 6.y is routed to 1.2.y, etc.
108 policy level level
110 Sets the debug level for messages related to policy decisions to
111 level.
112 policy decision direction address
114 Takes the specified decision for calls from or to address.
115 decision can be either allow or reject. direction is either from
116 or to. The address may be wildcarded by prepending a slash and
117 the number of significant bits (NSAP) or digits (E.164). The
118 rules are searched in the order in which they appear in atm‐
119 sigd.conf until the first match. If no rule matches, the call is
120 allowed.
121 entity [itf.]vpi.vci { options ... }
123 Activates a signaling entity on that specific VC. Multiple
124 entity clauses can appear in the same configuration. When using
125 entity, the option io vc is not available. entity is optionally
126 followed by the following options, enclosed in curly braces:
127 vpci (corresponds to sig vpci), mode (corresponds to sig mode),
128 qos (corresponds to vc qos), route, and default. The last two
129 options determine how outbound calls are routed. The route
130 option is followed by an address in the format used for
131 addresses in policy. If no route entry matches the called party
132 number of an outbound call, the entry marked with default is
133 selected.
134 When setting multiple parameters in the same group, the group name
136 doesn't have to be repeated if it is followed by the parameters in
137 curly braces. Example:
138 debug {
140 level warn
141 dump /var/tmp
142 log syslog
143 trace 100
144 }
145 Line breaks can be inserted in atmsigd.conf wherever spaces or tabs are
148 allowed. Everything between a `#' and the end of the line is considered
149 a comment. The `#' character cannot be escaped.
150 If an option is specified in atmsigd.conf and on the command line, the
152 command line has priority.
153
155 Certain options used by past versions of atmsigd but no longer docu‐
156 mented on the man page are still recognized and supported, but they
157 also yield a warning message. Future versions of atmsigd will not rec‐
158 ognize those options.
159
161 Werner Almesberger, EPFL ICA <Werner.Almesberger@epfl.ch>
162
164 atmsigd(8), qos(7), syslogd(8)
165Linux March 19, 2000 ATMSIGD.CONF(4)