Generic SIP Trunk to Genetec Sipelia

[baymax]

Hello,

I am facing an issue with the generic SIP Trunk integration between 3CX and Genetec Sipelia (Security System). While I have successfully set up the SIP trunk and can initiate calls from the Genetec Sipelia intercom system to 3CX, I'm encountering problems when trying to call from a Sipelia client to a 3CX extension.

Specifically, when making a call from the Sipelia client to a 3CX extension, the call always routes to the default destination instead of the intended extension. I've discovered that enabling "Call Source Identification" in the "Inbound Parameters" allows the call to ring default destination. However, I'm unsure about the numerous options available in the "Inbound Parameters" dropdown.

I'm looking for guidance on how to properly configure the "Inbound Parameters" to ensure correct call routing. Is there a way to understand how the call is being received by 3CX and configure the "Inbound Parameters" accordingly? It appears that I almost have it fully working other than this one small part.

Any help or insights would be greatly appreciated. Thank you!

 

[TheodorosG_3CX]

There is a 3CX Guide which explains how the PBX will handle the incoming calls and also how Call Source Identification works:
• https://www.3cx.com/docs/sip-trunk-inbound-calls/

However using one of the 3CX Supported Providers is the best option as we take care all the implementation.

 

[baymax]

Yeah, I looked at the link as I already went through your documentation. The documentation wasn't helpful, and I am not connecting to a SIP Trunk provider. I am connecting to a security system that can connect to other VoIP systems via a SIP trunk.

 

[TheodorosG_3CX]

Understood but this is not something we can advice as it is not supported.

 

[leejor]

Are you routing the call based on DID parameters ( as I suspect, as you mention that the call does go to the "default" destination). or what?
If you have access in your system, make use of the 3CX Activity Log (Verbose) to see what is being sent. It may be that there is no DID number being sent so routing cannot be done using that method.