sr-users

sr-users@lists.kamailio.org

1 participants
37563 discussions

Start a nNew thread

How the README file in each module's directory is generated?
by Ding Ma 28 Jan '15

28 Jan '15

Is there a doc tool? Or just use an editor? Thanks

1 0

usrloc and MongoDB
by Mickael Marrache 28 Jan '15

28 Jan '15

Hi, Is it possible to save user location data in a MongoDB database? If not, are you guys using p_usrloc in your projects? Can you please give me some feedback? Thanks, Mickael

2 3

How to run Kamailio as a stateful proxy
by Thomas Bäumer 28 Jan '15

28 Jan '15

Hello all, we are are a small network-provider and selling internet via FTTC and FTTH. To complete the portfolio we also sell telephony via a rented ClassV Service with provisioning API, but its not our system and not in our network. To get more informations about Registration-Status and calls I have now installed a kamailio as a statefull proxy between the subscriber and the softwitch: |----------| |subscriber|\ --------- |----------| \ /| Mobile| \ -------------- / --------- |----------| \ ------------ | Class V | / -------- |subscriber|---------| Kamailio |--------| Softswitch |-------| PSTN | |----------| / ------------ | | \ -------- / -------------- \ --------- |----------| / \| World | |subscriber|/ --------- |----------| I am really new in kamailio, so I just use the configuration named "Edge Proxy Configuration" shown in the documentation to the outbound module, see http://kamailio.org/docs/modules/4.2.x/modules/outbound.html example 1.1. We dont need NAT and STUN because all our subscribers get official IPv4 addresses. Outgoing calls (subscriber -> PSTN) are working fine, all SIP messages pass the Kamailio Proxy. But incoming Calls (World -> subscriber) miss the proxy and will be routed directly from the Softwitch to the subscriber. I think because of the Contact-Header in the subscriber REGISTER: Contact: <sip:49xxxxxxyyyyyy@134.xx.yy.zz;uniq=E41120B46C92D3818E72B> This is the IP of the subscriber FritzBox. So I just added some lines to replace the Contact-Header in the REGISTER to get all incoming Calls from the Softswitch to the Kamailio: if (is_method("REGISTER")) { if (src_ip==CUSTOMER_NET) { remove_hf("Route"); add_path(); $du = "sip:REGISTRAR_IP:REGISTRAR_PORT"; if ($ct != $null) { subst('/^Contact:(.*)@[a-zA-Z0-9.]+(.*)$/Contact:\1@KAMAILIO_IP\2/ig'); } } } and now the Contact-Header looks better: Contact: <sip:49xxxxxxyyyyyy@KAMAILIO_IP;uniq=E41120B46C92D3818E72B> Now the subscriber is registered on the Softswitch with the IP from the Kamailio. And now the Kamailio get the incoming Call, but directly route it back to the Softwitch and the call failed. Now my questions: - Is the "Edge Proxy Configuration" right for this setup? - How the Kamailio keep all registered IPs and Lines to route an incoming Call to the right subscriber? - Why the Kamailio route an incoming call directly back to the Softswitch? Thanks a lot. Regards Thomas

1 0

Can't start Kamailio with both db_postgres and tls
by Øyvind Kolbu 28 Jan '15

28 Jan '15

