Peter Kjellerstedt wrote:
<I am currently working on a project that sends data
<over RTP using a dynamically assigned payload type.
<I needed to capture what is sent and recalled that
<Ethereal had some mean to save the RTP payload. As
<it turned out this feature was only for saving
<audio data. However, not to be discouraged I figured
<I could hack the code to save the raw payload data
<instead.
Hi,
Ethereal can store G.711 A-law and G.711-Ulaw RTP packets in au-format
(Analyze/Statistics/RTP Streams/Analyse../Save payload),
but it is also possible to save payload data in rtpdump file format (raw
payload data + headers), but this is done from Analyze/Statistics/RTP
Streams/Show all.../Save as..). If you have missed it.
You can save in rtpdump format for any codec (i.e. both audio and video).
I have used this to replay e.g. H.263 video, H.261 video, MPEG-4 video,
G.723.1, G.711, AMR audio, GSM audio toward QuickTime player and/or JMF
JMStudio by using the rtpplay and some other tools.
I have also used the rtpdum format for post-processing of rtp-streams in
separate programs.
You can search on "rtpdump" on the Ethereal site and find some more details.
I have used JM Player with H.261 video, H.263-1998 video, G.723.1 audio,
G.711 U-law audio and GSM audio and some other codecs with static payload
types, if I remember correct. G.711 A-law is not supported in JMF.
You can not use JM Studio for dynamic payloads (but JMF could be used if you
do some programming).
QuickTime Player can be instructed to listen for RTP packets on certain port
by using an sdp-file that tells the relation between ports, payload type and
codecs.
I have used it for H.261 video, H.263-2000 video (dynamic payload), MPEG-4
video (dynamic payload), G.711 A-law, G.711 U-law, AMR audio (dynamic
payload) and some other codecs.
