sr-users October 2012

sr-users@lists.kamailio.org

87 participants
164 discussions

by Sangeeta Shah

Hi, I am seeing the following errors in syslog: Oct 8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR: presence_xml [notify_body.c:635]: while extracting tuple node Oct 8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR: presence_xml [notify_body.c:75]: while constructing offline body Oct 8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR: presence [presentity.c:1220]: preparing body Oct 8 16:21:54 RCS-Presence /usr/local/sbin/kamailio[6723]: ERROR: presence [publish.c:171]: Marking presentity Oct 8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO: presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via sip:8475551004@10.50.0.93:60562;transport=udp on behalf of sip:8475551004@10.50.251.12 for event message-summary Oct 8 16:21:55 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO: presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via sip:8475551004@10.50.0.93:60562;transport=udp on behalf of sip:8475551004@10.50.251.12 for event presence.winfo Oct 8 16:21:57 RCS-Presence /usr/local/sbin/kamailio[6734]: INFO: presence [notify.c:1581]: NOTIFY sip:8475551004@10.50.251.12 via sip:8475551004@10.50.0.93:60562;transport=udp on behalf of sip:8475551004@10.50.251.12 for event presence I am using Kamailio 3.3 with Presence and RLS with integrated XCAP. The only significant change i made today is update the presence and RLS config to DB ONLY mode. Thanks, Sangeeta -- Sangeeta Shah

12 years, 1 month

$fs syntax

by Juha Heinanen

wiki tells: $fs - reference to the forced socket for message sending (if any) in the form proto:ip:port should it be [proto:]ip:port instead? -- juha

12 years, 1 month

Kamailio 3.2.4 presence

by Vitaliy Aleksandrov

Hi all, I'm facing problems with active subscription restoration after sipproxy restart. db_mode is 0 (DB_MEMORY_ONLY) and according to comments in the presence.h kamailio holds subscription in memory and periodically updates to db, but retrieves from db only at startup. And it's true, I see that kamailio tries to update the active_watchers table, but it never inserts new subscriptions there. There are no problems with access to the database since when db_mode is 2 (DB_ONLY) kamailio inserts new records into the active_watchers without any problems. Here are presence module settings: modparam("presence", "db_url", "sqlite:////var/db/presence.db") modparam("presence", "db_mode", 0) modparam("presence", "timeout_rm_subs", 1) modparam("presence", "pres_htable_size", 8) modparam("presence", "subs_htable_size", 8) modparam("presence", "max_expires", 3600) modparam("presence", "db_update_period", 60) modparam("presence", "clean_period", 60) Does anybody have success with db_mode = DB_MEMORY_ONLY and active_watchers db table ?

12 years, 1 month

is kamilio support RFC5626 now ?

by mike

dear kamilio developers : i read the kamilio 3.3.0' s new features , it say it support outbound , and i have place to handle reg-id and sip.instance . so , i wonder if the kamilio3.3.0 support RFC5626 now，so that the kamilio can be used as a edge proxy . i ask why because i can't find where kamilio add flow-token and path for the register request. thanks

12 years, 1 month

IPv6 addresses in dispatcher on IPv4 only proxy

by Alex Hermann

Hello, I am using the dispatcher module with a database table shared among multiple proxies. Some proxies do both IPv4 and IPv6, others only do IPv4. The problem is when i use an IPv6 address in the dispatcher table. Then the IPv4-only proxies fail to load the table. ERROR: dispatcher [dispatch.c:325]: could not resolve [IPv6 address] WARNING: <core> [mem/f_malloc.c:474]: WARNING:fm_free: free(0) called ERROR: dispatcher [dispatcher.c:321]: could not initiate a connect to the database ERROR: <core> [sr_module.c:889]: init_mod(): Error while initializing module dispatcher (/usr/lib/kamailio/modules_k/dispatcher.so) Is there any setting i can use on the IPv4-only proxies to make it skip the IPv6 records? (apart from listening on an IPv6 address) -- Greetings, Alex Hermann

12 years, 1 month

Error while running TLS enabled Kamailio proxy

by Kamal Palei

