Connecting FusionPBX and Freepbx

[Newbee]

Hello All,

I'm Needing some guidance and help on setting up sip connection with FusionPBX and Freepbx
This is the scenario
Two FreePBX boxes (hosted in the cloud) that have Iax trunk connecting each other. one box has the extension ranging from 4XX and the other has 6XXX and can call each other just dialing the extension number.
now one side (that would be my box) moving to FusionPBX, Otherside has no plan to move to this wonderful Fusionpbx at this time.

I'm needing to build a sip trunk and set up call routing, and call each other without hitting any IVR, etc..
I only need FreePBX to reach domain one.mydomin.ltd and one.mydomin.ltd is the only one allowed to call the FreePBX
see the diagram


Any help would be greatly appreciated
Stay Safe.
Thank You.
NewBee

 

[Newbee]

So far this is what I got
FusionPBX Side Gateway


On FreePBX Trunk


FreePBX side call rout all set too

When I ran Sip show peers command in asterisk (freepbx) I get
fusiontofreepbx/fusiontofreepbx 68.12.15.200 Yes Yes 5060 OK (21 ms)
looks like freepbx side trunk is up but can't make any calls sngrep don't even show the calls

Thanks

 

[Newbee]

Ok got it to work.
this is how this done if anybody looking for a solution like me

FusinPBx side
1. add Bridge with Destination

sofia/Internal/$1@your-freePBX-IP:5060

2. setup Inbound Routes

Distination_number add as your dial plan
3. in Outbound Routes


Again Distination_number add as your dial plan ( my settings I'm dialing 6xxx and 8xxx range of extensions at Freepbx )
4. add your FreePBX IP CIDR (xxx.xxx.xxx.xxx/32) to domains in Access Control sections
5. rescan the sip profiles

then Freepbx

Make trunk



then add the Outbound route as your fusion extension range

____________________________
Special thanks to Mark and Elden at FusionPBX team for showing me how to do this

Hope this will help somebody someday

 

[Lilian_Sash]

I have followed through these steps and my trunk is not registering. Kindly help

 

[ewdpb]

I have followed through these steps and my trunk is not registering. Kindly help

You have better chances of getting help if you say things like: "this is what I see in the logs", "my environment is different in X, Y, Z", etc. I notice that people in this forum are very kind and helpful (for the most part) if they see you have done your homework.

So, do you have any logs?

 

[Newbee]

I have followed through these steps and my trunk is not registering. Kindly help

your trunk in FreePBX should not show register
anyway can you post your setting and setup in detail

Thanks

 

[Newbee]

Actually I miss one step

you have to add your freePBX IP to the FusionPBX access controls list

Go to Advanced then Access Controls, Click domains then click ADD
Enter your CIDR (ex xxx.xxx.xxx.xxx/xx)
Save and reload ACL

 

[robvandenbulk]

I have followed through these steps and my trunk is not registering. Kindly help

Trunk don't need to REG

 

[paulash134]

I have one way working between FusionPBX and FreePBX using these settings, if I add the ACL change then it makes one way working between the FreePBX and the FusionPBX. So I can get it working one way or the other, not both ways. In the working FusionPBX to FreePBX state I get this when I attempt a call from the FreePBX to the FusionPBX
2021-07-16 08:15:04.932550 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/8961@51.XX.165.219) Running State Change CS_NEW (Cur 1 Tot 152)
2021-07-16 08:15:04.932550 [DEBUG] sofia.c:10279 sofia/internal/8961@51.XX.165.219 receiving invite from 90.221.21.101:5060 version: 1.10.3 -release 64bit
2021-07-16 08:15:04.932550 [DEBUG] sofia.c:10373 verifying acl "domains" for ip/port 90.XX.21.101:0.
2021-07-16 08:15:04.932550 [DEBUG] sofia.c:2434 detaching session ecf5a9f6-e60d-11eb-a16f-5f34298731f1
2021-07-16 08:15:04.932550 [DEBUG] switch_core_state_machine.c:604 (sofia/internal/8961@51.XX.165.219) State NEW
2021-07-16 08:15:14.952547 [WARNING] switch_core_state_machine.c:688 ecf5a9f6-e60d-11eb-a16f-5f34298731f1 sofia/internal/8961@51.XX.165.219 Abandoned
2021-07-16 08:15:14.952547 [NOTICE] switch_core_state_machine.c:691 Hangup sofia/internal/8961@51.XX.165.219 [CS_NEW] [WRONG_CALL_STATE]

It would seem that the ACL entry is necessary, however, if I amend the ACL entry to include the FreePBX IP address it will no longer work connecting FusionPBX to FreePBX, The FreePBX to FusionPBX then may work.