Incoming to CallCentric, not to 3CX

[DrCopter]

I'm setting up a locally hosted 3CX server on a Raspberry Pi. My SIP provider is Call Centric. I've followed their steps and I can use 3CX to make calls to US telephone numbers, but not receive them. In my CallCentric dashboard, it indicates the call was received. It also has a section showing that my phone is registered, it lists my public (dynamic) IP address and the 3CX server's internal LAN IP address.

On the 3CX side, everything passes the firewall test with my UniFi security gateway. I'm able to make and receive calls to 3CX extensions within the LAN, and I can make outgoing calls. It's just external calls seem to get stopped at the CallCentric - 3CX interface, or so I suspect, since the "number you are not available, message 1007) seems to come from CallCentric.

Is there some other setting I should look into on the 3CX side to "pull" these calls in better? I'm new to SIP trunks, but is my dynamic public IP a problem? It seemed to be pushed to CallCentric just fine, and I do have a FQDN I could pass if I ever found a spot... but that didn't seem to be the issue yet because (for the time being) CallCentric had it.

 

[leejor]

Make use of the 3CX Activity Log. That will show you the incoming call from your provider (if 3CX is getting it), and what 3CX is doing with it. There may be an issue sending the call to a destination within 3CX, or, a misconfiguration in the trunk settings, that causes the call to be rejected. The log should show that. The Verbose setting, will show a lot more detail, but usually isn't necessary.

 

[YiannisH_3CX]

You could also potentially run a packet capture on your firewall and see if the call hits your firewall.

 

[DrCopter]

Thank you both for the tips.
Still suspecting my firewall, I backed up my settings and migrated my account from my local network to an Amazon Web Services server to remove that from the equation. 3CX extensions re-established and function just fine within my network, even though the 3CX server is now offsite. I let that sit there for about 12 hours and double checked that the CallCentric account now has the correct (static) IP for the 3CX server- it does.

I set the alerts to verbose, dialed my CallCentric number a few times from a cell phone not connected to 3CX. I see no alerts during that time other than a "default best-route IP" update every ten seconds or so.

I continued to test so I called an internal extensions from a 3CX app on a phone, which connected and watched as they showed up in alerts immediately. I then tried dialing an external cell phone number (U.S. area code) from a 3CX app on my phone, it also connected and logged in alerts.

So it looks like at least the alerts are working properly. And I'm able to make use of the CallCentric account because it's hitting sip:[email protected]:5060 on the way outbound. But the lack of anything at all showing up still indicates to me that either there's a setting misconfigured on the 3CX side, or there's something wrong on the CallCentric side.

Still searching...

 

[YiannisH_3CX]

If there is nothing hitting the 3CX PBX then there is no setting on the PBX that will help you resolve the issue. If the calls were hitting the PBX and got rejected for some reason then we would be talking about a PBX issue but what you need to do is make sure that calls are reaching the PBX from Callcentric.

You can try creating another free Callcentric account and see if that works on your PBX. You can also use it to make calls from and to it as you test.

 

[BrianC]

Might be a dumb question, but do you have some sort of call treatment set up in Callcentric to send the call to your 3cx extension? You essentially have to tell Callcentric what to do with the call once is been received.