Dear All While executing TLS enabled Kamailio proxy (3.1.5), getting below error. * 0(15895) INFO: tls [tls_domain.c:227]: TLSs<default>: verify_depth=9 0(15895) ERROR: tls [tls_domain.c:393]: TLSs<default>: Unable to load certificate file './modules/tls/ser-selfsigned.pem' 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:02001002:system library:fopen:No such file or directory 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:20074002:BIO routines:FILE_CTRL:system lib 0(15895) ERROR: tls [tls_domain.c:394]: load_cert:error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib 0(15895) ERROR: <core> [sr_module.c:832]: init_mod_child(): Error while initializing module tls (/usr/local/lib/kamailio/modules/tls.so) 0(15895) ERROR: <core> [main.c:1532]: ERROR: main: error in init_child(PROC_INT) -- exiting 0(15895) : <core> [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil) (out of memory block!) - aborting 0(15893) ERROR: <core> [daemonize.c:307]: Main process exited before writing to pipe * I performed below steps to compile and install. 1. I had a working Kamailio-3.1.5 code base without TLS 2. Downloaded latest openssl source code 3. Compiled and generated libssl.a and libcrypto.a 4. Next, I recompiled kamailio proxy, compilation did not go through. I had to modify Makefile in modules/tls module, added path for openssl/bio.h and path for libssl.a 5. Then executed make all clean and make all include_modules=tls , this time compilation succeeded 6. Next I did make install 7. Generated certificates using openssl library that comes by default with ubuntu 10.04 lte 8. Added below entries in kamailio.cfg #!define WITH_TLS #!ifdef WITH_TLS loadmodule "tls.so" modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg") modparam("tls", "private_key", "/etc/certs/localb2bua.com/key.pem") modparam("tls", "certificate", "/etc/certs/localb2bua.com/cert.pem") modparam("tls", "ca_list", "/etc/certs/demoCA/cert.pem") enable_tls=yes #!endif 9. Then I tried running kamailio proxy It complained not getting tls.so and tls.cfg Copied these files from modules/tls to /usr/local/etc/kamailio/ path 10. Then I was able to run Kamailio proxy and got the errors pasted at top of email (* Unable to load certificate file './modules/tls/ser-selfsigned.pem') * Please guide me what should I do to avoid this error. Thanks a lot. -Kamal * *

12 years, 1 month

unsubscribe

by Pablo R. Digonzelli

Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714

12 years, 1 month

Re: [SR-Users] Kamailio 3.3.0 CDR logging call "duration"

by Daniel-Constantin Mierla