Hi, I'm trying to add tls to our services, but seem hindered by "something". When enabling the tls module it seems to turn off the SSL setting in postgresql, and since we require SSL on our postgres servers Kamailio can't connect and it fails to start. If I disable WITH_TLS it will start. If I comment out the sqlops modparam it will also start. Kamailio on RHEL6, from ~4.1.6 git rev 2f690887b45dbc49a8038b1fa041d47cd9ae39ea. # kamailio -V version: kamailio 4.1.6 (x86_64/linux) flags: STATS: Off, 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, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 16:48:10 Sep 26 2014 with gcc 4.4.7 Very simpel config file: debug=3 log_stderror=no log_facility=LOG_LOCAL0 fork=yes children=2 #!define TLSFILE "/kamailio/tls-fooserver1.cfg" port=5060 #!define WITH_TLS #!ifdef WITH_TLS enable_tls=yes #!endif include_file "/kamailio/databases.cfg" loadmodule "tm.so" # Transaction (stateful) module loadmodule "tmx.so" # Extensions from Kamailio TM module loadmodule "sl.so" # Stateless replier module loadmodule "rr.so" # Record-Route and Route module loadmodule "pv.so" # Module holding Pseudo-Variables loadmodule "sqlops.so" # SQL operations loadmodule "db_postgres.so" # POSTGRES-backend for database API module #!ifdef WITH_TLS loadmodule "tls.so" #!endif modparam("sqlops","sqlcon",SQLOPS_DATA) #!ifdef WITH_TLS modparam("tls", "config", TLSFILE) #!endif route{ exit; } SQLOPS_DATA is just a normal "data=>postgres://user:pass@server/db". TLSFILE contains: [server:default] method = TLSv1 verify_certificate = no require_certificate = no private_key = /ssl/key certificate = /ssl/cert ca_list = /ssl/terena_chain2.pem [client:default] verify_certificate = no require_certificate = no From messages on startup: Dec 15 13:50:19 fooserver1 kamailio[12115]: INFO: tls [tls_init.c:385]: init_tls_compression(): tls: init_tls: disabling compression... Dec 15 13:50:19 fooserver1 kamailio[12115]: INFO: <core> [tcp_main.c:4836]: init_tcp(): init_tcp: using epoll_lt as the io watch method (auto detected) Dec 15 13:50:19 fooserver1 kamailio[12118]: WARNING: <core> [daemonize.c:352]: daemonize(): pid file contains old pid, replacing pid Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: rr [rr_mod.c:159]: mod_init(): outbound module not available Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_mod.c:346]: mod_init(): With ECDH-Support! Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_mod.c:349]: mod_init(): With Diffie Hellman Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_init.c:549]: init_tls_h(): tls: _init_tls_h: compiled with openssl version "OpenSSL 1.0.1e-fips 11 Feb 2013" (0x1000105f), kerberos support: on, compression: on Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_init.c:557]: init_tls_h(): tls: init_tls_h: installed openssl library version "OpenSSL 1.0.1e-fips 11 Feb 2013" (0x1000105f), kerberos support: on, zlib compression: on#012 compiler: gcc -fPIC -DO PENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -DTERMIO -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPEN SSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: WARNING: tls [tls_init.c:611]: init_tls_h(): tls: openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 5242880 and 2621440 bytes Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold1 has been changed to 5242880 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold2 has been changed to 2621440 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [udp_server.c:176]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is initially 124928 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [udp_server.c:227]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is finally 249856 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [udp_server.c:176]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is initially 124928 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [udp_server.c:227]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is finally 249856 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:275]: fill_missing(): TLSs<default>: tls_method=9 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:287]: fill_missing(): TLSs<default>: certificate='/path/ssl/fooserver1.uio.no.crt' Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:294]: fill_missing(): TLSs<default>: ca_list='/voip/packages/mgmt/ssl/terena_chain2.pem' Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:301]: fill_missing(): TLSs<default>: crl='(null)' Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:305]: fill_missing(): TLSs<default>: require_certificate=0 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:312]: fill_missing(): TLSs<default>: cipher_list='(null)' Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:319]: fill_missing(): TLSs<default>: private_key='/path/ssl/fooserver1.uio.no.key' Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:323]: fill_missing(): TLSs<default>: verify_certificate=0 Dec 15 13:50:19 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:326]: fill_missing(): TLSs<default>: verify_depth=9 Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:670]: set_verification(): TLSs<default>: No client certificate required and no checks performed Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:275]: fill_missing(): TLSc<default>: tls_method=9 Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:287]: fill_missing(): TLSc<default>: certificate='(null)' Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:294]: fill_missing(): TLSc<default>: ca_list='(null)' Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:301]: fill_missing(): TLSc<default>: crl='(null)' Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:305]: fill_missing(): TLSc<default>: require_certificate=0 Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:312]: fill_missing(): TLSc<default>: cipher_list='(null)' Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:319]: fill_missing(): TLSc<default>: private_key='(null)' Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:323]: fill_missing(): TLSc<default>: verify_certificate=0 Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:326]: fill_missing(): TLSc<default>: verify_depth=9 Dec 15 13:50:23 fooserver1 /usr/sbin/kamailio[12118]: INFO: tls [tls_domain.c:673]: set_verification(): TLSc<default>: Server MAY present invalid certificate Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: db_postgres [km_pg_con.c:82]: db_postgres_new_connection(): SSL SYSCALL error: Resource temporarily unavailable#012FATAL: no pg_hba.conf entry for host "129.240.1.1", user "foo_test_user", database " foo_test", SSL off#012 Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: db_postgres [km_pg_con.c:95]: db_postgres_new_connection(): cleaning up 0x7fce98be0c78=pkg_free() Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: sqlops [sql_api.c:166]: sql_connect(): failed to connect to the database [data] Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: <core> [sr_module.c:927]: init_mod_child(): init_mod_child(): Error while initializing module sqlops (/usr/lib64/kamailio/modules/sqlops.so) Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: <core> [pt.c:490]: fork_tcp_process(): ERROR: fork_tcp_process(): init_child failed for process 7, pid 12125, "tcp receiver (generic) child=0" Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12125]: ERROR: <core> [tcp_main.c:4962]: tcp_init_children(): ERROR: tcp_main: fork failed: Success Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12118]: ALERT: <core> [main.c:774]: handle_sigs(): child process 12125 exited normally, status=255 Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12118]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12126]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12124]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12123]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12122]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12121]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12120]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Dec 15 13:50:26 fooserver1 /usr/sbin/kamailio[12127]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received Any ideas? Best regards, Øyvind

