Change country and prefix restrictions in the IllyVoIP app

Edit channel-specific fraud controls in the IllyVoIP app, distinguish allowlists from blocklists and reconcile revision conflicts before saving again.

Use the app’s Fraud Control screen to review outbound calls, SMS and inbound caller restrictions separately. Start from a successfully loaded current policy. A failed load is not an empty policy, and changing one channel does not update the others automatically.

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. Load and record the current policy

  1. Open Fraud Control and wait for the policy and country choices to load.
  2. Read any unavailable-state or administrator-restriction notice.
  3. Choose the specific channel you intend to change.
  4. Keep a private note of the existing settings and the small change you need.

Avoid broad disable-all changes to diagnose one failed destination. Identify the channel, destination or caller prefix and the relevant reported reason first. The same country selection can mean the opposite thing under a different policy mode.

2. Choose the country mode deliberately

Block selected countries adds those countries to the channel’s blocklist. Allow only selected countries limits the channel to its selected countries, subject to all other applicable restrictions. Review the mode and selections together.

  1. Open the country picker for the intended channel.
  2. Select the required countries and read any locked administrator entries.
  3. Save the picker selection back to the editor.
  4. Review the resulting policy before the final screen save.

An empty allowlist permits no countries. An empty blocklist adds no customer-selected country block, while other restrictions still apply. For inbound calls, consider the caller’s country or prefix, not merely the countries of your own purchased phone numbers.

3. Review prefix rules alongside countries

Enter prefixes as digits only, one per line, using the international country code and intended following digits. Do not include a plus sign, spaces or an access prefix such as 00. Check the breadth of each rule before saving.

A nonempty allowed-prefix list adds a further requirement; an empty one removes that additional prefix requirement. A blocked prefix still blocks a matching number, even if it also matches an allowed prefix. An allowed prefix does not override a country or administrator restriction. Use the main fraud-control guide for the full rule semantics.

4. Check the outbound rate ceiling separately

The outbound maximum price per minute is a rate threshold in euros, not a daily budget or maximum total call charge. Review the current sell rate and billing terms when choosing it. Calls at an allowed rate can still accumulate cost over time.

To remove the optional ceiling deliberately, clear the field and save; zero is not the off value. Removing it expands the rates the account may use. Do not remove it simply because a price could not be confirmed or a different rule blocked a call.

5. Save and reconcile conflicts

  1. Review all pending channel changes, prefix lists and the rate field together.
  2. Save once against the loaded policy and wait for the result.
  3. Reopen the screen to verify the current saved values.
  4. If another administrator changed the policy, reload the latest version and compare it with your note before reapplying only the intended edit.

Do not keep resubmitting a stale editor or restore every old field to clear a conflict. Preserve another administrator’s legitimate changes. If the screen cannot obtain a usable current policy, stop editing until that prerequisite is resolved.

6. Check the result without weakening protection

Review relevant Fraud Control activity and match the channel, destination, time and call or message reference. Arrange any required traffic test deliberately with the team. A policy save does not prove every destination works, and a successful call does not show all fraud risks are covered. Send Support a focused sanitized example when the result differs from the saved rules.

Related guides

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