Why not TDMoIP / CESoIP?

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:

  • not suitable for distributed sites with limited internet access
  • makes constant parasite load on the servers
  • requires delays to compensate jitters
  • has issues with asynchronous-to-synchronous transition

Fur such kind of integrations we prefer to have our own agent software on-site with hardware E1/T1 interfaces.

  • good timings driven by E1/T1 clock or GPS
  • good framing due to synchronous composition on the site
  • less traffic due to transfer only valuable demultiplexed information

icE1usb

IcE1usb-usb side.jpg

We have chosen Osmocom icE1usb as a primary interface for our projects for several reasons:

  • good compatibility with big range of hardware hosts due to use USB
  • in opposite to most of DAHDI interfaces it is in production
  • open-source hardware design
  • no need for the kernel driver
  • suitable API for our purposes
  • available at Sysmocom's web shop

Why not TDMoIP / CESoIP?[edit]

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.

icE1usb[edit]

IcE1usb-usb side.jpg

We have chosen Osmocom icE1usb as a primary interface for our projects for several reasons: