|Summary:||ASTERISK-01631: [request] Add timestamp to sip debug output|
|Date Opened:||2004-05-15 14:12:32||Date Closed:||2011-06-07 14:04:42|
|Environment:||Attachments:||( 0) patch_currentcvs.txt|
( 1) patch_debugtimestamps.txt
|Description:||It would be very useful to have a timestamp displayed with each packet send/received. Even just a raw unix timestamp would be useful.|
It would also be nice to show the 'from' IP address on the display of received packets.
|Comments:||By: Brian West (bkw918) 2004-05-15 22:13:37|
timestamps on sipdebug are useless. You can do sip debug peer XX or sip debug ip X.X.X.X
The messages hould appear as they are without much modification.
By: jht (jht) 2004-05-15 22:54:39
When testing in combination with border controllers and NAT routers packets sometimes come back from unexpected IP addresses, so sip debug ip x.x.x.x wouldn't show these.
Timestamps would be useful when trying do debug protocol issues and trying reconstruct a sequences of events.
By: khb (khb) 2004-05-17 22:50:17
Asterisk provides timestamps in the log files but not on the console.
I usually tail -f on the log files, but I can see that someone would want timestamps on the console.
Also the current format of packet print is not pretty.
Try this patch and see if you like it.
I've used the format in this patch for a while and found it more readable.
By: khb (khb) 2004-05-17 23:17:29
I forgot that two patches (ASTERISK-1614) haven't made it into CVS yet, so if you are using cvs as of the time of this note, you need to use the second patch (patch_currentcvs.txt). This time I am actually ahead of CVS, weird.
By: twisted (twisted) 2004-06-16 23:37:36
I'd have to say that while this is a good idea, it is indeed useless, as sip debug messages appear in the order in which things happen. If you need timestamps on your sip debug, I would suggest using a capture utility such as ethereal, as it will give you all you want and more, in order of reciept.