22 Mar
2011
22 Mar
'11
6:42 p.m.
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 project).
I need to know the correct one to make an ebuild package for Gentoo.
Thank you for your answers..
Regards,
Claudio
22 Mar
22 Mar
10:37 p.m.
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 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 project).
I need to know the correct one to make an ebuild package for Gentoo.
Thank you for your answers..
--
AMOOMA GmbH - Bachstr. 124 - 56566 Neuwied --> http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998
Bücher: http://das-asterisk-buch.de - http://ruby-auf-schienen.de
23 Mar
23 Mar
1:57 a.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 set.
Moreover, what if it's a new installation and need only common modules and a
few of modules_s.. Then which flavour is recommended (ser or sip-router) and
which name should the main binaries have.
Again, thank you.
Claudio
On Tue, 22 Mar 2011, Sascha Daniels wrote:
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 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 project).
I need to know the correct one to make an ebuild package for Gentoo.
Thank you for your answers..
--
AMOOMA GmbH - Bachstr. 124 - 56566 Neuwied --> http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998
Bücher: http://das-asterisk-buch.de - http://ruby-auf-schienen.de
7:41 a.m.
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 structure specific for
kamailio. Then just few things are enabled by default: kamailio's
internal statistics and tm module extensions used by seas module.
Then, no matter which flavour you select, all modules are installed, so
you can combine them, you need to be sure you create the database table
structure specific for what modules you use.
Cheers,
Daniel
On 3/23/11 2:57 AM, Claudio Furrer wrote:
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 set.
Moreover, what if it's a new installation and need only common modules and a
few of modules_s.. Then which flavour is recommended (ser or sip-router) and
which name should the main binaries have.
Again, thank you.
Claudio
On Tue, 22 Mar 2011, Sascha Daniels wrote:
> 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 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 project).
>>
>> I need to know the correct one to make an ebuild package for Gentoo.
>> Thank you for your answers..
>>
>>
>
> --
> AMOOMA GmbH - Bachstr. 124 - 56566 Neuwied --> http://www.amooma.de
> Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998
>
> Bücher: http://das-asterisk-buch.de - http://ruby-auf-schienen.de
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
1:33 p.m.
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" "sbin/sercmd" etc...
$ make prefix=/ group_include="standard mysql" \
include_modules=avpops \
exclude_modules="rtpproxy nathelper ratelimit mediaproxy" \
mode=debug all
$ make prefix=/ BASEDIR=/tmp/sip-router install
Also tried the same but adding FLAVOUR=ser or FLAVOUR=sip-router. Same
results.
Only by modifying the Makefile.defs, the flavour variable get a binary
name different. Flavour=ser give me ser* names, flavour=sip-router or no
one specified gives siprouter* names, then flavour=kamailio gives
kam* names.
I know it's a mess (with myself) but I have a concept misundertanding. I
interpret sip-router project has 2 names, kamailio and ser, but not its
own name (sip-router).
Then it's a matter of packaging issue which i have.
Then, no matter which flavour you select, all modules are installed, so you
can combine them, you need to be sure you create the database table structure
specific for what modules you use.
Ok, i understand about modules and db. It's clear.
Thank you Daniel.
--
Claudio
2:06 p.m.
Hello,
On 3/23/11 2:33 PM, Claudio Furrer wrote:
ok, I will try to look at it, maybe some other variables have to be set
there, I am using only the kamailio flavor.
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.
--
Daniel-Constantin Mierla
http://www.asipto.com
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" "sbin/sercmd" etc...
$ make prefix=/ group_include="standard mysql" \
include_modules=avpops \
exclude_modules="rtpproxy nathelper ratelimit mediaproxy" \
mode=debug all
$ make prefix=/ BASEDIR=/tmp/sip-router install
Also tried the same but adding FLAVOUR=ser or FLAVOUR=sip-router. Same
results. Only by modifying the Makefile.defs, the flavour
variable get a binary
name different. Flavour=ser give me ser* names, flavour=sip-router or no
one specified gives siprouter* names, then flavour=kamailio gives
kam* names.
I know it's a mess (with myself) but I have a concept misundertanding. I
interpret sip-router project has 2 names, kamailio and ser, but not its
own name (sip-router).
Then it's a matter of packaging issue which i have.
Indeed, you are rigth, there are two application built out of the source
tree:
- ser
- kamailio
To be able to switch between them, 'sip-router' might be used as
placeholder in some case, but there is no sip-router application built
out of it, of course, unless you want it to be so. The flavour build
option is intended to make easy the creation of binaries and configs
with different names without changing anything inside the files. Since I
am using kamailio and that works fine, maybe ser/sip-router is a bit
mixed. I will have a look in the next days.
Thanks,
Daniel
Then, no
matter which flavour you select, all modules are installed, so you
can combine them, you need to be sure you create the database table structure
specific for what modules you use.
Ok, i understand about modules and db. It's
clear.
Thank you Daniel.
--
Claudio
2:28 p.m.
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 flavour
variable get a binary
name different. Flavour=ser give me ser* names, flavour=sip-router or no
one specified gives siprouter* names, then flavour=kamailio gives
kam* names.
I know it's a mess (with myself) but I have a concept misundertanding. I
interpret sip-router project has 2 names, kamailio and ser, but not its
own name (sip-router).
Then it's a matter of packaging issue which i have.
Indeed, you are rigth, there are two application built out of the source tree:
- ser
- kamailio
To be able to switch between them, 'sip-router' might be used as placeholder
in some case, but there is no sip-router application built out of it, of
course, unless you want it to be so. The flavour build option is intended to
make easy the creation of binaries and configs with different names without
changing anything inside the files. Since I am using kamailio and that works
fine, maybe ser/sip-router is a bit mixed. I will have a look in the next
days. >> /usr/share/man/man8/siprouter.8.bz2
--- /usr/share/man/man5/
>> /usr/share/man/man5/siprouter.cfg.5.bz2
--- /usr/sbin/
>> /usr/sbin/siprouter_mysql.sh
>> /usr/sbin/sercmd
>> /usr/sbin/siprouter
--- /etc/
--- /etc/init.d/
>> /etc/init.d/siprouter
>> /etc/siprouter/
>> /etc/siprouter/siprouter-basic.cfg
>> /etc/siprouter/siprouter.cfg
>> /etc/siprouter/dictionary.sip-router
>> /etc/siprouter/siprouter-advanced.cfg
--- /etc/conf.d/
>> /etc/conf.d/siprouter
Best regards,
Claudio
24 Mar
24 Mar
6:46 a.m.
On 3/23/11 3:28 PM, Claudio Furrer wrote:
Ok Daniel, thank you.
By now this diff makes me happy with apps name..
--- Makefile.defs.orig 2011-03-22 14:57:24.759454311 -0300
+++ Makefile.defs 2011-03-23 10:06:57.997000132 -0300
@@ -133,7 +133,7 @@
ifeq ($(FLAVOUR),sip-router)
# main binary name
-MAIN_NAME=ser
+MAIN_NAME=siprouter
else ifeq ($(FLAVOUR),ser)
# main binary name
MAIN_NAME=ser
Then setting flavour=sip-router I get binaries with siprouter* names.
OK, thanks for reporting, as I said, I will have a look in the next days
or so.
Cheers,
Daniel
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 flavour variable get a binary
name different. Flavour=ser give me ser* names, flavour=sip-router or no
one specified gives siprouter* names, then flavour=kamailio gives
kam* names.
I know it's a mess (with myself) but I have a concept misundertanding. I
interpret sip-router project has 2 names, kamailio and ser, but not its
own name (sip-router).
Then it's a matter of packaging issue which i have.
Indeed, you are rigth,
there are two application built out of the source tree:
- ser
- kamailio
To be able to switch between them, 'sip-router' might be used as placeholder
in some case, but there is no sip-router application built out of it, of
course, unless you want it to be so. The flavour build option is intended to
make easy the creation of binaries and configs with different names without
changing anything inside the files. Since I am using kamailio and that works
fine, maybe ser/sip-router is a bit mixed. I will have a look in the next
days. For example:
--- /usr/share/man/man8/
--
Daniel-Constantin Mierla
http://www.asipto.com
>> /usr/share/man/man8/siprouter.8.bz2
--- /usr/share/man/man5/
>> /usr/share/man/man5/siprouter.cfg.5.bz2
--- /usr/sbin/
>> /usr/sbin/siprouter_mysql.sh
>> /usr/sbin/sercmd
>> /usr/sbin/siprouter
--- /etc/
--- /etc/init.d/
>> /etc/init.d/siprouter
>> /etc/siprouter/
>> /etc/siprouter/siprouter-basic.cfg
>> /etc/siprouter/siprouter.cfg
>> /etc/siprouter/dictionary.sip-router
>> /etc/siprouter/siprouter-advanced.cfg
--- /etc/conf.d/
>> /etc/conf.d/siprouter
Best regards,
Claudio
4799
days inactive
4801
days old
7 comments
3 participants
participants (3)
-
Claudio Furrer -
Daniel-Constantin Mierla -
Sascha Daniels