Authentication Troubleshooting

Last updated: June 20, 2006

This section is only applicable to the lab application and to a test application with the required feature license.

Possible Setup Issues

When a mobile station performs the global challenge at the first time since the test set is powered On or fully preset, the Call History (COUNT) result fails because the Expected Call History (COUNT) doesn't equal to the Received Call History (COUNT) due to the expected COUNT value unavailable. The expected COUNT value is available and set to the same value of received COUNT after the first authentication. See Global Challenge Information for details.
It is possible that the test set and the mobile station use the different RAND values in a Global Challenge since the mobile station may send access channel messages with specified RANDC before the test set sends an Access Parameter Message or ANSI-41 RAND Message . In this case, the Global Challenge fails. To avoid this issue, it is recommended to implement SSD Update first.
The authentication result does not impact the normal call processing (registration, call connection). For example, a call can be connected even if the Global Challenge or Unique Challenge authentication fails. Please note that this behavior is different from the standard, but provides more flexibility to perform other MS tests in the event that the authentication test fails.