
A benchmark test may be used either for comparison (e.g., comparing the performance of two products), or for
prediction (e.g., the configuration specified for a benchmark test is similar enough to a service provider’s requirements
that the result of the test can be used as an estimate of the performance of their deployed system).
Pre-written scripts provided for ETSI TS 186 025-2 Use Cases:
pre-written scripts:
- ISDN-ISDN
- ISDN-PSTN
- PSTN-ISDN
- PSTN-PSTN
comming soon:
- SIP-ISDN
- SIP-PSTN
- PSTN-SIP
- ISDN-SIP
- SIP-SIP
In order to accomplish these goals, a suite of benchmark tests must cover a range of scenarios that are representative of
the real world. Given the early nature of the IMS/PES deployments, the data required to construct these scenarios is still
in the process of being collected. For that reason, the benchmark test described here is more useful for prediction than
for comparison.
Call Profiler Traffic Patterns
- Saw Tooth - ramps up to a peak number of calls and then ramps down from peak
- Blast - all calls go off-hook simultaneously, are connected for a specified time, and then disconnected
- Ramp - gradually increases connected calls to a specified number and then maintains those number of calls
- Steady Call rate - delivers a fixed, regulated call rate into the system under test
- Rolling Blast - a defined set of channels go off-hook at once, and the pattern is repeated for all assigned channels
- Poisson Distribution - defines call arrival rate by a statistical distribution