sr-users December 2020

sr-users@lists.kamailio.org

67 participants
88 discussions

ERROR: <core> [core/parser/parse_uri.c:1326]: _parse_ruri(): bad uri </sip?jwt=..
by Syed Shahryar 15 Dec '20

15 Dec '20

I am sending JWT tokens via SIP URL through JSSIP for authentication before websocket connection is made. However, I am getting errors like: ERROR: <core> [core/parser/parse_uri.c:1326]: _parse_ruri(): bad uri < */sip?jwt=..* I have the following setting in kamailio config: modparam("xhttp", "url_match", "^/sip") // only match this path Is this a bug or some configuration issue? How do I resolve it? -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

2 1

X-Forwarded-for IP to asterisk
by Mihai Cezar 15 Dec '20

15 Dec '20

Hello, Is it something like the XFF for Kamailio so I can see in asterisk (sip show peers) the ip of the registered softphone and not Kamailio's IP ? Thanks!

4 5

How to use port number using $env in listen
by Syed Shahryar 15 Dec '20

15 Dec '20

I tried many combinations of the following but I keep getting syntax errors: listen=tls:TLS_IP:$env(TLS_PORT) advertise PUBLIC_IP:$env(TLS_PORT) TLS_IP and PUBLIC_IP are constants defined at the top using #!define. And, TLS_PORT is supposed to be the env variable. -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

2 1

Losing MySQL connections
by Duarte Rocha 15 Dec '20

15 Dec '20

Greetings all, I'm having some dropped MySQL connections in my Kamailio in times of low or no activity in the proxy. These are the errors i'm getting : db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) <core> [db_query.c:348]: db_do_update(): error while submitting query usrloc [ucontact.c:1147]: db_update_ucontact_ruid(): updating database failed usrloc [ucontact.c:1663]: update_contact_db(): failed to update database registrar [save.c:784]: update_contacts(): failed to update contact sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) In order to try to fix this i've added timeout_interval and ping_interval from the db_mysql module. Is this the best approach? I've restarted my Kamailio but i don't see any ping going to my BD. Is there any other config that I need to add so that the pings are sent? Is it possible to do a ping to verify connection and reconnect mannualy on the config file? Best Regards,

2 1

Problems debugging memory issues
by Sheldon L 15 Dec '20

15 Dec '20

Hi, I'm trying to investigate a possible memory leak issue in Kamailio and I'm following the instructions indicated in https://www.kamailio.org/wiki/tutorials/troubleshooting/memory I'm using Kamailo 4.4 with the following kamailio internals: Print out of kamailio internals Version: kamailio 4.4.2 (x86_64/linux) 892ad6 Default config: /apollo/env/TachyonPlatformKamailio/etc/kamailio/kamailio.cfg Default paths to modules: /apollo/env/TachyonPlatformKamailio/lib64/kamailio/modules Compile 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, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE=262144 MAX_LISTEN=16 MAX_URI_SIZE=1024 BUF_SIZE=65535 DEFAULT PKG_SIZE=8MB DEFAULT SHM_SIZE=64MB ADAPTIVE_WAIT_LOOPS=1024 TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select Source code revision ID: 892ad6 Compiled with: x86_64-unknown-linux-gnu-gcc 4.9.4 Compiled on: 23:36:48 Dec 8 2020 Thank you for flying kamailio! I have attached to one of the kamailio tcp receiver processes via GDB and I am trying to dump memory blocks from the memory manager. However, mem_block is not in the current_context. The following is the output from my gdb session: Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-amazon-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/codedeploy-agent/deployment-root/95bb1634-e653-4cec-b327-99b18b9227a8/d-7AJ1XZP58/deployment-archive/sbin/kamailio...done. Attaching to program: /apollo/env/TachyonPlatformKamailio/sbin/kamailio, process 8946 ptrace: Operation not permitted. (gdb) set $i=0 (gdb) set $a = mem_block->first_frag No symbol "mem_block" in current context. (gdb) info list Undefined info command: "list". Try "help info". (gdb) info threads No threads. Is there something I need to do before accessing the mem_block symbol? Also do you have any other suggestions for debugging memory leaks that may not be documented? Note: i can't upgrade to the latest version of Kamailio as we have custom modules and would require considerable effort to upgrade. Thanks, Sheldon.

2 1

sngrep TLS connection
by Agiftel 15 Dec '20

15 Dec '20

Hi all, does anyone was able to use sngrep (with -k option) to decrypt TLS connections? I'am doing what help says; used private key is the correct one; but no traffic is seen on sngrep. If i use not ecrypted call i can see everything, so sngrep is working good. Any hint? regards -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

5 8

Kamilio+asterisk = deregister after 2-3 minute
by Mihai 15 Dec '20

15 Dec '20

Hi, I am forwarding all the traffic to my asterisk server ( including registers) everything seems to work when i first register but if stay idle 2-3 minute it gets unregistered and then i can't register back unless i restart kamailio see attached print screen

6 6

voltdb support
by Ali Taher 14 Dec '20

14 Dec '20

Hello, I just need to know if kamailio can communicate with Voltdb for sqlops operations for example. Regards, Ali Taher

2 8

Kamailio v5.4.3 Released
by Daniel-Constantin Mierla 14 Dec '20

14 Dec '20

Hello, Kamailio SIP Server v5.4.3 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.3. For more details about version 5.4.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/12/kamailio-v5-4-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Wrong To tag in t_reply
by Ivan Ribakov 14 Dec '20

14 Dec '20

Hi all, I’m trying to implement following routing behaviour: - ingress INVITE is sequentially forked to 1 or more endpoints - under certain conditions sequential forking may be stopped and pre-defined error returned to the caller Here’s is part of the config responsible for handling errors: failure_route[ROUTE_ELEMENT_FINAL_FAILURE_HELPER] { route(ROUTE_ELEMENT_FINAL_FAILURE); } route[ROUTE_ELEMENT_FINAL_FAILURE] { # We need to check if the error happens before the first egress, because T-state is not defined yet so we can not use t_reply if ($var(before_first_egress) == 0) { t_reply("$var(sipCode)", "$var(sipMessage)"); } else { sl_send_reply("$var(sipCode)", "$var(sipMessage)"); } } Here is a simple scenario where delivering call to first endpoint times out after receiving 180 Ringing (using custom fr_inv_timer value) where: - .33 is caller - .208 is Kamailio - .138 is callee Notice that 504 is retransmitted by Kamailio. Here is a comparison of 180 and 504 returned by Kamailio: As can be seen, 180 was proxied from the callee and has callee’s to-tag (tag=CALLEE1), however 504 that was generated by Kamailio using t_reply() has a different to-tag (presumably generated by Kamailio). How can I tell Kamailio not to generate new to-tag but to use the last one that proxied back to the caller? Thanks in advance for any help! Regards, Ivan

2 2

← Newer
1
2
3
4
5
6
7
8
9
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 December 2020