asterisk users - Dec 2008 - Asterisk 1.6.0.1, IMAP Voicemail storage and temporary greetings.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm have a bit of a problem with temporary greetings.

I'm using 1.6.0.1 with IMAP storage.   If I go into comedian mail and
record a temporary greeting, I get a Message [0] on my IMAP server.  In
addition, I get
/var/spool/asterisk/voicemail/default/134/temp.[gsm|wav|WAV] files.

I have imapgreetings=no in the voicemail configuration file, as well as
temporary greeting notification.

If I go into commedian mail and delete my temporary greeting, Alison
tells me that the temporary greeting has been deleted.   I then am
immediately told that I have a temporary greeting set.   The files are
still in the spool directory and Message [0] is still in my mailbox.

If I delete Message [0], I still get the notification.

If I delete the files in /var/spool/asterisk/voicemail/defaults/134/, I
no longer get the notification.

It appears as though * is looking for the temporary greeting on the
local box, which is what I'd expect because of my configuration option.
 It also appears that * isn't deleting the file(s) when I ask it to.  It
also isn't taking them out of IMAP, which is compounded by the fact that
I don't think that based on my configuration there should be an email
anyway.

Has anyone seen this behavior and found a fix for it?

TIA,

Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFJNzDBCFu3bIiwtTARArEtAJ0aTBxevdz886GXfjyRqier/sAaKQCfdwlm
iPVZDS0Sbq2vyjHal++vJiQ=dW2m
-----END PGP SIGNATURE-----

On Wednesday 03 December 2008 19:22:09 Barry L. Kline
wrote:
> It appears as though * is looking for the temporary greeting on the
> local box, which is what I'd expect because of my configuration option.
>  It also appears that * isn't deleting the file(s) when I ask it to. 
It
> also isn't taking them out of IMAP, which is compounded by the fact
that
> I don't think that based on my configuration there should be an email
> anyway.
You might want to try 1.6.0.3-rc1, released yesterday.  In the fixes were
included something similar to this.  In case 1.6.0.3-rc1 does not fix this
issue, please open a report on http://bugs.digium.com.

-- 
Tilghman