for some reason once in a while kamailio processes fail to execute mysql
queries while at the same time an mysql test script that is run once per
second from cron works fine.
kamailio executes mysql queries during normal sip message processing and
also when it processes an OPTIONS ping test request:
sql_query("sip_proxy", "SELECT table_version FROM version WHERE table_name='domain'", "result");
if ($rc == 1) {
sql_result_free("result");
options_reply();
} else {
xlog("L_ERR", "$rm <$ru> failed sql test\n");
sql_result_free("result");
send_reply("500", "Server Internal Error");
};
here is an example:
...
Dec 15 00:51:08 proxy1 php: MySQL server test succeeded
Dec 15 00:51:09 proxy1 php: MySQL server test succeeded
Dec 15 00:51:10 proxy1 /usr/bin/sip-proxy[29894]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query
Dec 15 00:51:10 proxy1 /usr/bin/sip-proxy[29894]: ERROR: db_mysql [km_dbase.c:145]: db_mysql_async_exec_task(): failed to execute query on async worker
Dec 15 00:51:10 proxy1 php: MySQL server test succeeded
Dec 15 00:51:11 proxy1 php: MySQL server test succeeded
Dec 15 00:51:13 proxy1 php: MySQL server test succeeded
Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29891]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query
Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29891]: ERROR: <core> [db_query.c:291]: db_do_delete(): error while submitting query
Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29883]: ERROR: OPTIONS <sip:xxx:5060> failed sql test
Dec 15 00:51:14 proxy1 php: MySQL server test succeeded
Dec 15 00:51:14 proxy1 /usr/bin/sip-proxy[29886]: ERROR: OPTIONS <sip:xxx:5060> failed sql test
Dec 15 00:51:15 proxy1 php: MySQL server test succeeded
Dec 15 00:51:15 proxy1 /usr/bin/sip-proxy[29885]: ERROR: OPTIONS <sip:xxx:5060> failed sql test
Dec 15 00:51:16 proxy1 php: MySQL server test succeeded
Dec 15 00:51:17 proxy1 php: MySQL server test succeeded
Dec 15 00:51:18 proxy1 php: MySQL server test succeeded
...
all db_mysql module params are at their default values.
any idea why kamailio at connection loss does not automatically create
new connections?
is there a means to somehow debug this further?
-- juha
In the ACC modules' database table (acc) in Kamailio sometimes from_tag,
to_tag and callid of an INVITE and corresponding BYE completely match. But
sometimes from_tag in INVITE is to_tag of BYE and to_tag of BYE will become
from_tag of INVITE. Why this happens? Is this normal?
Regards
rtpengine readme tells:
4.2. rtpengine_disable_tout (integer)
Once an RTP proxy was found unreachable and marked as disabled, the
rtpengine module will not attempt to establish communication to that
RTP proxy for rtpengine_disable_tout seconds.
Default value is "60".
does this mean that after 60 seconds is passed, rtpengine module will
again try to use that RTP proxy, i.e., the RTP proxy does never become
permanently disabled unless disabled by nh_enable_rtpp mi command?
does the this param apply also if all RTP proxies of a set (perhaps
consisting of only one proxy) are unreachable?
-- juha
Hello,
Kamailio SIP Server v4.1.9 stable release is out.
This is marking the end of maintenance for 4.1.x series.
Kamailio project maintains the last two stable branches, at this moment
these are 4.2 and 4.3. Therefore, anyone running older releases is
advised to upgrade in the near future to the latest version of one of
those branches, preferably 4.3, in order to benefit of proper maintenance.
For more details about version 4.1.9 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2015/12/kamailio-v4-1-9-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Note: the latest stable branch is 4.3, at this moment with its latest
release v4.3.4. See more details about it at:
* http://www.kamailio.org/w/kamailio-v4-3-0-release-notes/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/miconda - http://www.linkedin.com/in/miconda
Hi list!
firstly, the described below issue is harmless to us, and is just little bit
annoying, but analysing the nature of issue decided to share the results,
and hear the opinion of community.
Scenario:
- WebRTC client connected to Kamailio's websocket
- after some time I close tab with WebRTC, in browser.
- using "kamctl fifo ws.dump" and "netstat -npa |grep kama |grep tcp" I can
see that the connection is closed
- but Kamailio still triing to send keepalive to that connection, and in
syslog I got errors:
Dec 18 12:28:18 /usr/sbin/kamailio[4471]: WARNING: websocket
[ws_frame.c:245]: encode_and_send_ws_frame(): TCP/TLS connection get failed
Dec 18 12:28:18 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_frame.c:797]:
ping_pong(): sending keepalive
Analysing sources, and using debug level 3 I see such logs (after the webrtc
client is closed, and )
Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:468]:
wsconn_get_list(): counter wsc [0xb1acb270] prev => [(nil)] next => [(nil)]
Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:495]:
wsconn_get_list(): wsc [0xb1acb270] id [2] ref++
Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:504]:
wsconn_get_list(): wsconn_get_list returns list [0xb666f410] with [1]
members
What is strange: in some tests, after unsuccessful sending of Ping,
kamailio's "wsconn_get_list" clean up that connection, but in some tests,
kamailio try sending Ping to old connection during 5-10 minutes (this time
is not constant from test to test)
Suddenly my current knowledge of C is not enough to find out were is the
problem's root.
General question is: is this correct list for such issuing? Or it should be
in Dev list?
once again - the problem is harmful (afetr some time, kamailio stop trying
sending ping to inactive connection, but it is annoying to see errors in
logs)
Cheers!
--
View this message in context: http://sip-router.1086192.n5.nabble.com/websocket-sometimes-log-errors-afte…
Sent from the Users mailing list archive at Nabble.com.
Hi
I'm looking for any pointers to resolve and issue I have .
When callee does a hang-up the call terminates on kamailio and asterisk but the caller's phone handset doesn't receive the BYE and doesn't hang-up.
If the caller does the hang up then the call terminates and the callee's handset hands up .
My setup is
Kamailio WAN -> Kamailio Lan -> Asterisk LAN
I'm using Path and dispatcher modules to route the SIP traffic to the backup end asterisk server my the domain in the SIP request.
Gerry Kernan
Infinity IT | 17 The Mall | Beacon Court | Sandyford | Dublin D18 E3C8 | Ireland
Tel: +353 - (0)1 - 293 0090 | E-Mail: gerry.kernan(a)infinityit.ie
Managed IT Services Infinity IT - www.infinityit.ie
IP Telephony Asterisk Consulting - www.asteriskconsulting.com
Contact Centre Total Interact - www.totalinteract.com
Hello,
I am going to release v4.1.9 later today, as last to be officially
packaged version from branch 4.1.
It is strongly recommended to migrate to a newer version, because the
focus of developers is on the two most recent stable branches.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hello,
I've been browsing the net and the (not so friendly) documentation but
found no readily available solution.
I have tried to fabricate on myself but it seems it's not that easy
without getting deeply familarised with
SIP protocol internals which I don't quite want know.
The problem seems simple enough, maybe you can easily tell the solution.
There is kamailio at ip 256.10.10.1. It's task is to accept
connections from SIP clients
and forward them to PBX at 256.20.20.1, and accept PBX packets and
forward them to the
clients. PBX handles registration, options, invites, everything.
Kamailio does not authenticate, authorise, just forwards everything
back and forth, like a mindless proxy.
No NAT involved.
[The reason is that K. have to call external scripts whenever an
outbound call (towards the clients) is
initiated, which the PBX is unable to. Please don't advise other
solutions (which isn't able to call executables
in-session).]
I have created a simplistic config which is not expected to work and
it doesn't quite (plenty of security stuff left out now):
route {
if(src_ip==myself) {
add_path();
$du="sip:256.20.20.1:95060";
} else {
if(src_ip!="256.20.20.1") {
$du="sip:256.20.20.1:95060";
} else { #from gateway pkts aren't changed
}
if(!t_relay()) {
sl_reply_error();
break;
}
}
There is several possible problems, but it seems Contact: is one main
one since it contains the client instead of
the proxy. Possibly this may even be the almost-good solution.
I'm sure there's an easy and pretty solution so before I start to make
ugly ones I ask the wise people.
Thanks,
Peter
