astribank_is_starting(8) [debian man page]

ASTRIBANK_IS_STARTING(8)												  ASTRIBANK_IS_STARTING(8)

NAME

       astribank_is_starting - Mark / check is a Xorcom Astribank (xpp) is starting

SYNOPSIS

       astribank_is_starting [-d] [-v] [-t timeout] <-a|-r|-w>

       astribank_is_starting [-d] [-v]

       astribank_is_starting -h

DESCRIPTION

       astribank_is_starting is an internal tool used by various xpp scripts to mark that there may be an Astribank device currently initializing,
       and to check for that mark.

       Technically the mark is a SysV semaphore.

OPTIONS

       -a
	      Add.  Set the mark. Should return 0 unless there's an error.

       -r
	      Remove.  Reset the mark. Should return 0 unless there's an error.

       -ttimeout
	      Timeout.	Set the timeout value for the -w option. Default is 60 seconds.

       -w
	      Wait.  Wait for mark to be reset. Should return 0 unless there's an error.

       Without -a or -r: return 0 if the mark has been set, or a non-zero value otherwise.

       -d
	      Print debug information to stderr.

       -v
	      Verbose execution.

       -h
	      Displays usage message.

FILES

       /proc/sysvipc/sem
	      If set, the astribank should appear there with the ID 11211168 (0xAB11A0).  Naturally the ID (or rather, the usage of a semaphore in
	      the first place) is an implementation detail that may change.

NOTES

       astribank_is_starting  is used to mark the fact that an Astribank may be currently reenumerating (technically: distonnecting and connecting
       as a new USB device) after loading the firmware. Thus the script that loads the firmware (/usr/share/dahdi/xpp_fxloader) uses this  utility
       to set the mark.

       The mark is reset by /usr/share/dahdi/waitfor_xpds , which is typically run by the DAHDI init script and waits for all Astribanks to finish
       loading.

       Q: Why do you use a semaphore?

       A: because, unlike the filesystem, it is writable at any given time.

BUGS

       Option ordering matter. The -v and -d options should preceed the actions (-a, -r and -w).  The  -ttimeout  option  should  preceed  the	-w
       option.

SEE ALSO

       semctl(3)

AUTHOR

       This  manual  page  was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> .  Permission is granted to copy, distribute and/or modify this
       document 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.

								  16 August 2009					  ASTRIBANK_IS_STARTING(8)

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)