Set up an authenticator and save recovery codes in the IllyVoIP app

Enroll an authenticator in the IllyVoIP app, verify a current code, save recovery codes and complete the required new sign-in.

Authenticator enrollment changes your IllyVoIP account sign-in security. Complete the setup, save the recovery codes privately and sign in again with the new method. This is separate from App Lock on a device and from a SIP-line password.

These instructions follow the Android app version 1.0.46, build 272. Available actions depend on your account permissions and current service state. Other installed versions may present different controls.

1. Prepare private recovery storage

  1. Use your own trusted device and a compatible authenticator application.
  2. Have access to the account’s current password and existing recovery arrangements.
  3. Choose a secure place for recovery codes that remains available if this phone is lost.
  4. Avoid screen sharing or public screenshots during enrollment.

Do not start setup on another person’s authenticator just because your own device is unavailable. The setup secret lets an authenticator generate future codes and must be protected like a credential.

2. Start two-step verification setup

Open the account’s two-step verification screen and choose authenticator setup. The app asks you to confirm the current password before creating a new setup secret and QR code. Cancel if this is not the account or security change you intended.

If password confirmation fails, resolve the account-access problem first. Do not repeatedly start new enrollment sessions or assume that merely seeing a QR code means the authenticator method is enabled.

3. Add the setup to your authenticator

  1. Use the displayed QR code when your authenticator can scan it securely.
  2. On the same device, use the offered copy-secret control and your authenticator’s manual-entry workflow when needed.
  3. Check the account label in the authenticator so you can find the correct entry later.
  4. Keep the secret out of messages, photos and shared clipboard history.

The reviewed app displays the QR code and manual secret. It does not require an automatic deep-link import to work. Follow your authenticator’s actual manual-entry controls rather than assuming every app uses the same labels.

4. Confirm a current six-digit code

Return to IllyVoIP and enter the current code for the new authenticator entry. Submit once and wait for the result. If the code is rejected, check that it belongs to the correct entry and is still current; also check the device’s time synchronization. Do not send a recovery code in the enrollment-code field.

5. Save the recovery codes before acknowledging

  1. When the recovery-code dialog appears, copy the complete set into your approved private storage.
  2. Verify that the saved copy is readable and associated with the correct account.
  3. Acknowledge that you saved the codes only after checking that copy.
  4. Follow any missing-code warning instead of assuming a new set was created.

The app deliberately keeps this handoff open until acknowledgement. Do not rely on being able to reopen the same full list later. Existing preserved recovery material and a newly issued set are different outcomes; follow the screen’s explanation and retain only the currently valid material.

6. Sign in again and verify the enabled state

After enrollment and the recovery handoff, the app signs you out so you can sign in using the updated security method. Complete that sign-in and reopen account security to confirm the authenticator is enabled. A successful enrollment response alone does not prove you retained usable recovery access.

If you lose access, use the documented recovery path. Support should not need your setup secret, current authenticator code or full recovery-code list in an ordinary ticket. Record the stage where setup failed and the sanitized message instead.

Related guides

Reviewed 13 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.