sr-users

sr-users@lists.kamailio.org

11 participants
37526 discussions

Kamailio NOTIFY
by Spinov Evgeniy 19 Feb '11

19 Feb '11

Hello all. I'm having problem with sending NOTIFY packet for event dialog. The problem is, that all NOTIFY packets sent with this event is empty. ( Content-length: 0 ) and in fact, not passing actual status to the phone. In my case this is SPA962. NOTIFY packets for event presence are sent fine and status is changing normally. The same phone, works fine with Asterisk. Asterisk is sending NOTIFY with non-zero content and changing status for the subscriber as well. I've turned on pua module to send PUBLISH requests at Kamailio, it's filling DB table with subscription, everything runs fine and NOTIFY packets are coming to subscribed phone, but they are empty. I also have presence_dialoginfo module on and pua_dialoginfo module on. I've tried on Kamailio 3.0.3 and 3.1.1. Content always empty. There is no sense of pasting here packet dumps, cause everything is like should be: (UAC) SUBSCRIBE, event: presence ---> K K ---> 202 OK (SPA) SUBSCRIBE, event: dialog ---> K K ---> 202 OK PUBLISH, event: presence ---> K K ---> 200 OK NOTIFY, event: presence, Content-Length: XXX ---> UAC NOTIFY, event: dialog, Content-Length: 0 ---> SPA962 As result, softphone changes status and hardphone ( SPA962 ) - no. May be it's cause of PUBLISH event value? Please advise.

2 10

why function result -1 cannot be assigned to variable?
by Juha Heinanen 19 Feb '11

19 Feb '11

i have a local function x that returns a positive integer or -1. when it returns -1, assignment $var(tmp) = function_x("$rd"); produces to syslog an error: Feb 19 07:32:44 sip /usr/sbin/sip-proxy[27284]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (1415,40-1415,40) i have had that function for years, but have not noticed these errors in earlier versions than 3.1. any ideas why the error is produced and how to get rid of it? -- juha

1 0

Interfaces guestures
by Spinov Evgeniy 18 Feb '11

18 Feb '11

Hello, all. I'm having Kamailio 3.0.4. Server have 2 physical interfaces, one is private, second is public. INVITE request is coming to Kamailio from public interface and being routed by Kamailio to one of ther asterisk boxes, which is in private network. Packet is routed to correct interface, but SRC address of packet, containing public Kamailio IP. As of that, asterisk is unable to communicate properly with Kamailio. I'm not applying any packet changes in Kamailio config and cannot get why Kamailio is doing that? Kamailio is listening both networks and able to send packets with correct IP, but somewhy sending an invalid one. Am I doing something wrong? Thank you.

2 1

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

18 Feb '11

