User's Manual Part 2
Nomad User’s Manual Appendix B – Call Performance Events
Copyright © Spirent Communications, Inc. 2013 146
Appendix B – Call Performance Events
Call Outcome Events
Call Outcome
Definition
No Service
There was no service available when the call was attempted.
Failed Attempt
A Mobile Originated Call was placed and an outgoing call was
established followed by the phone’s return to the call placement
state.
Voicemail
A Mobile Terminated call was placed and the nonstandard
voicemail response was received from the mobile.
Busy
A Mobile Terminated call was placed and the nonstandard busy
response was received from the mobile. A busy response
typically results when the network is unable to place the call.
Fast Busy
A Mobile Terminated call was placed and the nonstandard fast
busy response was received from the mobile. Both the fast busy
response and the no capacity response typically indicate an issue
with the communication path to the server.
No Capacity
A Mobile Terminated call was placed and the nonstandard no
capacity response was received from the mobile. Both the fast
busy response and the no capacity response typically indicate an
issue with the communication path to the server.
Access Timeout
Mobile Originated Call – A call was placed but no state change
occurred before the Access Timeout time.
Mobile Terminated Call – The connection did not take place before
the Access Time.
Drop
The call was ended before the expected duration had elapsed.
Physical Link Error
The Bluetooth connection between the test mobile and the
Nomad hardware unit was not active at the time a call was
supposed to occur.
Logical Device Error
The test mobile failed to respond properly to a command issued
by Nomad via the Bluetooth connection.
BC Error (BlueCore Error)
The Bluetooth module was not in a nominal state at the time a call
was supposed to occur.
User Terminated
The Stop button on the handset was pressed during a call.
Call Succeeded
Any call that lasts the expected duration is considered a
successful call.