sr-users September 2017

sr-users@lists.kamailio.org

86 participants
123 discussions

by Sebastian Damm

Hi, I'm trying to set up a Kamailio (4.1.3) server which converts between IPv6 and IPv4. Everything looks pretty good. Now I have a test client which sends packets via IPv6, but in contact header, SDP etc. there are still IPv4 addresses. (This comes from some converting from v4 to v6 earlier.) Thus, Kamailio tries to do a fix_nated_contact(). But after fixing, the Contact URI is wrong. Example: inbound Contact: <sip:bob@192.168.8.132> outbound Contact: <sip:bob@1234:1234:0:1234:0:0:0:2> The correct way of transforming the Contact URI would be: Contact: <sip:bob@[1234:1234:0:1234:0:0:0:2]> This incorrect Contact URI doesn't hurt first, but when the called party wants to hang up the call, it addresses the URI from Contact header, and Kamailio can't parse the Request URI: Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: rr [loose.c:934]: loose_route(): failed to parse Request URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: domain [domain.c:140]: is_uri_host_local(): error while parsing R-URI Is this a bug in the nathelper module? Was it never meant to handle IPv6 addresses? Or do I understand something wrong? Best Regards, Sebastian

7 years

NatHelper ignoring force_socket module parameter

by Asgaroth

Hi All, I have a strange issue, I have set the module parameter for nathelper's force_socket to a specfic ip/port, however, when I perform a sip trace I can see that all locally generated options messages are not sent from the socket defined in the modules parameters. I am not setting $fs anywhere in the script, so I am not over-writing it. Do any of the other module parameters have a bearing on if nathelper uses the force_socket parameter? My current nathelper settings are: modparam("nathelper", "received_avp", "$avp(RECEIVED)") modparam("nathelper", "natping_interval", 20) modparam("nathelper", "natping_processes", 4) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_from", "sip:keepalive@domain.com") modparam("nathelper", "sipping_method", "OPTIONS") modparam("nathelper", "sipping_bflag", NAT_BFLAG) modparam("nathelper", "force_socket", "1.2.3.4:5060") I am using kamailio v4.3.1: # kamailio -V version: kamailio 4.3.1 (x86_64/linux) f38e67 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: f38e67 compiled on 18:15:23 Jul 20 2015 with gcc 4.4.7 Thanks

7 years

Kamailio IMS deployment

by Ramya Y

Hi, I am newbie to kamailio world and we would like to deploy Kamailio based IMS platform. Can any body share the link or Step by step procedure(user Guide) to deploy Kamailio IMS. Regards, Ramya

7 years, 1 month

Roadmap to Kamailio v5.1

by Daniel-Constantin Mierla

Hello, being discussed at the previous IRC devel meeting before the summer, it's time to plan the preparation for next major release, respectively Kamailio 5.1 series. As an initial proposal, a timeline can be: - Mon, Oct 16, 2017 - freeze the development - in 3-4 weeks after that, create the branch 5.1 - 2-3 weeks after, do the release of v5.1.0 That means more or less by end of November we will have first version of 5.1 series. There are still 4 weeks of development, hopefully enough to get ongoing work finished. I know from github tracker that there are people working on redis support for usrloc. I will focus on exporting more functions to kemi, right now should be around 60%, by freeze should be more than 80% (likely that means all of what most of people use these days, because there are some modules that I guess are not much used). Maybe one or two modules will be pushed as well from my side. I think we should also do an IRC devel meeting to try to sync better on this. Maybe by mid of next week, I will send another email shortly. Should anyone have more details to add or adjust the proposal, do not hesitate to reply to mailing list! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

7 years, 1 month

Having kamailio bind to a VRF device

by George Diamantopoulos

