i'm trying to find out why handle_uri_alias() function is not finding
any params in ACK request.
i have in script just before handle_uri_alias() call debug statement
that prints $rm and $ru and it shows correctly:
Apr 1 17:00:45 lohi /usr/sbin/sip-proxy[22980]: INFO: handling uri alias of ACK sip:+35862345670@192.168.15.100:5060;user=phone;alias=86.133.100.125:5060t1
handle_uri_alias() has in the beginning
if ((msg->parsed_uri_ok == 0) && (parse_sip_msg_uri(msg) < 0)) {
LM_ERR("while parsing Request-URI\n");
return -1;
}
rest = msg->parsed_uri.params.s;
rest_len = msg->parsed_uri.params.len;
LM_INFO("params are %.*s\n", rest_len, rest);
if (rest_len == 0) {
LM_INFO("no params\n");
return 2;
}
and here is what comes to syslog:
Apr 1 17:00:45 lohi /usr/sbin/sip-proxy[22980]: INFO: nathelper [nathelper.c:1513]: params are
Apr 1 17:00:45 lohi /usr/sbin/sip-proxy[22980]: INFO: nathelper
[nathelper.c:1515]: no params
why is msg->parsed_uri.params empty str after calling
parse_sip_msg_uri()?
-- juha
i tried to use some of the header field related selects listed on page
http://sip-router.org/wiki/cookbooks/selects/devel
but noticed that they are provided by s textops module. i also noticed
that s and k texops modules have functions whose names are the same.
should the two modules be merged or what in order to be able use stuff
from both?
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#59 - wrong type mismatch error
User who did this: Juha Heinanen (jh)
Severity: High -> Medium
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=59
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 - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - wrong type mismatch error
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - statement
if (@cfg_get.local.phone_timeout > 10) {
xlog("hello\n");
};
produces during proxy startup errors
0(18059) : <core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 507, column 35-38: bad expression: type mismatch: str instead of int at (507,35)
0(18059) : <core> [cfg.y:3382]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 509, column 6: invalid route statement
0(18059) : <core> [cfg.y:3379]: parse error in config file /etc/sip-proxy/sip-proxy.cfg, line 512, column 2-3:
this is a bug in parser, because parser has no way to know what the type of the value in the cfg value will be when the statement is executed and thus should not report an error.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=59
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 user has added themself to the list of users assigned to this task.
FS#59 - wrong type mismatch error
User who did this - Juha Heinanen (jh)
http://sip-router.org/tracker/index.php?do=details&task_id=59
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.
