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

D&U MODE-Ring Group CID stops working correctly when core updated from 14.0.28.83 to 14.0.28.85 or higher

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      Sprint 64
    • ToDo:
    • Asterisk Version:
      13
    • Distro:
      FreePBX Distro

      Description

      The caller ID on ring groups calls previously was set to the Fixed CID Value as specified in the ring group settings. After a recent update of Core, the caller ID being used on external calls is the extension number instead of the extension's external caller ID, the trunk caller ID, or the ring group caller ID. That is causing our calls to go out to cell phones with a four digit caller ID, which causes most phones to ignore the call as spam. After playing with different versions of Core, I found that the issue did not exist on 14.0.28.83. When updating to 14.0.28.85, the issue begins. That changelog for 14.0.28.85 shows two changes that are suspect. Note that all other modules are on the latest stable version.

      14.0.28.85: FREEI-2848 core with outbound CID
      14.0.28.84: FREEI-2738 PBX does not forward the original callerID to a misc destination

      Let me know if you need any additional info, traces, etc. An outline of the call flow is below.

      The call is coming from an external extension (6790 in this case). 6790 is dialing a ring group (24532). That ring group has a single entry of XXXXXX2558#. The caller ID setting on the ring group is set to Fixed CID Value of XXXXXX6666. When the call arrives on my cell phone, the caller ID is 6790 instead of XXXXXX6666 when I'm on 14.0.28.85.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jphilip Philip Joseph
                Reporter:
                kg4ysy kg4ysy
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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