sr-users January 2019

sr-users@lists.kamailio.org

84 participants
100 discussions

siptarce module and SIP-Replying Messages

by Mojtaba

Hello, I am using siptrace module in Kamailio. As you know, it sends a copy of signalling message for specific destination. Like HOMER project. Because of i won't run main route block in destination, i just have changed this block like below: request_route { //do some works. drop(); exit; } I know it would make a question in your mind why i do this? No problem, Let's come back to question. All things works correct except Replying SIP message. The destination is trying to relay Replying SIP message that it get from siptrace module in other server. How can i disable replying SIP mesages? With Best Regards --Mojtaba Esfandiari.S

6 years

Response VIA Header

by Soltanici Ilie

Hi, version: kamailio 5.1.6 (x86_64/linux) 7d1964 Also, i'm using force_rport(); in routing configuration file, but 'received' parameter anyway is missing :( Thank You.

6 years

RADIUS auth func diff

by morfair＠gmail.com

Hello! In auth_radius manual present two functions: radius_www_authorize() and radius_proxy_authorize(). What is the difference?

6 years

Re: [SR-Users] Error in db_mysql while using presence

by Henning Westerholt

Am Mittwoch, 9. Januar 2019, 09:47:07 CET schrieb Ravindrakumar Bhatt: > I tried on command line with LOCK TABLES watchers write; and it works > fine. also i am usinf root@localhost with all permissions still same errors > show continuously. please tell if any more details are required for same. > Errors: Hello Ravindrakumar, I would suggest then to enable mysql query logging and have a look to the actual query that is executed from the module and match to the errors below. Please keep the sr-users list in CC. Best regards, Henning > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} presence > [subscribe.c:2827]: get_db_subs_auth(): while querying watchers table > Jan 9 00:11:23 client1 /usr/local/sbin/kamailio[2704]: ERROR: {1 1 > SUBSCRIBE NGFiMGJmM2VlYWQyNTQ5NWJjNmVmYTExY2ZhMWM1NDQ.} presence > [subscribe.c:1217]: handle_subscribe(): getting subscription status from > watchers table > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:11:56 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:12:36 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: db_mysql > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > 'active_watchers' was not locked with LOCK TABLES (1100) > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: <core> > [db_query.c:132]: db_do_query_internal(): error while submitting query > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [notify.c:1370]: publ_notify_notifier(): Can't query db > Jan 9 00:13:16 client1 /usr/local/sbin/kamailio[2713]: ERROR: presence > [publish.c:178]: msg_presentity_clean(): Updating watcher records > > On Wed, Jan 9, 2019 at 1:55 AM Henning Westerholt <hw(a)kamailio.org> wrote: > > Am Dienstag, 8. Januar 2019, 14:57:21 CET schrieb Ravindrakumar Bhatt: > > > I am using latest kamailio stable version. i have used it for presenece > > > > and > > > > > BLF. i am facing issue in presence related method when i am setting > > > sub_db_mode to any db related mode like 3. > > > > Hello Ravindrakumar, > > > > the presence module uses a database LOCK TABLE command and this fails. Can > > you > > check if the database user that is used from Kamailio has the appropriate > > permissions to issue this command on the database? You can try e.g. with > > mysql > > command line client. > > > > > Version : > > > version: kamailio 5.2.0 (x86_64/linux) 535e13 > > > flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > > > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, > > > Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, > > > BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB > > > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > > > id: 535e13 > > > compiled on 06:32:22 Jan 8 2019 with gcc 4.8.5 > > > > > > Kamailio.cfg setup: > > > modparam("presence|presence_xml", "db_url", DBURL) > > > modparam("presence", "server_address", "sip:XX.XX.XX.XX:5050") > > > modparam("presence", "send_fast_notify", 0) > > > modparam("presence", "db_update_period", 20) > > > modparam("presence", "clean_period", 40) > > > modparam("presence", "subs_db_mode", 0) > > > modparam("presence", "fetch_rows", 1000) > > > > > > # ----- presence_xml params ----- > > > #modparam("presence_xml", "db_url", DBURL) > > > modparam("presence_xml", "force_active", 1) > > > > > > # ----- pua params ----- > > > modparam("pua", "db_url", DBURL) > > > modparam("pua", "db_mode", 2) > > > modparam("pua", "update_period", 60) > > > modparam("pua", "dlginfo_increase_version", 0) > > > modparam("pua", "reginfo_increase_version", 0) > > > modparam("pua", "check_remote_contact", 1) > > > modparam("pua", "fetch_rows", 1000) > > > > > > # ----- pua_dialoginfo params ----- > > > modparam("pua_dialoginfo", "include_callid", 1) > > > modparam("pua_dialoginfo", "send_publish_flag", FLT_DLGINFO) > > > modparam("pua_dialoginfo", "caller_confirmed", 0) > > > modparam("pua_dialoginfo", "include_tags", 1) > > > modparam("pua_dialoginfo", "override_lifetime", 124) > > > > > > # ----- dialog params ----- > > > modparam("dialog", "db_url", DBURL) > > > modparam("dialog", "enable_stats", 1) > > > modparam("dialog", "db_mode", 1) > > > modparam("dialog", "dlg_flag", FLT_DLG) > > > modparam("presence_dialoginfo", "force_single_dialog", 0) > > > Error: > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: db_mysql > > > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > > > 'active_watchers' was not locked with LOCK TABLES (1100) > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: <core> > > > [db_query.c:132]: db_do_query_internal(): error while submitting query > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [notify.c:1369]: publ_notify_notifier(): Can't query db > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [presentity.c:1152]: update_presentity(): updating watcher records > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: db_mysql > > > [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Table > > > 'watchers' was not locked with LOCK TABLES (1100) > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: <core> > > > [db_query.c:132]: db_do_query_internal(): error while submitting query > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence > > > [subscribe.c:2827]: get_db_subs_auth(): while querying watchers table > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19527]: {1 1 SUBSCRIBE > > > MTlkYjI2NTBhYTFlMTBjYmYyMDgzNzQxYTM3OTE4OGE.} ERROR: presence > > > [subscribe.c:1217]: handle_subscribe(): getting subscription status from > > > watchers table > > > Jan 8 04:34:37 client1 /usr/local/sbin/kamailio[19523]: {1 1 PUBLISH > > > MzQ4ZjNhOGRlYWZlY2QyMDQwMGZlZjg0N2JlZGE2YWM.} ERROR: presence > > > [publish.c:499]: ki_handle_publish_uri(): when updating presentity > > > > > > I am currently using presence with memory only db_mode but for > > > > persistence > > > > > i would like to use db_only mode which is not possible due to this > > > issue. > > > Any idea or suggetions for this issue. > > > > Best regards, > > > > Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment

