Network engineering guidelines overview 93
voice into fixed-length IP packets, provide ISDN signalling, and translate
PSTN numbers into IP addresses. The IP packets are transported across
the IP data network with a low latency that varies with strict limits.
The term "voice services" also includes fax services.
IP evolvedfrom a protocol that allowed multi-vendor hosts to communicate.
The protocol adopted packet-switching technology,providing bandwidth
efficiency for bursty data traffic that can tolerate high latency and jitter
(variation in latency). Since IP supported the TCP transport layer, which
provided connection-oriented and reliable transport, IP took on the
properties of being connectionless and a best-effort delivery mechanism.
The TCP/IP paradigm worked well in supporting data applications at that
time.
New considerations come into play now when the same corporate network
is expected to deliver voice traffic. The intranet introduces impairments,
delay,delay variation, and data packet loss, at levels that are higher than
those delivered by voice networks. Delay between talker and listener
changes the dynamics and reduces the efficiency of conversations, while
delayvariation and packeterrors causes introduces glitches in conversation.
Connecting the IP Trunk3.01 (and later) nodes to the corporate intranet
without preliminary assessments and QoS mechanisms can result in
unacceptable degradation in voice service. Correct design procedures and
principles must be considered.
A good design for the IP Trunk3.01 (and later) network must begin with
an understanding of traffic and the underlying network that will transmit
the traffic. See Figure 24 "IP Trunk 3.01 (and later) network engineering
process" (page 94).
Nortel Communication Server 1000
IP TrunkFundamentals
NN43001-563 02.01 Standard
Release 5.5 21December 2007
Copyright© 2007, Nor tel Networks
.