sr-users November 2015

sr-users@lists.kamailio.org

80 participants
125 discussions

[CFP] reminder! FOSDEM RTC dev-room talks: deadline Friday
by Daniel Pocock 25 Nov '15

25 Nov '15

Reminder: speaker's deadline this Friday, 27 November at 23:59 UTC We have already received several really exciting talk proposals but there is still time for people to propose talks or encourage friends or colleagues to speak. Many other dev-rooms also have a deadline in the next few days and if your topic is applicable to more than one dev-room, you are welcome to make more than one submission. Please contact us or put a note in the memo field at the top of the talk proposal if you do that. All projects are encouraged to consider making a lightning talk too, it is an excellent opportunity to get exposure for your project: even though you only have 15 minutes, it can be a much larger and more diverse audience than in some dev-rooms. For full details, please see the call for papers: http://danielpocock.com/fosdem-2016-free-rtc-dev-room-and-lounge We invite all potential speakers and participants to discuss the selection process and other aspects of FOSDEM on the Free-RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc

1 0

Kamailio v4.3.4 Released
by Daniel-Constantin Mierla 25 Nov '15

25 Nov '15

Hello, Kamailio SIP Server v4.3.4 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.4. For more details about version 4.3.4 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/11/kamailio-v4-3-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

TLS not enough memory issue with git master
by Anthony Messina 25 Nov '15

25 Nov '15

