Metaswtich to 3cx SIP Trunk

[randybell]

I have dedicated SIP trunk and physical connection to my provider, they have metaswitch at their end.

I know this not a supported trunk from 3cx, that is why I am posting it here.

I am using 3cx v16 Enterprise.

Problem: The SIP trunk is connected, I can make outbound calls ok
Generally if I dial into the number of the SIP trunk, the call quickly hangs up. But, if I dial out to my cell phone, hang up and then call the number back within 10 seconds that call comes through just fine into 3cx

Any suggestions on where to start or suggest with my SIP provider?

 

[AWS2P]

Hi,
perhaps to give us a better overview can you start here please
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[leejor]

You might want to look at the 3CX Activity Log, to see what sort of messages you are getting, when the calls fails. Compare that with one where he call does get through.

Have you successfully run the 3CX Firewall Checker? My first guess would be a firewall/port issue.

 

[randybell]

• 3CX Version,Ent 16.0.619
• Server OS, Windows 10 Pro
• Is the 3CX Server Hosted and where? Local LAN
• IP Phone Make/Model/Firmware - not relavant
• Provisioning Method: Local - Direct IP into the PBX server
• Trunk Provider: Generic - they are metaswitch
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO (but not relavant)

On the failed inbound calls; I don't see anything in the activity log

 

[AWS2P]

is the log set on verbose to have full details?

 

[leejor]

On the failed inbound calls; I don't see anything in the activity log

If there is no log, and you don't require Verbose mode to see this, then the call is not reaching 3CX, for some reason. The registration may not be correct, in other words, your provider is sending the call Invite to the incorrect address, or, something is blocking the Invite, perhaps your firewall.

Again, run the Firewall Checker, and be certain that all passes.

 

[randybell]

firewall checker passes.
but there is no firewall as previously. it is directly connected to the pbx

The provider got back and reported, saying that it is something on the 3cx side, but these reference don't mean much to me. Any ideas

Cause: A subscriber is configured to use a disabled IP Destination.

Action: Ensure that the subscriber's Caller ID Service is configured to reference an enabled IP Destination

 

[leejor]

If by "subscriber", they mean you (the IP that 3CX is registering with), then you might ask them what the IP is, and see if it matches the public IP you are actually using. I'm not really certain what they mean regarding caller ID, since the problem is incoming and they are sending CID. You would need to see an Invite, from them, even if it is rejected by 3CX, before you can troubleshoot anything within the PBX. Confirm with them, where (what IP) they are sending the incoming calls to, and that it is correct.