[SR-Users] Core compiled with Sctp support

Daniel-Constantin Mierla miconda at gmail.com
Tue Nov 22 10:35:37 CET 2011


Hello,

On 11/18/11 2:44 PM, Stefan Ljung wrote:
> Just one more question.
> Iget these warnings:
> CC (gcc) [ser]          sctp_server.o
> sctp_server.c:504:2: warning: #warning no sctp lib support for 
> SCTP_FRAGMENT_INTERLEAVE, consider upgrading
> sctp_server.c:550:2: warning: #warning no sctp lib support for 
> SCTP_PARTIAL_DELIVERY_POINT, consider upgrading
> sctp_server.c:735:2: warning: #warning no sctp lib support for 
> SCTP_MAX_BURST, consider upgrading
these warnings are printed because you have a version of sctp lib that 
does not support some of the sctp extensions. But all should be fine anyhow.
> sctp_server.c: In function 'sctp_init_sock_opt_common':
> sctp_server.c:412: warning: unused variable 'optlen'
> sctp_server.c:411: warning: unused variable 'saved_errno'
> sctp_server.c:410: warning: unused variable 'pd_point'
These are harmless as well.

> Is that something I can live with ?
Yes.
> What do they do, is there any detailed description of them?

Maybe you find some comments in the code -- they are for internal usage, 
not for config file.

Cheers,
Daniel

>
>
> ------------------------------------------------------------------------
> *From:* Daniel-Constantin Mierla [mailto:miconda at gmail.com]
> *Sent:* den 18 november 2011 12:53
> *To:* Stefan Ljung; kamailio users
> *Subject:* Re: [SR-Users] Core compiled with Sctp support
>
> Don't forget to keep the mailing list cc-ed -- private emails sent 
> from mailing lists discussion are going to be discarded.
>
> If you have libsctp devel package installed, try compilation with:
>
> make SCTP=1 ... all
>
> Cheers,
> Daniel
>
> On 11/18/11 12:13 PM, Stefan Ljung wrote:
>>
>> So, its not.
>>
>> [test032 at wslint90]# ./ser -V
>>
>> version: ser 3.1.2 (i386/linux) 2fe4d6
>>
>> flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, 
>> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 
>> SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, 
>> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
>> USE_DST_BLACKLIST, HAVE_RESOLV_RES
>>
>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
>> MAX_URI_SIZE 1024, BUF_SIZE 65535, PKG_SIZE 4MB
>>
>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>>
>> id: 2fe4d6
>>
>> compiled on 11:31:57 Nov 18 2011 with gcc 4.1.2
>>
>> This result came after an untar and then make command.
>>
>> Here's my machine :
>>
>> [linux]# uname -a
>>
>> Linux wslint90 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 
>> i686 i686 i386 GNU/Linux
>>
>> What can I do to force it in ?
>>
>> /Stefan
>>
>>
>> ------------------------------------------------------------------------
>> *From:* Daniel-Constantin Mierla [mailto:miconda at gmail.com]
>> *Sent:* den 18 november 2011 11:59
>> *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - 
>> Users Mailing List
>> *Cc:* Stefan Ljung
>> *Subject:* Re: [SR-Users] Core compiled with Sctp support
>>
>> Hello,
>>
>> when sctp support is available, if you do 'kamailio -V' or 'ser -V' 
>> you should see USE_SCTP flag there.
>>
>> Not sure if sctp is enabled by default in listen sockets, you can do 
>> it anyhow with global parameter:
>>
>> enable_sctp=yes
>>
>> Cheers,
>> Daniel
>>
>> On 11/18/11 11:49 AM, Stefan Ljung wrote:
>>> I've downloaded sip-router 3.1.2 and have been struggling with the 
>>> make commands  for configuring. Compiling and installing.
>>> Can't really say that I master it.
>>> But I have finally managed to do all steps and started a example 
>>> ser.cfg.
>>> One of the features I want to play around eith is the sctp transport.
>>> From previous experiments with OpenSER I kearned that if I only 
>>> specify a listen host address without transport protocol all three 
>>> UDP TCP and SCTP sockets will be started.
>>> Ths time I only see UDP and TCP:
>>> Listening on
>>>              udp: 127.0.0.1:5060
>>>              tcp: 127.0.0.1:5060
>>> Aliases:
>>>              tcp: localhost:5060
>>>              tcp: localhost.localdomain:5060
>>>              udp: localhost:5060
>>>              udp: localhost.localdomain:5060
>>> I have read the c sources to verify that the sctp libs and header 
>>> files are in the right places, and they are.
>>> What I could need is a tip on how to verify that my core has been 
>>> compiled with sctp support. How can I see that ?
>>> In what files would there be a confimation of that the sctp feature 
>>> will be compiled in?
>>> /Stefan
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> -- 
>> Daniel-Constantin Mierla --http://www.asipto.com
>> Kamailio Advanced Training, Dec 5-8, Berlin:http://asipto.com/u/kat
>> http://linkedin.com/in/miconda  -- http://twitter.com/miconda
>
> -- 
> Daniel-Constantin Mierla --http://www.asipto.com
> Kamailio Advanced Training, Dec 5-8, Berlin:http://asipto.com/u/kat
> http://linkedin.com/in/miconda  -- http://twitter.com/miconda
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20111122/dad0cb9c/attachment-0001.htm>


More information about the sr-users mailing list