Ethereal-dev: Re: [Ethereal-dev] Transform "H323 Conversations" to a more generic "VoIP Conves
Alejandro Vaquero wrote:
Hi Miha and All,
I think the “H323 Conversation” is a really nice tool and soon
probably be new protocols added to have the same functionality (like
SIP and MGCP). To this mind, I think we should create a more generic
“Voip conversation”.
My idea is to have something similar than the “H323 Voip Conversation”
window but called something like “Voip conversations”. Here we will
have all the Voip calls together (H323, SIP, MGCP, etc..). In this
window each call will have:
“Protocol”: H323, SIP, MGCP, etc...
“IP:port A”
“IP:port B”
“Calling ID”: this could be the number in H323/SIP/MGCP. Some
protocols don’t always have this info, for example in MGCP we could
put the EndpointID and in SIP the sip URI.
“Called ID”
“Status”
“Comments”: here put some protocol specific comments like “Faststart”,
“H225 pkts” and “H245 pkts” on H323 calls
In this window will have a bottom similar than “Analyze” renamed
something like “Add to Analyze”. When clicked, this call will be added
to the “Voip Analysis” windows (similar than the “H323 Voip Analysis”
window). This will allow the user to add multiple calls to analysis.
For example if it is a call that started as H323 and then it is SIP,
you can add this “two” calls to analyze to have the whole picture.
Each call in the “Voip analysis” window will have a different
background color to be easily identified. This window will have the
following columns:
“Packet”
“Time”
“Delay”
“ IP:port A” (we have to add this since multiple call can be added)
“Side A” (the protocol dependent message type like “H225 SETUP”, “H225
ALERTING”, “INVITE”, “CRCX” etc….)
“Direction”
“Side B”
“IP:port B”
“Comments”
Let me know your thought. If you agree I can start working on this.
Yes, I do think that the H323 Vonversation *is* a very helpful tool
(although I don't use any VoIP, so it won't be helpful for me
personally, but I think of this as a good "proof of concept").
I would like to have something not only for the VoIP conversations. The
same mechanism would be helpful for a lot of other protocols as well.
So before start a special implementation for each and every protocol
seperately, we might find a general way to create such a thing.
And I do think, that this would be possible to some extend. However,
this will be a bit more work for the first time implementation.
I could help you with the GUI parts of that, but my knowledge on the
current conversation stuff is limited.
Regards, ULFL
