
Quality of Service 199
IP Telephony Configuration Guide
TCP traffic behavior
Most of corporate intranet traffic is TCP-based. Different from UDP, which has no flow control,
TCP uses a sliding window flow control mechanism. Under this design, TCP increases its window
size, increasing throughput, until congestion occurs. Congestion results in packet losses, and when
that occurs the throughput decreases, and the whole cycle repeats.
When multiple TCP sessions flow over few congestion links in the intranet, the flow control
algorithm can cause TCP sessions in the network to decrease at the same time, causing a periodic
and synchronized surge and ebb in traffic flows. WAN links can appear to be overloaded at one
time, and then followed by a period of under-utilization. There are two results:
• bad performance of WAN links
• IP telephony traffic streams are unfairly affected
Business Communications Manager router QoS support
With a Business Communications Manager system, the VoIP gateway and the router are in the
same box. The Business Communications Manager router performs QoS and priority queuing to
support VoIP traffic. The router supports VoIP in the following two ways:
• In a DiffServ network, the Business Communications Manager system acts as a DiffServ edge
device and performs packet classification, prioritization, and marking. The router performs
admission control for H.323 flows based on the WAN link bandwidth and utilization. When
received, the WAN link marks the H.323 flows as Premium traffic and places the flows in the
high priority queue.
Note: Differentiated Service (DiffServ) is a QoS framework standardized by the Internet
Engineering Task Force (IETF).
• In a non-DiffServ or a legacy network, the router manages the WAN link to make sure
Premium VoIP packets have high priority in both directions when crossing a slow WAN link.
Kommentare zu diesen Handbüchern