In the spirit of "send text," I've put together a straw-man proposal for an easy-to-generate and fast-to-process extensible format for saving SIP log messages:
I quite like this scheme. It is very simple to generate and parse and will be blazingly fast. It would also be very simple to create a utility to generate "human-readable" versions from it which would address that particular concern.
Comments about the format:
- add a version number to the header
- set aside a range of tags for vendor attributes.
A few miscellaneous comments about contents:
- for sent messages: local ip:port used to send the message + transport used + destination ip:port
- for received messages: remote ip:port message was received from + local ip:port + transport used
- it may be a good idea to have a predefined tag which can be used as an index into another diagnostic file. e.g. pointer into a PCAP file or vendor diagnostic log.
- Is there anything we want to jam in here to help debug TCP/TLS issues or is that out of scope?
_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP