<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello, all!<br>
<br>
During the last Public Meeting[1], we've discussed about automated
tools to deploy and configure OpenSIPS extensions, such as RTPProxy,
RTPengine,
<meta http-equiv="content-type" content="text/html; charset=utf-8">
OpenSIPS Control Panel, Homer, SNMP, OpenXCAP and many other
external tools that can be used in conjuction with OpenSIPS.<br>
Our initial assumption was that people find it difficult to
integrate these tools with our SIP Proxy, and they need an automated
solution that install and magically configure them in such a way
that they simply work. This will spare some time from documenting
and depoying the tools, and will provide a minimum working setup. If
more tuning has to be done, tutorials and extra documentation should
be consulted.<br>
<br>
What we would like to do now, is to ask you the following questions:<br>
1) Is integrating external tools a real problem that we have to
address?<br>
2) Do you find this kind of automated tool useful? Or you'd prefer
to use a different solution?<br>
3) How would you like to see this implemented? As an external tool?
Or perhaps using an already existing tool, but has to be configured
to know OpenSIPS integration?<br>
<br>
Your input is _really_ needed on this topic, so please don't
hesitate to list your ideas here. Together we can make OpenSIPS
integration better and faster :D.<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://www.opensips.org/Community/IRCmeeting20150429">http://www.opensips.org/Community/IRCmeeting20150429</a><br>
<br>
Cheers,<br>
<pre class="moz-signature" cols="72">--
Răzvan Crainea
OpenSIPS Solutions
<a class="moz-txt-link-abbreviated" href="http://www.opensips-solutions.com">www.opensips-solutions.com</a></pre>
</body>
</html>