Module: sip-router
Branch: master
Commit: cd93b6afcc6592b4ab8b45040af7f61caa0c1c70
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cd93b6a…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Sat Mar 27 23:26:24 2010 +0100
permissions(k): tag support for allow_address
- new column tag holding a string that is returned in config file upon
matching the address
- similar to tag for allow_trusted()
- reuses the avp and column name from allow_trusted()
---
modules_k/permissions/README | 10 ++-
modules_k/permissions/address.c | 17 +++--
modules_k/permissions/doc/permissions_admin.xml | 9 ++-
modules_k/permissions/hash.c | 80 +++++++++++++++++++++--
modules_k/permissions/hash.h | 6 +-
5 files changed, 103 insertions(+), 19 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=cd9…
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#55 - Extending TM timeout/408 handling
User who did this - Iñaki Baz Castillo (ibc)
----------
Please ignore the first solution I suggested ("giving lowest priority to locally generated 408 if such 408 was raised by fr_timer expiration") as finally I would get a 408 in failure_route anyway and I couldn't know the cause of such 408 (received from downstream, fr_inv_timer expiration, or fr_timer expiration). I'd just would like to do failover if fr_timer expired, so inspecting the 408 doesn't help me.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=55#comment65
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#55 - Extending TM timeout/408 handling
User who did this - Iñaki Baz Castillo (ibc)
----------
Another possible solution:
3) Generate local 503 if fr_timer expires.
According to RFC 3261 there are two posibilities if the transport layer fails:
- Timeout, no response, so 408 is locally generaged.
- Transport error so 503 is locally generated. Transport error can occur in both TCP and UDP:
- In TCP means that the TCP connection failed.
- In UDP means that the UAC received a ICMP indicating "UDP port 5060 unreachable".
The transport error for UDP is not handled by TM as it doesn't rely on the received ICMP. Also it seems that such ICMP mechanism is not interoperable between different TCP/IP stacks.
Anyhow, I would suggest that when fr_timer expires (in UDP) a locally generated 503 could make sense. Why not? If there is no response at all for a transaction then there is some kind of network issue or perhaps the remote server is down/congested. 503 seems suitable for me, even if RFC 3261 doesn't state it.
PS: As far as I know, other SIP stacks uses internal codes (like 7XX) to indicate such kind of errors (transport error, transport timeout...). I think something like that is a real need even if RFC 3261 didn't consider it (as they didn't consider NAT).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=55#comment64
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#55 - Extending TM timeout/408 handling
User who did this - Iñaki Baz Castillo (ibc)
http://sip-router.org/tracker/index.php?do=details&task_id=55
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 - Iñaki Baz Castillo (ibc)
Attached to Project - sip-router
Summary - Extending TM timeout/408 handling
Task Type - Bug Report
Category - tm
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Low
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hi, let's suppose the following case:
SR receives an INVITE and performs serial or parallel forking to gw1 and gw2.
Three cases:
case a)
- gw1 replies 480.
- gw2 replies 408.
case b)
- gw1 replies 480.
- gw2 replies 180 and fr_inv_timer expires so a local 408 is generated.
case c)
- gw1 replies 480.
- gw2 replies nothing and fr_timer expires so a local 408 is generated.
In any case, after the transaction fails I handle the winning response in failure_route in which I get a 408. But there is no way to determine which of the above 3 cases took place.
For cases "a" and "b" the 408 could be a good choice (also the 480) but in case "c" I'd strongly prefer using the 480. But there is no way, in failure_route, to determine if our case is "a", "b" or "c".
A non reliable pseudo-workaround is setting a transaction flag(RINGIN_RECEIVED) so when inspecting the 408 in failure_route we can "determine" if fr_timer expired (case "c") or not (cases "a" or "b"). This is not reliable as the flag could be set by other branch in which 1XX was received.
Possible solutions:
1) When TM chooses the winning response it must give lowest priority to locally generated 408 if such 408 was raised by fr_timer expiration, so for the above cases the winning response would be:
a) 408
b) 408
c) 480
or:
2) When fr_timer expires a new status code is locally generated, i.e. 478 "No response received at all". Such code would have lowest priority.
Opinions?
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=55
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 - Iñaki Baz Castillo (ibc)
----------
Andrei,
IMHO what you suggest it's reasonable and would cover most of the needs.
However I still consider special the 408 handling (local-fr_time, local-fr_inv_timer, received) so I will open a new report for it.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=54#comment63
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.