Hello, do not reply to private email only when it is about a discussion on the mailing list - such messages will be ignored. Try to store the value in an avp when processing the BYE, after loose_route(), and store that avp in acc. Daniel On 10/15/12 1:13 PM, Nord7 wrote: > Hello, > no I'm not getting error messages. > Problem: > I can not get kamailio record duration dialogue created field "duration". > I make a test call, answer it, wait 5-6 seconds and hang up. > Now I have to get 5-6 seconds duration in the "duration", but the > field is blank. The rest of the field information about the call is > entered correctly. > So the variable $ DLG_lifetime information about the duration of the > call does not get. > But most of all I am wrong somewhere. > > > 2012/10/15 Daniel-Constantin Mierla <miconda(a)gmail.com > <mailto:miconda@gmail.com>> > > Hello, > > do you get any error message or what is the problem you encounter? > > Cheers, > Daniel > > > On 10/15/12 10:14 AM, Nord7 wrote: >> Hello >> >> Kamailio 3.3.0 >> All default "extra fields" created in database. I create in >> Database new field "duration" and trying write in this field >> variable $DLG_lifetime (from dialog module) , but can't do this. >> What i'm doing wrong? >> >> installed modules: ACC, DIALOG >> # ----- acc params ----- >> /* what special events should be accounted ? */ >> modparam("acc", "early_media", 0) >> modparam("acc", "report_ack", 0) >> modparam("acc", "report_cancels", 0) >> modparam("acc", "detect_direction", 0) >> /* account triggers (flags) */ >> modparam("acc", "log_level", 1) >> modparam("acc", "log_flag", FLT_ACC) >> modparam("acc", "log_missed_flag", FLT_ACCMISSED) >> modparam("acc", "log_extra", >> "src_user=$fU;src_domain=$fd;src_ip=$si;" >> "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" >> "duration=$DLG_lifetime") >> modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) >> /* enhanced DB accounting */ >> modparam("acc", "db_flag", FLT_ACC) >> modparam("acc", "db_missed_flag", FLT_ACCMISSED) >> modparam("acc", "db_url", DBURL) >> modparam("acc", "db_extra", >> "src_user=$fU;src_domain=$fd;src_ip=$si;" /* extra fields >> created in DataBase */ >> "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" >> "duration=$DLG_lifetime") >> modparam("acc", "cdr_enable", 1) >> modparam("acc", "cdr_start_on_confirmed", 0) >> modparam("acc", "cdr_facility", "LOG_DAEMON") >> >> # ----- dialog params ----- >> modparam("dialog", "enable_stats", 1) >> modparam("dialog", "hash_size", 4096) >> modparam("dialog", "rr_param", "did") >> modparam("dialog", "dlg_flag", DLG_FLAG) /* DLG_FLAG=4 */ >> modparam("dialog", "default_timeout", 21600) >> modparam("dialog", "timeout_avp", "$avp(i:10)") >> modparam("dialog", "dlg_match_mode", 0) >> modparam("dialog", "detect_spirals", 1) >> modparam("dialog", "db_url", DBURL) >> modparam("dialog", "db_mode", 1) >> modparam("dialog", "db_fetch_rows", 500) >> >> >> ########Routing Logic######## >> >> route[RELAY] { >> >> # enable additional event routes for forwarded requests >> # - serial forking, RTP relaying handling, a.s.o. >> if (is_method("INVITE|SUBSCRIBE")) { >> t_on_branch("MANAGE_BRANCH"); >> t_on_reply("MANAGE_REPLY"); >> } >> if (is_method("INVITE")) { >> t_on_failure("MANAGE_FAILURE"); >> } >> setflag(DLG_FLAG); # flag 4 duration >> setflag(FLT_ACC); # do accounting ... >> setflag(FLT_ACCFAILED); # ... even if the transaction fails >> if (!t_relay()) { >> sl_reply_error(); >> } >> exit; >> } >> >> >> >> >> >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -http://www.asipto.com > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda > Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -http://asipto.com/u/kat > Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -http://asipto.com/u/katu > > -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu

12 years, 1 month

segfault in siptrace module using setflag?

by samuel

Hi folks, I was making some tests with kamailio (both 3.3.0 and 3.3.1 tgz) with siptrace module sending "homer" packets to a remote central agent where the data is stored and presented to the user. The related config is: # ----- siptrace params from HOMER ----- modparam("siptrace", "duplicate_uri", "sip:A.B.C.D:9060") modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) #HEPv2 == timestamp will be included to HEP header modparam("siptrace", "hep_version", 2) modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "hep_capture_id", 1) basically for all incoming messages, a route is called with the following actions: route[HOMER] { setflag(22); sip_trace(); } I've been making some tests and if I disable the setflag action, there is no problem (well, no transaction messages are sent to the central agent), but as soon as I activated setflag, kamailio crashes with the following error: <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 28 There's no concrete point in the config file where it fails so I think the problem is more tm-internals related. I can provide further information in case you need it. Just for adding information, and without any intention to start a flame-war, with opensips 1.8.0-tls the server does not crash... Thanks in advance! Samuel.

12 years, 1 month

Supporting TLS and DTLS in RTP Proxy

by Kamal Palei

Hi All I am planning to enhance RTP proxy to support TLS and DTLS. We have some requirements where we need to send RTP packets either over TLS or over DTLS. I really do not know where to start :-) Few things that I have thought over is 1. I will take opnssl code base and integrate with rtpproxy code. 2. Will refer kamailio proxy code how tls connection framework is there and try to copy the code from kamailio code base to rtp proxy code base, OR is there a better alternative here. If somebody has a better idea, kindly share. Thanks a lot. -kamal

12 years, 1 month

← Newer
1
...
6
7
8
9
10
11
12
...
17
Older →

Jump to page:

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