Did you look at the complete scenario files? For example, near the end of
ims_uas.xml, you will see the following:
<sendRmt type="res_call_info">
<param name="rtd_info" rtd="1" info="timestamp"/>
<!-- This sends the timestamp stored in start_time of rtd[1] -->
...
And near the end of ims_uac.xml, you will see:
<recvRmt type="res_call_info" timeout="8000">
<action>
<rtd_eval rtd="2" start="2" stop="r2"/>
<!-- This will look in the message recieved from partner for an IE
-->
<!-- [rtd_info:[rtd_id:2][rtd_start_time:xyz]] and use that to compute
-->
<!-- the rtd (difference with the timestamp_rtd="2", so this measures
-->
<!-- the time the INVITE took to reach the remote side). -->
...
This should make it clearer, I think. The "trick" is that a start_rtd stores a
timestamp in the associated rtd. Then, if the stop event is also local,
stop_rtd will allow the local sipp instance to compute the time difference but
if the stop event happens in a different scenario, this cannot be done so
easily anymore. Instead the start timestamp (obtained during local start_rtd)
must be transmitted to the instance running the counterpart scenario where the
"stop" timestamp is obtained. This is what the <sendRmt type="res_call_info">
inter-sipp message is doing. The difference can then be computed, by means of
the rtd_eval action upon receiving the Rmt message.
As a consequence, the RTD identifiers may potentially be different on both
sides of the overall scenario (e.g. in UAS and UAC), even though they are meant
to represent the same time interval. I think we tried to avoid that as it makes
these already complicated things even more confusing.
Regards,
-David
-----Original Message-----
From: Antoine Roly [mailto:[email protected]]
Sent: Tuesday, October 12, 2010 3:29 PM
To: [email protected]
Subject: [Sipp-users] sipp ims bench: rtd timers
Hi all,
I have a question related to rtd timers in sipp ims bench.
In the uac/uas scenarii, It said in ims_uas.xml that "The imestamp,
stored in rtd[2], will be reported to UAC side at end of scenario so it
can compute the time the INVITE took from UAC to UAS."
The send line in ims_uac.xml is <send retrans="500" start_rtd="1,2,4">
But the recv line in ims_uas.xml is "<recv request="INVITE"
start_rtd="5,2">"
Shouldn't it be <... start_rtd="5" rtd="2"> to stop the second timer?
Same question for rtd[1]. It is said in ims_uac.xml that "rtd[1] is
between sending INVITE at UAC and receiving ACK at UAS."
The send line in ims_uac.xml is: <send retrans="500" start_rtd="1,2,4">
But the recv line in ims_uas.xml is <recv request="ACK" start_rtd="1">
Shouldn't it be rtd="1" in order to stop the timer 1?
Thanks in advance
Regards,
A.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718.
Citibank, Brussels, account 570/1031255/09
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
