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

XACT Dialer - dial prefix is not working

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Broadcast (Commercial)
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • Asterisk Version:
      13.14.0
    • Distro Version:
      13.0
    • Distro:
      FreePBX Distro

      Description

      specifying a dial prefix is not working. For example I have a group called TEST and a dial number 065111702. I set up a campaign with the TEST group and with dial prefix set to 8.
      I have an outbound route with pattern 806511XXXX.
      That is not working.
      If I change the dial number to 8065111702 and do not specify any dial prefix it works fine.

        Gliffy Diagrams

          Attachments

          1. asterisk -rvvv trace.txt
            3 kB
            Jean-Olivier HEDOU
          2. Broadcast campaigns - Group options.JPG
            41 kB
            Jean-Olivier HEDOU
          3. Broadcast campaigns - New campaign.JPG
            107 kB
            Jean-Olivier HEDOU
          4. Broadcast campaigns - Numbers to call.JPG
            40 kB
            Jean-Olivier HEDOU
          5. Outbound Route Dial Patterns.JPG
            67 kB
            Jean-Olivier HEDOU
          6. Outbound Route Settings.JPG
            68 kB
            Jean-Olivier HEDOU

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                johedou Jean-Olivier HEDOU
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Feedback Requested:

                  NextupJiraPlusStatus

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