Hello,
I have a question related to SIPp logging.
It seems that messages logged in the SIPp error file are not terminated by an
end of line character.
This makes it difficult to read or parse.
See example below:
The following events occurred:
2023-11-09 14:46:52.564911 1699541212.564911: Call-Id: (...), receive
timeout on message (...) UAC:1 without label to jump to (ontimeout attribute):
aborting call2023-11-09 14:46:52.565879 1699541212.565879: Dead call
1-4148690@10.118.21.108 (aborted at index 1), received 'SIP/2.0 302 Moved
Temporarily^M
(...)
Content-Length: 0^M
^M
'2023-11-09 14:46:53.564003 1699541213.564003: Call-Id:(...)
In this example, the corresponding code is in call.cpp at line 2054:
WARNING("Call-Id: %s, receive timeout on message %s:%d without
label to jump to (ontimeout attribute): aborting call",
id, curmsg->desc, curmsg->index);
I don't see a \n at the end of the log message (or for any call to WARNING or
ERROR functions).
Shouldn't there be one ?
Or should the logging function add a \n ?
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
