Hello,
I am planning to release v4.0.7 based on latest source code in branch
4.0. This branch is going out of official maintenance, the current
latest stable branches being 4.2 and 4.1.
If you have any remarks regarding it, write back to mailing lists.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
Hi List,
there has been some problems trying to create builds for module kazoo due to the dependency of libraries (subject).
i think that one possible (tested successfully) solution is to integrate these libraries in lib folder and distribute them as part of kamailio.
i created them with "kamailio-" prefix and changed kazoo makefile to refer to these. if we proceed with this change, other modules dependent of json could also benefit from this inclusion.
Thoughts ?
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Jason Penton (jaybeepee)
Attached to Project - sip-router
Summary - crash in dns_cache.c when using natping
Task Type - Bug Report
Category - dns / dns cache
Status - New
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Crash in dns_cache.c
#0 0x0000000000464543 in dns_naptr_sip_resolvehost (name=0x7fff7ea6ce40, port=0x0, proto=0x0) at dns_cache.c:2811
#1 0x0000000000464d45 in dns_sip_resolvehost (name=0x7fff7ea6ce40, port=0x0, proto=0x0) at dns_cache.c:2876
#2 0x00007f35b2f9bb89 in send_keepalive (contact=0x7f35736e0c08) at nat_traversal.c:1557
#3 0x00007f35b2f9bcd1 in keepalive_timer (ticks=62930527, data=0x0) at nat_traversal.c:1591
#4 0x0000000000603b62 in fork_basic_timer (child_id=-1, desc=0x7f35b2fa6dc5 "TIMER NT", make_sock=1, f=0x7f35b2f9bc18 <keepalive_timer>, param=0x0, interval=1) at timer_proc.c:90
#5 0x00007f35b2f9fa79 in child_init (rank=0) at nat_traversal.c:1820
#6 0x000000000059674d in init_mod_child (m=0x7f35b9a0bf50, rank=0) at sr_module.c:921
#7 0x0000000000596a61 in init_child (rank=0) at sr_module.c:947
#8 0x00000000004a85da in main_loop () at main.c:1709
#9 0x00000000004ad5f9 in main (argc=7, argv=0x7fff7ea6f3a8) at main.c:2568
This crash will happen everytime with the call from nathelper:
( hostent = sip_resolvehost(&nat_ip, NULL, NULL);
the 3rd argument is the proto parameter in the target function which is dereferenced without a check in dns_cache.c:
origproto=*proto;
I am not sure what the fix will be (either assume proto is UDP if NULL) or nathelper must be specific when calling sip_resolvehost...
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=491
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hey guys,
I will log a bug for this but just for interest on the mailing list.
#0 0x0000000000464543 in dns_naptr_sip_resolvehost (name=0x7fff7ea6ce40,
port=0x0, proto=0x0) at dns_cache.c:2811
#1 0x0000000000464d45 in dns_sip_resolvehost (name=0x7fff7ea6ce40,
port=0x0, proto=0x0) at dns_cache.c:2876
#2 0x00007f35b2f9bb89 in send_keepalive (contact=0x7f35736e0c08) at
nat_traversal.c:1557
#3 0x00007f35b2f9bcd1 in keepalive_timer (ticks=62930527, data=0x0) at
nat_traversal.c:1591
#4 0x0000000000603b62 in fork_basic_timer (child_id=-1,
desc=0x7f35b2fa6dc5 "TIMER NT", make_sock=1, f=0x7f35b2f9bc18
<keepalive_timer>, param=0x0, interval=1) at timer_proc.c:90
#5 0x00007f35b2f9fa79 in child_init (rank=0) at nat_traversal.c:1820
#6 0x000000000059674d in init_mod_child (m=0x7f35b9a0bf50, rank=0) at
sr_module.c:921
#7 0x0000000000596a61 in init_child (rank=0) at sr_module.c:947
#8 0x00000000004a85da in main_loop () at main.c:1709
#9 0x00000000004ad5f9 in main (argc=7, argv=0x7fff7ea6f3a8) at main.c:2568
This crash will happen everytime with the call from nathelper:
( hostent = sip_resolvehost(&nat_ip, NULL, NULL);
the 3rd argument is the proto parameter in the target function which is
dereferenced without a check in dns_cache.c:
origproto=*proto;
I am not sure what the fix will be (either assume proto is UDP if NULL) or
nathelper must be specific when calling sip_resolvehost...
Cheers
Jason
Hi, all.
Still, I can not execute python script. There is a function called push (see testflow.py below). I placed command pusher.set(flow1) inside a push function.
From the kamailio I want to execute this "push" function( python_exec("push");). However, it does not work. Though when I delete push function, leaving just pusher.set(flow) commands, the script is executed when I run kamailio. But I do not want to run the script with Kamailio during initialization process.
Any ideas about this issue?
Kamailio configs:
modparam("app_python", "script_name", "/usr/local/etc/sip-router/testflow.py")
modparam("app_python", "mod_init_function", "mod_init")
modparam("app_python", "child_init_method", "child_init")
+++++++++++++++++++++++++++++++++++++
testflow.py file:
+++++++++++++++++++++++++++++++++++++
#! /usr/bin/python
import sys
import httplib
import json
class test(object):
def __init__(self, server):
self.server = server
def child_init(self, y):
return 0
def get(self, data):
ret = self.rest_call({}, 'GET')
return json.loads(ret[2])
def set(self, data):
ret = self.rest_call(data, 'POST')
return ret[0] == 200
def remove(self, objtype, data):
ret = self.rest_call(data, 'DELETE')
return ret[0] == 200
def installflowone():
call(["./installflows.sh"])
def rest_call(self, data, action):
path = '/wm/staticflowentrypusher/json'
headers = {
'Content-type': 'application/json',
'Accept': 'application/json',
}
body = json.dumps(data)
conn = httplib.HTTPConnection(self.server, 8080)
conn.request(action, path, body, headers)
response = conn.getresponse()
ret = (response.status, response.reason, response.read())
print ret
conn.close()
return ret
pusher = test('10.0.0.10')
flow1 = {
'switch':"00:00:08:00:27:62:77:1d",
"name":"flow-mod-1",
"cookie":"0",
"priority":"32000",
"ingress-port":"3",
"active":"true",
"actions":"output=4"
}
flow2 = {
'switch':"00:00:08:00:27:62:77:1d",
"name":"flow-mod-2",
"cookie":"0",
"priority":"30000",
"ingress-port":"4",
"active":"true",
"actions":"output=3"
}
def push(self):
pusher.set(flow1)
pusher.set(flow2)
def mod_init():
return test(object)
+++++++++++++++++++++++++++++++++++++++++++++
Best Regards,
Azamat Ailbayev
Mob.: +49 (0) 15215023005
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Savolainen Dmitri (snen)
Attached to Project - sip-router
Summary - htable sht_lock problem
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 4.2
Due in Version - Undecided
Due Date - Undecided
Details - i have config look like this
<code>
........
modparam("htable", "htable", "lock_test=>size=4;")
........
route{
$sht(lock_test=>some_item) = 0;
sht_lock("lock_test=>some_item");
xlog("L_INFO", "inside lock before inc");
$sht(lock_test=>some_item) = $sht(lock_test=>some_item) + 1;
xlog("L_INFO", "inside lock after inc");
sht_unlock("lock_test=>some_item");
}
</code>
in log file after SIP reguest
<code>
Nov 6 19:38:12 sw4 ./kamailio[8754]: INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config)
Nov 6 19:38:12 sw4 ./kamailio[8726]: INFO: <script>: inside lock before inc
</code>
there is no message "inside lock after inc"
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=490
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.