Block internal calls between groups?

Discussion in '3CX Phone System - General' started by hwcltjn, Aug 17, 2017.

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

    Joined:
    Aug 16, 2017
    Messages:
    26
    Likes Received:
    1
    Hello,

    It seems as though my question has been asked a number of times and that no one has ever found a real solution (or I couldn't find it!) - searching the forums has returned the following threads:

    Blocking Extension to Extension calls
    Prevent users groups calling other user groups
    Internal Call Blocking

    I have 3 groups, A, B and C.

    I need to prevent groups A and B from calling each other.
    However, I need groups A and B to be able to reach group C.

    Extensions in group A have format 51XX.
    Extensions in group B have format 52XX.
    Extensions in group C have format 53XX.

    I created the following outbound rule to limit group A from calling group B
    Code:
    Calls to numbers starting with prefix: 52
    Calls to numbers with a length of: 4
    Calls from extension groups: Group A
    Route: Block
    
    It didn't work.

    I know I can limit how an extension receives calls by creating an exception under the "Forwarding Rules" tab of the extension's settings - but this is far from ideal.

    This could probably be achieved using device dialplans (as has been suggested in some of the other threads) but does not solve my problem if a user is using the 3CX clients.

    So...
    1 - Is it possible to prevent one group from calling another?
    2 - Is it possible to allow extension 5111 to only be able to call extension 5333?

    I'm using v15.5 on Debian.

    Thanks for any help!
     
  2. expatel

    Joined:
    Apr 28, 2009
    Messages:
    3
    Likes Received:
    0
    Instead of blocking the outbound route, what happens if you create a fake trunk group, and route these calls out over the fake trunk group?
     
  3. hwcltjn

    Joined:
    Aug 16, 2017
    Messages:
    26
    Likes Received:
    1
    Good idea!
    I created a fake trunk pointing to 127.0.01 - registration definitely failed - but it doesn't work unfortunately, call is still routed to the extension.

    None of the other threads received answers from anyone at 3CX - could anyone tell us if this is possible?
     
  4. AndreasPo_3CX

    AndreasPo_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Aug 10, 2017
    Messages:
    138
    Likes Received:
    12
    Hi @hwcltjn,

    What you are trying to do can be achieved by adding exceptions to forwarding rules for each extension. Creating an outbound rule did not work because the call is internal and does not get routed through the outbound rule. Essentially you would have to go to every extension in Group A and add an exception for 5200-5299 (ranges are acceptable) and to every extension in Group B and add an exception for 5100-5199.
     
    AH2 likes this.
  5. hwcltjn

    Joined:
    Aug 16, 2017
    Messages:
    26
    Likes Received:
    1
    Thanks for the reply @AndreasPo_3CX
    That's what I suspected - hopefully there'll be a better way to do this in a not so distant release.
     
  6. AndreasPo_3CX

    AndreasPo_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Aug 10, 2017
    Messages:
    138
    Likes Received:
    12
    If you believe this is something that should be added you can post it as a feature request on our ideas section of the forum where it can be up-voted by other users and can be evaluated by the appropriate department.
     
    AH2 likes this.
  7. AH2

    AH2 New Member

    Joined:
    Mar 14, 2017
    Messages:
    112
    Likes Received:
    4
    Thanks, that works for me, hopefully that can be implemented on Group Settings.
     
Thread Status:
Not open for further replies.