Inbound Calls Routing

[fxbastler]

Hello

I have a question regarding the explanation at https://www.3cx.com/docs/sip-trunk-inbound-calls .

The entire description is missing the CID Rules, the CID Blacklist, and a few other small details (like call scripts with triggers on the trunk).

Let’s set the CID Blacklist aside for now - but shouldn’t the CID Rules appear quite prominently in the image at the bottom (and in the related explanation)? Or am I wrong?

 

[fxbastler]

^ This is also something that has been on my mind since the release of the original holiday.cs in the 3CX Call Script Store in 09/2024 - although it seems that the order was intentionally changed there to prioritize holidays over CID handling.

 

[fxbastler]

I'd like to cautiously ask 3CX - and others who can read code - again.

Am I the only one who's noticed that the 3CX holiday.cs file no longer works properly in the current 3CX v20 u7?

I cautiously asked around the corner a while ago - look above - whether the order in which DID matches in the script are processed is intentionally different from the usual processing in 3CX.

Now, in addition, you can in u7 define DIDs with a * at the end, and in some cases, you have to, because DID recognition is different than before in u6, and the script code hasn't been adjusted yet.

This also has completely different effects and I have already had the opportunity to customize some normal 3CX installations which run without scripts to solve some minor problems.

I can handle it myself and have adapted various scripts and snippets. Unfortunately, I have written a few posts with code about this in the forum over the last few months that are no longer correct due to the changes to the u7.

I'd be happy to explain this in detail. From what I've read so far, perhaps no one has noticed this in practice till now.

Is there any statement from 3CX on this?

 

[KyriacosS_3CX]

I'd like to cautiously ask 3CX - and others who can read code - again.

Am I the only one who's noticed that the 3CX holiday.cs file no longer works properly in the current 3CX v20 u7?

I cautiously asked around the corner a while ago - look above - whether the order in which DID matches in the script are processed is intentionally different from the usual processing in 3CX.

Now, in addition, you can in u7 define DIDs with a * at the end, and in some cases, you have to, because DID recognition is different than before in u6, and the script code hasn't been adjusted yet.

This also has completely different effects and I have already had the opportunity to customize some normal 3CX installations which run without scripts to solve some minor problems.

I can handle it myself and have adapted various scripts and snippets. Unfortunately, I have written a few posts with code about this in the forum over the last few months that are no longer correct due to the changes to the u7.

I'd be happy to explain this in detail. From what I've read so far, perhaps no one has noticed this in practice till now.

Is there any statement from 3CX on this?

There is a way to ask without too much caution - open a ticket, add some documentation/logs etc of what you are observing so the team can take a proper detailed look.

I am not questioning what you are saying, but there are too many variables at play to try and replicate what you are seeing based on the forum discussions.