[Asterisk-Users] MWI behavior change?

[Lenny Tropiano]

Worked like a champ!

(output from ngrep port 5060)
#
U 216.30.27.132:5060 -> 192.70.239.150:5060
  NOTIFY sip:lenny at 192.70.239.150 SIP/2.0..Via: SIP/2.0/UDP
216.30.27.132:5060;branch=25009d9b..From: "asterisk"
<sip:asterisk at 216.30.27.132>;tag=19a2df9f..Contact:
<sip:asterisk at 216.30.27.132>..To: <sip:lenny at 192.70.239.150>..Call-ID:
526fc5e93a6300a664f23a637726454e at 216.30.27.132..CSeq: 102
NOTIFY..User-Agent: Asterisk PBX..Event: message-summary..Content-Type:
application/simple-message-summary..Content-Length: 35....Message-Waiting:
no.Voicemail: 0/3.

-----Original Message-----
From: Mark Spencer [mailto:markster at digium.com] 
Sent: Wednesday, March 26, 2003 6:08 PM
To: asterisk-users at lists.digium.com
Cc: info at voiping.com
Subject: Re: [Asterisk-Users] MWI behavior change?


How about we say "yes" only if there are new messages....

cvs update and let me know if that worked.

Mark

On Wed, 26 Mar 2003, Lenny Tropiano / asterisk.org Mailing list wrote:

> Looking at the cvs rdiff from 1.5 to 1.6, apparently the behavior 
> changed?
>
> The old way it just checked "inbox" for new messages and turned on the 
> MWI.  Now it seems to add the new+old to turn on the Message Waiting 
> Indicator.  Personally after I've listened to the messages and saved 
> them in a Old "folder" it shouldn't count that for the MWI. I would 
> prefer the older behavior, and I think that would be more correct.
>
> Old Way: snprintf(tmp, sizeof(tmp), "Message-Waiting: %s\n", hasmsgs ? 
> "yes" : "no");
>
> New Way: snprintf(tmp, sizeof(tmp), "Message-Waiting: %s\n", (newmsgs 
> + oldmsgs) ? "yes" : "no");
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com 
> http://lists.digium.com/mailman/listinfo/asterisk-users
>