astribank_allow(8) [debian man page]
ASTRIBANK_ALLOW(8) ASTRIBANK_ALLOW(8) NAME
astribank_allow - License Xorcom Astribank (xpp) capabilities. SYNOPSIS
astribank_allow -D device-path [ options ] astribank_allow [-h] DESCRIPTION
Modern Astribanks (with USB product id's 116x) contain capabilities that may be licensed. astribank_allow is used to upload/download the licensing information to/from the device. Uploading a valid license file to an Astribank, changes its capabilities. The change becomes effective after a firmware reset (either by powering the device off and on again, or via the astribank_tool full reset option). Downloading license from the device, produces a valid license file for its current capabilities. This may be backed up, so the device may be later restored to its previous capabilities. The license file contains both a human readable description of the device capabilities for the end user and a hash of the licensing infor- mation used by Xorcom to generate/modify licensed capabilities. OPTIONS
-D device-path Required. The device to read from/write to. This is bus_num/device_num, where bus_num and device_num are the first two numbers in the output of lsusb(8) or dahdi_hardware(8). On older versions of this toolyou needed a complete path to the device, which would be /dev/bus/usb/bus_num/device_num, or /proc/bus/usb/bus_num/device_num. -w Write capabilities to EEPROM, otherwise read capabilities -f filename License filename (stdin/stdout if not specified) -v Increase verbosity. May be used multiple times. -d mask Set debug mask to mask. Default is 0, 0xFF is "everything". -h Displays usage message. SEE ALSO
fxload(8), lsusb(8), astribank_hexload(8), astribank_tool(8) AUTHOR
Alex Landau 29 March 2009 ASTRIBANK_ALLOW(8)
Check Out this Related Man Page
XPP_SYNC(8) User Contributed Perl Documentation XPP_SYNC(8) NAME
xpp_sync - Handle sync selection of Xorcom Astribanks. SYNOPSIS
xpp_sync <auto|dahdi|nn> xpp_sync [-v] DESCRIPTION
On a normal operation one Astribank device provides timing for all the other Astribank devices. When run without parameters, xpp_sync will display a list of Astribanks (xbuses) that are connected and registered as Dahdi spans. The current xpp sync master will be marked. If you this an Astribank is connected and yet it does not appear on the output of xpp_sync, it may be unregistered. Try running dahdi_registration . Parameters auto Automatically selects the best Astribank for syncing. dahdi Gets synchronization from the Dahdi sync master. nn Sets XBUS-nn as sync source. -v Also print the numeric xpp sync rank. (Parameter name is case-insensitive) Example output: Setting SYNC Current sync: 01 Best Available Syncers: + XBUS-01 (usb-0000:00:10.4-3) [usb:12345678] [ PRI_TE PRI_NT PRI_TE PRI_NT ] XBUS-00 (usb-0000:00:10.4-2) [usb:QA-01] [ FXS FXO ] ================================================== WARNING: FXO which is not the syncer cause bad PCM Affected Astribanks are: -------------------------------------------------- XBUS-00 ================================================== In this example we see that the recommended xpp sync master is XBUS-02 - it is the first on the list. It is also the actual syncer, as we can see from the '+' beside it. xpp_sync is normally called from the dahdi init.d script. The parameter it is called with defaults to auto, but it is possible to override that parameter (e.g: set it to dahdi) through the value of XPP_SYNC in /etc/dahdi/init.conf . FILES
/proc/xpp/sync (Deprecated: no longer supported) xpp_sync is essentially a nicer interface to /proc/xpp/sync . That file shows the current xpp sync master (and in what format you need to write to it to set the master). SEE ALSO
dahdi_registration(1), dahdi_cfg(1), README.Astribank perl v5.14.2 2009-09-30 XPP_SYNC(8)