IPmux-24 from RAD provides legacy services over packet networks. The
IPmux-24 converts the data stream from its user E1/T1 ports into packets for transmission over the network. The frame format of these
packets is IP or MPLS. These packets are transmitted via the IPmux-24 Ethernetnetworkport to the PSN. A remote
pseudowire device converts the packets back to the original user traffic format.
Popular models include IPMUX-24/FE/4T1/UTP/UTP/UTP/PE, IPMUX-24/1T1/NULL/NULL/UTP, IPMUX-24/FE/1T1/UTP/UTP/UTP, IPMUX-24/FE/4T1/UTP/UTP/UTP.
IPmux-24 PSEUDOWIRE FUNCTIONALITY
The ASIC-based architecture of the IPmux-24 provides a robust and high performance pseudowire
solution with minimal processing delay.
The RAD IPmux-24 supports various legacy over packet transport types, including
TDMoIP, CESoPSN, SAToP, HDLCoPSN. Proper balance between PSN throughput and delay is achieved via configurable
packet size. A jitterbuffer compensates for packet delay variation (jitter) of up to 180 msec
in the network.
PSEUDOWIRE QoS/CoS with the IPmux-24 Ethernet networks – outgoing pseudowire packets are assigned a dedicated VLAN ID
according to 802.1Q and marked for priority using 802.1p bits. IP networks – outgoing pseudowire
packets are marked for priority using DSCP, ToS, or Diffserv bits. MPLS networks –
outgoing pseudowire packets are assigned to a specific MPLS tunnel and marked for priority using EXP
IPmux-24 PSEUDOWIRE TIMING
End-to-end synchronization between circuits is maintained by deploying advanced clock recovery mechanisms.
Clock recovery conforms to G.823 and G.824 traffic interface using G.8261-defined scenarios.
Advanced clock recovery conforms to G.823 synchronization interface using G.8261-defined scenarios and achieves
16 ppb clock accuracy. The system clock ensures a single clock source for all TDM links. The system clock
uses master and fallback timing sources for clock redundancy. IPmux-24 also provides system clock input and output via
an optional external clockport.
One, two or four E1 or T1 ports provide connectivity to any standard E1 or T1 device.
The E1 and T1 interfaces support:
• Integral LTU/CSU for long haul applications
• G.703 unframed and G.704 framed modes
• CAS and CRC-4 bit generation (E1)
• D4/SF and ESF framing (T1)
• Robbed bit (T1).
IPmux-24 ETHERNET CAPABILITIES
RAD's IPmux-24 features an internal bridge, operating in VLAN-aware and VLAN-unaware modes.
VLAN stacking can be used for traffic separation between different users or services, by defining a service provider
VLANID per customer or service. When VLAN stacking is used, a service provider VLAN tag is added to the user traffic and
removed from network traffic. Both service provider VLANID and service provider VLAN priority can be defined.
IPmux-24 provides four priority queues for each port or pseudowire traffic. User traffic
can be prioritized according to the VLAN priority, DSCP, IP Precedence or per port basis.
Ingress and egress rate limitation can be activated per user and networkport. The
rate limitation is configured per packet types.
IPmux-24 can be configured and monitored locally via an ASCII terminal, or remotely via
Telnet/SSH, Web browser or RADview.
Management traffic can run over a dedicated VLAN. The RADview Service Center and Element
Manager packages control and monitor TDM over IP (TDMoIP) devices and circuits. The Service Center’s intuitive GUI, “point
and-click” functionality and easy-to-follow wizards increase the efficiency and
accuracy of the service provisioning process. IPmux-24 performs RADIUS client authentication. Using SSH and SSL
encryption protocols allows secure communication over potentially insecure IP-based networks.
Software download is supported via the local terminal, using XMODEM, or remotely, using
TFTP. After downloading a new software version, IPmux-24 automatically saves the previous version in
non-volatile memory for backup purposes. Similarly, copies of the configuration file
may be downloaded and uploaded to a remote workstation for backup and restore purposes.
IPmux-24 OAM AND DIAGNOSTICS
The following RFC-2495 E1/T1physical layer performance statistics are available:
LOS, LOF, LCV, RAI, AIS, FEBE, BES, DM, ES, SES, UAS and LOMF. IPmux-24 performs an internal built-in test
(BIT) after power-up. The results of the test are visible via the local terminal.
LAN and IP layer network condition statistics, such as packet loss and packet delay variation (jitter) are monitored and
stored by the device. Fault isolation, statistics and event logging are available.
Fault propagation initiates service port alarms, e.g. E1/T1LOS, to reflect packet
network fault conditions. Alarms detected at service ports are propagated to the
remote pseudowire device via the packetnetwork. Diagnostic loopbacks can be activated
inband. Performance monitoring is provided by Ethernet and IP-layer network condition statistics, such as packet sequence errors
(loss or misorder) and packet delay variation (jitter), which are monitored and stored by the device.
RAD’s TDM PW OAM mechanism ensures connectivity verification, round trip delay
measurement and pseudowire configuration mismatch prevention. The carrier-class version of IPmux-24
includes an alarm relay mechanism. The minor and major alarms are forwarded to a remote alarm device via dedicated pins
of the external clockRJ-45 connector.
IPmux-24/H is an environmentally hardened version intended for street-cabinet and cellular-tower