When IllyVoIP app sign-in opens a browser that already has an IllyVoIP session, you may see a message asking whether to keep that account or sign out and continue. This is a browser-session choice, not an account merge or a request to unlink Google or GitHub.
These steps follow the Android app in version 1.0.46, build 272. Use your own account and the permissions assigned to it; other installed releases can have different controls.
1. Read the account-switch message
The page explains that this browser is already signed into an IllyVoIP account. In an app sign-in flow, it asks you to sign out here to continue signing in or creating an account in the app. Check that you started the flow yourself and that the page belongs to the official Portal before making a choice.
- Decide which IllyVoIP account you intend to use in the app.
- Consider whether the existing browser session is still needed for work. Signing out there can interrupt that browser workflow.
- If you are unsure which account the browser currently uses, choose to keep it and inspect its account details before starting another login attempt.
2. Keep the current browser account when appropriate
Choose Keep current account if you do not want to sign out of the existing Portal session. That action returns to the current account’s dashboard. It does not mean a different app sign-in has completed, and it does not silently switch the current account to another provider identity.
Return to the app and inspect its actual sign-in state. If the original attempt has expired or was abandoned, begin a fresh deliberate attempt when you know which account to use. Do not repeatedly press the old browser Back button hoping it will select a different account.
3. Sign out and continue when you intend to switch
- Choose Sign out and continue with Google or Sign out and continue with GitHub, matching the provider you selected.
- Allow the browser flow to continue. This signs out the existing IllyVoIP Portal browser session.
- At the provider’s own sign-in or account-selection page, choose the intended identity. A provider already signed into another identity may not initially show the account you expect.
- Complete any IllyVoIP verification or account steps requested, then follow the offered return to the app.
Use your own provider credentials and verification method. The switch page does not reset the IllyVoIP password, change the account email, merge account balances or disconnect a previously linked provider. Those are separate account operations.
4. Verify the account after returning to the app
- Wait for the app to finish the return and read its resulting screen.
- Check the displayed account identity before opening customer records or using paid services.
- If the wrong account appears, stop there and use the normal sign-out and intended sign-in flow. Do not attempt to fix it by changing SIP credentials or buying another service.
- If the browser says the session or request expired, return to the app and start a fresh login rather than reusing a stale return link.
An open provider page is not proof that the app received its completed sign-in. Likewise, returning to the app without an error is not enough if the displayed account is wrong. Treat provider authentication, IllyVoIP account selection and the app return as separate checkpoints.
If the flow does not finish
Record whether the problem occurred at the existing-account message, the provider, IllyVoIP verification or the return to the app. Include the app version, browser and approximate time for Support. Never share the return URL, verification code, browser cookies or provider password. Avoid clearing all browser data as a first step; it can sign you out of unrelated services without resolving the intended account choice.
Related guides
- Set up the IllyVoIP mobile and Windows apps
- Manage two-step verification
- Add or change your login email and phone
- How to contact Support and request test credit
Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.