hi, could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
Cheers,
Henning
On 9/17/10 10:33 AM, Henning Westerholt wrote:
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
it is documented also in wiki: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#include_file
Cheers, Daniel
hello Henning, i know this allready, i mean in the default git repo (git head) users will understand it quickly thank you Henning Westerholt a écrit :
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
Cheers,
Henning
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
Default config is not that big right now and last version uses defines and string names for routes, making it easier to go through.
If you have clear ideas about how it should look, send them and will discuss if it is better or not.
Personally I don't see a big benefit for splitting the current version.
Cheers, Daniel
On 9/17/10 1:33 PM, Meftah Tayeb wrote:
hello Henning, i know this allready, i mean in the default git repo (git head) users will understand it quickly thank you Henning Westerholt a écrit :
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
Cheers,
Henning
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
daniel, like in freeswitch xml files is streeped down in several part, dialplan, directory, configuration and ... that make it easy for beginer to understand it quickly you put basic configuration in "kamailio_conf.cfg", routes in routes.cfg, auth or something in auth.cfg, modules in modules.cfg, and you include them from kamailio.cfg thank you Daniel-Constantin Mierla a écrit :
Default config is not that big right now and last version uses defines and string names for routes, making it easier to go through.
If you have clear ideas about how it should look, send them and will discuss if it is better or not.
Personally I don't see a big benefit for splitting the current version.
Cheers, Daniel
On 9/17/10 1:33 PM, Meftah Tayeb wrote:
hello Henning, i know this allready, i mean in the default git repo (git head) users will understand it quickly thank you Henning Westerholt a écrit :
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
Cheers,
Henning
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
Hello,
On 9/17/10 2:45 PM, Meftah Tayeb wrote:
daniel, like in freeswitch xml files is streeped down in several part, dialplan, directory, configuration and ...
that is a completely different architecture. The directory is in kamailio case the subscriber table in database. Then FS has per module specific configuration file, which is also the case for some of our modules, like tls, carrierroute, ldap or dispatcher.
Practically the config file of kamailio maps on dialplan. Since the module specific parts (I mean here module parameters) are too small, I don't think is good idea to have one file per each loaded module.
For kamailio case a split is usual done based on logical parts, but I am afraid is going to be confusing for beginners. For example initial checks done for each request, where one can test max forward, max message body, etc. requires more modules. Splitting is really good when you maintain many configs, where you have common parts, but for default config, again, I don't see a big benefit. If others have different opinions or suggestions, they can jump in discussion.
Daniel
that make it easy for beginer to understand it quickly you put basic configuration in "kamailio_conf.cfg", routes in routes.cfg, auth or something in auth.cfg, modules in modules.cfg, and you include them from kamailio.cfg thank you Daniel-Constantin Mierla a écrit :
Default config is not that big right now and last version uses defines and string names for routes, making it easier to go through.
If you have clear ideas about how it should look, send them and will discuss if it is better or not.
Personally I don't see a big benefit for splitting the current version.
Cheers, Daniel
On 9/17/10 1:33 PM, Meftah Tayeb wrote:
hello Henning, i know this allready, i mean in the default git repo (git head) users will understand it quickly thank you Henning Westerholt a écrit :
On Friday 17 September 2010, Meftah Tayeb wrote:
could we spleete the configuration file in several configuration file based on the default config, but diferent sexions? and we include it in the main conf file? like in routes, we create a folder "route" in /etc/sip-router (kamailio or ser) and we pute routes in separate files or in single file, and include it from sip-router.conf that will facilitate iverything thank you
Hi Meftah,
do you refer to splitting the cfg file in several pieces? This is possible with the #include directive, you can find more informations here:
http://by-miconda.blogspot.com/2009/12/best-of-new-in-kamailio-300-1-include...
Cheers,
Henning
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________
The message was checked by ESET NOD32 Antivirus.
-
Daniel-Constantin Mierla -
Henning Westerholt -
Meftah Tayeb