by PBX.lu Editorial on November 09, 2026
Calls to some numbers fail on VoIP with no error message: causes and fixes
When a VoIP phone reaches most numbers but fails on a few, showing nothing or playing a short busy tone, a network on the route has usually refused the call during set-up. The refusal carries a reason code that most phones never display. In Luxembourg, Belgium and Germany, the usual causes are a wrongly formatted number, a caller ID the destination country rejects from abroad, a recently ported number, a barred range or a codec mismatch.
At a glance
- Belgian operators must block calls from abroad that show a Belgian landline number (since September 2024).
- Germany hides German numbers on calls from abroad (since December 2022), so recipients who reject anonymous calls never see them.
- The fix starts with one failed call and its SIP response code.
In this article Why a failed VoIP call shows no error · Is the number in the format the network expects? · Is the receiving country refusing your caller ID? · Ported, barred and service numbers · Codec mismatches and router settings · What to send your provider when a call fails
Why a failed VoIP call shows no error
Your phone system sends each call as a request to your provider, which passes it from network to network until the destination accepts or refuses it. A refusal comes back as a SIP response code, defined in the IETF standard RFC 3261. Phones rarely show it; the code sits in your provider's logs.
SIP response code A three-digit reply that explains why a call was not connected. Typical ones on failed calls: 403 Forbidden (refused by a rule, such as a barred range or rejected caller ID), 404 Not Found (number unknown on that network), 484 Address Incomplete (digits missing), 488 Not Acceptable Here (no shared audio format) and 503 Service Unavailable (route down). Treat a code as a lead, not proof.
First, compare. If a number fails from your office phone but works from a mobile, the cause sits with your provider's route or your settings. If calls connect but sound poor, use the call quality checklist instead.
Is the number in the format the network expects?
Every number should leave your phone system in international format, called E.164: a plus sign, the country code, then the national number without its trunk prefix.
Belgium and Germany use a leading 0 for national calls, which disappears after the country code: Brussels 02 becomes +32 2, Berlin 030 becomes +49 30. Luxembourg has no trunk prefix, so a Luxembourg number never starts with 0. The same applies to the caller ID you send: Belgian rules expect it in full international format.
Luxembourg numbers also vary in length, because many companies add extension digits to a short base number. In August 2025, the numbering data provider e164 reported that routing systems following the published plan rejected some valid Luxembourg numbers of up to 13 digits, country code included, which the ILR had allowed as unpublished exceptions. If a long Luxembourg number fails, ask your provider whether a length check stopped it. The guide to keeping your Luxembourg numbers when moving to Teams Phone explains base numbers and extensions.
Your own dial rules can also damage numbers, for example by adding a 0 or treating a short Luxembourg number as an internal extension. Check the number in the phone system's call log, not the one the user typed.
Is the receiving country refusing your caller ID?
This cause catches cross-border businesses most often. All three countries act against calls from abroad that show a domestic number, a trick fraudsters use to look local. A cloud phone system that sends calls from another country can be caught too.
Belgium is strictest. Under the Royal Decree of 12 May 2024, the first Belgian operator to receive a call from abroad must block it if the caller ID is a Belgian landline, non-geographic or short number. This applies since 1 September 2024, and since 1 December 2024 for Belgian mobiles unless the caller is roaming. The check also covers forwarding fields. Exceptions for nomadic VoIP and cloud contact centres require written agreements between operators. In a communication of 26 June 2026, the regulator BIPT added that a Belgium-to-Belgium call routed through a server abroad counts as national only if the originating operator keeps it on dedicated national circuits under its full control.
Germany lets the call through but hides the number. Since 1 December 2022, German operators must suppress German caller IDs on calls from foreign networks, except mobiles roaming abroad, and recipients must be able to reject anonymous calls free of charge. If the person you call does, your call fails without a trace.
Luxembourg leaves it to operators. ILR regulation ILR/T24/1 of 8 January 2024 allows them to block calls from abroad showing a Luxembourg geographic number when they have enough evidence of fraud. In March 2026, the government told parliament that the ILR is revising the regulation.
To test this cause, make the same call once with your Luxembourg number and once with your Belgian or German number. If only one fails, the caller ID is the problem, and your provider needs a compliant route for that number.
Ported, barred and service numbers
Ported numbers. When a number moves operator, every network must learn its new route. Luxembourg's fixed operators share a central reference database for ported numbers under ILR regulation 16/204/ILR. A network with outdated data can still send calls to the old operator, which refuses them. If one recently moved number fails only from your provider, send it the number and the port date. The number porting guide explains the process.
Barred ranges. Many providers and phone systems block premium-rate numbers, such as Belgian 090x and German 0900, and some international destinations by default to limit toll fraud. Check the user's call permissions, then ask your provider which ranges are barred on your account.
Service numbers. Freephone and other non-geographic numbers, such as Belgian 0800 or 078 numbers, often work only inside their own country, because EU rules let the owner limit access from other areas. Look for a geographic alternative on the company's website.
Codec mismatches and router settings
A number that always fails with code 488 usually means no shared codec, the format that encodes the audio. It typically happens when a phone offers only wideband codecs such as G.722 or Opus while a network on the route expects G.711, the common format towards traditional phone networks. Allowing G.711 normally fixes it.
Router settings rarely affect only some numbers, but a feature called SIP ALG can rewrite call requests and break calls unpredictably. The call quality checklist explains how to switch it off.
What to send your provider when a call fails
Your provider can only fix a silent failure it can find in its logs. Open one ticket per pattern, with at least one example.
Copy this checklist
- Date and exact time of one failed call, with time zone
- Extension or user that placed the call
- Number dialled, as shown in the phone system's call log
- Caller ID shown on the call, and its country
- What the caller heard: silence, busy tone, an announcement or nothing
- Whether the number works from a mobile or with another caller ID
- Whether the number was ported recently, if known
- Request: "Please send the SIP response code, the network that returned it, and the route used for this destination."
A provider that can name the code and the network that sent it can usually say in one reply whether the fix is a dial rule, a caller ID setting or a route. If it cannot find the call at all, remember that when you compare providers.
Want the wider picture? Explore the features guide or compare providers active in Luxembourg and the Greater Region.
📅 Ready to explore Cloud PBX for your business?
A short call can tell you which setup fits the way you work, whether that is an app, FMC or simple forwarding.
Latest Insights (sidebar)
TLDR: Calls to some numbers fail on VoIP with no error message: causes and fixes
- Belgium blocks calls from abroad showing Belgian numbers; Germany hides foreign caller IDs, causing silent failures.
- Always check the SIP response code in your provider's logs to identify the exact cause.
- Send your provider the failed call time, dialled number, caller ID and what you heard.
Updated on 2026-11-06