Please help to fix issue with "No registration found" for outgoing call test

[Alexey Kononykhin]

Hello all

I'm starting to use 3CX, so apologize in advance for newbie question.

I have "IP based" SIP trunk configured, with SIP server's IP specified both in both Registrar/Server and Outbound Proxy fields. Outbound rule configured with previously configured SIP trunk specified in Route! field and empty "Calls to numbers starting with prefix" field (so call to any number has to use it based on the description).

Incoming calls work correctly, but when I try to call a number from 3CX application I hear "No line is available for this call", when I start "Outbound Call Test" from SIP Trunk Checked I receive "No registration found" error.

What did I miss?

Thanks in advance,
Alexey

 

[leejor]

If you have access to the 3CX Activity Log, see if there is an issue with registration. The fact you are receiving calls would suggest not, but, any errors the PBX has with the outgoing call will show in that log, and may help lead to a resolution..

 

[Alexey Kononykhin]

Hello leejor

Thanks for the response.
It's "IP based" SIP trunk, so authentication and "SIP REGISTER" doesn't have to be used as far as I understand.

In Activity log I see:

L:3.1[Extn:xxxx{00000000-01dc-c2d8-fe2b-a7a700000007}] Dialed number '+1yyyyyyyyyy' has no route!

And in Event Log:

Event ID 30052
Date 04/02/2026 10:43 PM
Details There was no user or outbound rule found for the number +1yyyyyyyyyy that Ext.xxxx dialed.

Is Outbound Rules is the only place where routes are defined? I have the single outbound rule defined there with the next parameters:

Prefix = Any
Call from Ext. = All
Length = Any
Department = <empty>
Route1 = <my SIP trunk>

Best regards,
Alexey

 

[ITSP]

Did you type the PLUS sign in? Have you tried it without and only calling local numbers?

 

[YiannisH_3CX]

Prefix = Any
Call from Ext. = All
Length = Any
Department = <empty>
Route1 = <my SIP trunk>

You need to specify at least 1 parameter for the PBX to match the outbound rule. My advice for getting started is to use a prefix. So if the number you are dialing starts with 0 then add as prefix and try again. As you get the hang of it you can make the outbound parameters more strict to fit your use case.

 

[Alexey Kononykhin]

Hello YiannisH_3CX

Thanks for the response and information.
I tried to add +1 to Prefix for Outbound Rule and still received the same response. But in ActivityLog in Debug mode I found the next messages:

04/03/2026 10:43:00.390 AM	L:13.1[Extn:xxxx{00000000-01dc-c33d-7ee8-f3930000001f}] Dialed number '+1242603yyyy' has no route!
04/03/2026 10:43:00.390 AM	[Flow] Target endpoint for +1242603yyyy is EndCall:EndCall{}
04/03/2026 10:43:00.390 AM	Looking for outbound rule: dialed = [+1242603yyyy], processed: [603yyyy]; from-ext: xxxx; OutCID: ''

So based on the message "Looking for outbound rule..." I suppose 3CX by some reason removed prefix +1242 from the number I dialed and looks only for the part starting from 603....
I added one more OutboundRule not for "603" prefix and outgoing calls started to work!

Could you clarify for me why +1242 prefixed is removed? I suppose it's some 3CX setting, related to country specified in License and Contact details (Bahamas which has prefix 1242), but is it possible to disable removing the prefix and if yes - where?

Best regards,
Alexey

 

[leejor]

The outbound rules will only "do" what you have specified. Do you have happen to have the e164 option enabled?

 

[Alexey Kononykhin]

It's newly installed system (and first one 3CX I installed and use). I didn't make any configuration about stripping prefix +1242 intentionally, but I could just missed smth during installation.

Thanks for the information about "E164 option". I found it in "Advanced->E164", with the next settings
Process E164 numbers = Yes
Country = "Bahamas (+1242)"
Remove if same country=Yes
International dial code = 011

Playing with it I found:
1) If set "Remove if same country" = No, then only "+" is stripped and 3CX tries to route call as 1242603yyyy
2) If set "Process E164 numbers" = No, then 3CX doesn't strip anything and routes exactly the same number as dialed from 3CX App.

Thanks for the help to all!

Best regards,
Alexey

 

[leejor]

The E164 options are a convenient way to convert numbers to a standard format, before being passed to the outbound rules.
I have found that outbound rules, which do the "heavy lifting" can cause unintended results when left too vague. It can be a lot to just expect them to work when you haven't specified exactly how that is to happen.

 

[SteveITS]

A couple additional notes to this...the browser of course actually makes a call so notifications must be enabled for the 3CX server URL, and then the computer making the call must have a microphone, because it's a call.