On 24.08.2009 16:05 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> :-) -- ahh, yes, imo, srctl sort of exists already, but is called
> kamctl.
are you saying that one can control s modules with kamctl? i know that
one can control both s and k modules with serctl (except for a
Daniel-Constantin Mierla writes:
> :-) -- ahh, yes, imo, srctl sort of exists already, but is called
> kamctl.
are you saying that one can control s modules with kamctl? i know that
one can control both s and k modules with serctl (except for async
t_uac_dlg).
-- juha
___
On 24.08.2009 15:14 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> kamctl is in sip-router, check tools directory.
ok, i looked at scripts dir where it used to be in k.
> You are more than welcome to implement the srctl, I am going to
> contribute if I am able to and use it
Daniel-Constantin Mierla writes:
> kamctl is in sip-router, check tools directory.
ok, i looked at scripts dir where it used to be in k.
> You are more than welcome to implement the srctl, I am going to
> contribute if I am able to and use it.
srctl sort of exists already, but is is called
On 24.08.2009 14:54 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
> Kamailio is the same -- will be a new major release of the sip server
> everybody know so far -- new features in core plus some new modules,
> either new development (memcache) or imported from ser (iptrtprox
Daniel-Constantin Mierla writes:
> Kamailio is the same -- will be a new major release of the sip server
> everybody know so far -- new features in core plus some new modules,
> either new development (memcache) or imported from ser (iptrtproxy). To
> update from kamailio 1.5 to 3.0 you wil
Daniel-Constantin Mierla wrote:
Hello,
On 24.08.2009 14:14 Uhr, Alex Balashov wrote:
The sip-router.org documentation is already excessively complicated
and difficult to understand for anyone who does not routinely work
with both the K and S code. At this point, the documentation, while
vol
Hello,
On 24.08.2009 14:14 Uhr, Alex Balashov wrote:
The sip-router.org documentation is already excessively complicated
and difficult to understand for anyone who does not routinely work
with both the K and S code. At this point, the documentation, while
voluminous, is overwhelming and, in p
