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 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.
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.
i stored timeouts to local cfg variables and tried to set them with
t_set_fr:
xlog("about to set fr to $sel(cfg_get.local.invite_timeout)/$sel(cfg_get.local.gw_timeout)\n");
t_set_fr("$sel(cfg_get.local.invite_timeout)",
"$sel(cfg_get.local.gw_timeout)");
xlog("after setting fr\n");
unfortunately, the above t_set_fr results in syslog error:
Mar 30 21:05:10 localhost /usr/sbin/sip-proxy[31365]: ERROR: about to set fr to 75000/3000
Mar 30 21:05:10 localhost /usr/sbin/sip-proxy[31365]: ERROR: <core> [sr_module.c:1546]: Could not convert PV to int
Mar 30 21:05:10 localhost /usr/sbin/sip-proxy[31365]: ERROR: after setting fr
why is that? the two local cfg variables have been set to int values
and no conversion should be needed:
Mar 30 21:05:00 localhost /usr/sbin/sip-proxy[31367]: INFO: Handling XMLRPC POST from <127.0.0.1> with body <<?xml version="1.0" ?><methodCall><methodName>cfg.set_now_int</methodName><params><param><value><string>local</string></value></param><param><value><string>invite_timeout</string></value></param><param><value><int>75000</int></value></param></params></methodCall>>
Mar 30 21:05:00 localhost /usr/sbin/sip-proxy[31367]: INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): local.invite_timeout has been changed to 75000
Mar 30 21:05:03 localhost /usr/sbin/sip-proxy[31363]: INFO: Handling XMLRPC POST from <127.0.0.1> with body <<?xml version="1.0" ?><methodCall><methodName>cfg.set_now_int</methodName><params><param><value><string>local</string></value></param><param><value><string>gw_timeout</string></value></param><param><value><int>3000</int></value></param></params></methodCall>>
Mar 30 21:05:03 localhost /usr/sbin/sip-proxy[31363]: INFO: <core> [cfg/cfg_ctx.c:411]: INFO: cfg_set_now(): local.gw_timeout has been changed to 3000
this is with current master branch.
-- juha
ps. it took a while before i found where the error comes from because
there is no script line number in the message.
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 - error message does not include cfg file line number
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 - cfg file statement
t_set_fr("$sel(cfg_get.local.invite_timeout)",
"$sel(cfg_get.local.gw_timeout)");
produced a single error message
Mar 30 21:05:10 localhost /usr/sbin/sip-proxy[31365]: ERROR: <core> [sr_module.c:1546]: Could not convert PV to int
which did not include cfg file line number.
it took me long time to find the function call from which the error was produced.
improvement request: include cfg file line number in errors like in the above.
-- juha
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=58
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#58 - error message does not include cfg file line number
User who did this - Juha Heinanen (jh)
http://sip-router.org/tracker/index.php?do=details&task_id=58
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.