If the goal is to merge both 'ser' and 'kamailio' under the
'sip-router' name, then perhaps the common control tool should be
'srctl'.
Regards,
Ovidiu Sas
On Thu, Apr 1, 2010 at 1:56 PM, Henning Westerholt
<henning.westerholt(a)1und1.de> wrote:
On Wednesday 24 March 2010, marius zbihlei wrote:
As kamailio and ser get more and more unified,
sharing common modules
and core, one of the last remaining points is the intermixed usage of
kamctl and sercmd to setup specific parameters. One example is the cfg
framework changes (from ser) that Kamailio 3.1.0 will bring, that will
require the use of "sercmd" on setting specific module config params.
The issue is that the documentation also references the "kamctl" utility
to specify reload actions etc.
What I suggest is that we strip kamctl with its fifo capabilities and
leave it only with DB, ACL management and such(that sercmd doesn't
provide), and use only sercmd on examples in the documentation files.
This will require no changes to code (well some features from kamctl
will be deprecated), but only documentation changes. This will ensure
that documentation is kept well organized and coherent across modules.
[..]
Hello,
any other opinions on this proposal? No oposition agaisnt the removal of the
common functionality in kamctl and promoting of serctl as the main server
control tool?
Best regards,
Henning
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev