Hi Guy.
Thanks for your suggestions - PDF sound like the most 'portable' :-D
The issue we have is that it is too time consuming to switch between systems to troubleshoot an issue so moving the data from the vendor system to one with wireshark would not be operationally feasible, it was worth thinking about though :-)
-John
On Mon, Nov 26, 2012 at 4:17 PM, Guy Harris
<guy@xxxxxxxxxxxx> wrote:
On Nov 26, 2012, at 1:11 PM, John Powell <
jrp999@xxxxxxxxx> wrote:
> Thanks for your input - sorry about the Microsoft document - for future reference - what type of document would suggest using to detail such information?
PDF?
> Now one vendor appears to be able to come some ways to what we need, the problem is the the vendor can not decode one of our VoIP signalling protocols because it is proprietary even though Wireshark does a decent job. For the SIP protocols the vendor solution will work.
Can the vendor write out capture files in a format that Wireshark can currently read? (When you're directly using dumpcap to capture the packets, you're writing out capture files and reading them later.)
If not, can they write them out in a format for which they have sufficient documentation to allow us to write code for Wireshark that can read them (and which they're willing to let us read and to write *publicly-available GPL-licensed* code based on that documentation)?
(I.e., use the vendor's solution as a replacement for dumpcap, but *not* as a replacement for the entire process including dissection of the captures.)
