[Voyage-linux] Voyage, Asterisk and Voyage One

[Demian Martin]

Mike:

I'm using Voyage for something quite different but have similar concerns for
my product.

 

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.

 

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. 

               Demian

 

 

Date: Wed, 21 Sep 2011 19:00:47 +1000

From: Michael Knill <michael.knill at ipcsolutions.com.au>

Subject: [Voyage-linux] Voyage, Asterisk and Voyage One

To: voyage-linux at voyage.hk

Message-ID: <D5CCCB96-D138-4524-AFDE-FEC4A5F117E2 at ipcsolutions.com.au>

Content-Type: text/plain; charset=us-ascii

 

To the list

 

I am looking at building an Asterisk appliance that I plan to put into
production at a large number of locations.

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.

 

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:

 

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.

 

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? 

 

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?

 

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?

 

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?

 

https://wiki.asterisk.org/wiki/display/AST/Asterisk+Packages#AsteriskPackage
s-APT%28Debian%2FUbuntu%29

 

There will probably be many more questions but thanks in advance for
answering some initial ones.

 

Regards

Mike

 

 

Demian Martin

Product Design Services

784 Cary Drive

San Leandro, CA 94577

demianm_1 at yahoo.com

209 613 6990

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20110921/3de7cab4/attachment.html>