Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Combine DID and CID inbound rule

Discussion in '3CX Phone System - General' started by coffeebaron, Jul 30, 2016.

Thread Status:
Not open for further replies.
  1. coffeebaron

    Joined:
    Jan 21, 2016
    Messages:
    2
    Likes Received:
    0
    Is it possible to combine DID and CID inbound rules?
    E.g. I have two DID's 123450 and 123451, and a couple of extensions 100 and 101, and an incoming call from CID 54321

    If a call from CID 54321 comes in on DID 123450 I want it to ring extension 100
    But if a call from the same CID 54321 comes in on DID 123451, I want it to go to voicemail of extension 101

    Can such a scenario be configured? It appears you can only create a rule based on either CID or DID but not both in the one rule.

    Using 3cx 15

    Cheers
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,117
    Likes Received:
    329
    You may have to make use of the forwarding options, in the (original) destination DID, to send particular callers (based on CID),to another destination.
     
  3. panas

    Joined:
    Feb 10, 2016
    Messages:
    3
    Likes Received:
    1
    Hi,

    Im looking for how to do this aswell. So combinding CID and DID to process a call. Does anyone know how to do this?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,117
    Likes Received:
    329
    You have to deal with one "directing" of the call, at a time. In the first case, you are sending using the DID information to send the call to a certain extension, then, you can use the CID to redirect to another extension. You can make use of a "dummy" extension as the first destination, and that extensions CID forwarding options, to send the call to the final extension.
     
Thread Status:
Not open for further replies.