sr-users

sr-users@lists.kamailio.org

19 participants
37529 discussions

Re: [SR-Users] pdb module timeouts
by Thomas Baumann 15 Feb '11

15 Feb '11

Hello, I did a fallback to the original source, without sucess. I still have massive timeouts. So far I have no idea, how to go on. ps. what lenght of the carrier codes would be ok ? 3...10 digits, additional characters needed like A,B,C,D,E,F? regards, Thomas Hi Henning, this change was done at pdbt.c: $ diff pdbt.c pdbt_changed.c 245c245 < bufsize = slen + 1 + 1 + 3 + 1 + 1; // line buff er (telephone number + colon + white space + carrier ID + newline + \0) --- > bufsize = slen + 1 + 1 + 4 + 1 + 1; // line buff er (telephone number + colon + white space + carrier ID + newline + \0) 257,258c257,258 < ret = snprintf(p, 5, "%d\n", node->carrier); < if (ret < 1 || ret > 4) { --- > ret = snprintf(p, 6, "%d\n", node->carrier); > if (ret < 1 || ret > 5) { If I run querys in filemode against the server, where is no timeout. pdbt query -f /tmp/numbers3 -r 10.12.18.21:10001 -q 1 | grep answer regards, Thomas -----Ursprüngliche Nachricht----- Von: "Henning Westerholt" <henning.westerholt(a)1und1.de> Gesendet: 11.02.2011 09:33:05 An: sr-users(a)lists.sip-router.org Betreff: Re: [SR-Users] pdb module timeouts On Wednesday 09 February 2011, Thomas Baumann wrote: > I am using the PDB module and server components for number portability. 2 > instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on > (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10 > -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded > timeout while waiting for response. > > One requested number was 307111094, where the module prints out a timeout. > > The funny part is, that I can see the responses at least arriving at the > 10.12.19.21 interface on time. > > Request send: 0,200855 s > Answer received: 0,201027 s > > That are 0,172 ms and far away from a timeout. > > What could be the reason ? Hi Thomas, a bit difficult to say on a first sight.. Maybe some scheduling or load issues on the local machine? I've just checked two production server here, i don't see it so far in the available logs. How much load do you've on the machine? And what kind of timeout value do you specified? > ps. A small change on the server part was done: handle 4 digit carrier > codes. Ah, i see. I guess its not a big change? Regards, Henning ___________________________________________________________ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar

2 1

CORE postgres module
by Bruno Bresciani 15 Feb '11

15 Feb '11

Hi, During my tests with kamailio 1.5.0 a core is generated when postgres is disconnected and I try register a user or make a call in kamailio. Analising the module postgres source code I notice that core is generated by the PQescapeStringConn located in db_postgres_val2str function. Someone know why this core is generated? Best Regards

2 2

Issue with avp
by Amit Nepal 14 Feb '11

14 Feb '11

