[asterisk-bugs] [Asterisk 0015717]: MWI is not sent to a SIP phone upon registration, but is after the mailbox is updated/checked

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Aug 21 16:53:06 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15717 
====================================================================== 
Reported By:                natmlt
Assigned To:                kpfleming
====================================================================== 
Project:                    Asterisk
Issue ID:                   15717
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 212162 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-08-13 19:21 CDT
Last Modified:              2009-08-21 16:53 CDT
====================================================================== 
Summary:                    MWI is not sent to a SIP phone upon registration,
but is after the mailbox is updated/checked
Description: 
chan_sip and app_voicemail are both configured to use realtime for
configuration; additionally, app_voicemail is configured to use ODBC for
message storage.

When a SIP phone registers, and the mailbox assigned to that SIP peer has
unread messages in it, the phone does *not* receive a MWI notification upon
registration. However, any action taken to cause app_voicemail to check the
status of the mailbox (leaving a message, deleting a message, calling in
just to hear how many messages are present) immediately sends a proper MWI
notification to the phone. In this configuration, the SIP phone is *not*
subscribing for MWI notification, it's relying on Asterisk's default 'push'
notification mechanism.

It would appear that the SIP phone registration, which results in an
internal subscription to the voicemail box, does not actually cause
app_voicemail to check the mailbox's status as it should.
====================================================================== 

---------------------------------------------------------------------- 
 (0109490) svnbot (reporter) - 2009-08-21 16:53
 https://issues.asterisk.org/view.php?id=15717#c109490 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 213699

_U  branches/1.6.1/
U   branches/1.6.1/apps/app_voicemail.c

------------------------------------------------------------------------
r213699 | kpfleming | 2009-08-21 16:53:06 -0500 (Fri, 21 Aug 2009) | 18
lines

Merged revisions 213697 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

........
  r213697 | kpfleming | 2009-08-21 16:39:51 -0500 (Fri, 21 Aug 2009) | 12
lines
  
  Ensure that realtime mailboxes properly report status on subscription.
  
  This patch modifies app_voicemail's response to mailbox status
subscriptions
  (via the internal event system) to ensure that a subscription triggers
an
  explicit poll of the mailbox, so the subscriber can get an immediate
cached
  event with that status. Previously, the cache was only populated with
the
  status of non-realtime mailboxes.
  
  (closes issue https://issues.asterisk.org/view.php?id=15717)
  Reported by: natmlt
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=213699 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-21 16:53 svnbot         Checkin                                      
2009-08-21 16:53 svnbot         Note Added: 0109490                          
======================================================================




More information about the asterisk-bugs mailing list