I'd like to know if anyone has a suggested fix for this... You have a 'cluster' of Asterisk servers that use DUNDi etc for registration redundancy, finding other phones etc. You have a separate Asterisk box for voicemail. For voicemail deposit/retrieval you trunk the call over to the voicemail server. This all works fine. No issues there. What about MWI though? Your phones register with the cluster, not with the voicemail server, and therefore the voicemail server has no knowledge of where the phones are and therefore cannot send out SIP NOTIFY messages to phones. This is a general architectural problem with Asterisk. Has anyone solved it? Are the developers working on fixing problems like this for 1.6? Doug.
For us the voicemail server doesn't have to know what phones are registered where. We have an externnotify script that drops x number of msgx.txt files into the respective voicemail folders after any call that goes through the voicemail server. x in this would be the number of messages. Since our servers are all exactly the same, we just blanket the script across all our call servers, but if you have specific servers where the phones are registered at, you can modify the SIP channel to update the db with server information and have the voicemail server just run the script across servers that that particular phone is currently registered with. The scripts we use are relatively lightweight, but can probably be turned into some sort of listening service to remove some of the ssh overhead required. Not a problem for us, but you might not like it much :) On Fri, 2006-10-06 at 11:49 -0600, Douglas Garstang wrote:> I'd like to know if anyone has a suggested fix for this... > > You have a 'cluster' of Asterisk servers that use DUNDi etc for registration redundancy, finding other phones etc. You have a separate Asterisk box for voicemail. For voicemail deposit/retrieval you trunk the call over to the voicemail server. This all works fine. No issues there. > > What about MWI though? Your phones register with the cluster, not with the voicemail server, and therefore the voicemail server has no knowledge of where the phones are and therefore cannot send out SIP NOTIFY messages to phones. > > This is a general architectural problem with Asterisk. Has anyone solved it? Are the developers working on fixing problems like this for 1.6? > > Doug. > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- Aaron Daniel Computer Systems Technician Sam Houston State University amdtech@shsu.edu (936) 294-4198
I did write some code once that worked but was not used in the end. The customer did a very clever and elaborate solution that did not involve asterisk. In the code when a call came in the local asterisk server would talk to a server on a socket on the main voicemail machine. The local/client code would redirect the MWI counter code to read from the main server socket instead of the local file system. The server side socket used similar asterisk code to count the messages on the remote server instead of on the local asterisk server. Then the normal asterisk code would trip the MWI light. The server address and whether to use the remote voicemail server counter were in the vm.conf file. It could handle about 500 queries per second without much cpu time. It was built back under the 1.2 or 1.1 code base, so it might not work under the 1.4 code base(which I have not looked at yet.) Race Vanderdecken Code Tyrant Somewhere near Asheville, NC. -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Douglas Garstang Sent: Friday, October 06, 2006 1:49 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] Voicemail MWI I'd like to know if anyone has a suggested fix for this... You have a 'cluster' of Asterisk servers that use DUNDi etc for registration redundancy, finding other phones etc. You have a separate Asterisk box for voicemail. For voicemail deposit/retrieval you trunk the call over to the voicemail server. This all works fine. No issues there. What about MWI though? Your phones register with the cluster, not with the voicemail server, and therefore the voicemail server has no knowledge of where the phones are and therefore cannot send out SIP NOTIFY messages to phones. This is a general architectural problem with Asterisk. Has anyone solved it? Are the developers working on fixing problems like this for 1.6? Doug. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users