Accept incoming calls from all trunks

[Bucky]

We have over 20 internal PABX systems interconnecting. ATM for a user to work, a DID for their 3cx extension is required for each of the 20 trunks.
Is there some way to globally accept calls to my extension number from xx or any SIP trunk

 

[Evolute IT]

We have over 20 internal PABX systems interconnecting. ATM for a user to work, a DID for their 3cx extension is required for each of the 20 trunks.
Is there some way to globally accept calls to my extension number from xx or any SIP trunk

What is your setup? Because that doesn't make sense.

 

[leejor]

Are these trunks connected via bridge trunks? Are they sending the dialed digits, of the extension? If they are actually sending DID information, with the last 3 or 4 digits being the same from each trunk, then you could set up rules using a leading wildcard (*), on each trunk

 

[Bucky]

No they are 'generic' SIP trunks. We have our 3CX PABX connecting with a variety of other SIP telephony systems like Asterisk, Freeswitch, Genesys etc - around 20 in total so 1 trunk per system
In order to recieve a call from each system, a SIP trunk needs to be inplace referencing the sources IP (or some credentials).
I also noticed that in order for this to work I had to set each trunks Inbound Parameters > Call Source Identification to From:Host part GWHostPort to avoid an error about conflicting DID

I tried adding a DID of (*) and got 'only following characters allowed, a-z,0-9,+,#'
But yes, I would like a wildcard DID on a trunk to match an inbound call to any internal number like extension / digital receptionist / ringroup / call queue.

If I am doing it wrong and there is a better way please let me know

 

[leejor]

What sort of DID are you sending on each trunk group? Are you able to send any DID you wish? If the destination extension were 212, for example, one trunk could send a DID of 6665550212 and the DID rule as *212 or *0212, or *50212. etc.. Another trunk could send 7776660212 with a rule of *60212. You can use the * wildcard, but some digits must match what is being sent.

 

[Bucky]

Its all internal so for example we have hundreds of 6 digit extensions on 3CX. They are all 400xxx and 401xxx so the other systems will be sending an INVITE to 3CX with 40[1-2][email protected]

 

[leejor]

If you are attempting to send the dialed extension number, in the To field of the Invite, and it is not being sent in the DID field, then you will have to use a 3CX Bridge trunk. They are capable of interpreting the information in the To field to route a call to that extension.

DID information will usually be further down, in the Invite, something like Original called number ( I tried to find an example). The originating PBX must be capable of sending this information as does a "normal" SIP provider, when you subscribe to a DID service.

Here is a link to an archived 3CX page, on using bridge trunks, to another PBX type.

https://web.archive.org/web/20161213151353/http://www.3cx.com/docs/bridging-asterisk-pbx/

It seems the use of Bridge trunks between non -3CX PBXs is now discouraged, in recent versions, as there have been a number of issues arise. In some cases, it has been a no-go altogether. You need to be very familiar with the call routing, of the PBXs, at both ends. Caller ID problems are common.

 

[Bucky]

Thanks leejor for doing all this work. Yes ok if thats the case thanks I will steer clear of that. It looks like for every extension I will have to have 1x DID and 1x incoming call route * the number of trunks.
I am comparing to an Avaya IP Office where you just create an 1x incoming call route of
Trunk ID = 1
Incoming DID = *
Destination = .
The . means that ANY did coming in on trunk 1 will attempt to match extensions, huntgroups, shortcodes. Very neat and tidy