See this thread on another forum also: http://pbxinaflash.com/forum/showthread.php?t=2851
I have a couple installs that do something very very similar, but i haven’t been able to figure out what triggers it.
System Details:
FreePBX 2.5.1.0
Running Asterisk Version : Asterisk 1.4.21.2
Asterisk Source Version : 1.4.21.2
Zaptel Source Version : 1.4.12.1
Libpri Source Version : 1.4.7
Addons Source Version : 1.4.7
All FreePBX modules up to date.
-- Goto (macro-get-vmcontext,s,300)
-- Executing [[email protected]:300] NoOp("SIP/1347422825-b7907c68", "") in new stack
-- Executing [[email protected]:2] Set("SIP/1347422825-b7907c68", "VMGAIN=""") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?vmx|1") in new stack
-- Goto (macro-vm,vmx,1)
-- Executing [[email protected]:1] GotoIf("SIP/1347422825-b7907c68", "0?s-NOANSWER|1") in new stack
-- Executing [[email protected]:2] Set("SIP/1347422825-b7907c68", "MODE=unavail") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?notdirect") in new stack
-- Goto (macro-vm,vmx,5)
-- Executing [[email protected]:5] NoOp("SIP/1347422825-b7907c68", "Checking if ext 500 is enabled: ") in new stack
-- Executing [[email protected]:6] GotoIf("SIP/1347422825-b7907c68", "1?s-NOANSWER|1") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?vmx|1") in new stack
-- Goto (macro-vm,vmx,1)
-- Executing [[email protected]:1] GotoIf("SIP/1347422825-b7907c68", "0?s-NOANSWER|1") in new stack
-- Executing [[email protected]:2] Set("SIP/1347422825-b7907c68", "MODE=unavail") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?notdirect") in new stack
-- Goto (macro-vm,vmx,5)
-- Executing [[email protected]:5] NoOp("SIP/1347422825-b7907c68", "Checking if ext 500 is enabled: ") in new stack
-- Executing [[email protected]:6] GotoIf("SIP/1347422825-b7907c68", "1?s-NOANSWER|1") in new stack
-- Goto (macro-vm,s-NOANSWER,1)
-- Executing [[email protected]:1] Macro("SIP/1347422825-b7907c68", "get-vmcontext|500") in new stack
-- Executing [[email protected]:1] Set("SIP/1347422825-b7907c68", "VMCONTEXT=default") in new stack
-- Executing [[email protected]:2] GotoIf("SIP/1347422825-b7907c68", "0?200:300") in new stack
-- Goto (macro-get-vmcontext,s,300)
-- Executing [[email protected]:300] NoOp("SIP/1347422825-b7907c68", "") in new stack
-- Executing [[email protected]:2] Set("SIP/1347422825-b7907c68", "VMGAIN=""") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?vmx|1") in new stack
-- Goto (macro-vm,vmx,1)
-- Executing [[email protected]:1] GotoIf("SIP/1347422825-b7907c68", "0?s-NOANSWER|1") in new stack
-- Executing [[email protected]:2] Set("SIP/1347422825-b7907c68", "MODE=unavail") in new stack
-- Executing [[email protected]:3] GotoIf("SIP/1347422825-b7907c68", "1?notdirect") in new stack
-- Goto (macro-vm,vmx,5)
-- Executing [[email protected]:5] NoOp("SIP/1347422825-b7907c68", "Checking if ext 500 is enabled: ") in new stack
-- Executing [[email protected]:6] GotoIf("SIP/1347422825-b7907c68", "1?s-NOANSWER|1") in new stack
-- Goto (macro-vm,s-NOANSWER,1)
-- Executing [[email protected]:1] Macro("SIP/1347422825-b7907c68", "get-vmcontext|500") in new stack
-- Executing [[email protected]:1] Set("SIP/1347422825-b7907c68", "VMCONTEXT=default") in new stack
-- Executing [[email protected]:2] GotoIf("SIP/1347422825-b7907c68", "0?200:300") in new stack
-- Goto (macro-get-vmcontext,s,300)
I have no idea whats triggering it. PARK was not involved. It was one lady calling in, and interacting with the voice mail of one of the extensions (500). VMX is NOT turned on, and there are NO follow me settings. The extension is the destination for two inbound routes. Its a fairly straightforward config.
With default logging settings, this will fill up the entire hard disk with log entries in about 12 hours. The PBX largely continues to function when in this status, but its slow to respond to ssh and web connections (for obvious reasons), if it responds at all. A reboot is required to clear the condition.
Anyone experiencing this type of issue - please post your CLI outputs and any important system details here.