[exit-FAILED@macro-vm:1]

FreePBX Tips and Tricks
1

This is a new install running FreePBX version 2.6.0.3. Everything is working fine except when attempting to access the VM app. Here is an excerpt from the log when just trying to leave a voicemail for x3031.

-- Executing [s-CHANUNAVAIL@macro-vm:2] VoiceMail("SIP/3030-b7bf5d78", "3031@default|u") in new stack
-- Executing [s-CHANUNAVAIL@macro-vm:3] Goto("SIP/3030-b7bf5d78", "exit-FAILED|1") in new stack
-- Goto (macro-vm,exit-FAILED,1)
-- Executing [exit-FAILED@macro-vm:1] Playback("SIP/3030-b7bf5d78", "im-sorry&an-error-has-occured") in new stack
-- <SIP/3030-b7bf5d78> Playing 'im-sorry' (language 'en')
-- <SIP/3030-b7bf5d78> Playing 'an-error-has-occured' (language 'en')
-- Executing [exit-FAILED@macro-vm:2] GotoIf("SIP/3030-b7bf5d78", "0?exit-RETURN|1") in new stack
-- Executing [exit-FAILED@macro-vm:3] Hangup("SIP/3030-b7bf5d78", "") in new stack
2

This was caused by a malformed voicmail.conf file. Here is part of the file:

[general]
#include vm_general.inc
#include vm_email.inc
[default]

[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
3999 => 3999,Support VM,[email protected],attach=yes|saycid=no|envelope=no|delete=no
3030 => 3030,test,attach=no|saycid=no|envelope=no|delete=no
3031 => 3031,test2,attach=no|saycid=no|envelope=no|delete=no
(END)

I just deleted all of the empty brackets, issued amportal restart and it works fine.

Anyone have any idea where the empty brackets came from ??