I have a stream of RTP packets some of which have payload type = 0 (G711) and some have payload type = 101 (DTMF). I have an application where both in-band and out-of-band DTMF digits are transmitted. When I use Wireshark to capture the RTP stream and extract the payload to a .au file, the audio sounds bad. From a plot I can see that the audio in the .au file contains spikes which causes the pops and clicks in the audio. My guess is that Wireshark does not distinguish between payload types in an RTP stream. It just sees the RTP packets as one payload stream (when in fact there are two: payload type 101 and 0). So wireshark mistakenly extracts the payload of each RTP packet and decodes the RTP payload stream as if it was one audio signal. Can somebody confirm this? asked 18 Apr '11, 10:35  john38274 |
2 Answers:
Wireshark is equipped to handle G.711 A-law and u-law encoded RTP streams. Other streams, or multiplexed streams like RFC 2833, cannot be properly handled. answered 18 Apr '11, 13:44  Jaap ♦ |
You could try to filter out payload type 101 and try again. Also make sure that you do not have duplicate RTP packets. If the case you can try edicap -d answered 29 Jun '12, 10:31  grinob |
it shows payload type dynamic 96 for my case. But the system ensures that packet should be type G.711 a -law. Wireshark can't play RTP for my case. Anything need to be modified for my case?