3 Jun
2013
3 Jun
'13
12:10 p.m.
Klaus,
Thanks for the tip. I have been using (uri==myself) up to know but I was
trying to move towards a more multidomain configuration, was kinda
hoping to get rid of hardcoded stuff in particular servers.
Daniel,
Can the fact that port in ruri makes host part not longer matching as
own domain be considered a bug or it is the accepted working mechanism?
The "register_myself" parameter made me think that it should match host
part at least (port is not important for me), but in my case port in
ruri makes the whole host not matching. Hope I have clearly expressed my
thoughts ;).
Ta,
DanB
3 Jun
3 Jun
4:47 p.m.
New subject: kamcmd vs kamctl
Hey Guys,
since I am considering administrating kamailio over console, I was
wondering what is the current recommended way to do it:
* kamcmd - new tool, lost track of it's existing support
* kamctl - old tool, many commands returning "ERROR: command disabled"
- eg LCR ones.
Ta for any kind of tip.
DanB
7:30 p.m.
New subject: kamcmd vs kamctl
Hello,
On 6/3/13 4:47 PM, DanB wrote:
Hey Guys,
since I am considering administrating kamailio over console, I was
wondering what is the current recommended way to do it:
* kamcmd - new tool, lost track of it's existing support
* kamctl - old tool, many commands returning "ERROR: command
disabled" - eg LCR ones.
both are maintained and probably you need both.
First is a tool, kamcmd, is written in C for communication with kamailio
using binrcp - practically executing RPC commands. It can connect from a
remote host.
Second one, kamctl, is a shell wrapper managing kamailio database and
communicating with kamailio via fifo file by default, but it can invoke
sercmd as well (see kamctlrc for setting ctl engine). Thus, at the end
of the day, you may just use kamctl, but with kamcmd used inside.
Support for lcr was not maintained by the developer of the module as the
tables got quite complex in the structure, requiring many parameters.
But if someone wants to introduce them back, it is no problem.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
9:45 p.m.
New subject: is_uri_host_local() maybe not considering IP:PORT
On 6/3/13 12:10 PM, DanB wrote:
Klaus,
Thanks for the tip. I have been using (uri==myself) up to know but I
was trying to move towards a more multidomain configuration, was kinda
hoping to get rid of hardcoded stuff in particular servers.
Daniel,
Can the fact that port in ruri makes host part not longer matching as
own domain be considered a bug or it is the accepted working
mechanism? The "register_myself" parameter made me think that it
should match host part at least (port is not important for me), but in
my case port in ruri makes the whole host not matching. Hope I have
clearly expressed my thoughts ;).
It should match if host part of r-uri is a domain
in 'domain' table. If
it doesn't, send the output with debug=3. So, no matter the port in uri,
if host part matches a domain, it will be true for myself condition.
Btw, your email client is breaking the thread.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
3985
days inactive
3985
days old
3 comments
2 participants
participants (2)
-
DanB -
Daniel-Constantin Mierla