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

In Trunks module, "Hide Caller ID" option will cause the "Outbound Caller ID" field to disappear even though its entry is still being used in call routing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core - Trunks/Routing
    • Labels:
      None
    • Asterisk Version:
      13.22.0
    • Distro Version:
      12.7.6-1904-1.sng7
    • Distro:
      FreePBX Distro

      Description

      When setting up or editing a Trunk, there is an option that reads "Hide CallerID."  If that option is changed to "yes," then FreePBX appears to automatically add "hidden" to the beginning of the "Outbound Caller ID" field in the CNAM section.  That is not a bug.  That's expected operation.  Adding the word "hidden" to the Caller ID field is the standard method of engaging in Caller ID blocking.

      However, when the "Outbound Caller ID" field has the word "hidden" at the beginning (in quotes), as in "hidden" <2135551212> (whether it was put there by the above item or because I typed it manually), the GUI will then completely hide that field from the user.  That makes it impossible for the user to change the numerical CID <2135551212> that is sent along with the CNAM field "hidden" when calls are placed.  Blocking user access to this field is a bug, because the numerical portion of this field is still being used by FreePBX to build dialplans and is still used by Asterisk when routing calls.  Hiding the field creates the impression that the field is not being used and makes it impossible for the user to edit the field.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                martin_anderson Martin Anderson
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:

                  NextupJiraPlusStatus

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