Hi,
I just tested it and the results of trace_shortmsg are very different:
SIPp 3.1:
2013-03-13 02:16:05:798 1363137365.798988 S
[email protected] CSeq: 0 REGISTER
REGISTER sip:xxx.net;transport=UDP SIP/2.0
2013-03-13 02:16:05:878 1363137365.878923 R
[email protected] CSeq: 0 REGISTER
SIP/2.0 401 Unauthorized
2013-03-13 02:16:05:879 1363137365.879427 S
[email protected] CSeq: 1 REGISTER
REGISTER sip:xxx.net;transport=UDP SIP/2.0
2013-03-13 02:16:05:986 1363137365.986806 R
[email protected] CSeq: 1 REGISTER
SIP/2.0 200 OK
Date\tTime\tTimeepoch\t(S|R)\tCallid\tCSeq\tRequest-Response-Line
SIPp 3.4 early
2013-03-13 09:16:03:851177 S
[email protected] CSeq:0 REGISTER
REGISTER sip:xxx.net;transport=UDP SIP/2.0
2013-03-13 09:16:03:932984 R
[email protected] CSeq:0 REGISTER
SIP/2.0 401 Unauthorized
2013-03-13 09:16:03:933446 S
[email protected] CSeq:1 REGISTER
REGISTER sip:xxx.net;transport=UDP SIP/2.0
2013-03-13 09:16:04:017125 R
[email protected] CSeq:1 REGISTER
SIP/2.0 200 OK
Date Time\t(S|R)\tCallid\tCSeq\tRequest-Response-Line
Here are three problems:
* The Epoch-Time is missing: since (I guess) many users are parsing
these lines for delay-calculation or other time-triggered operations,
this epoch-time is very important.
* The column indices are changing: here, the parsers will also fail.
* The time-format: In my assupmtion, "09:16:03:851177" is not correct,
as the micorseconds are fractions of the second. Hence,
"09:16:03.851177" would be correct
The other two topics are obviously fixed:
* missing leading zeros: "09:16:04:017125" shows the leading zero
* synchronised timestamp in long- and shortmsg:
===============================================================
----------------------------------------- 2013-03-13 09:16:03:851177
UDP message sent (349 bytes):
REGISTER sip:a1.net;transport=UDP SIP/2.0
===============================================================
presents the similar timestamp than in the shortmsg-log above
HTH and thanks for your work
Michael
On 12.03.2013 23:31, Robert Day wrote:
> On Sat, 2013-02-16 at 23:58 +0100, Michael Hirschbichler wrote:
>> mentioning the error-log: can you take a look at the time-formatting of
>> the -trace_msg logs?
>>
>> Currently, they are formatted as 2013-02-16 23:40:21:589.216 which is
>> incorrect. The correct (parseable) formatting should (IMHO) be
>> 2013-02-16 23:40:21.589216 (as the ms und us are fractions of a second).
>>
>> Additionally, the leading zeros of the microseconds are removed.
> ...
>> the timestamps of the trace_msg and trace_shortmsg differ.
> ...
>
> The commit I've just made (git hash 89eede) should fix these three
> issues - if you are able to check out and compile the latest code from
> https://sourceforge.net/p/sipp/git , I'd be glad to know whether you
> think it's an improvement.
>
> Best,
> Rob
>
--
Michael Hirschbichler, Mag. Dipl.-Ing.
Institute of Telecommunications
Vienna University of Technology
A-1040 Wien, Favoritenstr. 9-11/388
Phone: +43 1 58801 38846
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
