However, this security measure doesn’t just block attackers; it can also occasionally block misconfigured devices or devices with invalid login credentials. Customers cannot unblock their own IP addresses. Once the issue has been resolved, the IP address can be unblocked by easybell Support. Please contact our customer service team for assistance.

To help you identify the cause, we have compiled a list of the most common reasons for an IP block. This allows you to check where the failed login attempts are coming from and resolve the issue yourself before contacting our support team to have the block removed.

1. Outdated login credentials

It is common for phones to be brought back online that were previously associated with an account that no longer exists or whose password has been changed. This can happen quickly if, for example, you delete a virtual extension in the customer portal but it remains stored on end devices or in a softphone. If such devices are not reset or at least have their login credentials updated, their registration attempts will eventually result in a lockout.

What you can do: Depending on when the lockout occurred, consider which devices (including computers and laptops with softphones!) you most recently put back into service. Start there by checking the login credentials and correcting them if necessary.

2. Typing errors in the softphone

Whether in the username or password, typos in login credentials are a common cause of IP bans. Softphones are particularly prone to this issue, but hardware phones are not exempt either.

What you can do: Re-enter the login credentials on your devices. Start with the devices that were most recently put into service.

3. Test devices will not be reset.

Phones are often configured in advance for testing. When the production connection is set up, the test accounts are deleted in the customer portal, but the devices and softphones are not reset. These devices then attempt to register using the no-longer-existing credentials, triggering a lockout.

What you can do: Please check the login credentials on all devices you use for telephony. Start by checking the devices that were activated shortly before the lockout. For larger installations, it may help to take most devices offline and bring them back online one by one to pinpoint the source of the issue.

4. Incorrect installation of telephone systems

If incoming and outgoing calls are managed by a telephone system that performs a general registration process, particular care must be taken during setup. The complexity of most telephone systems carries a high risk of errors and makes diagnosis difficult. For example, it may be the case that, although the login details are entered correctly and registrations are successful, incorrectly configured call signalling leads to a block.

What you can do: Please check your system configuration and verify that it corresponds exactly to our relevant instructions.

5. Call scripts make too many call attempts

It is not only registrations with invalid data or incorrect call signalling that can lead to an IP ban. In some sectors, calls are initiated by computer programmes, and only once the call has been successfully connected does a human take over the conversation. The result may be that the high number of call attempts is interpreted as an attack and met with an IP ban.

What you can do: Find a reputable business sector or reduce the number and frequency of call attempts. Whatever the reason for an IP being blocked, please always try to identify the cause first

Back

Created on: 12. June 2026