Black Box MT1050A, MT1051A, MT1050A-E1, MT1051A-E1, MT1051A-E1-CX Specifications

1

Inexpensively migrate
to Ethernet.

Get more out of your
legacy equipment
without costly, across­the-board upgrades.

Use TDMoIP tech­nology, which is much
more versatile than
VoIP.

Models available for
T1, E1, FXS, and FXO.

Robust QoS support.

Full-featured network
monitoring.

Three clocking
methods.

O

ur Multi-Input IP Muxes extend

T1, E1, or Foreign Exchange
Station/Foreign Exchange Office
(FXS/FXO) services transparently
over widely deployed IP networks.
A Multi-Input IP Mux on the
forwarding end takes a data
stream at its T1, E1, or analog
voice interface, divides it into
fixed-size packets, and assigns
an IP header to each packet.
The packets are then sent to
the Multi-Input IP Mux on the
receiving end, where the headers
are removed, the data stream is
reconstructed, and the clock is
regenerated before the data
stream is sent to its destination.

Multi-Input IP Muxes also
offer large buffers to compensate
for network delays. They can be
used to extend T1, E1, or POTS
circuits over IP networks for
metropolitan area network
applications. All muxes feature a
10-/100-Mbps Ethernet port that

Save a ton of money—migrate to

Ethernet without upgrading

everything in your system!

Key Features

MULTI-INPUT IP MUXES

operates at full or half-duplex.
This connectivity enables carriers
and enterprises to migrate to
Ethernet without discarding
investments in legacy equipment,
especially expensive PBXs.

Two models are available for
T1, three for E1, and one model
each for FXS or FXO connectivity.

All signals are GO at start-up.

You can configure and monitor
Multi-Input IP Muxes locally via
an ASCII terminal or remotely via
Telnet™. Upon startup, the muxes
perform an internal built-in test
(BIT), and the results of the test
are visible at the local terminal.
Multi-Input IP Muxes also feature
end-to-end alarm generation
and Alarm Indication Signal
(AIS) indication.

Incredible packet-pushin’ action.

With Multi-Input IP Muxes,
packets are configurable! Plus
these muxes can compensate for

packet-delay variation (jitter)
up to 300 msec in the network.
High-performance buffering
and forwarding techniques can
reduce an end-to-end processing
delay to as low as 3 msec.

The muxes’ Quality of Service
(QoS) support also enables you
to give TDMoIP packets a higher
priority when they’re sent to
network switches and routers.
Models with a User Port feature
an internal Layer 2 Ethernet switch
that’s transparent to LAN bridging.
It enables rate limiting, VLAN
tagging, and priority labeling
according to 802.1p&Q.

Three o’clock rock of reliability.

Choose between internal,
loopback, or adaptive clocking.
These three methods maintain
reliable synchronization between
TDM devices. And these muxes
support standard IP features like
PING, ARP, and next hop.

Black Box Corporation • 1000 Park Drive • Lawrence, PA 15055-1018 • Tech Support: 724-746-5500 • www.blackbox.com • e-mail: [e-mail]

© 2005. All rights reserved.

Black Box Corporation.

1/24/2005 #10267

2

Actually, many network environments do. But how one environment
benefits can greatly differ from how another one does. Here are several
examples:

• Utility companies can use TDMoIP to achieve transparent
connectivity between sites for legacy services.

• Cellular operators can reduce 2G access costs with TDMoIP while
building IP networks for 3G migration.

Which network environments benefit most from TDMoIP?

T

DMoIP is simpler and less

expensive than VoIP, and it’s a
superior alternative in many other
ways— especially in applications
where the existing PBX function­ality is all you need.

If voice communication is

your chief concern, TDMoIP

provides higher voice quality
with much lower latency than
VoIP. In addition, TDMoIP can
support all applications that run
over T1 circuits— not just
voice— and that’s something
VoIP just can’t do. Also, unlike
VoIP, TDMoIP can provide

Technically Speaking:TDMoIPvs.V oIP

traditional leased-line services
over IP, and it’s transparent to
protocols and signaling.

Compared to VoIP, TDMoIP
also has an evolutionary, not
revolutionary, approach to
migrating to IP or Ethernet. That
way, your investment protection

is maximized and you can get the
most use out of legacy equipment.
Last but not least, TDMoIP
supports installed PBXs with
no loss of functionality.

The chart below summarizes
the key differences between
TDMoIP and VoIP.

TDMoIP (TDM Transport over IP)

Simple and evolutionary

• Uses standard protocols, such as T1, E1, and IP.

• Low cost of ownership.

Complex and revolutionary

• Uses new and evolving protocols, like H.323, MGCP, and SIP.

• Its complexity requires the retraining of IT staff.

VoIP (IP Telephony)

Supports existing PBXs

• That means a significant cost savings to you!

• Little disruption to business.

Transparent to signaling and protocols

• No loss of PBX functionality.

• Superior voice quality.

• Much lower latency.

Configurable packet size

• Minimizes delay.

• Minimizes overhead.

Enables data, voice, and video extension

• Bandwidth can handle a variety of applications.

DS0-level bundling and cross-connect features

Forklift upgrade required (who wants to reinvent telephony?)

• You have to deal with costly upgrades and replacements.

• Compatibility issues are also a problem.

Translates between signaling formats

• Limited support for existing PBX features.

• Long call-setup times.

Packets depend on codec samples

• Longer delays as sample is recorded.

• Overhead is required on each voice session.

Primarily voice

• You’ve paid for all those upgrades, and you’re mostly limited
to a single type of application!

Voice switching per call

• Incumbent carriers can use TDMoIP to maintain their investment
in existing equipment and provide full legacy functionality over the
packet-switched network. In turn, operational costs are reduced.

• Metropolitan carriers can optimize Ethernet for multiservice
transport with TDMoIP.

• Enterprises can use TDMoIP to reduce network expenses by
running all traffic over Ethernet.