Hello, I have a use case where I need to have kamailio bind to a VRF device. The configuration in question is similar to the example below, where eth1 is a slave to the VRF-lite device: +----------+ +-------------------+ | eth0 | | vrf-green | | 1.1.1.1 | | 127.0.0.1 | +----------+ +-------------------+ | +----------+ | eth1 | | 2.2.2.2 | +----------+ Both the main routing table and "vrf-green" routing table have a default route. What I need to be able to do is have kamailio bind to both interfaces: listen=eth0:5060 listen=vrf-green:5060 And additionally be able to use force_send_socket to select an interface, for example: force_send_socket(udp:2.2.2.2:5060); However, I can't get this to work. The above configuration fails because there is no listen directive for 2.2.2.2. Also, kamailio doesn't process packets received on the VRF with the above listen directives, it behaves as if it doesn't listen on 2.2.2.2 indeed. In addition using either of the below: listen=udp:2.2.2.2:5060 or listen=eth1:5060 fails with an error upon starting kamailio. According to the kernel documentation: Applications that are to work within a VRF need to bind their socket to the VRF device: setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1); or to specify the output device using cmsg and IP_PKTINFO. The question is, is VRF useable with kamailio right now? Or is development needed? Thanks! BR, George

7 years, 1 month

rtpengine - optional srtp

by Daniel-Constantin Mierla

Hello, wondering if anyone has a quick answer to spare some time searching the web or source code -- is there a way to offer optional SRTP (just SDES is also fine) in SDP with RTPEngine? The use case is when the target device is not yet known to support (or not) SRTP. There are couple of ways in specs or practices (e.g., RFC5939/6871, or advertising crypto attributes on RTP/AVP stream, or offering two streams one RTP and one SRTP), I am looking to find if it is possible to do it with RTPEngine and which of the options are supported/what are the parameters for doing it... Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

7 years, 1 month

call disconnects after 32 seconds

by Adesh Pandey

Hi, I have set up the Kamailio as load balancer using dispatcher module but all the calls get disconnected after 30 seconds (call is forwarded to Asterisk Box and answered as well). I have used example configuration from the below URL: http://kamailio.org/docs/modules/4.3.x/modules/dispatcher.html#idp51014772 Please help me to understand what is wrong and what shall I do it to fix. Thank You!! Adesh P. -- Adesh Pandey Sr. Software Developer [image: phone] +91 92129 92129 Ext: 56 [image: moible] +91 8527384897 [image: Profile Pic] [image: Facebook] <https://www.facebook.com/VoiceTree?_rdr>[image: Twitter] <https://twitter.com/MyOperator>[image: Twitter] <https://www.youtube.com/user/MyOperatorCo>[image: Linkedin] <https://www.linkedin.com/company/voicetree-technologies>[image: Google+] <https://plus.google.com/+MyoperatorCo/posts> [image: Logo] <http://myoperator.co/>

7 years, 1 month

issue when trying to start kamailio using db_postgres and dialplan modules

by David Escartín

hello all we are having an issue when trying to start kamailio using these modules and a kamailio version higher than 4.2 we install libpq5 and libpq-dev and we always have this error 0(10800) ERROR: <core> [core/sr_module.c:582]: load_module(): could not open module </usr/local/kamailio-5.0/lib64/kamailio/modules/db_postgres.so>: /usr/local/kamailio-5.0/lib64/kamailio/modules/db_postgres.so: undefined symbol: PQconnectdbParams do you know which lib or packet would we miss? we are trying to install it on centos6, ubuntu 10 or centos7 best regards david

7 years, 1 month

Debian Stretch

by Jurijs Ivolga

Hi Guys, I recently tried to use Debian Stretch in production and it didn't went well. On load(500k-700k SIP messages per day) I get a problem that at some point there was a pike of CLOSE_WAIT connections(up to 2k of CLOSE_WAIT connections) and no new connections was possible, I tried to figure out where problem is, but I didn't found anything in system or Kamailio logs, Kamailio just stopped to receive traffic via TCP, but UDP continued to work. Test environment where was no load I didn't faced such issue. Just curious is there anybody who are using Debian Stretch in production without issues? Jurijs

7 years, 1 month

event_route[usrloc:contact-expired] not called after contact expires

by Yuriy Gorlichenko

Hi I added this eventroute for manipulate temprorary entires in my subscriber table but it is not called in my cfg. May be i didn't setted up in scf but didnf found any special params for this. I use kamailio 5.0.3 version: kamailio 5.0.3 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 09:39:55 Sep 8 2017 with gcc 4.9.2 My registrar and usrloc modules setted up as usual modparam("registrar", "method_filtering", 1) modparam("registrar", "max_expires", 3600) modparam("registrar", "gruu_enabled", 0) modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 3) modparam("usrloc", "use_domain", MULTIDOMAIN) thx for advice

7 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users September 2017