With the named routes it wouldn't be too difficult to follow a big config file...<br><br>just my 0.02,<br>sam.<br><br><div><span class="gmail_quote">2007/5/14, Jiri Kuthan <<a href="mailto:jiri@iptel.org">jiri@iptel.org
</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As for me I am largely in favor of having a kind of config-file "super-store" or "exchange" -- it
<br>appears there is never enough of those :-)<br><br>-jiri<br><br>At 18:01 14/05/2007, Alfred E. Heggestad wrote:<br>>Hi Nils<br>><br>>It would be very useful to have 1 (one) big configuration file implementing<br>
>a superset of the most popular features (nathelper, tls, presence etc..)<br>>and split into logical parts, so people can remove/disable unwanted features.<br>><br>>If you can publish the ser.cfg for the SER running on sip:
<a href="http://iptel.org">iptel.org</a> that would<br>>be even better.. Nothing beats a working config from long-term deployment.<br>><br>>I am currently also assisting Greger now, to get the ser.cfg build system
<br>>up2dated with working configuration files..<br>><br>><br>>/alfred<br>><br>>Nils Ohlmeier wrote:<br>>>Hello everybody,<br>>>as we want to provide more examples for the configuration the following the question came up:
<br>>>Do you prefer<br>>>- one big example configuration<br>>> - probably harder to understand<br>>> - easier to maintain for us<br>>>- one example config file per "feature"<br>>> - probably easier to understand your desired "feature"
<br>>> - you might have problems to integrate all your desired "features" into one config without breaking anything<br>>> - harder to maintain for us, as we have to update several files :-)<br>>>As the configuration examples are indented to be for the community, I would like to know what you prefer or if you see other options.
<br>>>Thanks<br>>> Nils<br>>>_______________________________________________<br>>>Serdev mailing list<br>>><a href="mailto:Serdev@lists.iptel.org">Serdev@lists.iptel.org</a><br>>><a href="http://lists.iptel.org/mailman/listinfo/serdev">
http://lists.iptel.org/mailman/listinfo/serdev</a><br>><br>><br>>_______________________________________________<br>>Serdev mailing list<br>><a href="mailto:Serdev@lists.iptel.org">Serdev@lists.iptel.org</a>
<br>><a href="http://lists.iptel.org/mailman/listinfo/serdev">http://lists.iptel.org/mailman/listinfo/serdev</a><br><br><br><br>--<br>Jiri Kuthan <a href="http://iptel.org/~jiri/">http://iptel.org/~jiri/</a>
<br><br>_______________________________________________<br>Serdev mailing list<br><a href="mailto:Serdev@lists.iptel.org">Serdev@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serdev">http://lists.iptel.org/mailman/listinfo/serdev
</a><br></blockquote></div><br>