Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-6893

Unknown/Blocked Caller ID management for each DID Inbound Route (not Globally like provided by Blacklist module).

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.11
    • Fix Version/s: None
    • Component/s: Blacklist
    • Environment:

      FreePBX Distro 4.211.64-7 / Asterisk 11.5.1 and FreePBX 2.11

    • ToDo:
    • Distro Version:
      4.211.64-7
    • Distro:
      FreePBX Distro

      Description

      Providing a way to manage (to let user to e.g. Hangup an incoming call) unknown/blocked incoming callers (read Note below) for a very specific DID Inbound Route other than for all inbound routes defined in a system.

      Note:
      Unknown/Blocked Incoming Callers: meaning that each external incoming calls that announce itself with "no Caller ID" appearing with <> or UNKNOWN labels (in CDR or, e.g., into the FAX List) it should be considered here.

      In particular I saw a reference on the "CallerID Number" parameter (see help tool tip) available into each Incoming Route's settings page but it seems not actually implemented as described.

      As reference please read the Forum's thread:

      http://www.freepbx.org/forum/general-help/unknownblocked-caller-id-management-for-each-did-inbound-route-and-not-globally

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tm1000 Andrew Nagy
                  Reporter:
                  parnassus parnassus
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.