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

Voicemail Notification notifies on a new message, but doesn't stop calling numbers in the list despite someone on the list accepting the message.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 12, 13
    • Fix Version/s: 12, 13
    • Component/s: VM Notify (Commercial)
    • Labels:
      None
    • Environment:

      FreePBX 12 Distribution, fully updated.

    • Sprint:
      Beta 13
    • ToDo:
    • Distro:
      FreePBX Distro

      Description

      Purchased the VM Notify module today and set up one notification. The list has 3 numbers in it prioritized as 1, 2, and then 3.

      A voice mail is left, priority 1 is called. Recipient accepts the message and the system hangs up the call. A success email is sent saying that the recipient has accepted. After the timeout has been reached, it then calls recipient priority 2. That recipient does not answer, so after a second retry and no answer, it then called recipient priority 3. This recipient then accepted and a success email was sent. After another retry timeout span, it started over again, calling recipient priority 1.

      I then had to remove all numbers from the list to force it to quit and it then sent a failure email.

      During this entire time, the voice mail was not in the mailbox anymore.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jfinstrom James Finstrom
                Reporter:
                thecodemonk Aaron Smith
              • 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.