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

Voicemail notify not sending out voice notifications

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 13
    • Fix Version/s: None
    • Component/s: VM Notify (Commercial)
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13
    • Distro Version:
      10.13.66 64bit
    • Distro:
      FreePBX Distro

      Description

      Works perfect when rollback to 13.0.8. All newer deletes/or moves voicemail to old, but will not dial any extensions or external numbers to notify. also get this error in fwconsole debug...
      OUT > [2016-May-12 22:17:02] [INFO] (enc/vmnotify-newvm.php:80) - vmnotify: inserted id 17 for 599@default message from callerid: 524
      OUT > [2016-May-12 22:17:02] [ERROR] (enc/vmnotify-newvm.php:108) - vmnotify failed to copy /var/spool/asterisk/voicemail/default/599/INBOX/msg0000* to /var/lib/asterisk/sounds/vmnotify/599/17 checking if another message is available
      Tested on clean install with same results as my working server.

        Gliffy Diagrams

          Attachments

            Issue Links

            duplicates

            Bug - A problem which impairs or prevents the functions of the product. FREEPBX-12304 Voicemail Notification not alerting

            • Minor - Minor loss of function, or other problem where easy workaround is present.
            • Closed

              Activity

                People

                • Assignee:
                  jfinstrom James Finstrom
                  Reporter:
                  donmiller Donald Miller
                • 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.