<div dir="ltr">Frist impression - the name "Excluded modules" is a bit deceptive when you actually select the modules you do wish to include<br>during compilation<br><br><div class="gmail_quote">On Thu, Jan 19, 2012 at 7:11 PM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
A new OpenSIPS configuration tool has been just added to OpenSIPS
trunk, and it will also be present in the future 1.8 release.<br>
This is a graphical tool that allows in an easy way to configure,
compile and generate OpenSIPS configuration files - all by simply
running <br>
<b>make menuconfig</b><br>
<br>
Currently, the Interface allows the user to do the following :<br>
<br>
1. Configure OpenSIPS compilation related options such as :<br>
- <b>Compilation Flags</b>. For example, the user can now
easily compile in TCP support from within the GUI, or enable memory
allocation debugging, etc. Each compilation flag functionality is
explained in short in the GUI.<br>
- <b>Module Compilation Selection</b>. The user can now easily
select to compile modules that have external dependencies, and that
are not compiled in by default. For example, the user can choose to
also enable the MySQL support by enabling the db_mysql module. The
interface will also notify the user about the dependencies that must
be installed based on the modules that the user has selected.<br>
- <b>Installation Prefix</b>. The user can use the GUI to
configure the OpenSIPS installation path to be used<br>
<br>
2. <b>Install OpenSIPS and Cleanup OpenSIPS</b> sources<br>
- Upon configuring OpenSIPS related options from above, the user
can choose to install OpenSIPS directly from the GUI.<br>
<br>
3. <b>Generate OpenSIPS config files</b><br>
- The tool can also generate OpenSIPS configuration files based
on the user's preferences. So far, we have defined three main
classes of OpenSIPS configuration files :<br>
- Residential<br>
- Trunking<br>
- Load-balancer<br>
<br>
For each type of configuration file, the user can choose to
enable/disable certain options. For example, for the Residential
script, the user can choose to enable presence support, to handle
NAT, and many more. After the user has properly configured it's
desired OpenSIPS script in the GUI, it will have the option to
generate and obtain the final OpenSIPS cfg.<br>
<br>
The interface dependencies are <br>
- curses development library for compiling the GUI<br>
- m4 for generating OpenSIPS configs based on user preferences.<br>
<br>
Testing and feedback is very much welcomed.<br>
<br>
Regards,<span class="HOEnZb"><font color="#888888"><br>
<pre cols="72">--
Vlad Paiu
OpenSIPS Developer</pre>
</font></span></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>