FusionPBX as ITSP

Status
Not open for further replies.

atux_null

New Member
Mar 29, 2018
21
0
1
Hi all. for lab purposes i need to create a fake ITSP. the network setup has an isolated network where the FusionPBX has some extensions (1000-1003) and some clients that will register one each as sip trunk. So:
  1. extension 1000 is on PBX_1
  2. extension 1001 is on PBX_2
  3. extension 1002 is on PBX_3
  4. extension 1003 is on PBX_4
Now PBX_1 calls 1003 and reaches PBX_4 and the 1000 is shown as caller ID.

I would like to push some numbers as DID in each trunk and have the following:
  • ext 1000 to have DIDs:50000-50099
    • each DID will be assigned to a device in PBX_1
  • ext 1000 to have DIDs:50100-50199
    • each DID will be assigned to a device in PBX_2
  • ext 1000 to have DIDs:50200-50299
  • each DID will be assigned to a device in PBX_3
  • ext 1000 to have DIDs:50300-50399
    • each DID will be assigned to a device in PBX_4


So when a device (50001) in PBX_1 calls 50103 it will go to trunk 1001 and reach the device in PBX_2. As caller ID it has to be shown the originator (50001). and so on for all the PBXs.


is there a way to achieve that, please?
 

ad5ou

Active Member
Jun 12, 2018
884
197
43
Start with building your 4 extensions.

Then build a "bridge" under "Applications>Bridges"
Name: Trunk 1000 or whatever makes sense to you
Destination: sofia/internal/sip:$1${regex(${sofia_contact(1000@pbx.mypbxexample.com)}|^[^@]+(.*)|%1)}
Description: optional

Build a new bridge as above for each of the other 3 extensions. Changing the "..1000@pbx.." part to match each extension.
You should have 4 bridges built and 4 extension built at this point.

Now build destinations for the did ranges. You can use regex to match the digit ranges or build 400 destinations but the destination for each grouping will be the bridge you built earlier.
^(50[0]\d{2})$ to trunk1000
^(50[1]\d{2})$ to trunk 1001
^(50[2]\d{2})$ to trunk 1002
^(50[3]\d{2})$ to trunk 1003
 

ad5ou

Active Member
Jun 12, 2018
884
197
43
Actually that probable needs to tweak a bit to make those normal internal dial plans instead of destinations.
but that is the basics

Edit... build destinations as above but once they are built, edit the context from "public" to your server's "domain name"
1619189842968.png1619189877801.png
 
Last edited:

atux_null

New Member
Mar 29, 2018
21
0
1
Thanks for the replies. i got stuck in the destinations part. what do i have to fill in.192.168.1.240 is the Fusionpbx IP. In the caller id name it is expecting only number. The regex fails
1619425755709.png
 

Attachments

  • 1619425657357.png
    1619425657357.png
    49.4 KB · Views: 11

ad5ou

Active Member
Jun 12, 2018
884
197
43
The destination should be the regex from above.
Then select the "action" as the bridge statement built in previous step.

In Fusion, if the text is in bold, it is considered a required item. Most other fields are optional and quite often should be left blank or default.
1619443793188.png
Once it is saved, it should show up under "Dialplans>Dialplan Manager" at order 100
 
Status
Not open for further replies.