(→ice1usb) |
(→ice1usb) |
||
Line 14: | Line 14: | ||
= ice1usb = | = ice1usb = | ||
− | We have chosen [https:// | + | We have chosen [https://osmocom.org/projects/e1-t1-adapter/wiki/IcE1usb Osmocom icE1usb] as a primary interface for our projects for several reasons: |
* good compatibility with big range of hardware hosts due to use USB | * good compatibility with big range of hardware hosts due to use USB | ||
* in opposite to most of DAHDI interfaces it is in production | * in opposite to most of DAHDI interfaces it is in production | ||
Line 20: | Line 20: | ||
* no need for the kernel driver | * no need for the kernel driver | ||
* suitable API for our purposes | * suitable API for our purposes | ||
− | * available at | + | * available at [https://sysmocom.de/products/lab/icE1usb/index.html Sysmocom's web shop] |
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:
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: