Using FusionPBX as SIPTRUNK server

mhank

New Member
Feb 25, 2025
8
0
1
42
Good morning everybody,

I am in need of some good advise!

We need to route DIDs (inbound calls) to our customers, via IP (or FQDN)

Each customer have their own tenant
A customer e.g. have 100 DIDs and we need to send the inbound calls (we receive) to the customers own PBX/switch

But for the love of good, we can not make it work.

Any good advise?
 
I have something like this working for giving multiple phone systems access to a single SIP trunk. No registration involved at all, all IP-based.
Multiple inbound routes looking like the attached.
 

Attachments

  • ksnip_20250307-123512.png
    ksnip_20250307-123512.png
    51.8 KB · Views: 22
Thank you,
But that is not a solution.
To many mistakes can happen

I need to the drop down with predefined siptrunks (sorry, for not being clear about that)
 
@mhank SIP Trunks application when installed does not show up as any other typical FusionPBX application you see under the [Applications] sub-menu. You'd rather see it as a new category named 'SIP Trunks' with all your existing extensions underneath it in your Dialplan > Destinations > Actions dropdown. As mentioned in the README file, its a basic application that actually uses bridge statements to route calls to existing extensions in your domain/system with the called number in the TO header.
 
@mhank SIP Trunks application when installed does not show up as any other typical FusionPBX application you see under the [Applications] sub-menu. You'd rather see it as a new category named 'SIP Trunks' with all your existing extensions underneath it in your Dialplan > Destinations > Actions dropdown. As mentioned in the README file, its a basic application that actually uses bridge statements to route calls to existing extensions in your domain/system with the called number in the TO header.

Thank you,

But it still does not help the fact, that it screws up the system, so e.g. the webserver fail to restart/start afterwards, without you Editing the files first.

But, none or less, extensions are (to the best of my knowledge) since they only support registrations, not Peering,
 
IP Authentication
Create an extension for the authorized IP address using Accounts -> Extensions. Then, use the CIDR on the extension edit page to authorize the IP address. This is easier to accomplish on FusionPBX 5.3 or higher. After that, got to Status -> SIP Status and press the RELOADACL button.
 
IP Authentication
Create an extension for the authorized IP address using Accounts -> Extensions. Then, use the CIDR on the extension edit page to authorize the IP address. This is easier to accomplish on FusionPBX 5.3 or higher. After that, got to Status -> SIP Status and press the RELOADACL button.
Interesting - thank you,
I will test it out