Inbound DID FusionPBX as Hosting

[Fernando Villarroel]

Hi All.

I am testing dSIPRouter and FusionPBX as FusionPBX Hosting

https://dsiprouter.readthedocs.io/en/latest/use-cases.html#fusionpbx-hosting

Both machines dSIPRouter and FusionPBX are hosted in Digitalocen with public ip addresses.

i created a domain test.com in FusionPBX

I registered two extensions with the IP Address of dSIPRouter as SIP Proxy Server

The calls between extensions are mapped to context test.com of FusionPBX and works fine.

Now i am trying to mapping Inbound calls DID to my Endpoint group named fusionpbx

The call is received in FusionPBX from dSIPRouter but the ACL denies the call.

So  i need to allow the ip address of dSIPRouter in Access Control List of FusionPBX, that way the inbound call works.

My problem is: now the calls between extension doesn't work because now the calls are mapped into public context and i receive error 404 not found.

Is this behavior normal?

Or could you tell me some tips in order to solve my problem?

The Log is:

2024-05-29 22:08:50.805385 93.67% [INFO] sofia.c:10459 sofia/internal/6001 @test.com receiving invite from 161.35.xx.xxx:5060 version: 1.10.11 -release 64bit call-id: 3170949237 @192.168.1.86
2024-05-29 22:08:50.805385 93.67% [DEBUG] sofia.c:10553 verifying acl "providers" for ip/port 161.35.xx.xxx:0.
2024-05-29 22:08:50.805385 93.67% [DEBUG] sofia.c:10582 IP 161.35.238.98 Approved by acl "providers[]". Access Granted.

......

2024-05-29 22:08:50.805385 93.67% [INFO] mod_dialplan_xml.c:639 Processing 6001 <6001>->6000 in context public

404 not found 161.35.xx.xxx destination_number 6000 sip_to_user 6000 sip_req_user 6000)

Regards

[Mack Hendricks]

Hey Fernando,

Create an additional endpoint group that points to FusionPBX on port 5080 and route DID’s to that. Endpoint group.  Basically dSIP will be sending traffic to FusionPBX on 5060 using pass-thru auth port 5080 for incoming traffic from your carrier 

--
You received this message because you are subscribed to the Google Groups "dSIPRouter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dSIPRouter+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dSIPRouter/f1b79ce4-ddb6-442e-838a-429648a19963n%40googlegroups.com.

[Fernando Villarroel]

Hi Mack

Thank you for your answer.

I followed your steps.

First i created the new endpoint group "inbounddid" that points to FusionPBX on port 5080

Then i'm routing inbound DID from carrier to this new endpoint group "inbounddid" as you can see

But anyways FusionPBX require auth ACL for dSIPRouter IP

024-05-30 20:08:16.325387 94.00% [DEBUG] sofia.c:10553 verifying acl "providers" for ip/port 161.xx.xx.xx:0.
2024-05-30 20:08:16.325387 94.00% [DEBUG] sofia.c:2419 detaching session 51015b0b-4f32-47d6-aff2-4936c22f35e0
2024-05-30 20:08:16.325387 94.00% [DEBUG] switch_core_state_machine.c:600 (sofia/external/994...@xx.xxx.xx.xx State NEW
2024-05-30 20:08:26.365368 95.20% [WARNING] switch_core_state_machine.c:684 51015b0b-4f32-47d6-aff2-4936c22f35e0 sofia/external/994...@xx.xxx.xx.xx Abandoned

What am i doing wrong ?

I would appreciate some feedback.

[Mack Hendricks]

Have you reloaded the ACL’s 

dSIP should only be in the ACL for the external interface (5080) - not the internal interface (5060)

Mack Hendricks

Managing Partner

dOpenSource, A Flyball Company &

dSIPRouter Founder 

(o) 313-789-1313

[Fernando Villarroel]

Hi Mack

Now i see where I’m wrong
My FusionPBX only listened internal and external profiles on same nic device (eth0)

Thank you for you help