I cannot be called, outgoing calls continue to work.
A telephony fault can have various causes. It therefore makes sense to eliminate sources of error step by step. If you can already say that the fault only affects incoming connections, you have already achieved a great deal.
Now check the following aspects:
Note for new customers:
If you have a new connection or a number that has just been ported, it may take up to three days before you can be reached from all networks.
Possible sources of error if you cannot be reached inbound
Software problems
Data connections are controlled by countless computers. And everyone has probably experienced a computer crash. This can also happen in your VoIP hardware, router or network infrastructure.
Especially if your device has worked before, a very simple trick usually helps: restart your router and other hardware.
Incorrect configuration
First check whether you have entered the correct registrar in your VoIP-enabled device. You can find this in the following table.
As a rule, you can also see in the user interfaces of the devices whether a phone number has been successfully registered or not.
Further details can be found in our current configuration instructions.
| Product | Registrar |
|---|---|
| SIP Trunk / VoIP | voip.easybell.de |
| Cloud Telefonanlage | pbx.easybell.de |
The router or telephone system does not forward the call to the telephone
Check whether the telephone number is assigned to a telephone in your router or telephone system.
DECT connection is disrupted
Make sure that DECT telephones are not set up too close to the router, as DECT and WLAN can interfere with each other.
Problems with branded routers, cable connections and natting
It can happen that network operators preconfigure hardware in such a way that the SIP port 5060 in the router is already occupied.
If you are using VoIP end devices behind a VoIP-capable router, please try to use our alternative port 5064 if your device allows this.
