On 3/23/11 3:28 PM, Claudio Furrer wrote:
The sercmd is always with this name, even for kamailio flavour, since it is
kind of separate application. What changes are the ctl tools, like kamctl or
serctl.
Yes, you're right. Only ctl tools changes.
Only by modifying the Makefile.defs, the
Hello,
ser and sip-router flavours are completely the same, just different
names for binaries and tools. Historically, being the initial project,
ser stays the default flavour
kamailio is different, installing what was traditionally provided by
kamailio (openser), one being the database
Hello,
ser and sip-router flavours are completely the same, just different names for
binaries and tools. Historically, being the initial project, ser stays the
default flavour
I can't get different names for binaries and tools, ser flavour or
sip-router flavour give me always sbin/ser
Hello,
On 3/23/11 2:33 PM, Claudio Furrer wrote:
Hello,
ser and sip-router flavours are completely the same, just different names for
binaries and tools. Historically, being the initial project, ser stays the
default flavour
I can't get different names for binaries and tools, ser flavour or
Hello,
What is (or should be) the binary main name when using FLAVOUR=ser,
FLAVOUR=sip-router or no FLAVOUR specified?
I'm getting ser as the name whatever I set to FLAVOUR var at compile time. Is
it right? (Makefiles.defs says ser in these cases but not sure the intention
of the sip-router
Hi.
If you use FLAVOUR=kamailio you will get kamailio, kamctl and kamdbctl
as binary.
Regards
Sascha
Am 22.03.2011 19:42, schrieb Claudio Furrer:
Hello,
What is (or should be) the binary main name when using FLAVOUR=ser,
FLAVOUR=sip-router or no FLAVOUR specified?
I'm
Hi Sascha,
Thanks your answer..
I'm coming from ser flavour, and need to upgrade to 3.x, then my doubt is
specifically related with ser/sip-router. Now I've already have ser binaries
(ser, sercmd, etc) and am i asking if new binaries should be named as ser* or
siprouter* based on the flavour
