<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Mike:<o:p></o:p></p><p class=MsoNormal>I’m using Voyage for something quite different but have similar concerns for my product.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have had very good results with the Voyage read only mode and not having problems with unrecoverable crashes. I often don’t bother to shut down formally and just pull the plug with no ill effect. The problem of a place to write for temporary info is well done since it’s all in ram. The more permanent stuff is usually written back when the card is shut down. I believe it’s possible to make some parts of the card always writeable.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If your application of Asterix would support this I suggest that you operate a host server that holds the critical nonvolatile stuff for the users (call logs etc.). Since a VOIP system is always connected to the web to be useful sending small data (call records and even voice mail) to a server is small overhead for a really reliable device (and may create an additional revenue option). I suggested this for an application that had to run in an Asus router and it worked very well. <o:p></o:p></p><p class=MsoNormal> Demian<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText>Date: Wed, 21 Sep 2011 19:00:47 +1000<o:p></o:p></p><p class=MsoPlainText>From: Michael Knill <<a href="mailto:michael.knill@ipcsolutions.com.au">michael.knill@ipcsolutions.com.au</a>><o:p></o:p></p><p class=MsoPlainText>Subject: [Voyage-linux] Voyage, Asterisk and Voyage One<o:p></o:p></p><p class=MsoPlainText>To: <a href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a><o:p></o:p></p><p class=MsoPlainText>Message-ID: <<a href="mailto:D5CCCB96-D138-4524-AFDE-FEC4A5F117E2@ipcsolutions.com.au">D5CCCB96-D138-4524-AFDE-FEC4A5F117E2@ipcsolutions.com.au</a>><o:p></o:p></p><p class=MsoPlainText>Content-Type: text/plain; charset=us-ascii<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>To the list<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I am looking at building an Asterisk appliance that I plan to put into production at a large number of locations.<o:p></o:p></p><p class=MsoPlainText>Having a CF die on me at one of my existing customers, I am wary of using any distributions that cannot significantly reduce writes to the CF as this failed site was tailored for reduced writes but obviously not enough.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Well that being said, obviously Voyage Linux is an excellent development platform for this appliance but I have some questions that I would love if the community could answer:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>1) There is very little documentation for Voyage One which seems the best place to start. Is Voyage One designed for gateways only and no writing to CF as would be required if implementing Voicemail? What about the ASTDB. Is that put in tmpfs as there are many registration writes to it and what I anticipate was the main reason my CF died.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>2) I read on another post that I could partition the CF for voicemail and mount as rw and change the asterisk.conf file paths. Does this seem reasonable? <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>3) I suppose I could keep the ASTDB in tmpfs and write it say hourly to the CF or on specific events e.g. when a Call Forward is set. Does this seem reasonable?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>4) Is there any way that I could prevent log files from filling up tmpfs in /var/log which could prevent Asterisk writing to the ASTDB file?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>5) If I started with Voyage One, I would love to use the Digium Debian Asterisk packages below. I realise that this is not a Voyage problem but after I entered them into my sources.lst, it could not find any other than the standard Debian packages with apt-cache search asterisk-1.8. Has anyone got this working?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="https://wiki.asterisk.org/wiki/display/AST/Asterisk+Packages#AsteriskPackages-APT%28Debian%2FUbuntu%29">https://wiki.asterisk.org/wiki/display/AST/Asterisk+Packages#AsteriskPackages-APT%28Debian%2FUbuntu%29</a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There will probably be many more questions but thanks in advance for answering some initial ones.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Regards<o:p></o:p></p><p class=MsoPlainText>Mike<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Demian Martin<o:p></o:p></p><p class=MsoNormal>Product Design Services<o:p></o:p></p><p class=MsoNormal>784 Cary Drive<o:p></o:p></p><p class=MsoNormal>San Leandro, CA 94577<o:p></o:p></p><p class=MsoNormal>demianm_1@yahoo.com<o:p></o:p></p><p class=MsoNormal>209 613 6990<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>