Inbound Rule Wildcard DID at 12.5

Discussion in '3CX Phone System - General' started by joebocop, Mar 6, 2015.

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

    Joined:
    Dec 12, 2013
    Messages:
    96
    Likes Received:
    0
    Prior to v12.5, 3CX allowed the configuration of an "Inbound Rule" applying to every port on our 16-port Patton SN4316 VoIP gateway. This was convenient since the SN4316 is an analog device, and cannot detect a specific "DID" when it receives a call. We just used the " * " mask as the DID number, and assigned the rule to all 16 ports. "Any call coming into any of the 16 ports should be treated thus".

    In v12.5, this configuration is not permitted (see attached screen capture). This means that we must configure each of the 16 ports individually. If we need to make a quick change to the way inbound calls are handled, that means going through the interface and changing the settings on each port, for each of office hours and non-office hours.

    We are finding this inconvenient.

    Is there another way to get the "inbound rules" functionality to work with every port on an analog device at v12.5? Have I been using "Inbound Rules" incorrectly in the past?

    Thanks!
     

    Attached Files:

  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,429
    Likes Received:
    279
    Since it can not detect the DID - what is the point of the rule at all?
    Unless I am mistaken, do you not set the default route under the Gateway for Analog/T1/E1/etc type calls?

    Perhaps this too would cause additional maintenance in changing all of the routes quickly.
    Maybe point all the routes to a Dummy Extension which forwards. Then change the dummy extension when you need to make that quick change.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.