User's Manual Part 2

Nomad User’s Manual Chapter 10 – Call Performance Configuration Options
Copyright © Spirent Communications, Inc. 2013 135
10 Call Performance Configuration Options
Nomad provides various configuration options for call performance testing. These options include:
Mobile Originated Testing
Mobile Terminated Testing
Mobile-to-Mobile Testing
This section contains detailed instructions for each call performance configuration option.
10.1 Mobile Originated Testing
In a Mobile Originated test, the mobile test device makes calls to the Call Server for call control
testing. To perform Mobile Originated call performance testing:
Set the volume of the test handset to the maximum volume for optimal Audio Verification
results.
Determine which channel the test will be conducted on. All call performance testing
operates via Bluetooth connection.
On the Nomad Test Setup screen, configure that channel as a Mobile Originated task with
the following settings in the Call Campaign dialog:
o Dial/Answer Method: This field will only be visible to customers who have
purchased the ability to control devices via a tethered connection. This drop-down
allows those customers to choose between controlling via the Bluetooth connection,
or the tethered connection.
o Phone Number Settings: Enter the Number to call as provided by Spirent and the
Number calling from.
o Call Initiation Mode:
Synchronous Testing – Calls start simultaneously on all devices regardless
of call outcomes. For example, if one device drops a call, it will remain idle
until the next time all mobiles are scheduled to start a new call.
Asynchronous Testing – Each device follows its own call sequence without
regard to other device progress. In this mode, if one device drops a call, it
will wait for the specified time and then start a new call, even as the other
devices continue their first call.
o Access Timeout – A call attempt that has not connected within this amount of time
will be classified as an Access Timeout event.
o Duration – The length of each call in the test sequence.
In a Synchronous campaign, this refers to the total attempt duration
including access time and connected time.
In an Asynchronous campaign, this refers to the connected time only.
o Wait Time – The amount of idle time between the end of one call in the sequence
and the start of the next call.
o Attempts – The number of calls to attempt in this task sequence.