sr-users October 2012

sr-users@lists.kamailio.org

87 participants
164 discussions

getting siptrace error on start up
by Christopher Holland 23 Oct '12

23 Oct '12

getting this error: kamailio: ERROR: <core> [modparam.c:151]: set_mod_param_regex: parameter <trace_to_database> not found in module <siptrace> parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 63, column 46: Can't set module parameter I have set this to modparam("siptrace", "trace_to_database", "0") in my .cfg /I didn't compile siptrace when I compiled kamailio. I don't know how to add a module after compiling and installing kamailio. I haven't been able to find any documentaion on how to add a module after installing only compiling before installing. Thanks all for your help Christopher /

3 3

Kamailio Hosted Solutions
by Satyajeet Thokchom 23 Oct '12

23 Oct '12

I am looking for hosted Kamailio Solutions for my VOIP calling app in android and iphone. I have the app ready and have even setup kamailio server in our rackspace cloud but there is many problems like one way calling, noisy calls, no call connection etc. (application VOIP library , we are using IMSdroid and Idoubs , based on doubango SIP) I am looking for a hosted solutions affordable for me - with a support for 300 concurrent calls at a time. Best Regards, Satyajeet Thokchom Business Manager, NGBM Solutions Ltd Phone: India:+91-11-25541320 Mobile: 91 7428565264 Website: www.ngbm.net Web Support: www.ngbmsolutions.com Note: "This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately; you should not copy or use it for any purpose, nor disclose its contents to any other person"

1 0

turning off rev. dns
by Christopher Holland 22 Oct '12

22 Oct '12

I'm setting up Homer with kamailio for sip capturing. I've got it all set up and am getting this error. I have one interface for packet capture on a mirroired port and one interface for managment. I'm thinking that I have to only have kamailio listen on the packet capture interface and not the managment interface. Would that resolve this issue? loading modules under /usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/ 0(1832) WARNING: <core> [socket_info.c:1406]: WARNING: fix_hostname: could not rev. resolve 192.168.111.88 Listening on udp: 127.0.0.1:5060 udp: 192.168.111.88:5060 Aliases: udp: localhost:5060 config file ok, exiting... sense it's a local address it's not possible to do a rev. resolve of that address. Is there a way to turn off the rev. resolve. I've looked at this in the trouble shooting faq. How do I avoid Reverse-DNS-Lookups? A: Simply not use src_ip = "11.22.33.44" and use instead src_ip = 11.22.33.44! We had in our installation some serious trouble with requests coming from systems, where the hostname could not be reverse resolved (the DNS-Server responsible for this IP-Range was poorly configured and would not answer at all).

3 3

Remote Commands
by Ed Brady 22 Oct '12

22 Oct '12

Hi, I am trying to get a company who handles our billing and account provisioning connected to our Kamailio instance. I understand that XMLRPC is likely the best method for doing this, but I am unable to find direct commands equivalent to "kamctl add" or "kamctl rm". Is there a resource that lists the MI or XMLRPC commands, or do I need to create even simple commands? Thanks, Ed

2 4

Hangup call on leg B side
by pars3c 22 Oct '12

22 Oct '12

Hi , i don't know how to realize this: A --- INVITE---->proxy ----INVITE----> B <--- 200 OK ---BYE----> ---INVITE ----->C <--- 200 OK proxy <--- 200 OK -------ACK ---> -------ACK ---> When B answer the call, the proxy should immediately hang up the call and make a new invite. For user A is always the same call. I tried this : onreply_route { ################################ connect if (is_method("INVITE") && status == "200") { dlg_bye("callee"); drop(); } } But it doesn't work. When arrive 200 , the proxy drop the message to the user a , wait for a while, and then send a cancel to b (it should send a BYE, instead send a CANCEL, probably because it not have a ACK). How can I try this? Thanks

2 1

Kamailio 3.1.5 crashing during TLS connection setup
by Kamal Palei 22 Oct '12

22 Oct '12

