PBXes - Print: RE: Partial CID match for inbound routing

PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Feature Requests (http://www1.pbxes.com/forum/board.php?boardid=23)
--- RE: Partial CID match for inbound routing (http://www1.pbxes.com/forum/threadid.php?threadid=1260)

Posted by ayking on 26.03.2007 at 15:55:

Partial CID match for inbound routing

Just wondering if it's possible to do a partial CID match when using inbound routing? For example, I would like to have calls to a trunk from an area code to route to one menu while calls from another area code to another menu. Is this possible, or would it be too ambiguous for the system?

Thanks!

Posted by Diafora on 26.03.2007 at 17:25:

So what you are looking for, is wildcard matching in the "Caller ID Number" field of the Inbound Route.

Posted by ayking on 26.03.2007 at 18:08:

Yup, that's right.

Posted by bluegate on 26.03.2007 at 21:47:

yea! that would be a nice feature!! smile

Posted by i-p-tel on 12.04.2007 at 10:15:

Daumen hoch! RE: Partial CID match for inbound routing

The use of wildcards for CIDs has been implemented.

X matches any digit from 0-9
Z matches any digit form 1-9
N matches any digit from 2-9
[1237-9] matches any digit or letter in the brackets (in this example, 1,2,3,7,8,9)
. wildcard, matches one or more characters

Posted by Diafora on 12.04.2007 at 17:51:

Great addittion for Inbound routing flexibility.

Square brackets in the Caller ID Number result in a "Invalid Characters" error message.

Ex. 222[34]xxxxxx results in the above error.

Posted by i-p-tel on 13.04.2007 at 00:23:

RE: Partial CID match for inbound routing

Thanks for your comment. It is fixed.

Posted by euroasia on 29.05.2012 at 20:41:

RE: Partial CID match for inbound routing

I used "x" in inbound routing rules and it is not working.

Recently I received many spam calls for my USA number. They all came from 360 area code but with different CIDs, so I decided to blaock all CIDs starting with 360 or 1360. I setup inbound rules to set all calls with CID "360xxxxxxx" or "1360xxxxxxx" to "Hung Up", but spam calls still got through. Also "303" area code. I Googled these spam numbers and can see these spam calls make people mad.

Any thoughts to block them?

Posted by i-p-tel on 17.02.2021 at 10:31:

RE: Partial CID match for inbound routing

When using several inbound routes, some with caller ID and some with trunk name, those with trunk name will take priority.

So you have to add trunk name to those with caller ID, to make them go first.