Hello list,
for a few weeks now I am thinking about the idea of something like
"delayed branches".
For example if one INVITE lookup results in 2 contacts/branches, then
the first branch should be executed directly but the second should
experience a delay of some seconds, until the INVITE is being sent out
to the 2nd contact.
Such a feature would be really useful for users, if they would like to
configure their delayed redirects server-side and not client-side
(devices).
I have some doubts, whether it's reasonable in general, if a sip proxy
behaves like this (delays requests...) - what do you think?
Best Regards
Jasmin
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#78 - function for evaluating string value
User who did this - Juha Heinanen (jh)
----------
defines do not work here, since the idea is to be able to dynamically at runtime to change string values of cfg variables that may contain pseudo variables and transformations. such strings may, for example, appear as parameters of http_queries,
what comes to implementation, this kind of stuff is normal in interpreted languages, for example
#!/usr/bin/php
<?
$format = "Printing number %d\n";
printf($format, 1234);
?>
correctly produces
jh@rautu:~$ /tmp/test.php
Printing number 1234
what comes to my the specific trial implementation, it first calls spve fixup on the string value that may contain pseudo variables and then tries to get final string value based on the fixup result. what exactly is wrong with this? why all calls succeed, but final string value is not correct?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=78#comment92
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 noticed that msilo generated messages include a Contact header such
as:
Contact: <sip:jh@test.fi>;msilo=yes
according to rfc3428.txt this is wrong:
MESSAGE requests do not initiate dialogs. User Agents MUST NOT
insert Contact header fields into MESSAGE requests.
if no one objects, i'll fix msilo module accordingly, i.e., remove
contact header from msilo generated messages.
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#58 - error message does not include cfg file line number
User who did this - Daniel-Constantin Mierla (miconda)
----------
This is runtime and the t_set_fr() is not printing further error message, so only the core function evaluating the parameter writes a message.
In other cases, it is the module function that give more indications.
To be able to print the line, the generic param structure has to be extended to hold the line number, but this will solve the cases when such type of parameter is used.
Maybe the next module interface will pass to function a structure holding more details of running environment, such as cfg file name and line where the function in invoked.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=58#comment91
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#78 - function for evaluating string value
User who did this - Daniel-Constantin Mierla (miconda)
----------
That might not be that easy right now in cfg -- if I got right what you want it is not even in other languages -- i.e., evaluating C code from a char* variable.
However, #!subst or #!define preprocessor directives should help to some extent.
Example:
#!define MYID "$(ru{uri.user})"
myfunction(MYID);
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=78#comment90
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.