Call volume is the key metric to consider when determining the scale of any UC Monitor deployment. In Avaya environments, call volume affects not only database size and growth and collector load, but also bandwidth usage, as many endpoints send quality data to the collector. However, our testing indicates that the amount of additional bandwidth used is negligible.
The following breakdown is based on our testing and provides a range that includes the approximate usage in your environment.
The following table illustrates bandwidth usage that is based on the number of simultaneous calls and the average duration of each call:
|
|
Average Call Duration (in minutes) |
|||
|
Busy-Hour Calls |
2 |
3 |
4 |
5 |
|
1000 |
0.19 MBps |
0.29 MBps |
0.38 MBps |
0.48 MBps |
|
5000 |
0.95 MBps |
1.43 MBps |
1.91 MBps |
2.38 MBps |
|
10000 |
1.91 MBps |
2.86 MBps |
3.81 MBps |
4.77 MBps |
|
20000 |
3.81 MBps |
5.72 MBps |
7.63 MBps |
9.54 MBps |
|
50000 |
9.54 MBps |
14.3 MBps |
19.1 MBps |
23.8 MBps |
|
100000 |
19.1 MBps |
28.6 MBps |
38.1 MBps |
47.7 MBps |
The call detail records (CDRs) that the Avaya Communication Manager sends to the collector are 155 bytes per call. Only one CDR is sent for each call, containing information for both directions of call data flow. CDR-related traffic is further reduced when you install the UC Monitor collector near the Communication Manager.
|
Copyright © 2013 CA.
All rights reserved.
|
|