FS PBS throwing 404 to Inbound CallCentric

Starburst

New Member
Jul 8, 2026
23
1
3
54
FS PBX Version: 2.0.1
FreeSWITCH Version: 1.11.3

Trying to add CallCentric.
Both FS PBX and CallCentric show they are connected.

But when a test call is made in, FS PBX responds with:

WARNING [inbound routes] 404 not found

Both the destination_number and sip_to_user have entries in Inbound Routes set to what fs_cli is showing when I try to call in.

Has anyone tried connecting CallCentric to FS PBX or FreeSWITCH?

I found:

And tried to set the DID like they mentioned worked for them, but FS PBX just makes it 10 digits again.
 
Last edited:
Attach screenshots so we can see what you are doing. The rule remains the same. Do not modify inbound routes manually. Create a phone number, and it will create an inbound route for you. In your case, it's best to delete phone numbers from the inbound routes and phone numbers page and start from scratch.

If you still get a 404, attach a full FreeSWITCH log of the call here so we can see why it's not matching the route.
 
Attached is the fs cli log when I tried an incoming call. (Times are in Zulu/UTC/GMT)
Obviously I replaced MYCELL, CallCentric-1777, and CallCentric-DID for some security.

Sometimes with CallCentric, depending on the equipment you have to enter 1777xxxxxxxEXT, which I tried both ways.

Also tried entering the 1777xxxxxxx as a DID, and that did nothing.

Along with screenshots of the Gateway and ACL configs.

I deleted everything again, and redid them from scratch, still got a 404.

Thanks
 

Attachments

  • fs_cli_CallCentric_Inbound.txt
    fs_cli_CallCentric_Inbound.txt
    11.5 KB · Views: 3
  • CallCentric_ACL.png
    CallCentric_ACL.png
    14.7 KB · Views: 3
  • CallCentric_Gateway_Advanced.png
    CallCentric_Gateway_Advanced.png
    52.2 KB · Views: 3
  • CallCentric_Gateway_Settings.png
    CallCentric_Gateway_Settings.png
    46.5 KB · Views: 3
  • FSPBX_Gateways.png
    FSPBX_Gateways.png
    12 KB · Views: 3
I found your issue

Code:
404 not found 199.87.144.69 destination_number CallCentric-1777 sip_to_user CallCentric-DID sip_req_user gw+0ef24007-6de9-4969-951d-f267f96d0831


I assume CallCentric-DID is the real DID you are dialing, and you just replaced it for privacy. So that means CallCentric is passing the DID in the sip_to_user header instead of the default sip_req_user header.

To change which header FS PBX uses for matching, go to Advanced -> Default Settings and update the destination setting. Change it from ${sip_req_user} to ${sip_to_user}. Then remove your DID and create it again. The inbound route will be generated with the correct setting.

1790354220839.png