sip-router writes:
> Additional comments about closing: It's already implemented: start
> your .cfg file with #!KAMAILIO or #!OPENSER and you will have
> kamailio/openser syntax.
> Use #!SER if you want ser syntax and nothing or #!ALL or #!MAXCOMPAT
> if you want the combination between the two (ser & k syntax in the
> same time).
ok, thanks, juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#51 - route is not called and no error is produced
User who did this - Juha Heinanen (jh)
----------
i still think this is a bug, because trying to execute a non-existing route (in this case "$var(test)"), should produce an error to syslog.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51#comment47
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 been re-opened:
FS#51 - route is not called and no error is produced
User who did this - Juha Heinanen (jh)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51
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 been re-opened:
FS#51 - route is not called and no error is produced
User who did this - Juha Heinanen (jh)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51
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 is now closed:
FS#47 - allow choosing of avp syntax
User who did this - Andrei Pelinescu-Onciul (andrei)
Reason for closing: Implemented
Additional comments about closing: It's already implemented: start your .cfg file with #!KAMAILIO or #!OPENSER and you will have kamailio/openser syntax.
Use #!SER if you want ser syntax and nothing or #!ALL or #!MAXCOMPAT if you want the combination between the two (ser & k syntax in the same time).
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=47
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 is now closed:
FS#51 - route is not called and no error is produced
User who did this - Andrei Pelinescu-Onciul (andrei)
Reason for closing: Not a bug
Additional comments about closing: You are trying to execute the route "$var(test)" which does not exist (rvals are _not_ expanded when quoted).
It's the same as trying route("foobar").
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51
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 - pv argument support for route() function
Task Type - Feature Request
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 - it would be good if route() function would be able to take the name of the route to be executed from a pv argument. that would avoid long switch statements in the script. also, together with #include capability, it would make possible to add new route blocks to the script without a need change the parts of the script that calls them.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=52
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#52 - pv argument support for route() function
User who did this - Juha Heinanen (jh)
http://sip-router.org/tracker/index.php?do=details&task_id=52
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 - route is not called and no error is produced
Task Type - Bug Report
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 - i tested if route() with pv arg would work. i created a route block:
route [test] {
xlog("here we are\n");
return;
}
and then as the very first thing in the main route block i have:
$var(test) = "test";
route("$var(test)");
when i send the proxy a sip request, i don't get anything related to
this to syslog, i.e., no "here we are" line nor an error message.
if route() accepts a pv argument, then route [test] should be executed.
if it does not accept pv argument, an error should be produced.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=51
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#51 - route is not called and no error is produced
User who did this - Juha Heinanen (jh)
http://sip-router.org/tracker/index.php?do=details&task_id=51
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.