|Summary:||ASTERISK-00882: Sending prepended voicemail will crash *|
|Date Opened:||2004-01-20 11:35:54.000-0600||Date Closed:||2011-06-07 14:01:05|
|Description:||Apty of any type leaving voice mail message for b-pty. B-party listens to voicemail, prepends message and copies message to another user. System crash most of the time. I had it work once then attempted a second copy to another mailbox and system crashed. CVS-01/17/04-16:28:52|
|Comments:||By: Brian West (bkw918) 2004-01-21 01:13:12.000-0600|
prepend ... please give more details on what you are talking about because this is news to me...
By: fcs_1 (fcs_1) 2004-01-21 06:57:14.000-0600
Ok sure. My configuration is such that extensions.conf and voicemail.conf and sip.conf etc all use the a number id. So if I call 125 the voice mail for 125 will be in 125 voicemail box.
So leave a message for 125. I pickup that message from phone 125 thru comedian mail front door, enter 125,passwd, hear menu. Press 1, Listen to message, press 8 to copy/send message to another user, enter 126 (another phone), press 1 to prepend a recorded note, then #, message saved, crash. I tried this several times for the last 2 weeks and * crashed for me everytime. Monday I actually had it work one time then * kept crashing.
When it does not work. It does not remove the message waiting from 125 and when you listen to the message again in 125 it now has your added recorded comment. No copy was sent to 126.
Also another note not related to crash: When you record a message for a voicemail box user could a # trigger a delete/send/replay your recording instead of "your message sent" and return ? * currently leaves no chance for someone to change their minds on what they wanted to say.
edited on: 01-21-04 06:43
By: Brian West (bkw918) 2004-01-23 13:32:21.000-0600
i'm not seeing this bug.. I have tried many times to recreate this bug. What formats are you using in your voicemail.conf file?
By: fcs_1 (fcs_1) 2004-01-23 15:30:22.000-0600
using format=wav49|gsm|wav. Need any other info ? I can make it happen anytime.
By: fcs_1 (fcs_1) 2004-01-24 11:38:57.000-0600
tested CVS 01/23/04-23:50:34
After voicemail says to user "your message has been saved" * crash. Last two lines on console:
--User ended message by pressing #
--Playing 'vm-msgsaved' (language 'en')
[root@pbx]# Now I am at the system prompt and * has died
By: Brian West (bkw918) 2004-01-24 12:19:29.000-0600
just for the sake of this take the format line and make it format = gsm only and see. I suspect thats what the problem is. I will try it with more formats on my end later today.
By: fcs_1 (fcs_1) 2004-01-24 16:26:39.000-0600
Tried gsm only. Instead of attempting to write 3 files it writes one but it still crashed. Same as above.
Using gsm only will not be the answer since Windows Media 9 can't paly the files from email.
One other note I can record, play, send, leave a message from outside calls just can't forward a prepended message without a crash.
It seems it does not matter if I prepend a message. I am not able to forward a message without a crash.
Is there any issues with box setup like a missing recording or parm in the voicemail.conf file ?
edited on: 01-24-04 16:18
By: fcs_1 (fcs_1) 2004-01-24 17:11:33.000-0600
I made sure that two extensions had name recordings. This time I did forward the original message left at ext 125 to ext 295 without a prepended recording and it worked. Picking up the message at 295, then prepending a recording and sending it back to 125 cause * to crash as described above.
After restarting * I received MWI at station 125. The prepended recording was there in box 125 and 295. Should the message only be at 125 and not also in the senders mailbox 295 ?
edited on: 01-24-04 16:57
edited on: 01-24-04 16:59
By: philipp2 (philipp2) 2004-01-25 10:14:25.000-0600
I tested this today with CVS-01/13/04-19:02:42 (using a BT 101 behind NAT).
No crash of * that I could confirm. I forwarded a message (0003) that was recorded in Oct. 2003 [that old message I can listen to just fine, but when I forward it I get the error warning as indicated below]. I also noticed that suddenly the forwarded message file 0003.gsm has the executable bit set, while 0003.wav does not, and there is now a new file msg0003-prepend.WAV (also executable) in the originator's directory - shouldn't that just live in the recipients directory? All other voice recordings don't have x set for root.
P.S.: Just for your info: The previous message 0002 *does* give me trouble, i.e. I cannot listen to it because * just hangs up on me when I try to play it (WARNING: format_wav_gsm.c:194 check_header: Does not say data). This is due to a 0 byte .gsm and a 60 byte .wav file. Anyway, this is a different story (can't remember the bug # for this); also I remember having seen someone submitting a patch to fix headers for Windows Media Player playback which *might* be related.
-- Playing 'vm-extension' (language 'en')
-- Playing 'vm-forwardoptions' (language 'en')
-- Playing 'beep' (language 'en')
-- x=0, open writing: /var/spool/asterisk/voicemail/default/8755/Old/msg0003-prepend format: gsm, 0x811e028
-- x=1, open writing: /var/spool/asterisk/voicemail/default/8755/Old/msg0003-prepend format: wav49, 0x811d3a0
-- User ended message by pressing #
Jan 25 16:31:29 WARNING: format_wav_gsm.c:194 check_header: Does not say data
Jan 25 16:31:29 WARNING: file.c:769 ast_readfile: Unable to open /var/spool/asterisk/voicemail/default/8755/Old/msg0003.WAV
-- Playing 'vm-msgsaved' (language 'en')
== Parsing '/var/spool/asterisk/voicemail/default/8755/Old/msg0003.txt': == Parsing '/var/spool/asterisk/voicemail/default/8755/Old/msg0003.txt': Found
-- Playing 'vm-message' (language 'en')
-- Playing 'vm-saved' (language 'en')
-- Playing 'vm-goodbye' (language 'en')
By: Brian West (bkw918) 2004-01-25 11:26:34.000-0600
using latest CVS because we applied a recent fix to format_wav_gsm.c that fixed the files not working with wmp.
By: fcs_1 (fcs_1) 2004-01-25 11:35:40.000-0600
That patch does not solve problem with * crash only WMP error at end of file when it is played.
By: fcs_1 (fcs_1) 2004-01-26 13:41:00.000-0600
bkw do you need any other info ? For those who think they may offer * PBX as a solution to end users this is a critical path bug for deployment.
By: Brian West (bkw918) 2004-01-26 18:47:10.000-0600
Find kram or myself on irc and we will have to get in your box and watch it.
By: fcs_1 (fcs_1) 2004-01-26 19:29:56.000-0600
bkw: side note: I am not on irc. Do you have a recomendation for win client software ? None of my Linux systems are running a gui and I am assuming irc is gui ??
By: Brian West (bkw918) 2004-01-26 21:04:31.000-0600
use BitchX on those systems .. thats what I use
By: fcs_1 (fcs_1) 2004-01-27 14:15:36.000-0600
bkw918: ok have BitchX and looked for you ar irc.freenode.net #bkw_ So if this is correct any times you are normally on ?
By: Brian West (bkw918) 2004-01-28 00:56:37.000-0600
#asterisk my nick is bkw_
By: fcs_1 (fcs_1) 2004-01-28 16:16:58.000-0600
Thanks to bkw for assistance. I have been running only asterisk and not safe_asterisk.
Running in safe_asterisk the system does not crash. A line I do not see when it crashes under run "asterisk" is "Parsing '/var/spool/asterisk/voicemail/default/125/INBOX/msg0000.txt'" In run asterisk mode it crashes before this line prints to screen and dies right after I hear the vm-goodbye recording.
One thing that happened under safe_asterisk is that now the mailbox user that had the original message and prepended a voice message received the prepend message as a new message. So 125 prepends a message to send to 295, Both 125 and 295 received the same prepended message. Is this correct ?
By: fcs_1 (fcs_1) 2004-01-29 07:38:11.000-0600
I think the problem might be related to the process return handling. Voicemail pops out of voicemail menu after you press # to save the prepend message as it sends the message under safe_asterisk and crash under asterisk. You should return back to the voice mail menu instead of returning back to the extensions.conf processing.
So two problems:
1. voicemail should stay in the menu until user wants out. Maybe that last # was not cleared after the prepend and it returns.
2. Asterisk not returning properly to extensions.conf processing once it sends message.
By: fcs_1 (fcs_1) 2004-02-02 06:49:19.000-0600
Original problem of asterisk crash using asterisk and not safe_Asterisk still is a bug problem.
By: Brian West (bkw918) 2004-02-02 11:13:44.000-0600
Yes we know its still a problem and its on my list. :P