Dear All I have setup Kamailio 3.1.5 with TLS enabled. Whenever I receive the REGISTER request from endpoint, trying to forward to next proxy. For that I have added below code in kamailio.cfg * if(is_method("REGISTER")) { t_relay_to("tls:115.114.48.75:5061"); exit(); } *I see once REGISTER received at Kamailio proxy, it is sending TCP synch packet to next proxy, next proxy sends back a synch+reset packet. Then kamailio proxy is crashing with log as below. *root@B2BUA:/usr/local/src/scripts# 9(2347) ERROR: <core> [tcp_main.c:4139]: connect 115.114.48.75:5061 failed 9(2347) : <core> [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil) (out of memory block!) - aborting * The complete log is given as below. Please let me know how to get out of this issue. I used -m 64 option while starting proxy, but same result. Thanks, Kamal, NECS, Bangalore * 0(2336) INFO: <core> [tcp_main.c:4730]: init_tcp: using epoll_et io watch method (config) 0(2338) INFO: usrloc [hslot.c:53]: locks array size 512 0(2338) INFO: tls [tls_init.c:511]: tls: _init_tls_h: compiled with openssl version "OpenSSL 1.0.1c 10 May 2012" (0x1000103f), kerberos support: off, compression: on 0(2338) INFO: tls [tls_init.c:519]: tls: init_tls_h: installed openssl library version "OpenSSL 1.0.1c 10 May 2012" (0x1000103f), kerberos support: off, zlib compression: off compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM 0(2338) INFO: tls [tls_init.c:373]: tls: init_tls: disabling compression... 0(2338) WARNING: tls [tls_init.c:587]: 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 0(2338) INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): tls.low_mem_threshold1 has been changed to 5242880 0(2338) INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): tls.low_mem_threshold2 has been changed to 2621440 0(2338) INFO: <core> [udp_server.c:184]: INFO: udp_init: SO_RCVBUF is initially 112640 0(2338) INFO: <core> [udp_server.c:235]: INFO: udp_init: SO_RCVBUF is finally 262142 0(2338) INFO: <core> [udp_server.c:184]: INFO: udp_init: SO_RCVBUF is initially 112640 0(2338) INFO: <core> [udp_server.c:235]: INFO: udp_init: SO_RCVBUF is finally 262142 0(2338) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 0(2338) INFO: tls [tls_domain.c:176]: TLSs<default>: tls_method=9 0(2338) INFO: tls [tls_domain.c:188]: TLSs<default>: certificate='/etc/certs/pocserver.com/cert.pem' 0(2338) INFO: tls [tls_domain.c:195]: TLSs<default>: ca_list='(null)' 0(2338) INFO: tls [tls_domain.c:202]: TLSs<default>: crl='(null)' 0(2338) INFO: tls [tls_domain.c:206]: TLSs<default>: require_certificate=0 0(2338) INFO: tls [tls_domain.c:213]: TLSs<default>: cipher_list='(null)' 0(2338) INFO: tls [tls_domain.c:220]: TLSs<default>: private_key='/etc/certs/pocserver.com/key.pem' 0(2338) INFO: tls [tls_domain.c:224]: TLSs<default>: verify_certificate=0 0(2338) INFO: tls [tls_domain.c:227]: TLSs<default>: verify_depth=9 0(2338) INFO: tls [tls_domain.c:544]: TLSs<default>: No client certificate required and no checks performed 0(2338) INFO: tls [tls_domain.c:176]: TLSc<default>: tls_method=9 0(2338) INFO: tls [tls_domain.c:188]: TLSc<default>: certificate='(null)' 0(2338) INFO: tls [tls_domain.c:195]: TLSc<default>: ca_list='(null)' 0(2338) INFO: tls [tls_domain.c:202]: TLSc<default>: crl='(null)' 0(2338) INFO: tls [tls_domain.c:206]: TLSc<default>: require_certificate=1 0(2338) INFO: tls [tls_domain.c:213]: TLSc<default>: cipher_list='(null)' 0(2338) INFO: tls [tls_domain.c:220]: TLSc<default>: private_key='(null)' 0(2338) INFO: tls [tls_domain.c:224]: TLSc<default>: verify_certificate=1 0(2338) INFO: tls [tls_domain.c:227]: TLSc<default>: verify_depth=9 0(2338) INFO: tls [tls_domain.c:529]: TLSc<default>: Server MUST present valid certificate 2(2340) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 1(2339) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 4(2342) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 0(2338) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 6(2344) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 3(2341) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 7(2345) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 6(2344) INFO: ctl [io_listener.c:224]: io_listen_loop: using epoll_et io watch method (config) root@B2BUA:/usr/local/src/scripts# 9(2347) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled 8(2346) INFO: rtpproxy [rtpproxy.c:1403]: rtp proxy <udp:127.0.0.1:7729> found, support for it enabled root@B2BUA:/usr/local/src/scripts# 9(2347) ERROR: <core> [tcp_main.c:4139]: connect 115.114.48.75:5061 failed 9(2347) : <core> [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil) (out of memory block!) - aborting 0(2338) ALERT: <core> [main.c:742]: child process 2347 exited by a signal 6 *

2 2

