[ previous ] [ next ] [ threads ]
 
 From:  "Marcel Wiget" <mwiget at gmail dot com>
 To:  "Michael Iedema" <michael at askozia dot com>
 Cc:  "Chris Buechler" <cbuechler at gmail dot com>, m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] SIP proxy for m0n0wall 1.3x
 Date:  Sun, 11 Nov 2007 18:25:55 +0100
thanks everyone for the feedback. I submitted the SIP feature to the
freebsd6 branch of m0n0wall: rev r221. Test images, built with patched
m0n0dev can be found at

ftp://ftp.mwcube.net/pub/m0n0wall/siproxd/

I only tested the WRAP image so far...
and so far I haven't done any memory optimization as previously
discussed. Keep that in mind though.

- Marcel




On Nov 7, 2007 8:03 PM, Michael Iedema <michael at askozia dot com> wrote:
> On 11/7/07, Marcel Wiget <mwiget at gmail dot com> wrote:
> > BTW I do understand that anything we add to m0n0wall increases the
> > memory footprint on the flash but also at runtime in memory. Flash
> > space is not a big deal these days, but RAM is. Has anyone thought of
> > the possibility to have files removed during startup from the ramdisk
> > when its service is disabled? In case of siproxd, this might save
> > about 1 Mbytes. Enabling the service will then simply require a
> > reboot.
>
> I encountered the same problem when working on AskoziaPBX. Asterisk
> has many modules and sounds which take up space being stored in and
> run from memory. I added another read-only partition to the image
> which stores these items directly on the CF media. Something like this
> could be done for the "service" related binaries and libraries in
> m0n0wall as well.
>
> -Michael
>