I have noticed the following issue which began with builds somewhere between git master commits bff0a08 and 6173ef7. I did not see this issue with my previous builds and haven't been able to pin down the problem, which is why I haven't formally filed a bug. Any help or guidance is appreciated, because this has crippled my use of Kamailio. Only a restart enables it to work again until the issue recurs. ERROR: tls [tls_server.c:189]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: 8870536 ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading I currently build against and run openssl-1.0.1k-12.fc22.x86_64. I have a very small operation and the only change on the operational side is that all 5 of my mobile UACs (yes, that's all) have switched from CSipSimple/Android to Zoiper/Android, which doesn't yet have support for client-side certificates so verify_certificate and require_certificate are off for both the server and client config. The server is started with: /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -m 64 -M 8 I have tried modifying the shared mem to 128 but the issue still occurs. Even right now, I am seeing the error when only one UAC has established a TLS connection: # kamcmd tls.list { id: 572 timeout: 3475 src_ip: 10.77.79.156 src_port: 58688 dst_ip: 10.77.79.3 dst_port: 5061 cipher: ECDHE-RSA-RC4-SHA SSLv3 Kx=ECDH Au=RSA Enc=RC4(128) Mac=SHA1 ct_wq_size: 0 enc_rd_buf: 0 flags: 2 state: established } # kamailio.cfg enable_tls=yes loadmodule "tls.so" modparam("tls", "connection_timeout", 60) #modparam("tls", "tls_log", 1) #modparam("tls", "tls_debug", 1) #modparam("tls", "low_mem_threshold1", -1) #modparam("tls", "low_mem_threshold2", 0) modparam("tls", "session_cache", 1) # tls.cfg [server:default] method = TLSv1+ verify_certificate = no require_certificate = no private_key = /etc/kamailio/example.org.key.pem certificate = /etc/kamailio/example.org.crt.pem server_name = example.org cipher_list = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA- AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256- SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-GCM- SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:RC4- SHA:AES256-GCM-SHA384:AES256-SHA256:CAMELLIA256-SHA:ECDHE-RSA-AES128- SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:CAMELLIA128- SHA:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK [client:default] method = TLSv1+ verify_certificate = no require_certificate = no private_key = /etc/kamailio/example.org.key.pem certificate = /etc/kamailio/example.org.crt.pem cipher_list = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA- AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256- SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-GCM- SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:RC4- SHA:AES256-GCM-SHA384:AES256-SHA256:CAMELLIA256-SHA:ECDHE-RSA-AES128- SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:CAMELLIA128- SHA:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK Thanks. -Anthony -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

3 16

Kamailio/RTPProxy incorrect port 0
by Igor Potjevlesch 25 Nov '15

25 Nov '15

Hello, I can't figure out why Kamailio reports hundreds of calls with the following error: "/usr/local/sbin/kamailio[2997]: ERROR: rtpproxy [rtpproxy.c:2727]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy" It seems that each time this error occurs, we got a one-way audio call. I already check and increase the limit for opening files that the process can open with ulimit -n 500000. But, anyway, if I look to /proc/$PID/fd, I never see more than 1000 files open. I also check the socket with netstat: same; I can see the error while there's only less than 800 sockets open. Is someone know what can be the trigger of this? Regards, Igor.

5 10

Kamailio:Contact validation during INVITE
by Prashant Desai 25 Nov '15

25 Nov '15

Hi, We observe that the following kamailio API is trying to find out user registration by comparing source IP and port with stored contact, if it fails, then it compares based on incoming SIP msg contact uri. is_registered(struct sip_msg* _m, udomain_t* _d){ getContactP(_m,_d); } pcontact_t * getContactP(struct sip_msg* _m, udomain_t* _d) {); //Getting pcontact from source IP and port if (ul.get_pcontact_by_src(_d, &received_host, _m->rcv.src_port, _m->rcv.proto, &c) == 1) { LM_DBG("No entry in usrloc for %.*s:%i (Proto %i) found!\n", received_host.len, received_host.s, _m->rcv.src_port, _m->rcv.proto); } if (c == NULL) { //Getting pcontact from contact uri. if (ul.get_pcontact(_d, &ct->uri, &c) == 0) { } } We have use case where INVITE message is from same source IP and port but having unregistered contact.With this scenario,is_registered() will return success. We would like to know reason behind comparing the source IP and port to fetch the pcontact? Regards, Prashant

3 5

Releasing Kamailio v4.3.4
by Daniel-Constantin Mierla 25 Nov '15

25 Nov '15

Hello, I am considering to release Kamailio v4.3.4 next week on Wed, Nov 25 or the following day. As usual, announce any issues that you are aware and not reported to sr-dev or bug tracker. Also, if some patch was not backported and you think it has to be, write to sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat

1 1

Build error on Solaris 11 with Solaris Studio
by Spencer Thomason 25 Nov '15

25 Nov '15

Hello, I realize its probably uncharted waters but I was hoping someone could point me in the right direction… I attempting to build Kamailio on a UltraSPARC T2 box running Solaris 11.3 with Sun cc and I’m not getting very far: $ CC=cc gmake all CC (cc) [kamailio] timer_proc.o cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit programs "timer_funcs.h", line 111: warning: argument mismatch "timer_funcs.h", line 111: syntax error before or at: __func__ "timer_funcs.h", line 111: syntax error before or at: __func__ "timer_funcs.h", line 111: syntax error before or at: __func__ "timer_funcs.h", line 111: syntax error before or at: __func__ "timer_funcs.h", line 111: syntax error before or at: __func__ "cfg/../atomic/atomic_unknown.h", line 59: #warning: no native memory barrier implementations, falling back to slow lock based workarround "cfg/../lock_alloc.h", line 72: warning: argument mismatch "cfg/../lock_alloc.h", line 72: syntax error before or at: __func__ "cfg/../lock_alloc.h", line 72: syntax error before or at: __func__ "cfg/../lock_alloc.h", line 72: syntax error before or at: __func__ "cfg/../lock_alloc.h", line 72: syntax error before or at: __func__ "cfg/../lock_alloc.h", line 72: syntax error before or at: __func__ "ut.h", line 236: warning: argument mismatch "ut.h", line 236: syntax error before or at: __func__ "ut.h", line 236: syntax error before or at: __func__ "ut.h", line 236: syntax error before or at: __func__ "ut.h", line 236: syntax error before or at: __func__ "ut.h", line 236: syntax error before or at: __func__ "ut.h", line 240: warning: argument mismatch Any help would be greatly appreciated! The contents of config.mak are below: # this file is autogenerated by make cfg MAIN_NAME= kamailio CFG_NAME= kamailio SCR_NAME= sip-router FLAVOUR= kamailio INSTALL_FLAVOUR= kamailio SRC_NAME= sip-router RELEASE= 4.3.3 OS= solaris ARCH= sparc64 C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.3.3"' -DARCH='"sparc64"' -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"cc 5.1"' -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4003003 -DCFG_DIR='"/usr/local/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DDBG_QM_MALLOC -DMEM_JOIN_FREE -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DUSE_PTHREAD_MUTEX -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H DEFS_RM= PROFILE= CC= cc LD= cc MKDEP= cc -xM1 MKTAGS= ctags LDFLAGS= -xO5 C_INCLUDES= CC_MKDEP_OPTS= MOD_LDFLAGS= -G -xO5 LIB_LDFLAGS= -G -xO5 UTILS_LDFLAGS= -xO5 LIB_SONAME= "-h " LD_RPATH= -"-R " LIB_SUFFIX= .so LIB_PREFIX= lib LIBS= -lfast -ldl -lresolv -L/usr/local/lib -lxnet -lnsl -lrt LEX= flex YACC= yacc YACC_FLAGS= -d -b cfg PREFIX= /usr/local LOCALBASE= /usr/local TAR= gtar INSTALL= ginstall INSTALL_CFG= ginstall -m 644 INSTALL_BIN= ginstall -m 755 INSTALL_MODULES= ginstall -m 755 INSTALL_DOC= ginstall -m 644 INSTALL_MAN= ginstall -m 644 INSTALL_LIB= ginstall -m 755 INSTALL_TOUCH= touch INSTALL_SHARE= ginstall -m 644 Q= 1 CC_EXTRA_OPTS= CPU= CFLAGS_RM= CFLAGS= -m64 -g -xO5 -fast -native -xarch=v9 -xCC -xc99 $(CC_EXTRA_OPTS) MOD_CFLAGS= -xcode=pic32 $(CFLAGS) LIB_CFLAGS= -xcode=pic32 $(CFLAGS) UTILS_CFLAGS= $(CFLAGS) BASEDIR= $(DESTDIR) basedir= $(BASEDIR) DESTDIR= LIBDIR= lib64 RUNBASEDIR= $(DESTDIR) runbasedir= $(RUNBASEDIR) PREFIX= $(LOCALBASE) prefix= $(PREFIX) cfg_prefix= $(basedir)$(prefix) cfg_dir= etc/$(MAIN_NAME)/ bin_prefix= $(basedir)$(prefix) bin_dir= sbin/ modules_prefix= $(basedir)$(prefix) modules_dir= $(LIBDIR)/$(MAIN_NAME)/ doc_prefix= $(basedir)$(prefix) doc_dir= doc/$(MAIN_NAME)/ man_prefix= $(basedir)$(prefix) man_dir= man/ ut_prefix= $(basedir)$(prefix) ut_dir= share_prefix= $(basedir)$(prefix) share_dir= share/$(MAIN_NAME)/ lib_prefix= $(basedir)$(prefix) lib_dir= $(LIBDIR)/$(MAIN_NAME)/ data_prefix= $(basedir)$(prefix) data_dir= $(MAIN_NAME)/ cfg_target= $(prefix)/$(cfg_dir) lib_target= $(prefix)/$(lib_dir) data_target= $(prefix)/$(data_dir) run_prefix= $(runbasedir) run_dir= var/run/$(MAIN_NAME)/ run_target= $(run_prefix)/$(run_dir) override makefile_defs:=1 C_DEFS:=$(filter-out $(DEFS_RM) $(extra_defs),$(C_DEFS)) $(extra_defs) CFLAGS:=$(filter-out $(CFLAGS_RM) $(CC_EXTRA_OPTS), $(CFLAGS)) $(CC_EXTRA_OPTS) Thanks! Spencer

1 0

Grab users password from WWW-Auth header
by Alexandru Covalschi 24 Nov '15

24 Nov '15

Hello! My problem is I need to do users authentication through API. So I need to replace if (!www_authenticate("$td", "subscriber")) { www_challenge("$td", "1"); } With if (!my_auth_script()) { www_challenge("$td", "1"); } The main problem is - how can I grab or compare users password? I know nonce, which I understand is MD5 salt. Can I, for example, grab users password from API, then grab the MD5 string and the nonce user sent me, calculate MD5 on base of API password and nonce - and then compare MD5 strings sent by user and calculated? -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

3 11

Issue with SNMPstats
by Igor Potjevlesch 24 Nov '15

24 Nov '15

Hello, I have configured the SNMPstats module fine in my machine because I get the SNMP information with the new KAMAILIO MIBS but I don't understand why the value of kamailio dialogs is always 0: KAMAILIO-MIB::kamailioCurNumDialogs.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInProgress.0 = Gauge32: 0 KAMAILIO-MIB::kamailioCurNumDialogsInSetup.0 = Gauge32: 0 KAMAILIO-MIB::kamailioTotalNumFailedDialogSetups.0 = Counter32: 0 However I can see the transactions: KAMAILIO-SIP-COMMON-MIB::kamailioSIPSummaryTotalTransactions.0 = Counter32: 54797 Should I configure an specific parametr of the SNMPstats module? Regards,

3 6

MESSAGE is not successfull in Kamailio IMS
by Thierry Luo 24 Nov '15

24 Nov '15

Hi All, I installed kamailio on Ubuntu as IMS pCSCF/iCSCF/sCSCF. REGISTER is fine, but when I tried to send a MESSAGE (SMS) from one user to another, it was always not successful. I captured IP packets on the server, and it seemed that the error was caused on pCSCF. User1 and User2 are both behind their NAT network. Suppose User1's private IP is Private_IP1, and User1's public IP (on router) is Public_IP1, and User2's private and public IPs are Private_IP2 and Public_IP2: User1 pCSCF iCSCF sCSCF user2 MESSAGE ----------------> MESSAGE ---------------------> MESSAGE -------------------> MESSAGE <----------------------------------------------------- MESSAGE ---------------------------------------------------------------------------- ----> Unfortunately, from the captured data on the server, in the last step, the MESSAGE was sent to the Private_IP2 of User2. It should be sent to the Public_IP2. Of course, the datagram with the destination of Private_IP2 cannot reach User2 successfully. Please help analyze why the pCSCF sent the MESSAGE packet to User2's private IP instead of public IP. The configuration file was attached for reference. BR. Thierry Luo

2 6

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2026

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 November 2015