["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

---

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: Wednesday, November 23, 2011 10:55 AM
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] how to display h.460.19 related values?

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

---

From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of woo johnman
Sent: den 23 november 2011 10:28
To: wireshark-users@xxxxxxxxxxxxx
Subject: [Wireshark-users] how to display h.460.19 related values?

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