Ethereal-users: Re: [Ethereal-users] saving file in rtpdump -ascii format

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: "Martin Regner" <martin.regner@xxxxxxxxx>
Date: Sat, 16 Apr 2005 09:41:23 +0200
Janice Lau wrote:
<yes, now i am able to send the .rtp file ( which i saved from
<Ethereal) to another port specified by me using rtpplay...and also
<captured the whole packets using Ethereal !! It's really a great time
<for me to figure this thing out !!

Yes, you should be able to use rtpplay for that.
I haven't used rtpsend myself, but guess that rtpllay could be useful if you want to edit something in the file (e.g.
if you need to send with a different payload type) before sending it.

<by the way, Martin, i tried on the command convert between  "-dump"
<format and "-ascii" format, but the output .txt consists nothing.. how
<am i going to get an "ascii" format file besides this way?

I used
<rtpdump -F ascii  -f  sampleg723.rtp -o sampleg723.txt

and got something like below in sampleg723.txt

0.000000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6769 ts=480 ssrc=0x46a58959

3.328000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6904 ts=65280 ssrc=0x46a58959

3.387000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6905 ts=65760 ssrc=0x46a58959

Hower it might be better to use "-F hex" so that the payload bytes are also included
<rtpdump -F hex  -f  sampleg723.rtp -o sampleg723hex.txt

and got something like below in sampleg723hex.txt
0.000000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6769 ts=480 ssrc=0x46a58959
data=f8fef530580c806801037a369838d97733f6bf33085aba464456c081d1b7f1ab290332e34440063751a263b4531e1e3c

3.328000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6904 ts=65280 ssrc=0x46a58959
data=a00608b5880a0298fc254fd3ea27c95d6f2757af790182be0cf7c095417269475e1564504407ea01aad2e6983c6b8937

3.387000 RTP len=60 from=0.0.0.0:0 v=2 p=0 x=0 cc=0 m=0 pt=4 (G723,1,8000) seq=6905 ts=65760 ssrc=0x46a58959
data=d0a6f50340d7a8f005f28a5f58b3ad4f134df3d0dffe4c585cf0d5aa0682007d00ec65f0b4c5eb96fd02261bdf017df3

I'm not sure that the files generated in this way will work with rtpsend, since I have rtpsend myself yet.