Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 199)

Common Configuration

# P0602477 Ver: 3.1.11 Page 199

Phone Line Behavior During Simulation

The call simulation functions are designed to exercise all normal higher-level software

paths in the system (above the most basic hardware interface functions). No physical

phone line connections or actual DTMF tones need be present. While a call

simulation script file is executing, the phone line software does not alter the line’s

on-hook or off-hook state (e.g., to answer a simulated call or to execute a busy

command), and performs only the associated software state changes and messaging

functions (e.g., the voice path to the line is active). All lines undergoing call

simulation should be placed in a busy state prior to starting the call simulation.

Call Simulator Conditions and Usage

The system software and the applications are unable to distinguish call simulator

traffic from real telephone traffic. However, all call simulator driven traffic has some

regular pattern as configured in the script file(s). For the most part, internal conditions

occurring while the call simulator is running are indistinguishable from real

conditions, except for the intensity and constancy of the workload.

It is possible to drive the system too hard by using unrealistic call lengths or by

executing application paths that normally account for only a small percentage of the

total calls at any time. Be aware of the call scenarios that have been created and used

while observing and/or extrapolating call simulator results. Use only realistic call

patterns and leave a few phone lines for actual calls (to be made from within the

testing environment) to observe the overall system response and behavior from a real

caller’s viewpoint.

1 2 ... 194 195 196 197 198 199 200 201 202 203 204 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 199