Hello Marius, thanks a lot for submitting the patch. It works like a charm now. But to be honest I had troubles to find this patch, I just checked the daily tarball [http://sip-router.org/tarballs/sr/] and found this change. How I can get patch e914f97b4 in a better way ? regards, Thomas >Hello >I have made a patch to 3.1(e914f97b4) . The poll() event list was not >cleared when a response was received so when 2 servers responded one >after the other it might block in an incorrect recv(). Can you please >test with this? >Marius ___________________________________________________________ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar

4 4

Re: [SR-Users] ERROR: failover functions used, but AVPs paraamters required are NULL
by Gary Chen 18 Feb '11

18 Feb '11

Never mind. I used wrong kamailio.cfg file. From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, February 17, 2011 8:51 AM To: Gary Chen Cc: sr-users(a)lists.sip-router.org Subject: Re: [SR-Users] ERROR: failover functions used, but AVPs paraamters required are NULL Hello, can you send all log messages printed by: kamailio -E -ddd Thanks, Daniel On 2/17/11 2:42 PM, Gary Chen wrote: kamailio version 3.1.2 I am trying to setup dispatcher to use its failover feature. Here is dispatcher part of configure file: loadmodule "dispatcher.so" modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "ds_ping_interval", 30) modparam("dispatcher", "ds_probing_threshhold", 10) modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=4") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_from", "sip:lb1 <at> m-lab-ca805-sig.kd-lab.de") modparam("dispatcher", "dst_avp", "$avp(dsdst)") modparam("dispatcher", "grp_avp", "$avp(dsgrp)") modparam("dispatcher", "cnt_avp", "$avp(dscnt)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "flags", 2) But it is still give the following error: 0(1917) ERROR: dispatcher [dispatcher.c:624]: failover functions used, but AVPs paraamters required are NULL -- feature disabled Does anybody know why? Gary _______________________________________________ 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 -- Daniel-Constantin Mierla http://www.asipto.com

2 1

Re: [SR-Users] Bad File Descriptor
by Daniel-Constantin Mierla 17 Feb '11

17 Feb '11

Please keep the mailing list cc-ed. My previous email had other comments/questions inline, can you answer them as well? They are relevant in troubleshooting. Thanks, Daniel On 2/17/11 7:57 PM, David J. wrote: > version: kamailio 3.1.1 (x86_64/linux) 88bda8 > 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, 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, PKG_SIZE 4MB > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > id: 88bda8 > compiled on 04:39:27 Dec 9 2010 with gcc 4.3.2 > > > > On 2/17/11 1:46 PM, Daniel-Constantin Mierla wrote: >> Hello, >> >> what is the version you are using? >> >> On 2/17/11 7:35 PM, David J. wrote: >>> 5(20390) ERROR: <core> [udp_server.c:586]: ERROR: udp_send: >>> sendto(sock,0x7f67f7f94d14,4,0,69.117.34.101:2048,16): Bad file >>> descriptor(9) >>> 5(20390) ERROR: nathelper [nathelper.c:1722]: udp_send failed >>> >>> >>> I see this error when I try to restart kamailio after crash; >> >> What is the cause for the crash? Do you have a log or core for that? >> >>> I see the cause of this problem is 'stale' entries in the location >>> table; >>> >>> If I delete this entries kamailio starts fine; any suggestions to >>> prevent this from continuously happening. >> Is any change in the IP address of the server upon restart? >> >> Do the errors persist or they stop after a while? They are related to >> NAT keepalives sent by nathelper module, so they don't affect the sip >> traffic and if they are for stale contacts then they are fully >> harmless. The stale contacts should be automatically removed after a >> while by usrloc module. >> >> Cheers, >> Daniel >> > -- Daniel-Constantin Mierla http://www.asipto.com

1 0

Bad File Descriptor
by David J. 17 Feb '11

17 Feb '11

5(20390) ERROR: <core> [udp_server.c:586]: ERROR: udp_send: sendto(sock,0x7f67f7f94d14,4,0,69.117.34.101:2048,16): Bad file descriptor(9) 5(20390) ERROR: nathelper [nathelper.c:1722]: udp_send failed I see this error when I try to restart kamailio after crash; I see the cause of this problem is 'stale' entries in the location table; If I delete this entries kamailio starts fine; any suggestions to prevent this from continuously happening. Thanks.

2 1

Kamailio 1.5.5 No TLS Segmentation Fault
by Stagg Shelton 17 Feb '11

17 Feb '11

Hello, We have been having a problem with Kamilio faulting and dumping core files on occasion. I have not been able to reproduce the failure at will, but notice the back trace seems to point toward actions with the dialogue. Below is from a backtrace of a core file from just a few minutes ago. Can anyone determine what may have caused the system to error and stop processing? Thanks Stagg Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x00007f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 474 d_entry = &(d_table->entries[dlg->h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x00007f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = "unref_dlg" #1 0x00007f8a11d5180f in unref_dlg_from_cb (t=0x7f89f7d9c660, type=4096, param=0x7f8a1836a6e0) at dlg_handlers.c:622 dlg = 0x7f89f7e07470 #2 0x00007f8a18138ea3 in run_trans_callbacks (type=4096, trans=0x7f89f7d9c660, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f89f7dc30e8 backup = 0x71a9d0 trans_backup = 0xffffffffffffffff __FUNCTION__ = "run_trans_callbacks" #3 0x00007f8a181273cc in free_cell (dead_cell=0x7f89f7d9c660) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x7fff4282f190 p = 0x7f89f7d3b068 #4 0x00007f8a18127bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f89f7d9c660 tmp_cell = 0x0 i = 4075 #5 0x00007f8a181342a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = "tm_shutdown" #6 0x00000000004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = "destroy_modules" #7 0x000000000041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x0000000000420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 12 do_exit = 1 ---Type <return> to continue, or q <return> to quit--- shutdown_time = 60 __FUNCTION__ = "handle_sigs" #9 0x00000000004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 21442 si = 0x0 __FUNCTION__ = "main_loop" #10 0x0000000000423410 in main (argc=3, argv=0x7fff4282f498) at main.c:1321 cfg_log_stderr = 0 cfg_stream = 0x1fe1010 c = -1 r = 0 tmp_len = 0 port = 0 proto = 4910128 ret = -1 rfd = 4 tmp = 0x7fff4282ff8a "" options = 0x4b77e0 "f:cCm:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:" rand_source = 0x4b7d9c "/dev/urandom" seed = 3628387751 __FUNCTION__ = "main" (gdb) (gdb) quit

3 7

Failover with UCARP and Monit
by Hugh Waite 17 Feb '11

17 Feb '11

Hello, I am setting up a high-availablilty kamailio system using UCARP to failover between active and standby instances. To detect failure, we intend to use Monit. Monit can monitor the kamailio PID and start the process when needed (Example on the wiki http://www.kamailio.org/dokuwiki/doku.php/install:configure-initd-script) and it can also do OPTIONS pings to verify it is working. If the pings fail we will initiate a ucarp swap. However if the server is currently in standby, it does not have the V-IP address, so I don't want to run the OPTIONS pings (I think). Does anyone use a similar system and can provide an example of how ucarp, monit and kamailio can work together? Many thanks, Hugh Waite

4 5

Kamailio and Asterisk Realtime Integration using Asterisk Database
by Pavel Miskov 17 Feb '11

17 Feb '11

Hi all, I am trying to integrate Kamailio and Asterisk as explained in http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb document but I have some problems. 1. When Asterisk sends the call back to Kamailio, Asterisk generates new INVITE but with wrong From URI. In From header, "Display name" is OK (Phone A) but "From URI" is wrong (it is URI of Phone B). 2. When Phone B answers the call, Asterisk generates another INVITE to Phone B. When Phone B sends OK to this second INVITE Asterisk generates another INVITE to Phone A. 3. When Phone B sends BYE, Asterisk generates INVITE to Phone A and when it receives OK from Phone A it sends BYE to Phone A. I can fix the first problem with transformation in Kamailio but is this the way how it is supposed to work or I misconfigured something? I have tried this with kamailio 3.1 and asterisk 1.6.2.16.1 (and 1.8.2.3). Thanks Pavel

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