When a FreePBX extension cannot call an international number entered with a plus sign, FreePBX dialing international numbers with plus sign troubleshooting should start with number format and call flow. The plus sign may be valid for users but may not match the outbound route pattern or trunk’s expected format.
This problem does not always indicate a failed SIP trunk. The call may stop before FreePBX selects a route. Alternatively, the route may match but deny the extension, transform the number incorrectly, or send it to a provider that rejects the format.
What the plus sign means in FreePBX
Most international numbers use the E.164 format. In that format, a number begins with a country code and contains digits rather than a local dialing prefix. People often write the same number with a leading plus sign, such as +441234567890.
The plus sign is a presentation character for many users. It does not always function as a literal dialable digit in a PBX. A phone, softphone, endpoint, or dial plan may remove it before sending the call. Another device may pass it unchanged.
FreePBX builds outbound calls through Asterisk dialplan logic. The system evaluates the digits received from the extension, compares them with outbound route patterns, applies any transformations, and chooses a trunk. Therefore, the first question is simple: what string actually reached the PBX?
Use a controlled test. Record the number as entered, the number shown in the phone’s call history, and the number shown in FreePBX or Asterisk logs. Do not assume these values match.
Confirm where normalization should happen
Normalization means converting different user formats into one predictable format. For example, a business may accept +44... from users but send 01144... or 0044... to a carrier. The correct conversion depends on the carrier’s requirements and the organization’s dialing plan.
For FreePBX dialing international numbers with plus sign troubleshooting, choose one clear normalization point. It might be the endpoint, a FreePBX outbound route, a custom dialplan step, or the carrier. Duplicating the same conversion in two places can add digits twice or remove digits unexpectedly.
Compare the supported input formats
- Test a domestic number that normally works.
- Compare the same destination in the organization’s approved international format.
- Try the plus-prefixed version, if policy allows it.
- Record the digits received by FreePBX for each attempt.
These comparisons reveal whether the failure begins at the phone or inside the PBX. A device that sends a literal plus sign may need a dial-plan setting. A device that strips the plus sign may already be compatible with the route.
Keep the change narrow. Do not create a rule that accepts every possible character or number length. Broad matching can route malformed calls, bypass intended controls, or create unexpected toll exposure.
Inspect outbound route patterns carefully
Outbound routes decide which calls can leave FreePBX and which trunk receives them. Their dial patterns must match the number format presented to the PBX. A route designed for digits may not match a literal plus sign.
Review the route’s match pattern and prepend fields. In FreePBX, these settings have separate jobs. The pattern determines whether the route matches. Prepend adds digits before the call reaches the trunk. Prefix removes digits used for access or policy. These fields do not automatically convert every international format.
For example, a route might match a defined international prefix and prepend a carrier access code. That does not mean it will match +44.... Another route might expect a leading access digit, such as 9, before the international number.
Use a specific pattern strategy
- Record the user-facing format.
- Identify the format FreePBX receives.
- Confirm the format the carrier requires.
- Create the smallest pattern that covers approved destinations.
- Place more specific routes before broader alternatives.
- Test a permitted country and a deliberately restricted country.
Never solve a single plus-sign problem with an unrestricted catch-all route. A rule that matches almost anything can hide configuration errors and send unintended numbers to an expensive destination.
For background on dialplan and trunk behavior, consult the official Asterisk documentation. FreePBX provides a management interface, while Asterisk executes the underlying call logic.
Check route and trunk permissions
A matching pattern is only one part of authorization. FreePBX can restrict outbound routes by extension, extension group, or other administrative policy. An extension may place domestic calls but lack permission for international destinations.
Start with the extension that fails. Compare its permissions with a test extension that can place an approved international call. Check the assigned outbound route, class of service, and any time condition or user restriction involved in the path.
Next, review the trunk selected by the route. The trunk may require a specific number format, caller ID, authentication identity, or destination permission. Some providers block international traffic until the account receives approval. Others allow only selected countries or number ranges.
A provider rejection may appear as a busy signal, an announcement, a fast failure, or a SIP response. Capture the response instead of relying on the user’s description alone. The exact response helps separate a route mismatch from provider policy.
When comparing results, use the same destination and the same time window. Carrier policy, fraud controls, and account balances can change independently of FreePBX settings.
Trace the call from the extension to the carrier
Good FreePBX dialing international numbers with plus sign troubleshooting uses evidence at each boundary. The useful boundaries are the endpoint, FreePBX route selection, number transformation, trunk handoff, and carrier response.
A safe diagnostic sequence
- Confirm the extension is registered and can place a known working call.
- Capture the exact digits sent by the endpoint.
- Check whether an outbound route matched.
- Verify the selected trunk and any prepend or prefix action.
- Review the outbound call log or Asterisk console evidence.
- Check the SIP response from the provider.
- Repeat with an approved international number in the documented format.
Use a temporary test window and protect customer data in shared logs. Avoid posting full phone numbers, authentication details, or SIP credentials in tickets or public channels.
If you have command-line access, an administrator may use Asterisk logging and SIP tracing tools. The correct command depends on the Asterisk version, channel driver, and operational policy. Enable only the needed level, then disable verbose tracing after the test.
When the route matches but the provider gives no response, investigate trunk connectivity or signaling. A clear provider rejection usually points toward carrier policy, number format, caller ID, or account permissions. Failure before trunk activity points back to FreePBX routing or authorization.
Plan least-cost routing without weakening controls
Least-cost routing chooses among trunks based on destination, availability, or price. It can reduce calling costs, but it also increases the importance of precise number classification.
Build routing from approved destination groups. For example, separate domestic, international, premium, mobile, and restricted ranges where those categories apply. Assign each group only to trunks that the business has reviewed.
Use a primary trunk and a documented fallback only when both trunks are authorized for the same destinations. A fallback should not silently turn a blocked international call into an expensive call through another provider.
Review these controls before enabling automatic fallback:
- Which countries and number ranges are allowed?
- Which extensions may use each route?
- What happens when the preferred trunk rejects the call?
- Does the fallback preserve the required number format?
- Can administrators identify the route used after the call?
- Are spending alerts and carrier limits available?
Normalize first, classify second, and select the trunk third. That order makes the result easier to audit. It also prevents a route from making pricing decisions on inconsistent formats.
Common fixes that create new problems
Several quick fixes appear attractive but deserve caution. Adding a plus sign to every route pattern may not reflect how the endpoint sends digits. Changing the trunk to accept any format may shift the failure to the carrier.
Another risky approach is adding a catch-all route above existing routes. That can capture emergency, service, or restricted numbers. It may also bypass a carefully designed least-cost plan.
Changing several settings at once makes the result difficult to explain. Instead, record the current configuration, change one layer, and test one known destination. Keep a rollback note for every modification.
Also avoid treating a successful internal call as proof that outbound routing works. Internal extensions use a different dialplan path. A phone can be registered and still lack the route or permission required for external dialing. If one extension behaves differently, this guide to calls failing from one extension provides a useful comparison process.
Build a durable international dialing policy
Once the call works, document the intended format. State what users should dial, what FreePBX receives, and what each trunk expects. Include examples without publishing sensitive customer numbers.
Then record route ownership, permitted destinations, fallback behavior, and testing steps. Review the policy after carrier changes, number migrations, endpoint replacements, or dialplan updates.
Teach users one preferred format rather than several competing shortcuts. If the business wants users to enter international numbers with a plus sign, make the endpoint and PBX behavior support that choice consistently.
Finally, test both success and denial cases. A safe system should complete approved calls and reject unauthorized destinations predictably. Monitor call records for unexpected trunk selection or unusual international activity.
When to request help
FreePBX dialing international numbers with plus sign troubleshooting often involves several systems. If route matching, trunk policy, and number transformation remain unclear, pause changes before broadening the dial plan. Tech Rescue Ops LLC can review the call path remotely, compare a working and failing attempt, and help create a controlled routing plan.
For related checks, see the guide to FreePBX outbound caller ID configuration and the article on internal extension dialplan checks. Both issues can affect how a seemingly simple outbound call behaves.