Listen on all IPv6 addresses
by Anton Kvashenkin 22 Oct '12

22 Oct '12

Hello guys. In the Kamailio v.3.3.0 release notes http://www.kamailio.org/w/kamailio-v3-3-0-release-notes/ it says: all IPv6 network interfaces are auto-detected and Kamailio start listening on them (if no strict listening rules are set) But it doesn't happen. version: kamailio 3.3.1 (x86_64/linux) d75cb5 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, 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 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: d75cb5 listen is commented out @ cfg

2 1

Re: [SR-Users] rtpproxy delete fails
by Juha Heinanen 22 Oct '12

22 Oct '12

the patch below adds 't' flag to rtpproxy_destroy flags. if 't' flag is present when rtpproxy_destroy is called, to tag is not included in D command sent to rtpproxy thus causing destroy of the full call. 't' flag can be used to avoid piling up of unused rtpproxy calls by making it possible to call rtpproxy_destroy when 200 ok is received from a branch where rtpproxy is not used. is it ok for me to commit this patch or do long term rtpproxy users have a better idea? it would still make sense to include a timer in rtpproxy that cleans up un-used calls at an interval that corresponds to sip proxy's invite timeout. -- juha *** /usr/src/orig/sip-router/modules/rtpproxy/rtpproxy.c 2012-10-19 14:31:27.658485534 +0300 --- modules/rtpproxy/rtpproxy.c 2012-10-20 09:52:10.308389743 +0300 *************** *** 1678,1683 **** --- 1678,1684 ---- str callid, from_tag, to_tag, viabranch; char *cp; int via = 0; + int to = 1; int ret; struct rtpp_node *node; struct iovec v[1 + 4 + 3 + 2] = {{NULL, 0}, {"D", 1}, {" ", 1}, {NULL, 0}, {NULL, 0}, {NULL, 0}, {" ", 1}, {NULL, 0}, {" ", 1}, {NULL, 0}}; *************** *** 1700,1705 **** --- 1701,1710 ---- via = 1; break; + case 't': + case 'T': + to = 0; + break; case 'a': case 'A': case 'i': *************** *** 1736,1742 **** return -1; } to_tag.s = 0; ! if (get_to_tag(msg, &to_tag) == -1) { LM_ERR("can't get To tag\n"); return -1; } --- 1741,1748 ---- return -1; } to_tag.s = 0; ! to_tag.len = 0; ! if ((to == 1) && get_to_tag(msg, &to_tag) == -1) { LM_ERR("can't get To tag\n"); return -1; }

2 1

mediaproxy-ng fails to parse start_recording() command
by Juha Heinanen 22 Oct '12

22 Oct '12

i tried what happens when i call start_recording() after calling rtpproxy_manage() and got this kind of error to syslog: Oct 20 19:57:43 siika mediaproxy-ng[8423]: Failed to properly parse UDP command line '8554_13 R ngsgznnwgzpuovt(a)siika.tutpro.com mgpwe' from 127.0.0.1:51497, using fallback RE why the error? it is so that mediaproxy-ng does not support recording? -- juha

4 3

Re: [SR-Users] dangers of excluding 100rel?
by Alex Balashov 19 Oct '12

19 Oct '12

You can strip 100rel as long as it's Supported. However, not so good things happen if you strip it from Required. :-) -- Alex -- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/Andrew Mortensen <admorten(a)isc.upenn.edu> wrote:Can I safely strip 100rel support from INVITEs sent by callers registered to my proxy? We're using proxy-generated 302 redirects for call forwarding in our deployment. In general this works better for us than appending branches, as we rapidly ran into branch limits when dealing with large multiple appearance lines. However, we've run into a case where the caller, a Polycom 550, seems to get confused when a parallel forked call is redirected, 100rel is in use and the redirection target is also a multiple appearance line. The caller is correctly responding with PRACKs to all 180s, before and after the redirection. However, hanging up the call on the caller after the redirection, but before any remote party has answered, does *not* cause the caller to send a CANCEL to tear down the call. In fact, the caller doesn't send anything at all. The remote parties continue to ring until the ring timer expires, and the proxy sends CANCELs to all callee endpoints. That's clearly a Polycom bug, and we'll need to work with them to get it resolved. In the meantime, I'm looking for workarounds. One quick, crude option is to strip 100rel from the Supported header in the caller's INVITE. I've tested this, and it does solve the problem, but I'm concerned about side effects. I'm aware of the value 100rel has for calls to the PSTN, but in this case the calls never leave the local network. Are there situations where 100rel is critical for a parallel forked call? andrew _______________________________________________ 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

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
17
Older →

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 October 2012