Network design
306 Avaya Application Solutions IP Telephony Deployment Guide
As
Figure 80: Committed information rate (burst range)
on page 305 shows, traffic up to the
CIR is guaranteed, whereas traffic beyond the CIR usually is not. This is how Frame Relay is
intended to work. CIR is a committed and reliable rate, whereas burst is a bonus when network
conditions permit it without infringing upon the CIR of any user. For this reason, burst frames
are marked as discard eligible (DE), and are queued or discarded when network congestion
exists. Although experience has shown that customers can achieve significant burst throughput,
it is unreliable and unpredictable, and not suitable for real-time applications like IP Telephony.
Therefore, the objective is to prevent voice traffic from entering the burst range and being
marked DE. One way to accomplish this is to prohibit bursting by shaping the traffic to the CIR
and setting the excess burst size (B
e
– determines the burst range) to zero. However, this also
prevents data traffic from using the burst range.
Additional frame relay information
One interesting piece of knowledge is that most IXCs convert the long-haul delivery of Frame
Relay into ATM. That is, the Frame Relay PVC is converted to an ATM PVC at the first Frame
Relay switch after leaving the customer premise. It is not converted back to Frame Relay until
the last Frame Relay switch before entering the customer premise. This is significant because
ATM has built- in Class of Service (CoS). A customer can contract with a carrier to convert the
Frame Relay PVC into a constant bit rate (CBR) ATM PVC. ATM CBR cells are delivered with
lower latency and higher reliability.
Finally, under the best circumstances, Frame Relay is still inherently more susceptible to delay
than ATM or TDM. Therefore, after applying the best possible queuing mechanism, one should
still expect more delay over Frame Relay than is present over ATM or TDM.
VPN
Many definitions exist for Virtual Private Networks (VPNs). VPNs refer to encrypted tunnels that
carry packetized data between remote sites. VPNs can use private lines, or use the Internet
through one or more Internet Service Providers (ISPs). VPNs are implemented in both
dedicated hardware and software, but can also be integrated as an application to existing
hardware and software packages. A common example of an integrated package is a firewall
product that can provide a barrier against unauthorized intrusion, as well as perform the security
features that are needed for a VPN session.
The encryption process can take from less than 1 millisecond (ms) to 1 second or more, at each
end. Obviously, VPNs can represent a significant source of delay, and therefore have a negative
affect on voice performance. Avaya VPN products encrypt traffic with less than 1ms of delay,
and thus are appropriate for IP Telephony. Also, because most VPN traffic runs over the Internet
and there is little control over QoS parameters for traffic crossing the Internet, voice quality may
suffer due to excessive packet loss, delay, and jitter. Users might be able to negotiate a
service-level agreement with the VPN provider to guarantee an acceptable level of service.
Before implementing IP Telephony with a VPN, users should test their VPN network over time to
ensure that it consistently meets the requirements that are specified in the Avaya IP Voice
Quality Network Requirements Document Summary.
Содержание Application Solutions
Страница 1: ...Avaya Application Solutions IP Telephony Deployment Guide 555 245 600 Issue 3 4 1 June 2005 ...
Страница 20: ...About This Book 20 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 21: ...Issue 3 4 1 June 2005 21 Section 1 Avaya Application Solutions product guide ...
Страница 22: ...22 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 74: ...Avaya Application Solutions platforms 74 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 106: ...Call processing 106 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 124: ...Avaya LAN switching products 124 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 139: ...Issue 3 4 1 June 2005 139 Section 2 Deploying IP Telephony ...
Страница 140: ...140 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 186: ...Traffic engineering 186 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 204: ...Security 204 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 214: ...Voice quality network requirements 214 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 228: ...Avaya Integrated Management 228 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 239: ...Reliability Issue 3 4 1 June 2005 239 Figure 69 S8700 Media Server in a high reliability configuration ...
Страница 274: ...Reliability and Recovery 274 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 275: ...Issue 3 4 1 June 2005 275 Section 3 Getting the IP network ready for telephony ...
Страница 276: ...276 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 350: ...Implementing Communication Manager on a data network 350 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 356: ...Network recovery 356 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 366: ...Network assessment offer 366 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 367: ...Issue 3 4 1 June 2005 367 Appendixes ...
Страница 368: ...Appendixes 368 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 394: ...Access list 394 Avaya Application Solutions IP Telephony Deployment Guide ...
Страница 414: ...DHCP TFTP 414 Avaya Application Solutions IP Telephony Deployment Guide ...