Why is link bandwidth important?
During a call to a Remote Phone or Esi-Link site, voice packets travel in a steady stream in both directions. There must be adequate capacity — bandwidth — in the link for each of those packets to arrive at the opposite end with no more than an acceptable amount of latency and jitter. When an IP link is near-capacity or overloaded, some packets can be significantly delayed and discarded; as a result, a Remote Phone connection on such an IP link will suffer from serious audio distortion. Even a site with high-end broadband access may not have adequate available bandwidth, if that broadband access is heavily used.
During a call to a Remote Phone, voice packets travel in a steady stream in both directions. There must be adequate capacity — bandwidth — in the link for each of those packets to arrive at the opposite end with no more than an acceptable amount of latency and jitter. When an IP link is near-capacity or overloaded, some packets can be significantly delayed and discarded; as a result, a Remote Phone connection on such an IP link will suffer from serious audio distortion. Even a site with high-end broadband access may not have adequate available bandwidth, if that broadband access is heavily used.
Related Questions
- How does HyperIP handle congestion between two sites? For example, what will happen if the link/network between two sites is not dedicated or there is no bandwidth guaranteed?
- Why Is the Link with the Maximum Reservable Bandwidth Selected in CSPF Calculation Although the Tie-breaking Is Set to Most-Fill Mode?
- Can I monitor bandwidth usage per link or on an aggregate basis?