4 22

Registration to Kamailio World 2015 is open
by Daniel-Constantin Mierla 28 Jan '15

28 Jan '15

Hello, I would like to announce that registration to Kamailio World 2015 is open: - http://conference.kamailio.com/k03/registration/ The schedule is still work in progress, a preview list with several speakers is available at: - http://conference.kamailio.com/k03/speakers/ The structure of the event contains: - pre-conference technical tutorials in the afternoon of May 27, 2015 - conference presentations during May 28-29, 2015 More details at: - http://conference.kamailio.com/k03/schedule/ Looking forward to meeting many of you and have a great time again in Berlin! Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Trouble getting start time / call duration from dialog module
by Will Ferrer 28 Jan '15

28 Jan '15

Hi All I am in need of being able to see what the duration of the call was at the time of hang out. I tried turning on the dialog module, but the result is that the values I need are either null or always show as zero. I tried to follow the suggestions in the thread about this here: http://lists.sip-router.org/pipermail/sr-users/2010-October/065889.html In the end my config looks like this: loadmodule "dialog.so" ... modparam("dialog", "dlg_flag", 4) modparam("dialog", "dlg_match_mode", 1) ... request_route { if (is_method("INVITE") && (! has_totag() ) ) { dlg_manage(); } if (is_method("BYE")) { $var(elapsed) = ( $TV(s) - $dlg(start_ts) ); xlog ("L_INFO", "request_route DIALOG TEST: Completed $dlg(from_uri) to $dlg(to_uri), elapsed: $var(elapsed), now seconds: $TV(s), dlg start time: $dlg(start_ts), DLG_lifetime: $DLG_lifetime"); } .... Note that I put at the top of the request route just for testing purposes The result I get in the log is this: INFO: <script>: request_route DIALOG TEST: Completed sip:willf1976Test@develop-sbc.switchsoft.com to sip:+18054515526@develop-sbc.switchsoft.com, elapsed: 1421305210, now seconds: 1421305210, dlg start time: 0, DLG_lifetime: <null> I was wondering if any one could point out to me what I have set up wrong. Thanks in advance All the best. Will Ferrer Switchsoft

3 9

GeoIP Module and IPv6 seems not to match
by Jöran Vinzens 28 Jan '15

28 Jan '15

Hi All, i'm trying to get GEO IP Location for an IPv6 Setup. We downloaded the GeoLiteCityv6.dat from maxmind and referred to it in modparams of geoip. If i now place a call from an V6 User and do something like: if(geoip_match("$si", "src")) { xlog("L_NOTICE", "Call comes from IP '$si' ($gip(src=>cc)) CID=$ci F=$fU URI=$ru\n"); append_hf("X-GeoIP: $gip(src=>cc)\r\n"); } it will not match for any reason if i xlog the src IP it look like: "Src IP = 2A01:abc:321:123:0:0:0:2" so it should match to the GEO IP Database. In CSV version of geo IP database there is an entry for my IP Address. Since the Module is not that verbose, i cannot tell whether the entry exists or not. Just the result in my "if" is False. Has anybody experience with GEOIP and IPv6? thanks Best regards, Jöran

