Solved Trunk from Asterisk to 3CX without using "Bridge" way

[werton13]

Hi there! I'm using 3cx pbx version 15.5. sp6 (15.5.15502.6) on Windows server. My company is in close relationship with our partner company, which is on Asterisk.

I'm looking for a way, to build a trunk from Asterisk to 3CX without using a bridge. Because we want to see clear extension number for every call from our partner PBX without this bridge extension number.
With bridge incoming calls look like from this "(@(Ln.10001@To Company B Asterisk Bridge))". I believe it is very common scenario, so I hope to find here some advice.

Plz help..

 

[eddv123]

Since 3CX supports the bridging functionality I think you will be hard pressed to find a guide on doing this via a SIP trunk.

This is a legacy guide for building via bridge:
https://www.3cx.com/docs/

Here are some forum posts which may give you more information. I have setup a trunk between 3CX and Avaya (which was the only option), I did this with a VPN and directly. Asterisk should be no different I would of thought.

https://www.3cx.com/community/threads/bridging-3cx-with-an-asterisk-pbx.44726/
https://www.3cx.com/community/threads/3cx-to-asterisk-bridge.57673/
https://www.3cx.com/community/threads/setup-asterisk-to-connect-to-3cx.6146/

 

[leejor]

A bridge trunk on 3CX (Master) allows other SIP devices to register a trunk to 3CX as they would a provider. If the other PBX, allows a trunk to register to it, then 3CX could use a generic SIP trunk. Other than that it would have to register to an extension on the other PBX and vice versa, which limits your options greatly.

 

[Wendelspanswick]

We have linked a Mitel to the 3CX using the generic SIP template and it works fine.

 

[YiannisH_3CX]

Hello @werton13

If you try to add a Generic SIP trunk you will find an Asterisk template and although we have no instructions on how to set this up most of the settings are pre-configured to help you with the process.
Good luck

 

[werton13]

Good evening all!
I'm high apprecate all your answers, but i still dont see a solution..
I think - i poorly explayned my goal.
I need my users to see calling numbers from our Partner company phone system, as it was our internal department. The 3CX bridge just hide all Partner company numbers behind his own bridge Virtual extension number - for example 10001 and all calls shown as from 10001.

The SIP trunks works differently, all calling numbers displayed correctly, but 3CX sip trunk should be terminated at 'Main Trunk No' - so all calls incoming via this trunk going to the same extension number.
Yesterday i have tried to build a few simultaneous SIP trunks from my test Asterisk system to my production 3CX. I placed test Asterisk in the same ip subnet as internal ip of my 3CX and created
3 trunks to the same IP but with different extension numbers... and you know - it's worked - the calls are correctly placed to the destination extension numbers.
But this configuration doesn't want works in production.. i dont know why. The only difference is NAT in between my 3CX and Partner Asterisk, i need some kind of deep tech explain why it work in first scenario and dont want in second, any thoughts?

 

[leejor]

The SIP trunks works differently, all calling numbers displayed correctly, but 3CX sip trunk should be terminated at 'Main Trunk No' - so all calls incoming via this trunk going to the same extension number.

So, caller ID displays correctly, but, you do want calls doing to one destination, or you want calls to go to various destinations? Over a SIP trunk the originator (Asterisk), would have to be able to sent DID information. Then you would route based on the DID.

I placed test Asterisk in the same ip subnet as internal ip of my 3CX and created
3 trunks to the same IP but with different extension numbers... and you know - it's worked - the calls are correctly placed to the destination extension numbers.

So, If I understand correctly...you created several 3CX extensions and registered Asterisk trunks to them? If so, then caller ID would be that of the 3CX extension, incoming.

 

[werton13]

So, caller ID displays correctly, but, you do want calls doing to one destination, or you want calls to go to various destinations? Over a SIP trunk the originator (Asterisk), would have to be able to sent DID information. Then you would route based on the DID.

I want call to go to various destinations, not just to the DID of this trunk. What do you mean - "route based on the DID" ? In 3CX i can route any calls via this trunk to only one DID, depend of time.

So, If I understand correctly...you created several 3CX extensions and registered Asterisk trunks to them? If so, then caller ID would be that of the 3CX extension, incoming.

In this configuration (i'm just trying to find some workaround) call going to the DID of the trunk, which in this scenario match the target extension. And target extension can see right callerid of incoming call.


Can anyone link me where can I read more about trunk config section "Call Source Identification "? Can it help?

 

[leejor]

I want call to go to various destinations, not just to the DID of this trunk. What do you mean - "route based on the DID" ? In 3CX i can route any calls via this trunk to only one DID, depend of time.

on A "standard" SIP trunk, the provider cannot "dial' an extension as is done on a bridge trunk. this is handled using DID, so to route a call to a specific extension, depends on the originator being able to provide DID information with the call. You would then create DID rules to route to the desired extension. I do not know if Asterisk is capable of sending DID information.

https://www.3cx.com/docs/sip-trunk-inbound-calls/

 

[werton13]

Hi all. Thank all and many thanks to leejor for giving me right direction. I just want to complete this thread with solution description.
If your scenario is similar to mine - you need to:

1. make a General SIP trunk with DID number from one of your internal extensions, then add to this trunk DIDs for all of your internal extensions;
2. You need to add inbound rule for each of the trunk DID and configure it to route calls to corresponding extension number.

to configure many rules in bulk you can use export existing rules to CSV, edit it in excel and then import back.
good luck!

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.