| 1
1 introduction

Welcome to the iPort

e Telos iPort is designed to help you achieve one of two objectives:
Connect two Livewire-equipped facilities over a wide-area network, such that they
appear to be local to each other. As many as 8 bi-directional channels are possible. In the
simplest case, a single Livewire 8x8 interface Node and an iPort at each end provide 8x
bi-directional codec links over an IP channel.
Encode streams for Internet transmission to the public or for internal distribution
systems. ese are normally sent to a SHOUTcast or compatible server to generate the
many streams needed to support individual listeners. As many as 16 encode-only streams
are possible.
It uses state-of-the-art MPEG codec technology to conserve network bandwidth, while
preserving high audio quality. A range of codec types and bitrates are supported.
Codec Bitrates Notes
aaC 24 - 320kbps standard aaC
aaC-He 24 - 320kbps High-eciency aaC, also called aaC+
aaC-Hev2 24 - 320kbps latest generation aaC-He with parametric stereo enhancements
aaC-lD 24 - 320kbps low-delay aaC
layer 3 (MP3) 24 - 320kbps standard MP3
e codecs are all licensed from Fraunhofer IIS, the inventor of MP3 and co-inventor of
AAC. ey are the highest-possible quality implementations, running on a powerful Intel
floating-point processor.
All audio is connected via a single RJ-45 jack. Because it uses Livewire for the local audio
inputs/outputs, it does not need expensive and space-consuming onboard converters and
connectors.
Configuration is via a web interface. A front-panel LCD offers a simple and immediate
local display of basic operation status and parameters such as the assigned IP number.
ere are two Ethernet jacks, one for connection to the local network and the other to the
wide-area network.
In the link operating mode, the iPort is intended to be used over IP connections that have reasonably good
Quality of Service (QoS), with controlled packet loss, jitter, and bandwidth. The AAC codec has a conceal-
ment mechanism to deal with occasional packet loss, but it is not intended for conditions where packet