Re: h.264 with Wireshark

[Anders Broman <anders.broman () ericsson com>]

> And how can i do that?
Write code ;-)  ?
Decoder configuration Information (DCI) probably has to be stored in a per conversation struct to do a full dissection, 
if that's desired?
If you search the source code I'm sure you can find examples readme.developer is also a good start.
Some additions can probably be made without above, why not start on that?
Regards
Anders
________________________________
From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of Cristina 
Gil
Sent: den 5 februari 2010 16:37
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] h.264 with Wireshark

And how can i do that?

________________________________
From: Anders Broman [mailto:anders.broman () ericsson com]
To: Community support list for Wireshark [mailto:wireshark-users () wireshark org]
Sent: Fri, 05 Feb 2010 16:13:52 +0100
Subject: Re: [Wireshark-users] h.264 with Wireshark

Hi,
> Could I continue decoding H264 with wireshark the rest of the data ([Not decoded yet])?
Shure but it might not be easy as some decoding depends on parameters previously received if I remember correctly.

> I have also observed the data is given in hexadecimal. I read the H264 bitstream is coded with exponential golomb but 
> I don't really know if its true.
> Does wireshark the conversion?
Yes

Regards
Anders

________________________________
From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of Cristina 
Gil
Sent: den 5 februari 2010 13:19
To: 'Community support list for Wireshark'
Subject: Re: [Wireshark-users] h.264 with Wireshark

Thanks anders!!

It works, but i can only get the first data:

H.264
   FU identifier
          0... .... = F bit: No bit errors or other syntax violations
         .10. .... = Nal_ref_idc (NRI): 2
          ...1 1100 = Type: FU-A (28)
   FU Header
         1... .... = Start bit: the first packet of FU-A picture
         .0.. .... = End bit: Not the last packet of FU-A picture
         ..0. .... = Forbidden bit: 0
         ...0 0001 = Nal_unit_type: Coded slice of a non-IDR picture (1)
   H264 bitstream
          1... .... = first_mb_in_slice: 0
          .001 10.. = slice_type: P (P slice) (5)
           .... ..1. = pic_parameter_set_id: 0
[Not decoded yet]

Could I continue decoding H264 with wireshark the rest of the data ([Not decoded yet])?

I have also observed the data is given in hexadecimal. I read the H264 bitstream is coded with exponential golomb but I 
don't really know if its true. Does wireshark the conversion?

Thanks for your help!!!
________________________________
De: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] En nombre de Anders 
Broman
Enviado el: viernes, 05 de febrero de 2010 12:29
Para: Community support list for Wireshark
Asunto: Re: [Wireshark-users] h.264 with Wireshark

Try
Edit->preferences->protocols->h264 Dynamic payload type 96

________________________________
From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of Cristina 
Gil
Sent: den 5 februari 2010 10:38
To: wireshark-users () wireshark org
Subject: [Wireshark-users] h.264 with Wireshark
Hello,

I wanna decode H.264, i read the thread http://www.mail-archive.com/wireshark-users () wireshark org/msg03835.html but 
i wasnt able to decode h264... (wireshark --> preferences --> H.264 --> dynamic payload 125), I use Development Release 
1.3.2

I get a RTP+H264 stream:

10.. .... = Version: RFC 1889 Version (2)
0... .... = Marker: False
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0

Payload type: DynamicRTP-Type-96 (96)
Sequence number: 23252
Timestamp: 868956473
Synchronization Source identifier: 0xcbd5dcba (3419790522)
Payload: 7C05FFE5F98EB9B5AED78E67EB3C2A941606A7CCD179710B...

Is it possible to "decode" H.264 by decoding the RTP payload? How?

Thanks for your help!!

________________________________
AVISO LEGAL
La Informacion incluida en el presente correo electronico es SECRETO PROFESIONAL Y CONFIDENCIAL, siendo para el uso 
exclusivo del destinatario arriba mencionado. Si usted lee este mensaje y no es el destinatario señalado, el empleado o 
el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicacion por error, le informamos 
que esta totalmente prohibida cualquier divulgacion, distribucion o reproduccion de esta comunicacion, y le rogamos que 
nos lo notifique inmediatamente y nos devuelva el mensaje original a la direccion arriba mencionada. Gracias.


________________________________
AVISO LEGAL
La Informacion incluida en el presente correo electronico es SECRETO PROFESIONAL Y CONFIDENCIAL, siendo para el uso 
exclusivo del destinatario arriba mencionado. Si usted lee este mensaje y no es el destinatario señalado, el empleado o 
el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicacion por error, le informamos 
que esta totalmente prohibida cualquier divulgacion, distribucion o reproduccion de esta comunicacion, y le rogamos que 
nos lo notifique inmediatamente y nos devuelva el mensaje original a la direccion arriba mencionada. Gracias.




________________________________
AVISO LEGAL
La Informacion incluida en el presente correo electronico es SECRETO PROFESIONAL Y CONFIDENCIAL, siendo para el uso 
exclusivo del destinatario arriba mencionado. Si usted lee este mensaje y no es el destinatario señalado, el empleado o 
el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicacion por error, le informamos 
que esta totalmente prohibida cualquier divulgacion, distribucion o reproduccion de esta comunicacion, y le rogamos que 
nos lo notifique inmediatamente y nos devuelva el mensaje original a la direccion arriba mencionada. Gracias.

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe