This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

can’t save payload in both directions

0

i have the latest stable version 1.6.1 installed. i'm trying to extract audio from a VoIP call. unfortunately, i'm able to save in either forward or reversed direction but not both. when attempting to save in .au format i get the following error: "can't save in a file: saving in au format supported for alaw/ulaw streams"

when attempted to save in .raw format i get the following error: "can't save in a file: unable to save raw data in both directions"

i was previously able to save in these formats in both directions. i've seen previous posts of this error without any solutions. most of these were posts that mentioned the bug was fixed in older versions.

any suggestions?

ps - this is on windows 7

asked 09 Aug '11, 20:36

cesto's gravatar image

cesto
1112
accept rate: 0%

edited 09 Aug '11, 20:38


One Answer:

0

The error "can't save in a file: saving in au format supported for alaw/ulaw streams" only comes up when saving in one direction, not both.

The raw format never can save both directions.

Anyway, most likely cause is 'unclean' RTP streams, that is packet with payload type other that PCM A-law (8) or µ-law (0).

answered 10 Aug '11, 01:34

Jaap's gravatar image

Jaap ♦
11.7k16101
accept rate: 14%

Hi Jaap,

I can assure you the error comes up with I select "both" directions under .au format. Also, I have the RTP packet selected which shows G.711 pcmu (u-law).

When you say it's most likely due to an unclean RTP stream, is this from the VoIP device? Is there any adjustments I can make to avoid this error? Also, can I extract the audio from this stream that has been already capture since it plays correctly through the wireshark player?

thanks again!

(10 Aug '11, 14:25) cesto

i misread your reply about the u-law being 0 which it is as well. here's a cut and paste of the RTP packet:

Payload type: ITU-T G.711 PCMU (0)

i'm at a loss here, i can't seem to narrow this down to a device issue or wireshark issue.

(10 Aug '11, 18:04) cesto