THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#54 - Received replies should get higher preference than locally generated ones
User who did this - Andrei Pelinescu-Onciul (andrei)
----------
Alex,
DNS failover is automatically attempted if a 503 is received or on timeout (just making sure that you don't try to do in script something that is already automatically handled). I guess your example is valid if you don't want to do DNS failover on the local proxy, but on the upstream one.
Regarding the invented response: I would always prefer a timeout over some 500 a downstream proxy might have sent (the 408 says at least that there might be a working phone, but the user didn't pick it up). For 4xx responses is not so clear, it's debatable if one should prefer
a 408 over a 480 or even a 486.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=54#comment69
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#54 - Received replies should get higher preference than locally generated ones
User who did this - Alex Hermann (axlh)
----------
Andrei,
making the priorities configurable would be a nice addition.
For the example I gave with DNS based failover an even simpler solution is possible. In the DNS failover case i'm only interested in the replies from the last contacted host. Because the other hosts already gave responses i'm not interested in, hence the failover to the next host. So an option to only consider replies from the last host (branch) would (also) be a nice solution. I could use that in other cases too, because in general, i'm only interested in the responses from the last branch (but that might be related to my specific use cases).
The question i asked myself is: why would i prefer a (invented) response from a host that __fails__ above the response from a responding host. I couldn't find an anwer...
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=54#comment68
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.
currently, dialplan module dp_translate() function requires src/dest
style second parameter even in cases where a dialplan id consists of
rules where subst_exp and repl_exp are missing, i.e., when
dp_translate() is only used for matching and possibly setting of attrs
avp.
how about if i try to change the syntax of second param to be
src[/dst]
if /dst is missing then no replacement is done?
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#56 - Cfg parsing error for alias/listen and custom global parameter
User who did this - Iñaki Baz Castillo (ibc)
----------
Doesn't the grammar parser split the parameter declarations into lines?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=56#comment67
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#56 - Cfg parsing error for alias/listen and custom global parameter
User who did this - Iñaki Baz Castillo (ibc)
----------
Doesn't the grammar parser split the parameter declarations into lines?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=56#comment66
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 changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#56 - Cfg parsing error for alias/listen and custom global parameter
User who did this: Daniel-Constantin Mierla (miconda)
Task details edited:
-------
Following sequence of config rises errors:
<code>
alias="sip.mydomain.com"
myvar.msg="one" desc "One"
</code>
0(4069) : <core> [cfg.y:3382]: parse error in config file kamailio.cfg, line 104, column 10: syntax error
0(4069) : <core> [cfg.y:3382]: parse error in config file kamailio.cfg, line 104, column 10: unknown config variable
0(4069) : <core> [cfg.y:3379]: parse error in config file kamailio.cfg, line 104, column 11-15:
ERROR: bad config file (3 errors)
Line 104 is 'myvar...'
Having another core parameter in between is ok, e.g.,:
<code>
alias="sip.mydomain.com"
port=5060
myvar.msg="one" desc "One"
</code>
Seems alias/listen grammar eats up to myvar.msg, considering to be host definition.
-------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=56
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 - Daniel-Constantin Mierla (miconda)
Attached to Project - sip-router
Summary - Cfg parsing error for alias/listen and custom global parameter
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 - Following sequence of config rises errors:
alias="sip.mydomain.com"
myvar.msg="one" desc "One"
0(4069) : <core> [cfg.y:3382]: parse error in config file kamailio.cfg, line 104, column 10: syntax error
0(4069) : <core> [cfg.y:3382]: parse error in config file kamailio.cfg, line 104, column 10: unknown config variable
0(4069) : <core> [cfg.y:3379]: parse error in config file kamailio.cfg, line 104, column 11-15:
ERROR: bad config file (3 errors)
Line 104 is 'myvar...'
Having another core parameter in between is ok, e.g.,:
alias="sip.mydomain.com"
port=5060
myvar.msg="one" desc "One"
Seems alias/listen grammar eats up to myvar.msg, considering to be host definition.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=56
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.