(→icE1usb) |
(→Driver configuration) |
||
Line 37: | Line 37: | ||
<pre> | <pre> | ||
+ | log stderr | ||
+ | logging filter all 1 | ||
+ | logging color 1 | ||
+ | logging print category-hex 0 | ||
+ | logging print category 1 | ||
+ | logging print thread-id 0 | ||
+ | logging timestamp 1 | ||
+ | logging print file 1 | ||
+ | logging level e1d info | ||
e1d | e1d | ||
interface 0 icE1usb | interface 0 icE1usb |
Usual E1/T1 over IP protocols use generic frames over IP transfer that makes 2 megabits constant rate with up to 8000 packets per second. That approach:
Fur such kind of integrations we prefer to have our own agent software on-site with hardware E1/T1 interfaces.
We have chosen Osmocom icE1usb as a primary interface for our projects for several reasons:
We maintained [Osmocom E1D] in our Debian repositories. It has no modifications so you can shose any source of packages you want or build from the sources.
sudo apt install osmo-e1d
log stderr logging filter all 1 logging color 1 logging print category-hex 0 logging print category 1 logging print thread-id 0 logging timestamp 1 logging print file 1 logging level e1d info e1d interface 0 icE1usb usb-serial [interface serial number] line 0
Usual E1/T1 over IP protocols use generic frames over IP transfer that makes 2 megabits constant rate with up to 8000 packets per second. That approach:
Fur such kind of integrations we prefer to have our own agent software on-site with hardware E1/T1 interfaces.
We have chosen Osmocom icE1usb as a primary interface for our projects for several reasons:
We maintained [Osmocom E1D] in our Debian repositories. It has no modifications so you can shose any source of packages you want or build from the sources.
sudo apt install osmo-e1d
e1d interface 0 icE1usb usb-serial [interface serial number] line 0