[sr-dev] [tracker] Comment added: Extending TM timeout/408 handling

sip-router admin at sip-router.org
Wed Apr 14 01:41:12 CEST 2010


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)

----------
It seems that new TM module includes some functions to detect if there was a timeout and also provisional responses for the winning branch, so they could be used to inspect the locatl timeout cause and determine what to do in each case:

  failure_route[0] { 
    if (t_branch_timeout()) {
      if (t_branch_replied())
        log("the winning branch got a fr_inv_timer expiration (provisional responses were received) => 408\n");
      else
        log("the winning branch got a fr_timer expiration (no response at all) => 500\n");
        # I prefer to reply a 500 in this case as it really means a problem with the destination:
        t_reply("500", "The destination is unreachable");
    }
  }
----------

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=55#comment77

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.



More information about the sr-dev mailing list