From admin@sip-router.org Fri Nov 26 14:30:55 2010
From: sip-router <admin@sip-router.org>
To: sr-dev@lists.kamailio.org
Subject: [sr-dev] [tracker] Task opened: $Ts returns wrong timestamp
Date: Fri, 26 Nov 2010 14:30:54 +0100
Message-ID: <20101126133055.6403.488058253.swift@sip-router.org>
In-Reply-To: <FS105@sip-router.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1391203195=="

--===============1391203195==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below.=20

User who did this - Alex Hermann (axlh)=20

Attached to Project - sip-router
Summary - $Ts returns wrong timestamp
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - According to the docs on the wiki, $Ts should always return the sam=
e time for the same message. It doesn't, it returns the same time as $TS in m=
ost cases. It gets worse if the reply is locally generated (408), then the ti=
mestamp of the previous request handled by that process is returned.



Reproduce:

<code>
route {
  xlog("Ts:$Ts  TS:$TS request");

  t_on_reply(REPLY);
  t_on_failure(FAILURE);
  t_relay();
}


on_reply_route[REPLY] {
  xlog("Ts:$Ts  TS:$TS reply");
}


failure_route[FAILURE] {
  sleep(1);
  xlog("Ts:$Ts  TS:$TS failure");
}

</code>

Log:

First call:
<code>
Nov 26 14:10:08 wsproxy1[29897]: ERROR: <script>: Ts:1290777008  TS:129077700=
8 request
Nov 26 14:10:08 wsproxy1[29901]: ERROR: <script>: Ts:1290777008  TS:129077700=
8 reply
Nov 26 14:10:09 wsproxy1[29901]: ERROR: <script>: Ts:1290777009  TS:129077700=
9 failure
</code>

Expected would be that $Ts would always read 1290777008 for this call. As in =
failure_route the original request is handled, the expected value of $Ts woul=
d be the same as the initial value.


Next call:
<code>
Nov 26 14:10:09 wsproxy1[29908]: ERROR: <script>: Ts:1290777009  TS:129077700=
9 failure
</code>


Last call:
<code>
Nov 26 14:10:15 wsproxy1[29900]: ERROR: <script>: Ts:1290777015  TS:129077701=
5 request
<timeout>
Nov 26 14:10:16 wsproxy1[29908]: ERROR: <script>: Ts:1290777009  TS:129077701=
6 failure
</code>
Expected would be that $Ts would always read 1290777015 for this call, certai=
nly not 1290777009.


More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=3Ddetails&task_id=3D105

You are receiving this message because you have requested it from the Flyspra=
y bugtracking system.  If you did not expect this message or don't want to re=
ceive mails in future, you can change your notification settings at the URL s=
hown above.


--===============1391203195==--