Osmocom E1/T1 span recorder https://osmocom.org/projects/osmo-e1-recorder
Go to file
Harald Welte 2c5c079e53 print error message when config file cannot be opened
Change-Id: I52514adf853c0d2dc5114864f0713e549733786d
2019-12-04 12:08:33 +01:00
contrib add contrib/jenkins.sh 2019-11-24 18:42:29 +01:00
doc convert build system to autotools 2019-11-24 18:42:29 +01:00
src print error message when config file cannot be opened 2019-12-04 12:08:33 +01:00
tests tests: Add test_nodes.vty for VTY interface testing 2019-12-04 12:08:33 +01:00
.gitignore update .gitignore 2019-11-24 18:42:29 +01:00
Makefile.am convert build system to autotools 2019-11-24 18:42:29 +01:00
README initial import of incomplete project to record E1 lines 2016-07-28 09:04:11 +02:00
configure.ac convert build system to autotools 2019-11-24 18:42:29 +01:00
git-version-gen convert build system to autotools 2019-11-24 18:42:29 +01:00
osmoappdesc.py convert build system to autotools 2019-11-24 18:42:29 +01:00

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).