Osmocom E1/T1 span recorder https://osmocom.org/projects/osmo-e1-recorder
Go to file
Harald Welte 13351138e2 e1_inp: Use HDLC mode for signalling, not SIGN
The SIGN mode implies that LAPD instances are bound to the timeslots, which is
of course not what we want in a pure capturing/recording scenario.

Instead, use the new E1INP_TS_TYPE_HDLC mode, which allows us to capture
any HDLC framed messages on E1/T1 timeslots, whether LAPD or e.g. MTP.
2016-10-19 10:54:59 +02:00
src e1_inp: Use HDLC mode for signalling, not SIGN 2016-10-19 10:54:59 +02:00
README initial import of incomplete project to record E1 lines 2016-07-28 09:04:11 +02: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).