[Serusers] SIP Express Bundle - let's get started
Greger V. Teigre
greger at teigre.com
Mon Dec 10 07:25:28 CET 2007
[removed sems, semsdev, and serdev from cc]
I have updated the project page with:
- all the suggestions for what we have to install
- team members
http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes
g-)
Jai Rangi wrote:
> Wow, Great, Seems the balling is rolling forward and there is great
> feedback from every one.
> 1. Just want to confirm that I am in.
> 2. I would also vote for CentOS and vmware.
> 3. How about sipp, which can be a good performance testing tool.
> 4. I hope we will be using latest release (or at least 2nst last
> stable release) of kernel, mysql, apache, php, perl etc. The reason I
> mentioned this is that, serweb had issues with Apache 2.x and php 5.x.
>
> Cheers,
> -Jai
>
>
>
> On Dec 9, 2007 8:23 PM, ram <talk2ram at gmail.com
> <mailto:talk2ram at gmail.com>> wrote:
>
>
>
> On Dec 9, 2007 6:30 PM, SIP <sip at arcdiv.com
> <mailto:sip at arcdiv.com>> wrote:
>
> Greger V. Teigre wrote:
> > Hi guys, thanks a bunch for lots of input and I really
> appreciate the
> > willingness to contribute.
> > Thus, I have created a "project page":
> >
> http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes
> >
> > I thought we could gather the current perspective on that
> page and
> > document our decisions as we go. It will hopefully be useful
> in our
> > process, as well as documentation for us and others later.
> >
> > I have noted the following volunteers:
> > Jai: testing and installation work
> > ram: testing
>
>
> yes iam there.
>
>
> > SIP: tesing
> > Jiri: anyting?
> > Mike: testing and documentation
> >
> > Maybe we should set up a small mailing list for coordination
> emails,
> > but for now, let's use serusers (where I think all the
> comments came).
> > (I copy the other lists on this post, so the other lists
> know that the
> > discussion will move to serusers).
> >
> > Out of the comments, I read CentOS and vmware as the most wanted
> > combination. I have documented the pros and cons on the
> project page,
> > and suggest that we do some testing before we decide. I also
> tried out
> > rpath (which I have no previous experience with). My
> observations are
> > documented on the same page.
> >
> > Thus, I have started setting up a minimal CentOS virtual
> appliance
> > found in vmware's appliance directory on an esx server. I
> will send
> > details on accessing it to the volunteers once it is up and
> running
> > (decompressing, unpacking, and building a non-split disk
> takes an
> > awful lot of time :-( ).
> >
>
>
> CENTOS will be good idea.
>
>
>
> > Ok, further comments, ideas, etc, please post to serusers or
> edit/add
> > comments to the project page (requires an iptel.org
> <http://iptel.org/> account). I see
> > the following steps with documentation as we go (steps also
> found on
> > the project page):
> > 1. Testing and specification of what we want to accomplish
> > 2. Environment and OS setup to ensure that we easily can
> release new
> > versions
> > 3. Installation and configuration of the software. I assume
> this step
> > also will involve development of some tools we need, as well as
> > adaptation of existing stuff
> > 4. Testing and user documentation
> > 5. Packaging and deployment
> >Something I noted about the project. While I am all for a
> virtual image
> for testing purposes and getting things up and running while we're
> creating this project, I think the ultimate goal should be
> something
> like an ISO that's ready to go on a server. There are many of
> us in the
> systems world who have not bought into the whole virtualisation
> marketing gimmick when it comes to system deployment, and for
> the casual
> home user who's less comfortable with using VMs for an actual
> production
> system (which is, to be honest, a lot of people), it might be
> easier in
> the long term to get everything the way we want it and then
> make an ISO
> that's ready to drop onto whatever machine with all the
> components we need.
>
> BUT... first things first. :) We need a list of everything
> that's going
> to be in this bundle.
>
>
> yes , we need to look at common man and make this installation process
> and to be menu driven, while installation going on.
>
>
>
> My assumptions are (at the basic level):
>
> -SER 2.0 (in whatever state it's in atm)
> -SERWeb
> -RTPProxy
> -SEMS
>
>
> we need to look at Media proxy also as a base, since it has some
> monitoring tools.
>
>
> Secondary (but no less important) items that are a must-have:
> -MySQL (I'm voting for 5 series here, but that will require my
> patch for
> the mysql code in SER 2.0)
> -Apache (req'd for SERweb)
> -SIPsak
> -ngrep (invaluable for debugging as well as learning)
>
>
> yes all the tools needed
>
>
>
> Optional:
> -mediaproxy
> -freeradius
> -radiusclient (for those who want to mesh SER with an existing
> radius
> infrastructure perhaps)
>
>
> yes for the accurate billing we need to consider Radius
>
>
>
>
> Thoughts?
>
>
>
> we also need to look at modular solution.
> and documentation for the same.
>
> Like each service in one server.
>
> ram
>
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org <mailto:Serusers at lists.iptel.org>
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20071210/eb23f113/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2844 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20071210/eb23f113/attachment.bin>
More information about the sr-users
mailing list