User's Manual Part 1

Nomad User’s Manual Chapter 4 – Specifying Nomad Settings

4.3.2 Logging Session Auto-Stop

Spirent provides the ability to automatically stop the entire logging session if the number of

consecutive Bluetooth connection errors on any test device exceeds the provided threshold. This

check ensures that a user does not conduct an extended test using a non-functioning device,

possibly invalidating results for the entire test array. To configure Logging Session Auto-Stop:

 Choose whether to enable this functionality (recommended).

 Set the Threshold for the number of consecutive Bluetooth errors which constitutes

stopping a test.

Figure 4-6 - Logging Session Auto-Stop Area

4.3.3 Audio Verification

Nomad provides Audio Verification data for Call Performance tasks by determining the correlation

value of audio sent to the Call Server from the test mobile and audio echoed back. The correlation

coefficient is a threshold at which audio will be considered matching. This number should remain

unchanged, unless directed by Spirent.

Figure 4-7 - Audio Verification Area

4.3.4 CDR Lookup

In the CDR Lookup area, select the part of the dialed number (from the viewpoint of the call server

that Nomad is calling) that should be excluded when Nomad contacts the call server to retrieve Call

Detail Records.

This is an advanced setting that can be used when the Call Performance testing is performed in one

country and the call server resides in another – the Caller ID of the device that is calling the call

server can under certain circumstances look different than the number that was dialed.

The CDR Lookup setting can be used to indicate that prefixes (international dialing prefixes or

similar) should be excluded when matching telephone numbers for uplink score retrieval.