When you make a RADIUS request to SMS2 and the user is using CloudSMS, the token will be sent to the user prior to the RADIUS request returning. If your DNS, HTTPS connections, or network causes a delay then the RADIUS request is likely to timeout.
When a RADIUS request timeout occurs the device trying to use RADIUS normally retries 2-3 times, and this causes not only duplicate token requests but the user becomes confused as many tokens arrive at the same time on their phone and they don’t know which to use. This guide talks about how this problem can be resolved.

1. Increase the minimum time between RADIUS requests (per user).

“MinTimeBetweenRadiusRequestsPerUser” sets the minimum amount of time that should normally pass between unique RADIUS requests for a single user. During this time period additional text / SMS messages will not be sent to the user, the “State” value returned by RADIUS for challenge response will remain the same, and subsequent authentication requests will be assumed to be the same request.
Login failures override this value. If during the minimum time period specified above a user authenticates using incorrect details the next authentication request will be treated as a unique request.
You should increase this value until the problem stops. You should also investigate your network for the source of the delay – usually slow DNS lookups and the text message provider having gone from the cache or something delaying the https connection to the provider.

2. Restart AuthEngine after changing this value.

3. Restart NPS / IAS