1DAHDI_REGISTRATION(8) User Contributed Perl DocumentationDAHDI_REGISTRATION(8)
2
3
4

NAME

6       dahdi_registration - Handle registration of Xorcom XPD modules in
7       dahdi.
8

SYNOPSIS

10       dahdi_registration [-v] [-s sortorder] [-R] [on|off]
11

DESCRIPTION

13       Without parameters, show all connected XPDs sorted by physical
14       connector order.  Each one is show to be unregistered (off), or
15       registered to a specific dahdi span (the span number is shown).
16
17       All registerations/deregisterations are sorted by physical connector
18       string.
19
20       Span registration should generally always succeed. Span unregistration
21       may fail if channels from the span are in use by e.g. asterisk. In such
22       a case you'll also see those channels as '(In use)' in the output of
23       lsdahdi(8).
24
25       dahdi_registration is intended to be used when the kernel module
26       parameter xpp.dahdi_autoreg is false (and implicitly: when the module
27       parameter dahdi.auto_assign_span is true). See also the NOTES section
28       regarding "dahdi_span_assignments".
29
30       If dahdi_autoreg is true, the program will normally do nothing.
31
32   Parameters
33       off -- deregisters all XPD's from dahdi.
34
35       on -- registers all XPD's to dahdi.
36
37   Options
38       -v  verbose output.
39
40       -R  Force operations (on/off) even if the module parameter
41           dahdi_autoreg for xpp is enabled (which makes this program
42           unneeded).
43
44       -s sort_order
45           The sort order to use.
46
47       If the option is not used, the sort order is taken from the environment
48       variable XBUS_SORT and failing that: the hard-coded default of
49       SORT_XPPORDER.
50
51       The available sorting orders are documented in Dahdi::Xpp manual.
52
53   Sample Output
54       An example of the output of dahdi_registration for some registered
55       Astribanks:
56
57         $ dahdi_registration -s type
58         XBUS-01         usb:0000153     usb-0000:00:10.4-2
59                 XBUS-01/XPD-00: on Span 1
60                 XBUS-01/XPD-01: on Span 2
61         XBUS-00         usb:0000157     usb-0000:00:10.4-4
62                 XBUS-00/XPD-00: on Span 3
63                 XBUS-00/XPD-01: on Span 4
64                 XBUS-00/XPD-02: on Span 5
65                 XBUS-00/XPD-03: on Span 6
66                 XBUS-00/XPD-04: on Span 7
67                 XBUS-00/XPD-05: on Span 8
68                 XBUS-00/XPD-06: on Span 9
69                 XBUS-00/XPD-07: on Span 10
70         XBUS-02                 usb-0000:00:10.4-1
71                 XBUS-02/XPD-00: on Span 11
72                 XBUS-02/XPD-10: on Span 12
73         # Sorted: type
74

FILES

76       /proc/xpp/XBUS-nn/XPD-mm/dahdi_registration
77           Reading from this file shows if if the if the specific XPD is
78           registered. Writing to it 0 or 1 registers / unregisters the
79           device.
80
81           This should allow you to register / unregister a specific XPD
82           rather than all of them.
83

NOTES

85       dahdi_registration is intended to be used when the kernel module
86       parameter xpp.dahdi_autoreg is false (and implicitly: when the module
87       parameter dahdi.auto_assign_span is true), that is, Astribank devices
88       as detected by XPP (xbus / xpd) do not register automatically with the
89       DAHDI core. This tool is used to register tem in an explicit order. It
90       works well, but only if you can arange for all of the Astribanks of the
91       system to be available (and not already registered) at a specific point
92       in time.
93
94       Newer versions of DAHDI added support for registering a span to a
95       specific span/channelss numbers specification. This allows registering
96       them out of order. To use this capability, the module parameter
97       dahdi.auto_assign_span should be unset (set to 0) and thus spans of
98       detected DAHDI devices could be registered using
99       "dahdi_span_assignments" (which may also be run automatically from a
100       udev hook).
101
102       In this case there is no point in delaying XPP device registration with
103       dahdi and the parameter xpp.dahdi_autoreg should be set.
104       dahdi_registration will simply become a no-op.
105

SEE ALSO

107       dahdi_cfg(8), dahdi_span_assignments(8).
108
109
110
111perl v5.36.0                      2023-01-19             DAHDI_REGISTRATION(8)
Impressum