<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi all,<br>
what about <br>
1) link the /etc/asterisk/voicemail.conf to
/mnt/nfs/asterisk/etc/asterisk/voicemail.conf<br>
2) link /var/spool/asterisk/voicemail to
/mnt/nfs/asterisk/var/spool/asterisk/voicemail <br>
<br>
It works fine for me.<br>
BTW: if you chroot asterisk daemon remember to set the user UID to the
right one on each asterisk server.<br>
<br>
<br>
Josiah Bryan wrote:
<blockquote cite="mid200504121241.45880.jbryan@productiveconcepts.com"
type="cite">
<pre wrap="">On Tuesday 12 April 2005 11:49 am, Luki wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Also, what happens if for example, the user is accessing his VMB
on server 1 and changes his password, then travel to where server
2 is and tries to access his VMB? the config on server2 would
still have the old one.... so you need to sync voicemail.conf on
all servers too ...
</pre>
</blockquote>
<pre wrap="">If you use the realtime config via a DB, it should be OK. But I still
don't think that MWI will work properly if a message is left on server
A and user is actually registered on server B, which is NOT on the
same network and hence does NOT share the same voice mail spool. How
will B know there is a message left on A for the same user? Does
realtime share this info too? And if so, how does the message get
retrieved if B does not have access to files on server A, where the
actual message is?
</pre>
</blockquote>
<pre wrap=""><!---->
Why not just NFS mount the /var/spool/asterisk/voicemail directory from a
central server? That way, all servers share the same spool and the MWI will
get reflected on all servers.
-josiah
</pre>
</blockquote>
<br>
</body>
</html>