23 Dec
2010
23 Dec
'10
noon
i have tried to enable sctp by including in debian/rules
SCTP=1
and by including SCTP=$(SCTP) in make params.
in cfg file, i have
enable_sctp=1
but when i start sr, it does not report listening on sctp, only udp,
tcp, and tls.
i have not found anything about sctp in sr README/INSTALL etc files in
source dir.
question: how to enable sctp?
-- juha
23 Dec
23 Dec
12:33 p.m.
On 12/23/10 11:00 AM, Juha Heinanen wrote:
i have tried to enable sctp by including in
debian/rules
SCTP=1
and by including SCTP=$(SCTP) in make params.
in cfg file, i have
enable_sctp=1
but when i start sr, it does not report listening on sctp, only udp,
tcp, and tls.
i have not found anything about sctp in sr README/INSTALL etc files in
source dir.
question: how to enable sctp?
setting SCTP=1 for compilation time should do it.
Do you have USE_SCTP in kamailio -V output?
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
1:01 p.m.
Daniel-Constantin Mierla writes:
setting SCTP=1 for compilation time should do it.
not quite. i found the reason.
command
/usr/bin/make cfg CC=cc CFLAGS="-g -O2 -Wall" QUIET=1 FMSTATS=1 KMSTATS=1 SCTP=1
MAIN_NAME=trunk-proxy ..."
sgive to console:
"sctp development files not installed -- sctp disabled"
"sctp libraries not installed -- sctp disabled"
what are those files? perhaps it would be a good idea to mention about
them in INSTALL file.
-- juha
3 Jan
3 Jan
1:53 p.m.
On Thursday 23 December 2010, Juha Heinanen wrote:
Juha Heinanen writes:
Hi Juha,
i've added a small note to the INSTALL file as well.
Regards,
Henning
what are those files? perhaps it would be a
good idea to mention about
them in INSTALL file.
i needed to install libsctp-dev package. i added it to my control files
so that i'm reminded in the future about the missing package.
23 Dec
23 Dec
1:48 p.m.
conclusion about my sctp experiment was that after i got sctp activated
in the proxy and tried to forward a request out using sctp transport,
nothing happened. wireshark didn't show any packet going out after proxy
printed
Dec 23 13:18:08 sars /usr/sbin/sip-proxy[30485]: INFO: Routing INVITE
<sip:XXXXX@X.X.X.X:8000;transport=sctp>
and called t_relay.
-- juha
5 Jan
5 Jan
3:11 p.m.
On Dec 23, 2010 at 13:48, Juha Heinanen <jh(a)tutpro.com> wrote:
conclusion about my sctp experiment was that after i
got sctp activated
in the proxy and tried to forward a request out using sctp transport,
nothing happened. wireshark didn't show any packet going out after proxy
printed
Dec 23 13:18:08 sars /usr/sbin/sip-proxy[30485]: INFO: Routing INVITE
<sip:XXXXX@X.X.X.X:8000;transport=sctp>
and called t_relay.
Did you see any sctp address among the listening sockets printed on
startup? Any log message?
It is possible that you don't have a kernel with sctp support (in which
case the sctp support will be automatically disabled on startup). Try
enable_sctp = 1 in .cfg to get instead and error.
Andrei
3:18 p.m.
Andrei Pelinescu-Onciul writes:
Did you see any sctp address among the listening
sockets printed on
startup? Any log message?
yes, both proxies reported at startup that they are listening on sctp.
It is possible that you don't have a kernel with
sctp support (in which
case the sctp support will be automatically disabled on startup). Try
enable_sctp = 1 in .cfg to get instead and error.
no error messages if i include enable_sctp=1 in config. i can make more
experiments later. i sort of gave up and my test setup is not now ready.
-- juha
5069
days inactive
5082
days old
7 comments
4 participants
participants (4)
-
Andrei Pelinescu-Onciul -
Daniel-Constantin Mierla -
Henning Westerholt -
Juha Heinanen