Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
klaus
Klaus,
On 23-06 10:07, Klaus Darilion wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
I'd be happy to read it, just let us know when there is something to read.
Jan.
Hi Klaus,
On Tue, Jun 23, 2009 at 10:07 AM, Klaus Darilionklaus.mailinglists@pernau.at wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
Since SCTP was something not present in Kamailio, I could personally contribute with that.
Cheers,
Victor Pascual Ávila schrieb:
Hi Klaus,
On Tue, Jun 23, 2009 at 10:07 AM, Klaus Darilionklaus.mailinglists@pernau.at wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
Since SCTP was something not present in Kamailio, I could personally contribute with that.
Actually it is present, but I think nobody used/tested it :-)
2009/6/23 Klaus Darilion klaus.mailinglists@pernau.at:
Victor Pascual Ávila schrieb:
Hi Klaus,
On Tue, Jun 23, 2009 at 10:07 AM, Klaus Darilionklaus.mailinglists@pernau.at wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
Since SCTP was something not present in Kamailio, I could personally contribute with that.
Actually it is present, but I think nobody used/tested it :-)
Oh, sorry-- I meant it was not present in Kamailio Core CookBook for version 1.5.x
Thanks,
Victor Pascual Ávila schrieb:
2009/6/23 Klaus Darilion klaus.mailinglists@pernau.at:
Victor Pascual Ávila schrieb:
Hi Klaus,
On Tue, Jun 23, 2009 at 10:07 AM, Klaus Darilionklaus.mailinglists@pernau.at wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
So if someone volunteers on reading the docs I would supply them.
Since SCTP was something not present in Kamailio, I could personally contribute with that.
Actually it is present, but I think nobody used/tested it :-)
Oh, sorry-- I meant it was not present in Kamailio Core CookBook for version 1.5.x
Ok. Yes please - all the *sctp* parameters are yours and waiting to be filled up :-)
thanks klaus
2009/6/23 Klaus Darilion klaus.mailinglists@pernau.at:
Since SCTP was something not present in Kamailio, I could personally contribute with that.
Actually it is present, but I think nobody used/tested it :-)
I really think that the SCTP implementation in SER is much better than in Kamailio ;)
On Jun 23, 2009 at 10:07, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Hi!
The sr core cookbook has lots of empty entries: http://sip-router.org/wiki/cookbooks/core-cookbook/devel
Whereas the K core cookbook is rather full: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:1.5.x
I think most of the parameters still have the same meaning. I can volunteer on merging cookbook docu from K to SR, and try to get missing docu from the NEWS file. But in the end one of the core developers (Andrei? Jan?) should verify if the doc is correct?
That's great, I'll try to verify it. The biggest problem would be how to keep it in sync.
We should also mark the options that can be changed after start-up, at runtime. For example a lot of the core options can be changed at runtime, either using core as the config group, or the transport (tcp or sctp). E.g.:
debug -> sercmd cfg.set_now_int core debug 5 tcp_connect_timeout -> sercmd cfg.set_now_int tcp connect_timeout 2 udp_mtu -> sercmd cfg.set_now_int core udp_mtu 1300
One way to see all the options acessible using the cfg framework and defined in the core is to start sr, loading the cfg_rpc and ctl modules and then run: sercmd cfg.list | egrep "core|tcp|sctp"
but note that not all the options can be changed, some are read-only.
sercmd cfg.help <group> <option> might help (e.g. sercmd cfg.help core udp_mtu).
NEWS should help too (at least all the new options added that can be changed at runtime are "marked").
Andrei
Hi Andrei!
Andrei Pelinescu-Onciul schrieb:
One way to see all the options acessible using the cfg framework and defined in the core is to start sr, loading the cfg_rpc and ctl modules and then run: sercmd cfg.list | egrep "core|tcp|sctp"
Does this command return all the available parameters, or only the parameters which can be changed on-the-fly?
regards klaus
On Jul 03, 2009 at 15:43, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Hi Andrei!
Andrei Pelinescu-Onciul schrieb:
One way to see all the options acessible using the cfg framework and defined in the core is to start sr, loading the cfg_rpc and ctl modules and then run: sercmd cfg.list | egrep "core|tcp|sctp"
Does this command return all the available parameters, or only the parameters which can be changed on-the-fly?
Only options that can be read via the cfg. framework, both read-only and writable. There are still config options that are not registered with the config framework (some of them do not make sense. other were forgotten a.s.o).
Andrei
-
Andrei Pelinescu-Onciul -
Iñaki Baz Castillo -
Jan Janak -
Klaus Darilion -
Victor Pascual Ávila