Collapse AllExpand All

7.2.2. User Interface Previous topic Parent topic Child topic Next topic

Starting and stopping measurement:

The measurement is started/stopped via the AMO DEFTM.
Additional records for the call traffic measurement are only created when the measurement has been started, i.e. when the tag is set. In all other cases, only normal "charging relevant" tickets are created.

Filter function on the basis of the call traffic measurement table:

A list of the objects to be measured can be defined ("ALL" is likewise possible, and results in the entire traffic being recorded).
When call traffic measurement is started, only records with a relationship to objects in the call traffic measurement table are generated. In this check, the fields for calling party (i.e. FTBL-field CALLIPTY), connected party (or called party if connected party is not available) (DESTPTY­ field in FTBL), TRUNK number and PARTNER TRUNK number are compared with the entries in the call traffic measurement table. If at least one of these objects exists in the call traffic measurement table, the record is labelled as "relevant for call traffic measurement" (in the "Record Type" field).
A distinction is made between the following cases:
  • Normal stations (likewise secretary and executive) are checked against the station list.
  • Attendant console and night service are checked against the AC list. Furthermore, the attendant console group is checked against the entries in the attendant console group table.
  • Trunk and partner trunk are compared with the trunk object list. Furthermore, the trunk group and partner trunk group are compared with the entries in the trunk group list.
  • If a connection to a hunt group is involved, the DESTPTY is also compared with the hunt group object list. Furthermore, the head number is determined and likewise compared.

Record type:

Every ticket contains a field with information on whether this record is relevant for charging and / or for traffic measurement.

SWU / ADP load:

If the SWU / ADP load (average processor load of at least 10 seconds) is to be measured, a load ticket is generated every 10 seconds. In this case, the record type is likewise set to "traffic measurement relevant".

Activities of the attendant console:

If
  • the attendant activates / deactivates night service,
  • the attendant removes / inserts the jack,
  • AC-WIN stops / starts operation - with the following cases covered in this context:
    • the AC-WIN program is started / stopped,
    • the AC-WIN PC is activated / deactivated,
    • the attendant console is blocked / deblocked through an AMO command,
    An activity ticket is generated. In this case, the RECORD TYPE is likewise set to ASC "traffic measurement relevant".

Queuing time for hunting groups:

The time a connection waits - in the queue of a hunting group - is measured.