6 years

Dispatcher attributes

by Jason.Park

Hi. When using the attributes feature of the dispatcher module, is it possible to directly access/address an individual attribute directly? For example, if I use the following dispatcher text file: -- # line format # setid(int) destination(sip uri) flags(int,opt) priority(int,opt) attributes(str,opt) 1234 sip:10.10.10.10:5060;transport=tcp 0 0 attr1=red;attr2=blue -- And this config snippet, I was hoping to be able to access the attribute with a variable. -- modparam("dispatcher", "attrs_pvname", "$vxavp(ds_attrs)") if(ds_is_from_list(1234,1)) { x_log(“L_NOTICE”,”attr1: $xavp(ds_attrs=>attr1)\n”); } -- Jason Park | Lead Engineer | Voice Services | • Target<http://www.target.com/> | TNC | 816-273-8336

6 years

No Media in SIP Incoming calls

by Prashant Gupta

Hi, I have the following architecture - SIP provider <-> Kamailio <-> Asterisk servers Currently I have everything setup and incoming calls from Sip are routed to my asterisk server. The issue is however that when I answer the call, there is no media in the call. I have tried connecting with a normal local extension(not SIP,eg 1001) and there is a normal flow of media. When i try to sniff my connection via Wireshark on the asterisk server, there is an outflow of RTP packets but the same RTP traffic does not appear on the Wireshark of my Kamailio server connection. I am not sure if this is an RTP engine issue and how to resolve this. I have - modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:45038") this in my kamailio cfg but I don;t know which port to use here. Any suggestions?

