If your IllyVoIP Windows app misses an incoming-call alert, first establish whether the call reaches the app at all. Routing, desktop notifications and ringtone audio are separate checks. A notification setting cannot fix a number that is routed to another SIP identity.
This walkthrough follows the Windows app behavior in the delivered 1.0.44, build 270 baseline. Android release numbers do not establish a Windows update. Install the Windows app through the official IllyVoIP download link and check your own installed version.
1. Keep a receiving session available
- Open IllyVoIP, sign in to the intended account and let the calling screen finish connecting.
- Keep the app running and the computer awake on a working network. Do not use a closed application or a sleeping laptop as the first test condition.
- Check that the incoming IllyVoIP number is active and its saved route reaches the intended account or SIP identity.
- If a queue or team workflow is involved, confirm the intended user is eligible to receive its calls.
Do not switch between several accounts or calling devices during the test. Record which endpoint you expect to ring. A recent successful outgoing call is useful context, but it does not prove the purchased number’s incoming destination is correct.
2. Test a call with the app visible
- Arrange a short test from another device to the active IllyVoIP number.
- Keep the Windows calling screen visible and observe whether it shows the incoming call.
- Answer the current call using the available controls, check two-way audio, then end it.
- Record the time and call reference if available. Review normal charges before conducting tests.
If the app never shows the call, investigate readiness and routing before Windows banner preferences. Foreground call presentation can differ from background notifications, so an absent extra desktop banner while the app is already visible is not, by itself, evidence of a missed incoming call.
3. Review Windows notification settings
In Windows 11, open Settings → System → Notifications. Check that notifications are enabled and inspect IllyVoIP’s app entry when present. Review Do not disturb, its automatic conditions and priority-app settings. Microsoft’s reference explains these controls; the exact available options depend on your Windows version and policy.
If the app entry is missing, open the installed app and complete a normal signed-in session before rechecking. On an organization-managed computer, ask the administrator about notification policies instead of changing unrelated security settings.
4. Repeat with the app minimized
- Leave IllyVoIP running, minimize its window and keep the computer awake.
- Repeat the agreed incoming call. Look for its current incoming-call presentation and listen for ringing.
- Where an incoming banner offers Answer or Decline, use it only for that active call and check the app’s resulting state.
- If you find an old notification after the caller has hung up, reopen the app and check call history rather than assuming the old action can answer a new call.
The Windows incoming notification deliberately uses a general incoming-call description rather than exposing the caller’s identity in the banner. Inspect the app for current call details. A generic notification is not evidence that caller identification has been lost in the call itself.
5. Check ringtone and conversation audio separately
A visible notification does not prove audible ringing. The Windows incoming toast does not supply its own notification sound; check the app’s ringtone output, Windows sound volume and the actual headset or speakers. Conversely, hearing ringing without a banner points you toward presentation settings rather than a failed incoming route.
If the call answers but the other person cannot hear you, inspect microphone privacy access, selected input and mute. That is a different problem from a missing banner. Re-test after one deliberate change and keep the comparison simple.
Send Support the exact failing condition
Report the Windows and app versions, incoming-number route type, whether the app was visible or minimized, whether the computer was awake, and whether the failure was call arrival, banner, ringing or microphone audio. Include the time and call reference. A foreground result does not certify locked-screen, sleep, restart or every managed-desktop condition.
Related guides
- Set up the IllyVoIP mobile and Windows apps
- Check the destination when your IllyVoIP number does not ring
- Test your connection to IllyVoIP
- How to contact Support and request test credit
Reference
Current instructions and technical reference: Microsoft: Windows notifications and Do not disturb.
Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.