XPP_SYNC(8)
π XPP_SYNC β the Astribank sync queen π
okay bestie, welcome to XPP_SYNC(8), from the User Contributed Perl Documentation collection β¨ this little baddie is literally the vibe-check for your Xorcom Astribank synchronization, and she's about to explain everything π«Ά
β¨ NAME β¨
xpp_sync β Handle sync selection of Xorcom Astribanks. that's it, that's the job, and she does it flawlessly π
πΈ SYNOPSIS πΈ
xpp_sync <auto|dahdi|nn>
xpp_sync [-v]
π¦ DESCRIPTION π¦
so in normal operation, one Astribank device provides timing for all the other Astribank devices. one main character, everyone else follows. iconic behavior honestly π
When you run xpp_sync with no parameters, it'll show you a list of Astribanks (the xbuses) that are connected and registered as Dahdi spans. The current xpp sync master gets marked so you know who's holding the crown π
Wait, one of your Astribanks is connected but NOT showing up in thexpp_syncoutput? π She's probably unregistered bestie. Try runningdahdi_registration.
π Parameters π
autoβ Automatically selects the best Astribank for syncing. let her choose, she has taste β¨dahdiβ Gets synchronization from the Dahdi sync master. passing the crown upstream, slay πnnβ SetsXBUS-nnas sync source. picking your fave by name, we love a decisive queen π«Ά-vβ Also print the numeric xpp sync rank. receipts, numbers, data. obsessed π
(Parameter name is case-insensitive) β so scream it, whisper it, whatever, no cap π©·
π 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
==================================================
so in this example we see that the recommended xpp sync master is XBUS-02 β she's the first one on the list π₯ and she's also the actual syncer, which we can tell from the + sitting right beside her. main character confirmed π
β οΈ alsoooo take note: FXO which is not the syncer cause bad PCM π and the affected Astribank in this case is XBUS-00. read your warnings, bestie.
xpp_sync is normally called from the dahdi init.d script. the parameter it gets called with defaults to auto, but you can override that parameter (e.g: set it to dahdi) through the value of XPP_SYNC in /etc/dahdi/init.conf β¨ custom configuration is a whole lifestyle, live your truth π
π FILES π
/sys/bus/astribanks/drivers/xppdrv/syncβxpp_syncis essentially a nicer interface to/sys/bus/astribanks/drivers/xppdrv/sync. That file shows the current xpp sync master. πΈ
Writing to it, force XPP drivers to use a different sync master π«
π SEE ALSO π
dahdi_registration(1), dahdi_cfg(1), README.Astribank β go read the girlies, they're all part of the same friend group π«Ά
k bye bestie, go sync your Astribanks, you got this π
this page shipped with perl v5.40.1, dated 2026-06-15 β yes that's the XPP_SYNC(8) energy, periodt β¨ππ¦
π¦ where this page comes from
- ubuntu stonking: dahdi 1:3.4.0-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms