Incoming CID rule format

[saint_]

Hi all,
I found a page using kind of regex rules for called IR reformatting, but I would like to know if there are any specifications or limitations for the Inbound rule / CID rule ?

For example, if I want to allow
xxxyyy1000
xxxyyy1001
but send to spam
xxxyyy100[2-9

all i found in the documentation for this page is the use of wildcare for 1001 or xxxyyy for example.

Thank you

 

[cobaltit]

Is there something stopping you from testing? I mean the instructions seem pretty clear and I assume it follows standard convention of going top down until it finds a match.

https://www.3cx.com/docs/cid-reformatting/

 

[saint_]

Instruction in CallerID reformatting talk about source pattern and blocks, while inbound only talked about using a wildcard. I can test, but I'd rather have a correct and fully explained documentation on the authorized pattern used on the inbound side.

 

[cobaltit]

So if you wanted to know about the inbound rules, why is the subject CID rule format. Inbound rules are exactly as documented; wildcard only, no regex.

 

[saint_]

Because the menu to add the rules is under Inbound Rules, and called CID rules.

 

[cobaltit]

Gotcha. It was late when I read your title and then your mentioning of regex I went towards the CID reformatting. But yes on the trunk side you can do CID reformatting with regex but on the Inbound Rules section only by wildcard. I supposed you can combine them both to get the desired effect but if it's just for blocking spam calls I don't know that the administrative effort is worth it. Blacklist the really bad offenders and hope your provider gets on the STIR/SHAKEN train sooner rather than later.

 

[saint_]

Hi - Sorry for the late reply.
STIR/SHAKEN only works in the USA as far as I know. And if you have a bunch of numbers behind a PBX, it can't guarranty authenticity at 100%. Work in progress, but at the mean time, I'd rather deal with it on my own... Thanks for the info about CID