[sr-dev] Simplify the Configuration

[Luis Azedo]

+1 on Alekzander  statement
________________________________
From: sr-dev [sr-dev-bounces at lists.sip-router.org] on behalf of Alekzander Spiridonov [alekz at li.ru]
Sent: Thursday, March 19, 2015 3:33 AM
To: Kamailio (SER) - Development Mailing List
Subject: Re: [sr-dev] Simplify the Configuration

=D I believe you've learned too many applications.

Current syntax looks pretty fine for me and (as you've already mentioned) any separation could be achieved with include's.

Anyway I'm strongly against idea of any compile-time paths.

2015-03-19 10:13 GMT+03:00 Brian LaVallee <brian.lavallee at invite-comm.jp<mailto:brian.lavallee at invite-comm.jp>>:
Hi,

I would like to propose [and manage] an effort with the primary Kamailio developers to simplify the configuration syntax.  I'm not a developer, but used lot's of different applications and I'm familiar with various configuration formats.

Based on what I've seen, there are five (5) types of configuration directives used with Kamailio.

- C-Style Control Directives
- Apache-Like Name/Value Pairs
- Normal Name/Value Pairs
- Modify Parameter Procedures
- Routing Logic Scripting

I do understand some of this may be the result of merging multiple projects.  But this mixture of syntax slows adoption, drastically increases the learning curve for the user base.  By implementing a consistent standard to the configuration syntax, it will make using the application less complicated.

--

My first recommendation, would be to separate the routing logic from the primary configuration file.  This can easily be done with import/include.  However, I feel that a fixed path should be added during compile.

‘--with-routing=/etc/kamailio/routing/’

Then it would possible to modify the configuration parser to read all the files in that directory.  Allowing the separation of the route logic into individual files.  relay.cfg, reqinit.cfg, ... xmlrpc.cfg, tovoicemail.cfg, etc...  Making individual logic changes a bit easier.

To reach a fixed path solution, and keep some backwards compatibility, the first step should be... Use import/include and move all the route logic into /etc/kamailio/routing/basic.cfg

We can discuss on the mailing list or feel free to contact me directly.


Sincerely,
Brian LaVallee

_______________________________________________
sr-dev mailing list
sr-dev at lists.sip-router.org<mailto:sr-dev at lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev




--
Best regards,
Alekzander Spiridonov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20150319/7ebe9051/attachment.html>