Hi, I have been trying to load rpid while loading credentials. modparam("auth_db", "load_credentials", "$avp(i:123)=rpid") Now, I am trying to do a check in my routing logic. xlog("L_NOTICE","The avp is :$avp(i:123)"); (I dont get the value here either, i can't see the value when i do avp_print() if($avp(i:123)<5) { sl_send_reply("408","Message Here"); } I dont get the value of avp at that place. Any guidance please. -- Thank You Amit Nepal Systems Administrator Phoenix Internet Phone: 602-385-0731 602-234-0917#112 http://www.phoenixinternet.net

2 4

kamailio 1.5.5 crashes continue
by Andrew O. Zhukov 14 Feb '11

14 Feb '11

Core was generated by `/usr/local/sbin/kamailio -P /var/run/openser/openser.pid -m 32 -u openser -g op'. Program terminated with signal 6, Aborted. #0 0x00000039d8c30265 in raise () from /lib64/libc.so.6 (gdb) backtrace #0 0x00000039d8c30265 in raise () from /lib64/libc.so.6 #1 0x00000039d8c31d10 in abort () from /lib64/libc.so.6 #2 0x000000000046c397 in qm_debug_frag (qm=0x733c00, f=0x841420) at mem/q_malloc.c:137 #3 0x000000000046d99a in qm_free (qm=0x733c00, p=0x841450, file=0x4e4d30 "parser/digest/digest.c", func=0x4e4da0 "free_credentials", line=95) at mem/q_malloc.c:439 #4 0x0000000000495fac in free_credentials (_b=0x2b875404a130) at parser/digest/digest.c:95 #5 0x0000000000471a36 in clean_hdr_field (hf=0x2b875404a100) at parser/hf.c:116 #6 0x00002b8750ab78de in clean_msg_clone (msg=0x2b8754049130, min=0x2b8754049130, max=0x2b875404a748) at sip_msg.h:54 #7 0x00002b8750ab77b7 in run_trans_callbacks (type=2, trans=0x2b8754057ec0, req=0x2b8754049130, rpl=0x7c0eb8, code=200) at t_hooks.c:245 #8 0x00002b8750abe39d in t_reply_matching (p_msg=0x7c0eb8, p_branch=0x7fffbe5d11e8) at t_lookup.c:888 #9 0x00002b8750abe997 in t_check (p_msg=0x7c0eb8, param_branch=0x7fffbe5d11e8) at t_lookup.c:964 #10 0x00002b8750acd79b in reply_received (p_msg=0x7c0eb8) at t_reply.c:1395 #11 0x000000000041c6db in forward_reply (msg=0x7c0eb8) at forward.c:576 #12 0x000000000043ccf0 in receive_msg ( buf=0x712980 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP XXX.XX.XXX.13;branch=z9hG4bK8aa9.93e271f1.0;received=XXX.XX.XXX.13\r\nVia: SIP/2.0/UDP XXX.XX.XXX.236:5060;received=XXX.XX.XXX.236;branch=z9hG4bK37dacff3;rport=5060\r\nRec"..., len=576, rcv_info=0x7fffbe5d1340) at receive.c:212 #13 0x00000000004692e3 in udp_rcv_loop () at udp_server.c:449 #14 0x0000000000420ecb in main_loop () at main.c:774 #15 0x0000000000422e0f in main (argc=11, argv=0x7fffbe5d15c8) at main.c:1321 (gdb) q [root@ tmp]# openser -V version: kamailio 1.5.5-notls (x86_64/linux) flags: STATISTICS, EXTRA_DEBUG, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, PKG_SIZE 4194304 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. svnrevision: unknown @(#) $Id: main.c 5608 2009-02-13 16:48:17Z henningw $ main.c compiled on 09:42:37 Feb 10 2011 with gcc 4.1.2 Andrew.

2 3

kamailio and MySQL licensing question
by Siddhardha Garige 14 Feb '11

14 Feb '11

hello all, I have a question regarding MySQL licensing. We configured kamailio to work in edge proxy mode with drive-by registration to support our network architecture. One of our clients is interested in conducting some trails with us and we are setting up a test network at client's facility. As a part of this process we will be installing our custom kamailio on their servers with MySQL. We are not charging our client for kamailio and mysql implementation since they both are open source implementations. But we will be charging them for our time at clients facility. Are we violating any MySQL license policies by installing our custom kamailio with MySQL for our client? thanks Sid "May the light be with you." ______________________________________________ Siddhardha Garige www.luminepixels.com

2 1

Re: [SR-Users] Kamailio 1.5.4 and beyond - mhomed issue under Linux
by Sean O'Donnell 14 Feb '11

14 Feb '11

Hi all, I checked the GIT repository and noticed that there was a patch in forward.c for this issue. Looks like it was done 11/4/2010. Two questions: 1) Is there any reason that patch didn't make it into Kamailio 3.1.2 ? 2) Any reason I shouldn't apply that patck to my 1.5.4 release? Thanks, Sean O'Donnell Senior Engineer uReach Technologies, Inc. ---- On Thu, 10 Feb 2011, Sean O'Donnell (skodonnell(a)ureach.com) wrote: Hi all, I just started deploying Kamailio release 1.5.4, and I think there's an issue with how Kamailio identifies an outgoing interface when mhomed is enabled under Linux. I use Kamailio as a call distributor/proxy between a soft-switch/SBC and a voicemail platform. It runs on a CentOS 5.3 (Linux 2.6 kernel) host with two network interfaces and is configured such that it listens on both interfaces. One interface (public interface) handles traffic with the SBC, the other (private interface) handles with the VM platform. The 'mhomed' option is enabled. After upgrading from 1.5.3 to 1.5.4, I started noticing problems with UDP packets coming out of the public interface. After looking at some ngrep captures on that interface, I noticed that some packets had the source IP address of the private interface and also had Record-Route and Via headers for the private interface only - no headers for the public interface were there. Usually when I see the wrong source IP in a UDP packet, it's an issue with how routes are set up on the host. However, I had our network engineer double check them, and they seem fine (no ambiguous routes). The fact that I captured these messages on the public interface also indicates to me that the kernel is routing the message correctly. The missing Record-Route and Via for the public interface, however, lead me to believe that the proxy didn't correctly identify the outgoing interface in the first place. After looking at the ChangeLog for 1.5.4, I noticed that the some new logic was put in to improve performance when mhomed is enabled (r5971) in forward.c, and I think this is the issue. As I understand it, prior to 1.5.4, when mhomed was enabled, Kamailio determined the outgoing interface by creating a temporary UDP socket, invoking connect() on the socket with the packet destination, then checking the source IP of the socket that the kernel assigned using getsockname(). After the source address was determined, the temp socket was closed closed. As of 1.5.4, this was modified to reuse the temporary socket and just re-invoking connect() with a new destination address. The problem with the enhancement is that Linux (again, at least in the 2.6 kernels I'm using) doesn't seem to rebind a new source address to the socket when connect() is called more than once on a UDP socket. Instead, it keeps the original one, and thus the wrong interface is assumed. I wrote a small program to confirm this - basically creates a UDP socket, calls connect()/getsockname() multiple times using different destination addresses. I ran it on several 2.6 kernels, including Centos4.x and Centos5. The result was always that the source address of the socket wasn't changed after the first connect(), regardless of the destination address. The only way I could get it work as required was to first do a connect() using a zero'd out AF_UNSPEC address before doing the connect() to the remote address. I also ran it on Solaris and it worked. Go figure. I've downloaded the latest stable release (3.1.2) but I think the issue is still there, and I don't see anything in the user groups that addresses this. Any help would be appreciated. Thanks, Sean _______________________________________________ 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

2 1

Error running kamailio 3.1.0
by Lucas Alvarez 12 Feb '11

12 Feb '11

Hi, I have compiled kamailio 3.1.0 without any error and I having this error when running kamailio: ERROR: <core> [sr_module.c:523]: ERROR: load_module: could not open module </usr/local/lib/kamailio/modules_k/sl.so>: /usr/local/lib/kamailio/modules_k/sl.so: undefined symbol: fm_malloc Any will be appreciated. Regards, Lucas

2 1

After upgrade from openser 1.3.4 to kamailio 1.5.5 the same crash set
by Andrew O. Zhukov 12 Feb '11

12 Feb '11

[root@ tmp]# /usr/local/sbin/kamailio -V version: kamailio 1.5.5-notls (x86_64/linux) flags: STATISTICS, EXTRA_DEBUG, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, PKG_SIZE 4194304 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. svnrevision: unknown @(#) $Id: main.c 5608 2009-02-13 16:48:17Z henningw $ main.c compiled on 12:38:36 Feb 2 2011 with gcc 4.1.2 ----------------------------- Core was generated by `/usr/local/sbin/kamailio -P /var/run/openser/openser.pid -m 32 -u openser -g op'. Program terminated with signal 11, Segmentation fault. #0 0x000000000046b0e3 in fm_malloc (qm=0x72dc00, size=32) at mem/f_malloc.c:354 354 if ((*f)->size>=size) goto found; (gdb) backtrace #0 0x000000000046b0e3 in fm_malloc (qm=0x72dc00, size=32) at mem/f_malloc.c:354 #1 0x00002b30f2803087 in build_rr (_l=0x76f110, _l2=0x76fe80, user=0x7fffe9c5a500, tag=0x777a58, params=0x0, _inbound=0) at record.c:176 #2 0x00002b30f2802b7a in record_route (_m=0x76e0e0, params=0x0) at record.c:322 #3 0x00002b30f28047db in w_record_route (msg=0x76e0e0, key=0x0, bar=0x0) at rr_mod.c:212 #4 0x000000000040ed9b in do_action (a=0x73f5a0, msg=0x76e0e0) at action.c:874 #5 0x000000000040c03a in run_action_list (a=0x73f5a0, msg=0x76e0e0) at action.c:145 #6 0x000000000040e6a7 in do_action (a=0x73f810, msg=0x76e0e0) at action.c:746 #7 0x000000000040c03a in run_action_list (a=0x73e418, msg=0x76e0e0) at action.c:145 #8 0x000000000040c2a9 in run_actions (a=0x73e418, msg=0x76e0e0) at action.c:120 #9 0x000000000040c357 in run_top_route (a=0x73e418, msg=0x76e0e0) at action.c:195 #10 0x000000000043bda4 in receive_msg ( buf=0x70c980 "NOTIFY sip:XXXXXX.com SIP/2.0\r\nVia: SIP/2.0/UDP XX.XXX.101.68:5060;branch=z9hG4bK-6ee3865\r\nFrom: VTHome <sip:101650@XXXXXX.com>;tag=129d73a13db8ec7fo0\r\nTo: <sip:XXXXX.com>\r\nCall-ID: e3fd1da9-142a0a17"..., len=373, rcv_info=0x7fffe9c5ae90) at receive.c:175 #11 0x0000000000467eeb in udp_rcv_loop () at udp_server.c:449 #12 0x000000000042097b in main_loop () at main.c:774 #13 0x00000000004228b0 in main (argc=11, argv=0x7fffe9c5b118) at main.c:1321 (gdb) print size $1 = 32 (gdb) quit -------------------------------------------- Core was generated by `/usr/local/sbin/kamailio -P /var/run/openser/openser.pid -m 32 -u openser -g op'. Program terminated with signal 11, Segmentation fault. #0 0x000000000046bf7b in fm_status (qm=0x72dc00) at mem/f_malloc.c:609 609 size+=f->size,f=f->u.nxt_free,i++,j++){ (gdb) backtrace #0 0x000000000046bf7b in fm_status (qm=0x72dc00) at mem/f_malloc.c:609 #1 0x000000000041feb3 in sig_usr (signo=15) at main.c:563 #2 <signal handler called> #3 0x00000039d8cd4a51 in __recvfrom_nocancel () from /lib64/libc.so.6 #4 0x0000000000467bf4 in udp_rcv_loop () at udp_server.c:408 #5 0x000000000042097b in main_loop () at main.c:774 #6 0x00000000004228b0 in main (argc=11, argv=0x7fffe9c5b118) at main.c:1321 (gdb) print i $1 = 402 (gdb) print j $2 = 1 (gdb) print size $3 = 7234295468789601279 (gdb) print f $4 = (struct fm_frag *) 0x3738656435393838 (gdb) print f->size Cannot access memory at address 0x3738656435393838 ------------------------------------------------------------------- Andrew O. Zhukov

2 6

pdb module timeouts
by Thomas Baumann 11 Feb '11

11 Feb '11

Hello, I am using the PDB module and server components for number portability. 2 instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10 -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded timeout while waiting for response. One requested number was 307111094, where the module prints out a timeout. The funny part is, that I can see the responses at least arriving at the 10.12.19.21 interface on time. Request send: 0,200855 s Answer received: 0,201027 s That are 0,172 ms and far away from a timeout. What could be the reason ? regards, Thomas ps. A small change on the server part was done: handle 4 digit carrier codes. level3_logs: Feb 9 17:19:42 node2 /openser/sbin/kamailio[21200]: DEBUG: pdb [pdb.c:201]: querying '307111094'... Feb 9 17:19:42 node2 /openser/sbin/kamailio[21200]: WARNING: pdb [pdb.c:260]: exceeded timeout while waiting for response. ___________________________________________________________ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar

3 4

Change transport=tls within Contact Header
by Bernhard Suttner 11 Feb '11

11 Feb '11

Hi, is there a function to change the transport field within the Contact Header? t_relay does relay it to the UDP port of the PBX but the transport within the Contact Header is still set to TLS. Later, the PBX does try to establish a TLS connection. The idea is now, that kamailio does set the transport of the Contact Header to UDP. Another possible way would to be, that I use the re.subst method but maybe there is a special function for that. Thanks in advance. Best regards, Bernhard

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