IPmux-16 Installation and Operation Manual Chapter 1 Introduction
Overview 1-3
Features Management
IPmux-16 can be managed via a local terminal, Telnet, or via RADview, RAD’s
Network Management system. IPmux-16 has an RJ-45 port for the local terminal
connection for monitoring and control. Software upload and download and
configuration can be performed via the local terminal or via RADview.
T1
T1 ports and framers comply with ANSI T1.403 standards. The T1 jitter
performance is according to G.824, TR-62411. The T1 framers support
pass-through, SF, ESF and CAS. Integral LTU/CSU can be enabled for line
protection and long haul options. FDL and transmit PRM for T1/ESF are also
supported.
E1
E1 ports comply with G.703 and G.823 standards. E1 framers comply with G.704.
The E1 framers support pass-through, framed, CRC4 MF and CAS MF framing.
Integral LTU/CSU can be enabled for line protection and long haul options.
IP
The data stream coming from the E1 or T1 ports into IP frames is converted and
transferred over the Fast Ethernet port and vice versa.
The TDM bytes are encapsulated in a UDP frame that runs over IP and over
Ethernet.
The number of TDM bytes in an IP frame is configurable for throughput / delay
tradeoff.
A single IP address should be set per device (Host IP). A destination IP address can
be configured for each bundle (see Multibundling, below). IP ToS field support can
be configured for IP Level Priority.
Ethernet
IPmux-16 has a half/full duplex, 10/100 Ethernet port for LAN connectivity.
Each E1/T1 module includes a single, standard 10/100BaseT port with
auto-negotiation support, which provides the uplink to the network. If
auto-negotiation is disabled, IPmux-16 can be configured to any of the following:
• 100BaseT – full duplex
• 100BaseT – half duplex
• 10BaseT – full duplex
• 10BaseT – half duplex.
Half duplex operation in IPmux-16 is not recommended because collisions and
backoffs cause large delay variation and may exceed the delay variation buffer