Hi Woo,
can not you create filtered trace containing only related
H.460 message without any sensitive data?
It is hard to implement anything blind. Especially if I never
worked with real H.460 trace.
Regards,
Tomas
hi, Tomas and anders
I am sorry.For my comany security
policy I can't upload any files. TraversalParameters is defined in the H.460.19
which can be downloaded from ITU website.
Then it is hold in the H.245
OpenLogicalChannel or OpenLogicalChannelAck message as an
OCTSTRING.
I have never changed the *ncf.
Please teach me how to modify *.ncf file.
Regards,
Woo
2011/11/23 Kukosa, Tomas
<tomas.kukosa@xxxxxxxxxxxxxxxxxxxxxx>
Hi
Woo,
please
could you send us the capture file (only related frames) ?
It should
be decoded as H.460.19 is implemented. But I haven't tested it as I have never
got any example trace for it.
Regards,
Tomas
Hi,
An example
trace file will help, I couldnt find TraversalParameters in H245 so I'm unsure which parameter in H245 holds this, but if
it's an OCTET STRING in the H.245
spec
and no one
has made chenges in the .cnf file to call the H.460 dissection it will be
displayed as raw data as tha's what it is to the H.245
dissector/protocol.
Regards
Anders
Hi,
My wireshark can't decode all values by tracing down the
H.460.19 asn.1 trees. H.460.19 has 'TraversalParameters'
asn.1 subtree,this value is encoded as octstring and then encapsulated in
the H.245 message. Wireshark can only decode all H.245 value but keep h.460.19
as raw.
regards,
Woo
___________________________________________________________________________
Sent
via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:
http://www.wireshark.org/lists/wireshark-users
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe