<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Stefan,<br>
Thanks for volunteering. I think you are in the best position to judge
which applications are in popular demand and should be included. In
the initial release, I think we should focus on things that do not have
external dependencies (i.e. PSTN etc), as this will probably complicate
things. I prefer to create a focused, limited-functionality 1.0 release
and then rather quickly add more stuff instead of taking forever with
1.0.<br>
<br>
I think we should focus on enterprise-type apps in the beginning.<br>
g-)<br>
<br>
Stefan Sayer wrote:
<blockquote cite="mid:475C7871.7080601@iptego.de" type="cite">
<pre wrap="">Hi Greger and all others,
I like the idea very much and I will try to contribute on the SEMS side.
What do we want to have in services? voicemail, away announcement and
dial-in conference for the beginning? Maybe a prepaid b2b with SIP
authentication towards a gateway so people can easily and in a cheap way
(no setup fee) provide prepaid outbound PSTN connectivity?
Greger V. Teigre wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi guys, thanks a bunch for lots of input and I really appreciate the
willingness to contribute.
Thus, I have created a "project page":
<a class="moz-txt-link-freetext" href="http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes">http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes</a>
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
SIP: tesing
Jiri: anyting?
Mike: testing and documentation
</pre>
</blockquote>
<pre wrap=""><!----> Stefan: SEMS support
</pre>
<blockquote type="cite">
<pre wrap="">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 :-( ).
Ok, further comments, ideas, etc, please post to serusers or edit/add
comments to the project page (requires an 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
Let's get going!
g-)
------------------------------------------------------------------------
_______________________________________________
Sems mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sems@lists.iptel.org">Sems@lists.iptel.org</a>
<a class="moz-txt-link-freetext" href="http://lists.iptel.org/mailman/listinfo/sems">http://lists.iptel.org/mailman/listinfo/sems</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>