Osmocom E1/T1 span recorder
https://osmocom.org/projects/osmo-e1-recorder
Harald Welte
d8b9e552db
libosmo-abis Change-Id Ifb22b5544cf06012fa529828dfdf3f0d73b07e7d fixed spelling from existant -> existent, which breaks some of the tests here. Making this change catches up, but will of course fail when older libosmo-abis versions are used. Given the niche nature of osmo-e1-recorder, I think it's not worth investing time into that. Change-Id: Ib7430bf940dea33df79abe01baae670f188ff82e |
||
|---|---|---|
| contrib | ||
| doc | ||
| src | ||
| tests | ||
| .gitignore | ||
| Makefile.am | ||
| README | ||
| configure.ac | ||
| git-version-gen | ||
| osmoappdesc.py | ||
README
Osmocom E1 recorder =================== (C) 2016 by Harald Welte <laforge@gnumonks.org> The idea of this program is to be able to passively record E1/T1 based communications for purposes of data analysis. Recording of a single E1 link always requires two E1 interface cards, one for each direction. Recording can be performed either * passively, using a E1 Tap aapter * asa proxy / man-in-the-middle All timeslots will be opened in "raw" mode, making sure the recording will work wheter or not there is HLDC-based signalling (MTP or LAPD), PCM voice, TRAU frames or anything else on the line. Recording will be done on a per-timeslot basis, dumping the raw bytes read for this timeslot into a file. New files are started regularly, after reaching a pre-determined file size limit. File names contain RTC time stamping and timeslot number. Later possible extensions could include automatic detection of the payload and a more intelligent storage format (e.g. in case of HDLC bsaed signalling).