New Voicemail problem

[stuck]

My voicemail suddenly developed a problem with email so I restored from a backup configuration through backup and restore. That wiped out my greetings and the entire VM settings. When people call in after few rings instead of VM picking up it just hangs up. When I go to try and record a new greeting I see this on the CLI. As soon as I hit the option to record a new greeting, it instructs me to record then press # then the beep and then silence, it disconnects from asterisk and I can't record any messages. Then couple of seconds later the PC motherboard beeps once.



-- Executing [*97@from-internal:106] VoiceMailMain("SIP/505-b7d01ea0", "505@default") in new stack
-- <SIP/505-b7d01ea0> Playing 'vm-password' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'vm-youhave' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'vm-no' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'vm-messages' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'vm-opts' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'vm-options' (language 'en')
-- Recording the message
-- <SIP/505-b7d01ea0> Playing 'vm-rec-unv' (language 'en')
-- <SIP/505-b7d01ea0> Playing 'beep' (language 'en')
pbx*CLI>
Disconnected from Asterisk server
Executing last minute cleanups
root@pbx:~ $ /usr/sbin/safe_asterisk: line 117: 4337 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} </dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
cat: /var/run/asterisk.pid: No such file or directory
Automatically restarting Asterisk.
mpg123: no process killed

 

[darmock]

What version of asterisk are you running? This error is what came out with verison 1.6 beta 2 exactly the same message! if this is occuring on version 1.4 then we need to know why. So did you run update-source or update-source16?

Tom

 

[stuck]

Thanks for replying Tom,
I'm using Asterisk 1.4 I've only done the update-scripts and update-fixes. Never done update-source at all.

 

[darmock]

Thanks will look into it.

Tom

 

[stuck]

When I get a chance later I'll post the CLI output of a call that is routed to the VM and gets immediately hung up.
Please let me know if you need additional CLI output...

 

[stuck]

This is the last part of my CLI output when a call is directly routed to the VM and hung up by PIAF

-- Executing [s@macro-user-callerid:23] NoOp("SIP/887XXX-b7d040e8", "Using C allerID "AUBURN HTS, MI" <XXXXXXXXXX>") in new stack
-- Executing [s@macro-vm:2] Set("SIP/887XXX-b7d040e8", "VMGAIN=""") in new s tack
-- Executing [s@macro-vm:3] GotoIf("SIP/887XXX-b7d040e8", "1?vmx|1") in new stack
-- Goto (macro-vm,vmx,1)
-- Executing [vmx@macro-vm:1] GotoIf("SIP/887XXX-b7d040e8", "0?s-BUSY|1") in new stack
-- Executing [vmx@macro-vm:2] Set("SIP/887XXX-b7d040e8", "MODE=busy") in new stack
-- Executing [vmx@macro-vm:3] GotoIf("SIP/887XXX-b7d040e8", "1?notdirect") i n new stack
-- Goto (macro-vm,vmx,5)
-- Executing [vmx@macro-vm:5] NoOp("SIP/887XXX-b7d040e8", "Checking if ext 5 05 is enabled: disabled") in new stack
-- Executing [vmx@macro-vm:6] GotoIf("SIP/887XXX-b7d040e8", "1?s-BUSY|1") in new stack
-- Goto (macro-vm,s-BUSY,1)
-- Executing [s-BUSY@macro-vm:1] NoOp("SIP/887XXX-b7d040e8", "BUSY voicemail ") in new stack
-- Executing [s-BUSY@macro-vm:2] Macro("SIP/887XXX-b7d040e8", "get-vmcontext |505") in new stack
-- Executing [s@macro-get-vmcontext:1] Set("SIP/887XXX-b7d040e8", "VMCONTEXT =default") in new stack
-- Executing [s@macro-get-vmcontext:2] GotoIf("SIP/887XXX-b7d040e8", "0?200: 300") in new stack
-- Goto (macro-get-vmcontext,s,300)
-- Executing [s@macro-get-vmcontext:300] NoOp("SIP/887XXX-b7d040e8", "") in new stack
-- Executing [s-BUSY@macro-vm:3] VoiceMail("SIP/887XXX-b7d040e8", "505@defau lt|b") in new stack
== Spawn extension (macro-vm, s-BUSY, 3) exited non-zero on 'SIP/887XXX-b7d040 e8' in macro 'vm'
== Spawn extension (macro-vm, s-BUSY, 3) exited non-zero on 'SIP/887XXX-b7d040 e8'


I wonder if update-source would fix the VM problem

 

[andygee]

I was having the same issue with voicemail and when I did update-source on mine it resolved the issue for me.

Andy

This is the last part of my CLI output when a call is directly routed to the VM and hung up by PIAF

-- Executing [s@macro-user-callerid:23] NoOp("SIP/887XXX-b7d040e8", "Using C allerID "AUBURN HTS, MI" <XXXXXXXXXX>") in new stack
-- Executing [s@macro-vm:2] Set("SIP/887XXX-b7d040e8", "VMGAIN=""") in new s tack
-- Executing [s@macro-vm:3] GotoIf("SIP/887XXX-b7d040e8", "1?vmx|1") in new stack
-- Goto (macro-vm,vmx,1)
-- Executing [vmx@macro-vm:1] GotoIf("SIP/887XXX-b7d040e8", "0?s-BUSY|1") in new stack
-- Executing [vmx@macro-vm:2] Set("SIP/887XXX-b7d040e8", "MODE=busy") in new stack
-- Executing [vmx@macro-vm:3] GotoIf("SIP/887XXX-b7d040e8", "1?notdirect") i n new stack
-- Goto (macro-vm,vmx,5)
-- Executing [vmx@macro-vm:5] NoOp("SIP/887XXX-b7d040e8", "Checking if ext 5 05 is enabled: disabled") in new stack
-- Executing [vmx@macro-vm:6] GotoIf("SIP/887XXX-b7d040e8", "1?s-BUSY|1") in new stack
-- Goto (macro-vm,s-BUSY,1)
-- Executing [s-BUSY@macro-vm:1] NoOp("SIP/887XXX-b7d040e8", "BUSY voicemail ") in new stack
-- Executing [s-BUSY@macro-vm:2] Macro("SIP/887XXX-b7d040e8", "get-vmcontext |505") in new stack
-- Executing [s@macro-get-vmcontext:1] Set("SIP/887XXX-b7d040e8", "VMCONTEXT =default") in new stack
-- Executing [s@macro-get-vmcontext:2] GotoIf("SIP/887XXX-b7d040e8", "0?200: 300") in new stack
-- Goto (macro-get-vmcontext,s,300)
-- Executing [s@macro-get-vmcontext:300] NoOp("SIP/887XXX-b7d040e8", "") in new stack
-- Executing [s-BUSY@macro-vm:3] VoiceMail("SIP/887XXX-b7d040e8", "505@defau lt|b") in new stack
== Spawn extension (macro-vm, s-BUSY, 3) exited non-zero on 'SIP/887XXX-b7d040 e8' in macro 'vm'
== Spawn extension (macro-vm, s-BUSY, 3) exited non-zero on 'SIP/887XXX-b7d040 e8'


I wonder if update-source would fix the VM problem

 

[stuck]

Ditto,
I did the samething just now, and everything is working again. Thanks