THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#203 - Crash in presence_reginfo/presence.so
User who did this - Carsten Bock (carstenbock)
----------
Strange:
In my config i have:
####### Modules Section ########
# set paths to location of modules
mpath="/usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/"
loadmodule "presence_reginfo.so"
loadmodule "presence.so"
And as a result, my Kamailio does not start:
Feb 7 10:56:04 proxy1 /usr/sbin/kamailio[6650]: ERROR: presence_reginfo [presence_reginfo.c:75]: can't bind presence
Feb 7 10:56:04 proxy1 /usr/sbin/kamailio[6650]: ERROR: <core> [sr_module.c:932]: init_mod(): Error while initializing module presence_reginfo (/usr/lib64/kamailio/modules_k/presence_reginfo.so)
(unless i change the order)
Works as designed, i'd say.
In the module:
bind_presence= (bind_presence_t)find_export("bind_presence", 1,0);
if (!bind_presence) {
LM_ERR("can't bind presence\n");
return -1;
}
So, if the "presence" module is not loaded, it will not start, according to the source.
Can you provide further info, how i can reproduce this?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=203#comment497
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#203 - Crash in presence_reginfo/presence.so
User who did this - Carsten Bock (carstenbock)
----------
I will improve the module. That explains, why i couldn't reproduce it on my birthday.... :-)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=203#comment496
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#203 - Crash in presence_reginfo/presence.so
User who did this - Olle Johansson (oej)
----------
I loaded presence_reginfo before presence. If I move the order, it doesn't core.
So presence_reginfo should probably check for the presence module being loaded before using it ;-)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=203#comment495
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
Carsten Bock has taken ownership of the following task:
FS#203 - Crash in presence_reginfo/presence.so
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=203
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Olle Johansson (oej)
Attached to Project - sip-router
Summary - Crash in presence_reginfo/presence.so
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - FreeBSD
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Version 3.2.2 (doesn't exist in "Reported version" field :-) )
Last lines of log --------------------
0(94533) DEBUG: <core> [sr_module.c:928]: DEBUG: init_mod: presence_reginfo
0(94533) DEBUG: <core> [sr_module.c:667]: find_export_record: found <bind_presence> in module presence [/usr/local/lib64/kamailio/modules_k/presence.so]
Segmentation fault (core dumped)
GDB backtrace ----------------
Loaded symbols for /libexec/ld-elf.so.1
#0 0x0000000804ee851b in search_event (event=0x7fffffffe640) at event_list.c:347
347 pres_ev= EvList->events;
[New Thread 801004380 (LWP 101822)]
(gdb) bt full
#0 0x0000000804ee851b in search_event (event=0x7fffffffe640) at event_list.c:347
pres_ev = Variable "pres_ev" is not available.
(
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=203
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - C. Austin (vulpyne)
Attached to Project - sip-router
Summary - sr.pv.get fails for retrieving index header variable in Lua
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - For example: $(hdr(Remote-Party-ID)[2])
Doing this causes Kamailio to output an error to the log when it fails to parse the PV:
2012-02-02 16:38:58|E| 6(26940) ERROR: app_lua [app_lua_sr.c:892]: invalid pv [$(hdr(remote-party-id)[0])] (-1/26)
This was triggered using sr.pv.get("$(hdr(remote-party-id)[0])") from within Lua.
I have also tried sr.pv.get("$hdr(remote-party-id)[0]") which also failed:
2012-02-02 18:26:28|E|15(26956) ERROR: app_lua [app_lua_sr.c:892]: invalid pv [$hdr(remote-party-id)[0]] (21/24)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=202
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Wolfgang Kampichler (wkampich)
Attached to Project - sip-router
Summary - support for parsing URNs
Task Type - Improvement
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - The patch provides correct parsing of URNs (e.g. urn:service:sos.fire), t_relay does not break on RURI with URNs. PVs are set as follows: $ru= "urn:service:sos.fire"
$rz= "urn", $rU= "service", $rd= "sos.fire". Refer to http://tools.ietf.org/html/draft-ietf-ecrit-framework-13#page-29 for SIP signaling requirements for SIP proxy servers.
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=201
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.