[HELP] MWI light on Cisco 7940/79xx? lights prematurely?

I’m using A@H with Asterisk version 1.2.1 with a Cisco 7940 running SIP 7.4
I’ve found that the MWI lamp (aka the red light on the handset) lights up as soon as or very shortly after the wav file for a Voicemail begins writing. This seems to be premature and causes a “race” and timing issue.

In example, i can watch the CLI of my A@H box and as soon as i see the log entry stating that the wav file has been opened for writing for a voicemail being left, the red MWI lamp on the cisco phone lights up within 0-15 seconds of the message beginning. However, if i have email notification setup of the VM, that email notification is not sent out until the WAV file is closed (the voicemail message is now finished recording)…

The problem this creates is if i’m an unknowing user and i see my phone’s MWI lamp light up, I immediately or very quickly access my voicemails on my phone and Comedian tells me that i have one new message but it’s completely blank (no audio). So being the unknowing user that I am, i assume that someone must have not wanted to leave a message and hung up or something of that nature and i just delete it. When what’s really going on is that there is a new wav file present but it’s still being written to because the caller is still recording his message but i prematurely deleted it before the caller was finished leaving the message. Any thoughts on this? Anyone seen this behavior? Any thoughts on having the MWI lamp not being lit until the wav file / message is actually done recording ?? It would definitely seem that the phone is getting the SIP NOTIFY message but isn’t it being sent prematurely? Or is that behavior “by design” ? Can the NOTIFY message be postponed till after the recording has stopped like the email notification does?

I hope i was clear enough in my message. Thanks in advance for any and all suggestions or information. Below is the snippet what i see going on in my CLI with sip debug on:

[quote] – Recording the message
– x=0, open writing: /var/spool/asterisk/voicemail/default/4202/INBOX/msg0001 format: wav49, 0x8abdc90
– x=1, open writing: /var/spool/asterisk/voicemail/default/4202/INBOX/msg0001 format: wav, 0x8abf5e8[/quote]

[quote]12 headers, 3 lines
Reliably Transmitting (no NAT) to
NOTIFY sip:4215@ SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bK47c49c53
From: “Unknown” sip:Unknown@;tag=as58811c8d
To: sip:4215@
Contact: sip:Unknown@
Call-ID: 22c44aef5097675715b673715249a3bd@
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 82

Messages-Waiting: yes
Message-Account: sip:asterisk@
Voice-Message: 1/14 (0/0)[/quote]

I’ve seen this same problem on other phones but never seen a solution.

I actually have this same problem with ABE2.5 and Polycom 501/601’s.

If I find a solution, I’ll let you know.