User Extension > Forwarding Rules > CID Exceptions using variables

Status
Not open for further replies.

PD-SII

Silver Partner
Basic Certified
Joined
Aug 17, 2016
Messages
38
Reaction score
12
First .. if this has already been answered .. please feel free to send me a link to the article as there is quite a bit of information on these on forums and I may not have been hitting the correct key words.

I am looking to setup a Caller ID rule for a users extension (rather the DID that is associated with the users extension) that states any external call from a number beginning with area code 123-xxx-xxxx route normally to that users extension. Any call received from an outside number beginning with an area code other than 123 .. end call. However, I only want this rule to apply to external calls made specifically to this users DID. I was trying something along these lines under the users extension forwarding rules, but wasn't getting the results I was shooting for.. Obviously not the right place and maybe even using the wrong variables. If someone can provide an example on the proper/correct way of doing this, I would appreciate it. Thank you in advance for the help

123* - Forward to Extension (This would be the specific area code I want to route normally)
10* - Forward to Extension (I thought this may be necessary as all internal extensions start with 10 and may need this to continue to route those internal calls normally)
* - End Call (Everything else that doesn't match the above .. end call)
 
in inbound rules , create a CID rule and forward to your extension in and out office hours
 
Thanks for the responses everyone. The trick is applying the rule to a specific DID. Maybe it's not possible .. but never hurts to ask. I'm hoping to come across someone that has had this very odd need on their system and what they may have done as a solution .. hopefully with an example I can follow :)
 
  • Like
Reactions: Evolute IT
It sounds as if you may need to run the calls through an intermediate (dummy) extension (use the forwarding options in that extension) to weed out calls using caller ID. Without wildcards, as mentioned, you could only do it based on the full number, and apss the desired calls onto the final extension
 
I;ve done several test with CID , it works with wildcard, copy of my last test
my caller number start 0422, the rule applies and i've got message from remote pbx " final destination is not reachable contact administrator "
11950
 
My understanding, is that the "rule" is to apply to caller IDs, for a specific DID.
 
For sure Leejor your understanding of question is better than mine, my english is not yet enough good.:(

Sorry for my misunderstanding. :confused:
 
I just wanted to thank everyone for their replies .. greatly appreciated! Unfortunately it appears you can only apply CID variables to the trunk itself rather than to a specific DID. Never hurts to ask though. Hope all of you have a great rest of the day and thanks again for the quick replies today!
 
Are you able to setup that DID as it's own trunk, and apply the rules there?
 
  • Like
Reactions: PD-SII
Are you able to setup that DID as it's own trunk, and apply the rules there?
I had not thought of that .. but yes .. this does appear to work. For those out there curious to know what I did... I took revilo951's suggestion of moving the specific DID to it's own trunk and aws2p's CID's rules .. applying those rules to the specific trunk/specific DID since that DID is the only DID applied to that trunk.

3CX does appear to use a top down approach to applying the CID rules though .. not best match .. and you cannot use simply * as a catch all as I did try placing 123* first with * last and it didn't work. When I programmed (9) End Call rules at the top of the list with my 123* route to extension rule last .. it did work.
  • 0* = End Call
  • 2* = End Call
  • 3* = End Call
  • Etc.. thru 9*
  • 123* = Route to Extension (as the last CID entry)

Nice suggestion!
 
  • Like
Reactions: AWS2P
Cool finally i'm in :)
 
Last edited:
Status
Not open for further replies.