(→icE1usb) |
(→/etc/osmocom/osmo-e1d.cfg) |
||
Line 42: | Line 42: | ||
interface 0 icE1usb | interface 0 icE1usb | ||
usb-serial [interface serial number] | usb-serial [interface serial number] | ||
+ | line 0 | ||
+ | mode channelized | ||
</pre> | </pre> | ||
More information about logging section can be found [https://ftp.osmocom.org/docs/latest/osmomsc-vty-reference.pdf here]. | More information about logging section can be found [https://ftp.osmocom.org/docs/latest/osmomsc-vty-reference.pdf here]. |
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:
User manual can be found here.
We maintained Osmocom E1D in our Debian repository (amd64, arm64). It has no modifications so you can use any source of packages you want or build from the sources.
sudo apt install osmo-e1d
log syslog logging level e1d info e1d interface 0 icE1usb usb-serial [interface serial number] line 0 mode channelized
More information about logging section can be found here.
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:
User manual can be found here.
We maintained Osmocom E1D in our Debian repository (amd64, arm64). It has no modifications so you can use any source of packages you want or build from the sources.
sudo apt install osmo-e1d
log syslog logging level e1d info e1d interface 0 icE1usb usb-serial [interface serial number]
More information about logging section can be found here.