background image
Designing Voice-over-Data Networks 597
Figure 16-5 shows an example of legacy PBX-to-PBX connectivity. The connections are from
the PBX to the local exchange carrier, and then to a tandem switch. Then the connection is made
to an interexchange carrier's point of presence.
Figure 16-5
Private Branch Exchange (PBX)
Designing Voice-over-Data Networks
The requirements that drive the design issues when running voice over data are similar to the
other design issues that have been discussed throughout this book.
If the business requirement is to lower overall communications costs, a potential design solution
places voice over data. The cost savings result from not having to run a separate network for
voice and a separate network for data. For the design to be considered a success, the voice over
data network must successfully deliver the quality and performance of the existing voice
network. Data and voice networks were designed with different objectives. A traditional data
network allows and expects bursty data flow. Data comes in packets and grabs as much
bandwidth as it can at any given time. Data networks tolerate bursty data flow and first-come,
first-served access. In addition, the data rate adapts to network conditions and can tolerate small
delays.
In contrast, voice traffic does not flow in bursts. The packets are equally spaced. Voice packets
need a reserved amount of bandwidth. They don't need much; sometimes as little as 8 K is
enough. Whatever they need must be available during the duration of the call.
When e-mail is slow, the problem of receiving e-mail slowly is usually tolerated. When voice
traffic is slow and delayed, however, the result is unacceptable. If voice traffic runs over a
LA
10s
100s
213-666-5678
Tie trunks
CO trunks
CO
416-
526-1234
CO
Tie trunks
CO trunks
NY
10s
100s
213-345-2424
PSTN
IXC
FX
PSTN
87200333.book Page 597 Wednesday, August 22, 2001 1:41 PM