Good work, I am sure this will be endorsed by many and will be useful for lots of small VoIP user who are ready to expand. Only problem I have seen is that people who have done (deployed) this type of integration does not share complete solution mainly because of compititive disadvantage. But keeping the information at one place will definitely help. <br>
<br>I am also working on a 'howto' on integrating Asterisk with Ser that will describe step by step instructions on the deployment of asterisk. I have tons of many things in my plate but targeting to finish within next week or so. <br>
<br>-Jai <br>"Buy unmetered VoIP DID from DidForSale.com"<br><br><br><div class="gmail_quote">On Wed, Nov 5, 2008 at 9:04 AM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Greetings,<br>
<br>
As a developer and consultant who spends considerable time on projects<br>
involving the fusion of Asterisk and products derived from the SER<br>
ecosystem (OpenSER, Kamailio, OpenSIPS, the new SIP-Router), I have<br>
found that there is a great volume of interest in this topic on the<br>
mailing lists associated with all communities involved, but a<br>
comparative lack of focus that results in duplicated effort and lack of<br>
specialised response.<br>
<br>
This is mainly due, I think, to the fact that detailed Asterisk<br>
experience - while common - is not a prerequisite for working with the<br>
SER products, while for Asterisk people SER can often be a next step in<br>
scalability and VoIP service delivery platform enhancement that they are<br>
just getting into. And so on. There's pollution in the respective<br>
discursive spaces; a lot of Asterisk people posting to the SER lists<br>
ask a lot of Asterisk-specific questions in addition to any they may<br>
have about SER which can be construed as potentially off-topic by some<br>
members, and the opposite is true on the Asterisk lists when detailed,<br>
involved discussion about SER occurs.<br>
<br>
We need to capture that discussion that exists at the overlap and is<br>
specifically concerned with making these two systems work together,<br>
requiring somewhat detailed and esoteric understanding of both and a<br>
community of user support and knowledge that focuses on both of these<br>
conceptual and product universes.<br>
<br>
Toward that end, I am hosting a new mailing list with this succinct<br>
purpose, if slightly unwieldy name, and encourage all interested to<br>
join. It is called 'SER-Asterisk-Interwork' and can be accessed for<br>
subscription here:<br>
<br>
<a href="http://lists.evaristesys.com/mailman/listinfo/ser-asterisk-interwork" target="_blank">http://lists.evaristesys.com/mailman/listinfo/ser-asterisk-interwork</a><br>
<br>
The archives are available here:<br>
<br>
<a href="http://lists.evaristesys.com/pipermail/ser-asterisk-interwork/" target="_blank">http://lists.evaristesys.com/pipermail/ser-asterisk-interwork/</a><br>
<br>
You can post to the list at:<br>
<br>
<a href="mailto:ser-asterisk-interwork@lists.evaristesys.com">ser-asterisk-interwork@lists.evaristesys.com</a><br>
<br>
It's the same GNU Mailman stuff you are already used to.<br>
<br>
While it could be argued that this cross-product discussion is valuable<br>
to retain in both communities, I think there is considerable benefit to<br>
creating a specialised mailing list that focuses specifically on this<br>
integration path and the unique interoperation and configuration issues<br>
it creates. I think it would be good to get some of this discussion off<br>
of the SER and Asterisk-specific mailing lists where it has somewhat<br>
marginal relevance at times and refocus it. If you agree and are<br>
interested in this topic, you are invited to join the list.<br>
<br>
One last note: The SER/OpenSER community has been in a state of flux<br>
recently, with OpenSER undergoing a name change to Kamailio and<br>
subsequently seeing a fork. The incumbent Kamailio project is now<br>
in the process of merging with the original SER project. The choice of<br>
nomenclature for list is not meant to imply an endorsement of or<br>
affinity for the IPTel SER project per se. It is just that right now it<br>
serves the aim of terseness to use a common denominator, to refer to<br>
this family of projects as the "SER ecosystem." Whether you are a SER,<br>
OpenSER, Kamailio, or OpenSIPS user, you are part of that "SER<br>
ecosystem." That is why the list is named what it is.<br>
<br>
Thank you,<br>
<br>
-- Alex<br>
<br>
--<br>
Alex Balashov<br>
Evariste Systems<br>
Web : <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
Tel : (+1) (678) 954-0670<br>
Direct : (+1) (678) 954-0671<br>
Mobile : (+1) (706) 338-8599<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>