hi,Tomas
My Colleage has found some bugs in source files. We find two type bugsIn h460 cnf file.
1) OID dfinition error, For example, TransversalParameters OID is error defined. It should be such as 0.0.8.460 ... .
2) Message type error, For example,IncomingcallIndication is Not GD or FD. It is a generic parameter type.
It is simple to correct after careful check.
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
