Inbound authorization based on callerid without pin

VitalPBX Community Support General Discussion Inbound authorization based on callerid without pin

Up
0
Down
  • Post
    microvb
    Participant

    I have deployed VitalPBX for a client, and they are very happy with the result thus far.  It has proven to be much more stable than FreePBX, and is fairly intuitive with modern interface.

    There is one part of the business model which they are unable to implement using VitalPBX which appears there is something very close.  What they would like to do is setup a route (like the PIN verification route), using CallerID only — no pin prompt.  The feature in place which is very close, has the pin field as required.

    Is there any way to configure a list of numbers that are allowed to use specific trunks with specific dial plans assigned, that allows for outbound calling.  The flow works like this :

     

    1. Caller calls a specific number on the switch.
    2. Switch looks up callers caller id in database. If not listed, switch aborts the call with a Not In Service tone (or other tone that indicates the line is dead/inaccessible)
    3.  If listed in the database, switch then plays a dialtone or greeting, and allows caller to enter digits.
    4.  Digits are checked against a number plan, and if valid – call is routed to that number using the trunk assigned to that number plan.

    If such a feature doesn’t exist, could you please implement this.  I have been checking the system through every update and haven’t seen any change to the feature that comes close to what my client needs. The PIN is required for each number.

    0
Viewing 5 replies - 1 through 5 (of 5 total)
  • Replies

    We will analyze it your suggestion in deep with our team to give you a clear answer about it.

    0
    microvb
    Participant

    Could you please provide an update on this ?

    0

    This if for transit calls?

    You have a PBX, so the callers reach your PBX and if the number is in a DB, then, the caller is sent to a DISA?

    0
    microvb
    Participant

    I mentioned the flow in the original post as follows :

    1. Caller calls a specific number on the switch.
    2. Switch looks up callers caller id in database. If not listed, switch aborts the call with a Not In Service tone (or other tone that indicates the line is dead/inaccessible)
    3.  If listed in the database, switch then plays a dialtone or greeting, and allows caller to enter digits.
    4.  Digits are checked against a number plan, and if valid – call is routed to that number using the trunk assigned to that number plan.

    The feature you have in place that comes close, requires a PIN as mentioned when I first requested this. The request is to have the option to use Caller ID and a lookup-table in place of a PIN on that feature.

    0

    We pretend to release a new module named dynamic destinations, this module can be used with a Database (MySQL) or an URL to verify the CID Number, depending on the response of the database query or the URL, the caller will be sent to certain destinations defined in the same module. Check the attached picture

    0
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.