<br><br>
<div class="gmail_quote">On Dec 9, 2007 6:30 PM, SIP <<a href="mailto:sip@arcdiv.com">sip@arcdiv.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c">Greger V. Teigre wrote:<br>> Hi guys, thanks a bunch for lots of input and I really appreciate the<br>> willingness to contribute.<br>> Thus, I have created a "project page":<br>>
<a href="http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes" target="_blank">http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes</a><br>><br>> I thought we could gather the current perspective on that page and
<br>> document our decisions as we go. It will hopefully be useful in our<br>> process, as well as documentation for us and others later.<br>><br>> I have noted the following volunteers:<br>> Jai: testing and installation work
<br>> ram: testing</div></div></blockquote>
<div> </div>
<div>yes iam there.</div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br>> SIP: tesing<br>> Jiri: anyting?<br>> Mike: testing and documentation<br>><br>> Maybe we should set up a small mailing list for coordination emails,<br>> but for now, let's use serusers (where I think all the comments came).
<br>> (I copy the other lists on this post, so the other lists know that the<br>> discussion will move to serusers).<br>><br>> Out of the comments, I read CentOS and vmware as the most wanted<br>> combination. I have documented the pros and cons on the project page,
<br>> and suggest that we do some testing before we decide. I also tried out<br>> rpath (which I have no previous experience with). My observations are<br>> documented on the same page.<br>><br>> Thus, I have started setting up a minimal CentOS virtual appliance
<br>> found in vmware's appliance directory on an esx server. I will send<br>> details on accessing it to the volunteers once it is up and running<br>> (decompressing, unpacking, and building a non-split disk takes an
<br>> awful lot of time :-( ).<br>></div></div></blockquote>
<div> </div>
<div>CENTOS will be good idea.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br>> Ok, further comments, ideas, etc, please post to serusers or edit/add<br>> comments to the project page (requires an <a href="http://iptel.org/" target="_blank">iptel.org
</a> account). I see<br>> the following steps with documentation as we go (steps also found on<br>> the project page):<br>> 1. Testing and specification of what we want to accomplish<br>> 2. Environment and OS setup to ensure that we easily can release new
<br>> versions<br>> 3. Installation and configuration of the software. I assume this step<br>> also will involve development of some tools we need, as well as<br>> adaptation of existing stuff<br>> 4. Testing and user documentation
<br>> 5. Packaging and deployment<br>>Something I noted about the project. While I am all for a virtual image<br>for testing purposes and getting things up and running while we're<br>creating this project, I think the ultimate goal should be something
<br>like an ISO that's ready to go on a server. There are many of us in the<br>systems world who have not bought into the whole virtualisation<br>marketing gimmick when it comes to system deployment, and for the casual
<br>home user who's less comfortable with using VMs for an actual production<br>system (which is, to be honest, a lot of people), it might be easier in<br>the long term to get everything the way we want it and then make an ISO
<br>that's ready to drop onto whatever machine with all the components we need.<br><br>BUT... first things first. :) We need a list of everything that's going<br>to be in this bundle.<br></div></div></blockquote>
<div> </div>
<div>yes , we need to look at common man and make this installation process</div>
<div>and to be menu driven, while installation going on.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br>My assumptions are (at the basic level):<br><br>-SER 2.0 (in whatever state it's in atm)<br>-SERWeb<br>-RTPProxy<br>-SEMS<br></div></div></blockquote>
<div> </div>
<div>we need to look at Media proxy also as a base, since it has some monitoring tools.</div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br>Secondary (but no less important) items that are a must-have:<br>-MySQL (I'm voting for 5 series here, but that will require my patch for<br>the mysql code in SER 2.0)<br>-Apache (req'd for SERweb)
<br>-SIPsak<br>-ngrep (invaluable for debugging as well as learning)<br></div></div></blockquote>
<div> </div>
<div>yes all the tools needed</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br>Optional:<br>-mediaproxy<br>-freeradius<br>-radiusclient (for those who want to mesh SER with an existing radius<br>infrastructure perhaps)<br></div></div></blockquote>
<div> </div>
<div>yes for the accurate billing we need to consider Radius</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div class="Wj3C7c"><span id=""></span><br><br>Thoughts?<br></div></div></blockquote>
<div> </div>
<div> </div>
<div>we also need to look at modular solution.</div>
<div>and documentation for the same.</div>
<div> </div>
<div>Like each service in one server.</div>
<div> </div>
<div>ram<br></div></div>