From: Darrick H. <dha...@dj...> - 2007-05-04 14:20:14
|
Gary G. Hendershot wrote: > I implemented Astlinux 0.4.5 on four of my five branch office machines > on Tuesday and Wednesday after testing in the lab last weekend... > deployment went smoothly and did not run into anything odd ... the > fact that the update did not cause any disruption of service was noted > and appreciated ... No problem. You'll see a more disruptive change when we move to 0.5. It's necessary to help reduce the disruption in the future. > > All of my target machines are running in gateway mode ... they are all > Via C3 CPU machines ... during the build process I noted the option to > choose optimization for Via CPU's and did select this option ... I was > wondering, if there is indeed code in the package at this point that > actually does take advantage of some of the unique features in the Via > CPU or if this is a placebo ??? Right now it really doesn't do too much. We could reduce the number of drivers (since it does use it's own .config for the kernel) and we could build padlock features into openssl (and therefore openvpn). > I could use some instruction on how to properly setup OpenVPN within > Astlinux ... I have some pretty decent cookie cutter "step 1, step 2" > type things for OpenVPN in general but nothing specific to the way it > is implemented in Astlinux ... is there such a document out there ??? > anybody got a link to it ??? There are several ways to use OpenVPN. There were several additions to the rc.conf file related to openvpn in the 0.4.5 release. Looks like we may need to add a few more variables to allow openvpn to start as either a client or a server. Right now, the config is geared towards a server. Please add this as a feature request on the tracker at the sourceforge page. > while nobody at the main office was watching, I did a quick CF card > install on this machine to test if your recent Wanpipe efforts bore > fruit ... I was indeed able to get Astlinux running on this > computer and got it to recognize the Sangoma card ... I was able to > configure and successfully test the Sangoma card ... so I am convinced > your Sangoma Wanpipe implementation is now ready for prime time ... Thanks. It's good to have confirmation that the Wanpipe implementation works. The Rhino drivers should also work. > > However, I am still left with Trixbox at the main office unless I can > get my boss his CDR reporting using Astlinux ... is there any solution > to CDR reporting for Aslinux that would be reasonably simple to deploy > ??? I would need something that was at least very close to the > functional level provided in the reporting module that is packaged > with FreePBX ... If anyone would like to contribute to the project, this would be a good way. In FreePBX, the CDR data is most likely in a mysql database. The closest we could achieve would be sqlite. It hasn't been a need/priority for me so far, so it's not something I've really looked at too much. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |