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,
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.
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
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
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.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
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
Hello,
I am considering to release Kamailio v5.4.3 sometime next week, likely
on Monday, December 14, 2020. This is the usual heads up notification to
see if anyone is aware of issues not yet reported to bug tracker and if
yes, do it as soon as possible to give them a chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
This is a generic question about using environment variables in a config
file.
If I want to use below where TLS_IP itself is a constant defined somewhere
else. TLS_IP might be set via an env variable as well.
#!define TLS_TO_LISTEN tls:TLS_IP:$env(TLS_PORT)
Will that work? I see syntax errors and other weird issues. What's the
right syntax?
--
--
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.
Can someone share their configuration file explaining how they used consul
to achieve high availability?
--
--
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.
