Re: [SR-Users] tls with ubuntu 16.04

Hello, Just did enable_tls after loadmodule "tls.so" and this now works. Thanks. - Jayesh On Thu, Jul 14, 2016 at 11:06 AM Jayesh Nambiar wrote: > I did load the tls first but still get the same error. Here is the > loadmodule sequence: > > loadmodule "tls.so" > >

Re: [SR-Users] tls with ubuntu 16.04

I did load the tls first but still get the same error. Here is the loadmodule sequence: loadmodule "tls.so" loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule

Re: [SR-Users] is_direction / $fti / $tti not working possible

Thanks! you should use $fti and $tti only after loose_route(). If used before, it doesn't find the proper Route header and assumes downstream. The issue actually is the fact that there is some caching done in this case, to avoid doing same processing many times for same sip message. So getting

Re: [SR-Users] is_direction / $fti / $tti not working possible

Hello, you should use $fti and $tti only after loose_route(). If used before, it doesn't find the proper Route header and assumes downstream. The issue actually is the fact that there is some caching done in this case, to avoid doing same processing many times for same sip message. So getting

Re: [SR-Users] tls with ubuntu 16.04

Hello, load first the tls module and then the others. Cheers, Daniel On 13/07/16 19:54, Jayesh Nambiar wrote: > Opensl Version: > > OpenSSL 1.0.2g-fips 1 Mar 2016 > > > Order of loadmodules: > > loadmodule"mi_fifo.so" > > loadmodule"kex.so" > > loadmodule"corex.so" > > loadmodule"tm.so" > >

[SR-Users] is_direction / $fti / $tti not working possible

I'm missing something obvious here, throwing this out to get a couple extra sets of eyeballs on it. I can't get rr modules is_direction() or the $fti / $tti pv's to work in 4.3.x or 4.4.x Relevant parts of the config: loadmodule "rr.so" modparam ("rr", "enable_full_lr", 1)

Re: [SR-Users] tls with ubuntu 16.04

Hello, can you provide details about: - order of loaded modules: grep "loadmodule" kamailio.cfg - the version of libssl Cheers, Daniel On 13/07/16 16:48, Jayesh Nambiar wrote: > Hi, > Trying kamailio with Ubuntu 16.04 and I'm getting errors as follows: > > ERROR: tls [tls_init.c:490]:

Re: [SR-Users] Kamailio Enviroment

Hi, Hint: It would be convenient, if everyone just used reply to all ;-) Can you elaborate your question a bit more? Currently, there are two instances of the dispatcher being used: 1) At the Proxy-CSCF (for the SEMS SBC's, if needed) 2) At the Serving-CSCF's (for the Interconnect, in case

Re: [SR-Users] Kamailio know which Interface Packet would route out

Thanks Loic, Yes, thats correct Kernel decides the interface to take. That is why I want to figure out if we have any way to foresee that decision ! I got to know a new thing: onsend_route: http://www.kamailio.org/dokuwiki/doku.php/features:new-in-3.0.x#onsend_route I will try and make use of

Re: [SR-Users] Kamailio know which Interface Packet would route out

Hi, Interface selection is done by kernel when routing lookup is done, no ? If you have the same destination and multiple interface to reach it, kernel will chose the best one (according metric values). If you want to force trafic to go through an interface, interface must be attached to

[SR-Users] tls with ubuntu 16.04

Hi, Trying kamailio with Ubuntu 16.04 and I'm getting errors as follows: ERROR: tls [tls_init.c:490]: tls_pre_init(): Unable to set the memory allocation functions The error is identical to the one mentioned here: https://bugs.launchpad.net/ubuntu/+source/kamailio/+bug/1591992 Is there a

Re: [SR-Users] Rate limiting

The pipelimit module is the solution to all your problems. On 07/13/2016 04:09 AM, NITESH BANSAL wrote: Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh

Re: [SR-Users] Rate limiting

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh From: sr-users on behalf of NITESH BANSAL

Re: [SR-Users] shm_malloc

How shared memory pool concept has been implemented? Why shm_mem_size * 32 is being allocated? Is the entire segment separated by 32 byte byt 32 byte? Please explain me the shared memory pool in Kamailio. From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Wednesday, July

Re: [SR-Users] access to tls X509v3 Subject Alternative Name

On 13/07/16 08:56, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> The right format to try for a variable with index would have been >> $(tls_my_san_hostname[2]) -- have you tried that, too? > $var(san2) = $(tls_my_san_hostname[2]); > xlog("L_INFO", "***

Re: [SR-Users] access to tls X509v3 Subject Alternative Name

Daniel-Constantin Mierla writes: > The right format to try for a variable with index would have been > $(tls_my_san_hostname[2]) -- have you tried that, too? $var(san2) = $(tls_my_san_hostname[2]); xlog("L_INFO", "*** $var(san2)\n"); produces: Jul 13 09:51:44 sars

Re: [SR-Users] shm_malloc

Hello, Can you be more explicit about what do you expect? Daniel On 13/07/16 07:27, Prakash wrote: > > Hello Daniel, > > > > Many thanks for the response. > > Could you please provide me the behind scenes of shm_malloc()?. > > It will be very helpful for me to segregate without any flaws. >

Re: [SR-Users] access to tls X509v3 Subject Alternative Name

On 12/07/16 20:03, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> haven't tested nor looked at source code -- have you tried to see if it >> works with index (e.g, $tls_my_san_hostname[2])? > $var(san) = $tls_my_san_hostname[2]; > > results in $var(san) == 0. The right format to