<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Russell,<br>
<br>
I appreciate the idea you are trying to implement and the challenges
that you are faced with in dealing with external changes to the
voicemail box. You may still be able to use event based techniques with
an IMAP connection using the IDLE option in imap. The imap server
should notify you of changes to the box so that you don't have to keep
polling it. You would still need to figure out if the change
notification from the imap server involved the delivery of a new voice
message since an email box would likely be storing regular email as
well.<br>
<br>
That said, you may still be faced with using a polling technique. I
would definitely vote for having a configurable polling interval.
Currently polling every 10 seconds is far to frequent for the majority
of cases. Based on your event oriented approach it may be possible to
get the best of both worlds - event and polling based. To have fast MWI
indication it may be very reasonable for the voicemail system to
generate an event indicating that the voicemail box has been changed
and it may also be reasonable to also have a slower/longer configurable
polling interval in much the same way that an email client polls for
new messages. That way when the voicemail system changes the box the
indication will be pretty much immediate however, when the email system
changes the box, the indication could be updated at a much slower rate
- but most importantly a configurable one that will allow the system
managers to decide how frequently a box is polled for changes allowing
them to decide what is most ideal for their users.<br>
<br>
Russell Bryant wrote:
<blockquote cite="mid460AA6F8.7070100@digium.com" type="cite">I have
been working on a generic event system for Asterisk. As a part of this
project, I have converted the way that Asterisk handles message waiting
indication to be event based instead of polling based.
<br>
<br>
For example, instead of chan_sip checking each mailbox every 10 seconds
to see if there has been a change, it now waits for app_voicemail to
generate an event to indicate that has a change has been made.
<br>
<br>
However, I just realized a pretty big problem with this approach.
app_voicemail does not know every time that a mailbox gets changed. It
only knows about the instances where it gets changed by a caller.
There are other ways voicemail can get modified, such as with a web
based voicemail interface, or an email client in the case of using IMAP
storage.
<br>
<br>
If anyone has any thoughts on the subject, I would be interested to
hear them. I can probably still keep going with this and still get MWI
shared between servers. However, it may mean that the change won't
have the efficiency gain that I had hoped for. app_voicemail may have
to do its own polling of mailboxes that have been subscribed to so that
it knows about changes.
<br>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<table border="0" cellpadding="2" cellspacing="0" width="569">
<tbody>
<tr bgcolor="#000099" valign="middle">
<td colspan="2"><font color="#ffffff"
face="Verdana, Arial, Helvetica, sans-serif" size="2"><strong>Bob
Atkins </strong></font><font color="#ffffff"> </font></td>
</tr>
<tr valign="middle">
<td colspan="2"><font face="Verdana, Arial, Helvetica, sans-serif"
size="1"><em>President/CEO</em></font></td>
</tr>
<tr valign="middle">
<td width="233">
<p align="center"><font
face="Verdana, Arial, Helvetica, sans-serif" size="1"><b><font
color="#000080"><span
style="font-weight: bold; font-family: Trebuchet MS;"><a
href="http://www.digilink.net"><img
src="cid:part1.06040605.06090601@digilink.net" alt="DigiLink, Inc."
style="border: 0px solid ; width: 216px; height: 48px;"></a></span></font></b><br>
<font color="#006600">Business Inter-net-working</font><br>
<font color="#000099"><strong><em>The Cure for the Common ISP!</em></strong></font></font></p>
</td>
<td width="328">
<p align="right"><font color="#666666"
face="Verdana, Arial, Helvetica, sans-serif" size="1">Phone: </font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1">(310) 577-9450<br>
</font><font color="#666666"
face="Verdana, Arial, Helvetica, sans-serif" size="1">Fax: </font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1">(310) 577-3360</font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1"><br>
<font color="#666666">eMail:</font> <a class="moz-txt-link-abbreviated" href="mailto:bob@digilink.net">bob@digilink.net</a><br>
</font></p>
</td>
</tr>
</tbody>
</table>
<p> </p>
</div>
</body>
</html>