Guys,
So, what's the conclusion? Is this packet correct or not?
I think that:
1. If the packet is incorrect (in terms of BER-encoding), then
the BER error message should be put back, but the dissection
of the current sequence should not be aborted.
2. If we don't know whether it is
meddelande-
AB Från: Oleg Kostenko [mailto:[EMAIL PROTECTED]
AB Skickat: den 20 september 2006 10:41
AB Till: Anders Broman; wireshark-dev@wireshark.org
AB Ämne: Re[2]: Fwd: And again BER errors while decoding H248packets
AB Hello Anders,
AB Here is the fragment from the ASN.1 specification for H.248
, you wrote:
AB Hi,
AB I think part of the problem is that we are uncertain if this isn't a
AB protocol error in the stack you are using - zero length items??
AB Brg
AB Anders
AB -Ursprungligt meddelande-
AB Från: [EMAIL PROTECTED]
AB [mailto:[EMAIL PROTECTED] För Oleg Kostenko
AB Skickat
Hello,
Is there any progress on this issue (see below)?
--
Best regards,
Olegmailto:[EMAIL PROTECTED]
This is a forwarded message
From: Oleg Kostenko [EMAIL PROTECTED]
To: wireshark-dev@wireshark.org
Date: Tuesday, August 22, 2006, 5:14:59 PM
Subject: And again
regards
AB Anders
AB -Ursprungligt meddelande-
AB Från: [EMAIL PROTECTED]
AB [mailto:[EMAIL PROTECTED] För Oleg Kostenko
AB Skickat: den 1 september 2006 14:56
AB Till: wireshark-dev@wireshark.org
AB Ämne: [Wireshark-dev] [PATCH] H.248 Annex C and Annex E support
AB Hello,
AB This patch
Hello,
This patch will add the following functionality to the H.248
dissector:
1. Dissection of properties from Annex C.11 SDP equivalents.
2. Dissection of EventNames and SignalNames from Annex E Basic
Packages.
3. Dissection of event and signal parameters from Annex E.9 Analog
Hello,
I am developing an application that uses libwireshark.dll to decode
packets.
The protocol of each packet is known before the dissection is started, so I
just find the needed dissector with find_dissector() and then start
dissection with call_dissector(). The code that does it is a
