dahdi_test(8) System Manager's Manual dahdi_test(8)NAME
dahdi_test -- Test if the DAHDI timer provides timely response
SYNOPSIS
dahdi_test [ -v ]
DESCRIPTION
dahdi_test dahdi_test runs a timing test in a loop and prints the result of each loop. The test is as follows:
It reads 8192 bytes from the DAHDI timer device (/dev/dahdi/pseudo). This should take exactly 8000 ms . It uses calls to gettimeofday(2)
before and after that read to check that indeed exactly 8000ms have passed.
Values of 100% and 99.99% Are normally considered a definite pass. Values of 99.98% and 99.97% are probably OK as well.
OPTIONS -v
Be more verbose: print one line per test.
-c count
Run for count times instead of running forever.
FILES
/dev/dahdi/pseudo
The device file used to access the DAHDI timer.
SEE ALSO dahdi_tool(8), dahdi_cfg(8), asterisk(8). gettimeofday(2)AUTHOR
This manual page was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> Permission is granted to copy, distribute and/or modify this docu-
ment under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.
2005-06-25 dahdi_test(8)
Check Out this Related Man Page
dahdi_scan(8) System Manager's Manual dahdi_scan(8)NAME
dahdi_scan -- Print Configuration of DAHDI Spans
SYNOPSIS
dahdi_scan [spans]
DESCRIPTION
dahdi_scan prints information about DAHDI spans in the system. For analog spans it also provides a list of channels.
By default it prints information about all the spans in the system. However if parameters are provided, they will be considered to be a
list of span numbers and information will be printed for them.
Output is printed to the standard output. The format is that of an Asterisk configuration file (similar to a "ini" configuration file),
where the name of the section is the number of the span. Note that the specifically for analog spans some keys may appear more than once,
and hence you can not use a parser for an "ini" format and assume you have a dictionary.
EXAMPLES
Printing information for spans 1, 2 and 4:
dahdi_scan 1 2 4
And to print all the spans:
dahdi_scan
Information about a certain analog span:
[5]
active=yes
alarms=OK
description=Xorcom XPD #00/10: FXS
name=XBUS-00/XPD-10
manufacturer=Xorcom Inc.
devicetype=Astribank: Unit 1 Subunit 0: FXS
location=usb-0000:00:03.3-4
basechan=125
totchans=8
irq=0
type=analog
port=125,FXS
port=126,FXS
port=127,FXS
port=128,FXS
port=129,FXS
port=130,FXS
port=131,FXS
port=132,FXS
And an example of a digital span:
[1]
active=yes
alarms=RED
description=T2XXP (PCI) Card 0 Span 1
name=TE2/0/1
manufacturer=Digium
devicetype=Wildcard TE205P (4th Gen)
location=Board ID Switch 0
basechan=1
totchans=24
irq=193
type=digital-T1
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
The "type" field may contain: "analog", "digital-T1", "digital-E1", "digital-J1" or "digital-BRI".
FILES
Requires read access to /dev/dahdi/ctl .
SEE ALSO dahdi_cfg(8), asterisk(8).
BUGS
The program still does not do everything described in the man page.
It also assumes that spans don't skip channel numbers, and that their channel numbers are "running". This is anyway almost always the case.
And always the case in a normal boot process.
AUTHOR
This manual page was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> Permission is granted to copy, distribute and/or modify this docu-
ment under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.
On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.
2008-03-18 dahdi_scan(8)