Wireshark-bugs: [Wireshark-bugs] [Bug 11161] New: RTP/AMR/AMR-WB dissector is using a depreciate
Bug ID |
11161
|
Summary |
RTP/AMR/AMR-WB dissector is using a depreciated function to show the payload data
|
Product |
Wireshark
|
Version |
1.12.4
|
Hardware |
x86-64
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
TShark
|
Assignee |
bugzilla-admin@wireshark.org
|
Reporter |
ler224.bug@gmail.com
|
Created attachment 13578 [details]
tsahrk -T pdml output
Build Information:
$ tshark -version
TShark 1.12.4 (v1.12.4-0-gb4861da from master-1.12)
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with
SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15,
with Gcrypt 1.6.2, without Kerberos, with GeoIP.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, with 8148MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
https://ask.wireshark.org/questions/41919/tshark-rtpamr-payloaddata-export
I am trying to use tshark to export the RTP/AMR-WB payload data. When I run
tshark -r <filename>.pcap -T pdml, it looks like there is no "field name" for
the AMR payload. So I am not able to export them using a function similar to:
tshark -r file.pcap -T fields -e data.
example output of: tshark -r <filename>.pcap -T pdml, which Wireshark
decodes/identifies as RTP & AMR-WB:
<proto name="rtp" showname="Real-Time Transport Protocol" size="45" pos="48">
<field name="rtp.setup" showname="Stream setup by SDP (frame 6)" size="0"
pos="48" show="">
<field name="rtp.setup-frame" showname="Setup frame: 6" size="0" pos="48"
show="6"/>
<field name="rtp.setup-method" showname="Setup Method: SDP" size="0"
pos="48" show="SDP"/>
</field>
<field name="rtp.version" showname="10.. .... = Version: RFC 1889 Version
(2)" size="1" pos="48" show="2" value="2" unmaskedvalue="80"/>
<field name="rtp.padding" showname="..0. .... = Padding: False" size="1"
pos="48" show="0" value="0" unmaskedvalue="80"/>
<field name="rtp.ext" showname="...0 .... = Extension: False" size="1"
pos="48" show="0" value="0" unmaskedvalue="80"/>
<field name="rtp.cc" showname=".... 0000 = Contributing source identifiers
count: 0" size="1" pos="48" show="0" value="0" unmaskedvalue="80"/>
<field name="rtp.marker" showname="0... .... = Marker: False" size="1"
pos="49" show="0" value="0" unmaskedvalue="68"/>
<field name="rtp.p_type" showname="Payload type: AMR-WB (104)" size="1"
pos="49" show="104" value="68" unmaskedvalue="68"/>
<field name="rtp.seq" showname="Sequence number: 271" size="2" pos="50"
show="271" value="010f"/>
<field name="rtp.extseq" showname="Extended sequence number: 65807"
size="2" pos="50" show="65807" value="010f"/>
<field name="rtp.timestamp" showname="Timestamp: 102080" size="4" pos="52"
show="102080" value="00018ec0"/>
<field name="rtp.ssrc" showname="Synchronization Source identifier:
0x5c1aad1d (1545252125)" size="4" pos="56" show="1545252125" value="5c1aad1d"/>
</proto>
<proto name="amr" showname="Adaptive Multi-Rate" size="33" pos="60">
<field name="" show="Payload decoded as RFC 3267 bandwidth-efficient mode"
size="33" pos="60"
value="f163b18fbf3f6aa52b865b74da1800a166a6120168b8b007e2e6352ec4d79e229c"/>
<field name="amr.wb.cmr" showname="1111 .... = CMR: No mode request (15)"
size="1" pos="60" show="15" value="f1"/>
<field name="amr.toc.f" showname=".... 0... = F bit: Last frame in this
payload" size="1" pos="60" show="0" value="f1"/>
<field name="amr.wb.toc.ft" showname=".... .001 0... .... = FT bits:
AMR-WB 12.65 kbit/s (2) / Frame OK" size="2" pos="60" show="2" value="f163"/>
<field name="amr.toc.q" showname=".1.. .... = Q bit: Ok" size="1" pos="61"
show="1" value="63"/>
<field name="" show="Frame Data (32 Bytes)" size="32" pos="61"
value="63b18fbf3f6aa52b865b74da1800a166a6120168b8b007e2e6352ec4d79e229c"/>
</proto>
You are receiving this mail because:
- You are watching all bug changes.