On Monday 27 June 2011, Fabian Borot wrote:
I fixed the problem but I would like somebody to shed some light into this issue.
I noticed that when I run kamailio w/o telling where to load the kamailio.cfg file is when it failed. So I went to the kamctl script and notice that in the section where "kamctl start" happens the variable $STARTOPTIONS was empty. I went to the etc/kamailio/kamctlrc, un-commented the line with $STARTOPTIONS and made it like this:
STARTOPTIONS=" -f /usr/local/kamailio-3.1/etc/kamailio/kamailio.cfg" -> this points to the config file which is in a custom path
So, it seems that when one installs kamailio in a directory other than the default path with the prefix option ['make prefix="new path here" all' and 'make prefix="new path here" install'] you have to explicitly tell it somehow to load the config file from somewhere else. Or I did not do it correctly. Can somebody please confirm?. I thought that the initialization scripts would also take care of that. I have installed kamailio 1.4.3 1.5.0, 1.5.2 using the prefix option at 'make' time several times and never had this issue.
Hi Fabian,
I've just tested it in master branch and could reproduce it. It seems the kamctl command misses a variable inclusion in the start cmd. Not sure why it worked in 1.5 and earlier, did not tried it.
Can you please try the attached patch for the kamctl in your checkout? If you don't want to compile and install again, you could also do the changes in the installed version manually.
Best regards,
Henning