How is an international call routed?
Dialling and routing are related but not identical. E.164 defines the international destination-number structure. The originating provider still has to interpret the caller's access method, check the service, choose interconnection and deliver the call to the network currently responsible for the destination.
1. Dial-string interpretation
The originating device or network interprets + or an international prefix, country code and destination digits. Domestic routing and carrier-selection digits are handled here, not stored as destination identity.
2. Origin service checks
The caller’s provider applies account permissions, tariff rules, fraud controls and support for the destination range before selecting an onward route.
3. International interconnection
One or more carriers or gateways exchange the call towards a network that can reach the destination numbering plan. The visible number does not expose every intermediate carrier.
4. Number-portability resolution
Where the market supports portability, a carrier may consult routing data so a ported number reaches its current serving network rather than only its original allocation holder.
5. Destination-network delivery
The serving network resolves the subscriber or service endpoint and applies its own availability, screening, forwarding and device-registration rules.
Destination digits versus routing instructions
A common data-quality error is to store every digit a caller pressed as though it were part of the phone number. Keep the durable destination separate from origin-specific access, carrier selection and post-connect instructions.
| Layer | Example | Purpose | Where it belongs |
|---|---|---|---|
| International number | + country/service code + remaining E.164 digits | Stable destination identifier within the applicable numbering plan | Normally visible and saved |
| International prefix | 00, 010, 011, 0011 or another origin-specific value | Access to the origin network’s international service | Dial string only |
| Carrier-selection code | Country- and carrier-specific digits | Selects an originating or long-distance carrier where supported | Dial string only |
| Portability routing data | Database result, routing number or equivalent network data | Directs the call to the current serving network | Carrier signalling, not user-facing contact data |
| Extension or IVR choice | Extension, menu digit or post-connect instruction | Routes after the main endpoint answers | Separate from E.164 |
How does number portability change call routing?
Number portability lets a customer keep a telephone number when changing provider under the rules of the relevant market. The visible E.164 number can therefore remain the same while the terminating network changes. This is why a prefix or original number-block allocation is not a reliable statement of the current carrier.
The exact implementation is regional. In the United States, FCC material describes a portability database query that returns a Location Routing Number used to select the appropriate switch for a ported number. Ofcom describes UK portability as a regulated facility and points to separate technical arrangements for geographic, non-geographic and mobile numbers. These examples show the principle; they should not be copied as one universal routing architecture.
What can a portability or carrier lookup establish?
Original allocation
A numbering authority or allocation dataset may associate a number block with its original assignee. Portability means that organisation may no longer serve the subscriber.
Current routing network
An authorised lookup may return the network used for routing at the query time. Store the provider, market, field definition and timestamp.
Ported status
A result may indicate that the number moved from its original allocation. It does not reveal why it moved or who controls it.
Line or service category
Some sources classify geographic, mobile, VoIP or service ranges. Reassignment and provider methodology can limit the result.
Reachability
A carrier identity does not guarantee that the line is active, registered, in coverage, funded or accepting calls.
Identity and consent
Routing data does not prove a person’s identity, control of the number, or consent to receive a call or message.
When is an operator-assisted international call different?
Operator assistance is a service workflow rather than another E.164 number format. A carrier operator may help place a person-to-person, collect, third-party-billed or otherwise assisted call where the provider offers that service. The caller still needs the destination number, but access, billing approval and connection steps are handled under the originating carrier's current rules.
ITU dialling-procedure guidance notes that a blank international prefix can indicate that direct international dialling is unavailable and calls require operator assistance. That does not create one universal operator code. Access numbers, supported destinations, billing arrangements, language and hours can vary by country, carrier, account and device.
1. Contact the originating provider
Use the support channel or operator-access instructions published for the exact account and location.
2. State the requested service
Say whether the call is ordinary assisted, collect, person-to-person or third-party billed; availability is not universal.
3. Supply the complete destination
Provide the country calling code and national significant number without guessing a trunk prefix.
4. Confirm acceptance and price
Before connection, establish who will be billed, whether the other party must accept, and what service charges apply.
Why can a correctly formatted call still fail?
Correct digits solve only the numbering layer. A call can fail because international service is disabled, the origin carrier blocks a destination category, an interconnection route is unavailable, portability data is stale, the destination network rejects the call, the subscriber is unreachable, or screening classifies the traffic as unwanted. VoIP systems add signalling, codec, authentication and trunk-policy failures.
Diagnose in order: confirm the number and country-specific zero rule, confirm account permissions and price, test another known-good destination, record the exact error or announcement, and contact the responsible provider with the time, origin, destination category and observed result. Do not publish a subscriber's full number in a public support request.
Business routing and validation workflow
- Normalize once. Store the parsed E.164 destination separately from raw input, extension and origin dial string.
- Classify with maintained data. Record country or global-service category, possible line type, source version and the decision date.
- Query portability only when useful. Use an authorised source when live routing or channel selection justifies the privacy, cost and freshness burden.
- Keep routing evidence separate. Store original allocation and current-network results in distinct timestamped fields rather than overwriting the phone number.
- Observe the transaction. Delivery receipts, call outcomes or challenges are separate evidence layers and must not be converted into permanent ownership or consent claims.
Separate formatting, routing and live validation
Build the destination with the E.164 guide, label lookup evidence with the validation guide, and use the troubleshooting flow for a real failed call.
Standards and regulator sources
- ITU-T E.164: The international public telecommunication numbering planInternational Telecommunication Union. Verified 2026-07-19.
- Dialling procedures: trunk prefixes, international prefixes and country codesInternational Telecommunication Union. Verified 2026-08-29.
- ITU-T E.140: Operator-assisted telephone serviceInternational Telecommunication Union. Verified 2026-08-29.
- Number portabilityOfcom. Verified 2026-08-29.
- Nationwide Number Portability: background on routing mechanismsFederal Communications Commission. Verified 2026-08-29.
See our editorial and sourcing methodology.