Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c87a8bc654017a90dcbbab0002, userName='null'} |
---|
JIRAIDAUTH | EM-26855 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd8b0a59, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c8601a1bc701602339d1190006, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a0c8652ba79201656dbe5f14001b, userName='null'} |
---|
REV2 | UserResourceIdentifier{userKey=8a00a0c86573c0900165aaa1a0ed0045, userName='null'} |
---|
|
The traffic management mechanisms provided by the
are designed to ensure that high-priority, real-time voice traffic is processed before lower priority data traffic. At the same time, bandwidth not in use by voice traffic is made available so that data traffic can burst up to full line rate, making efficient use of WAN bandwidthThe traffic management mechanisms provided by the
are designed to ensure that high-priority, real-time voice traffic is processed before lower priority data traffic. At the same time, bandwidth not in use by voice traffic is made available so that data traffic can burst up to full line rate, making efficient use of WAN bandwidth.Traffic management mechanisms are applied to traffic in both the upstream (LAN to WAN) and downstream (WAN to LAN) direction. Each direction is independent of the other and can support different size priority queues. This is particularly useful in ADSL, where the downstream bandwidth is greater than the upstream bandwidth and it would be undesirable to limit downstream data traffic to the rate of the slower upstream link.
Classifying
High-priority voice traffic generated by endpoint devices such as IP phones and client adaptors is identified by their IP address. The user configures these addresses into a priority list using the traffic shaping features of the
VOS. As the
processes packets they are marked as either high or low priority based on this configuration.
...
The maximum WAN upstream bandwidth is multiplied by .85 in this formula to reduce the total bandwidth available for voice calls by 15%. This reduction is necessary because the
automatically reserves 15% of the total WAN bandwidth for low priority data traffic so that data traffic is not starved completely. Starving data traffic completely would increase the number of retry attempts and exacerbate congestion on the link during
periods of peak usage. The following table describes WAN bandwidth calculation examples. Caption |
---|
0 | Table |
---|
1 | WAN Bandwidth Calculation Examples |
---|
|
WAN Bandwidth Calculation | Description |
---|
(1544*.85)/85.6 = 15.3 or 15 total voice calls | The maximum number of G.711 voice calls supported by a T1 (1.544 Kbps). |
(768*.85)/85.6 = 7.6 or 7 total voice calls | The maximum number of G.711 voice calls supported by a 768Kbps SDSL. |
(256periods of peak usage. The following table describes WAN bandwidth calculation examples. Caption |
---|
0 | Table |
---|
1 | WAN Bandwidth Calculation Examples |
---|
|
WAN Bandwidth Calculation | Description |
---|
(1544*.85)/85.6 = |
|
...
...
...
15 total voice calls | The maximum number of G.711 voice calls supported by |
|
...
...
...
...
6 or 7 total voice calls | The maximum number of G. |
|
...
711 voice calls supported by |
|
...
Maximum Calls Allowed with Call Admission Control
...
View traffic shaping stats in the following combinations:
Caption |
---|
0 | Table |
---|
1 | WAN Bandwidth Calculation Examples |
---|
|
Type | Command | Extension |
---|
All interfaces | trafficstats | N/A | Per interface | N/A | -i intfName | Per class of service | N/A | -q CoSName | Per interface per class of service | N/A | -i intfName -q CoSName |
|
For each traffic policy, the following information is displayed:
...