3 4

Rpc question
by Pars3c 27 Jan '15

27 Jan '15

Hi, I need to request to kamailio the list of all the active dialog (with some dialog variable). Now , i'm doing it with a program that call the proxy with the xmlrpc module. The problem is that when it arrive to 350-400 calls, the reply fail because it has no memory free. Now ,i have setted the pkg memory to 12MB but at peak it reply with error. Now i shoul increase it. Is there another method to optimize the request of these data, to avoid every time to increase the memory parameter? Thanks to all

1 0

Re: [SR-Users] Need help on WebRTC with Kamailio as proxy
by rahul.ultimate 27 Jan '15

27 Jan '15

Kamailio is just acting as a proxy and protocol modifier so to say. It is workin with rtpengine from sipwise to handle media as evident from he logs. This architectue uses a TURN server and the browser is chrome with latest updates. The only thing whih I haven't done is enable TLS in kamailio and create certs. (which I'm not completely sure how to do).. Also, does it necessitates to have Apache ruuning https on 443 ? Thanks in advance Sent from Samsung Mobile -------- Original message -------- From: Gonzalo Gasca Meza <gascagonzalo(a)gmail.com> Date:27/01/2015 4:07 AM (GMT+05:30) To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] Need help on WebRTC with Kamailio as proxy Are you terminating media in Kamailio or just handling WS communication? If yes which version of Kamailio and rtp-proxy ? Have you tried passing media directly between Browser and Kamailio with any TURN server? Are you using latest Chrome version or FF ? A working sample config using the following architecture: https://github.com/spicyramen/llamato/tree/LlamatoReg signalling: sipml5 -- ws/wss --> Ec2 Kamailio --sip udp--> FS --sip udp--> * media: sipml5 ------------------------------------------------------------------------> * On Mon, Jan 26, 2015 at 12:44 PM, Rahul MathuR <rahul.ultimate(a)gmail.com> wrote: Hi Richard, Thanks for spending some cycles on it. It is OpenSSL 1.0.1e-fips 11 Feb 2013 On Tue, Jan 27, 2015 at 2:04 AM, Richard Fuchs <rfuchs(a)sipwise.com> wrote: On 26/01/15 02:21 PM, Rahul MathuR wrote: Hello, I am totally struck at a point while implementing Kamailio as proxy for WebRTC enabled UAC (Jssip). I am using Google's TURN server (rfc5766-turn-server for ICE/STUN). I am able to get to the point where the SIP server sends 183 session in progress to kamailio but after that I can only see - "STUN: using this candidate" "Successful STUN binding request from .." "SRTP output wanted, but no crypto suite was negotiated" This is fairly strange: Jan 27 00:35:46 localhost rtpengine[5262]: [tsb1jrsqsadn33jjsi4f port 30794] Failed to set up SRTP after DTLS negotiation: no SRTP protection profile negotiated Jan 27 00:35:46 localhost rtpengine[5262]: [tsb1jrsqsadn33jjsi4f port 30794] Failed to set up SRTP after DTLS negotiation: no SRTP protection profile negotiated Are you running a very old OpenSSL version by any chance? cheers _______________________________________________ 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 -- Warm Regds. MathuRahul _______________________________________________ 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

3 2

tcp_max_connection to 4096
by Varghese Paul 27 Jan '15

27 Jan '15

Hi Team, We are seeing some errors in our kamilio for TCP max conn (ERROR) : 2048 (the default). We are thinking to double the TCP connection for our kamailio registrar server. tcp_max_connections=4096 Is there any performance issue if we double the tcp_max_connections ?. Currently we are setting these parameters for TCP. tcp_connection_lifetime=3605 tcp_accept_no_cl=yes tcp_rd_buf_size=16384 Do we need to tune any other variable if we are setting max tcp connections to 4096 for better performance ? Thanks for looking into this. Regards Varghese Paul

2 1

Jump to page:

2025

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