6 years

kamailio rabbitmq segfault

by Sylvain Boily

Hello, I tried to test the rabbitmq module in kamailio with the debian 9 repo from kamailio.org but there is a segfault when the service is launched. Is there is people also have this issue? /etc/init.d/kamailio restart [....] Restarting kamailio (via systemctl): kamailio.serviceJun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.y:1659]: yyparse(): loading module rabbitmq.so Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/sr_module.c:575]: load_module(): trying to load </usr/lib/x86_64-linux-gnu/kamailio/modules/rabbitmq.so> Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/kemi.c:1295]: sr_kemi_modules_add(): adding module: rabbitmq Jun 9 13:02:03 siprouter kamailio: DEBUG: <core> [core/cfg.lex:1737]: pp_define(): defining id: MOD_rabbitmq Jun 9 13:02:03 siprouter kernel: [159315.610811] kamailio[13226]: segfault at 7f03b2296287 ip 00007f03b2080ca3 sp 00007fff133285c0 error 7 in librabbitmq.so.4.2.0[7f03b2074000+13000] Jun 9 13:02:03 siprouter /usr/sbin/kamailio[13226]: DEBUG: <core> [core/sr_module.c:988]: init_mod(): rabbitmq Sylvain

6 years

User connection history

by José Antonio Gutiérrez Delgado

Hi, I would like to know if there is a possibility to see a user's connection history, or at least their last connection. Thank you -- José Antonio Gutiérrez Delgado Responsable técnico Oficina: (+34) 923040031 <http://www.arsoft-company.com/> *Este mensaje se dirige exclusivamente a su destinatario/s y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.* *Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es tarea de todos.*

6 years

"Discarded invalid SRTP packet: authentication failed" warning

by David Cunningham

Hello, We're having an issue with rtpengine (used by Kamailio) where audio works initially, but then after an apparently random amount of time stop working. We see that when audio stops working rtpengine logs this: Dec 10 09:58:57 hostname rtpengine[376]: WARNING: [Pl1SeGDssOsDNWQdvey4lg.. port 48766]: Discarded invalid SRTP packet: authentication failed It then logs similar messages until the call hangs up. No such messages were logged while audio was working. Searching for this error message suggests that a change in the SSRC can cause the problem, but we don't see any such change in the PCAP. The source IP, port, codec, and SSRC all stay the same, and the Sequence increments as normal. Does anyone have suggestions on where to look next? We can share the PCAP privately if that would help anyone. Thanks for any advice! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

6 years

Re: [SR-Users] [EXT] Re: P-CSCF returns SIP error: 483 Too may hops

by Woscek, Martin W.

Yes, The DNS NAPTR records are correct. I have all running on single laptop, P:4060, I:5060, S:6060 and all DNS tests verified. I don’t have any traffic other than the P talking to itself until the number hops is exceeded. From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Iman Mohammadi Sent: Wednesday, January 9, 2019 9:49 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [EXT] Re: [SR-Users] P-CSCF returns SIP error: 483 Too may hops Hi Check the Ports in DNS and in configuration files.for example if you set 5060 in configuration of pcscf,set 5060 in dns for pcscf too For Registration REGISTER goes from pcscf to icscf first then icscf gets address of scscf in UAA from HSS,then icscf forwards REGISTER to scscf and ... On Wed, Jan 9, 2019, 18:04 Woscek, Martin W. <mwoscek(a)mitre.org<mailto:mwoscek@mitre.org> wrote: Hi all, I’ve stood up IMS 4.3.4. When I try to register with a boghe IMS client the P-CSCF gets in a loop and a SIP error: 483 Too may hops is returned. I would think the path would b to S-CSCF:6060 which would then check the HSS for user bob. The P-CSCF log attached. I believe Im missing some basic configuration setting here. If there is configuration (test scenario) documentation that I can be pointed to, it’d be appreciated. R, martin _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

6 years

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 January 2019