Hello,
My system hardware and audio device:
When I try and play back the rtp after making a sip call. I go to VOIP Calls | Player | Decode | Play. I get the following error message.
Can anyone suggest a solution to this problem? Many thanks for any advice, ===== Device info ======
======= Edit === After install audacity:
Audacity installed:
asked 22 Jan ‘11, 08:05 ant2009 edited 24 Jan ‘11, 07:17 |
2 Answers:
The Audacity audio device info gives the following picture:
How to change the ALSA configuration to give you the right device as the first one I don't know. The very best way is to put pressure on the PortAudio developers to fix the three years outstanding CRITICAL bug (*) (*) Yeah it's a rant, but it must be solved at the source, not be worked around by all (audio) developers... answered 24 Jan '11, 11:41 Jaap ♦ |
There's something off with the configuration of your audio system. First off, the PortAudio library has some issues finding your default device, on the default host API. That's a PortAudio lib problem by itself, but Wireshark tries to work around it looking for other host API/device configurations. It tries to work through the list of host APIs, the first one with devices on them is selected, then the first device on that is selected. An output stream is opened on it, with stereo output, 16 bit samples, 8 kHz sample rate. Now, your title says: "Invalid sample rate". That strikes me as odd, because the output configuration is trivial in itself. You could investigate further installing Audacity, and checking how it works the output host API/device options. answered 23 Jan '11, 06:00 Jaap ♦ Hello, thanks for your answer. However, installing audacity didn't work. I installed it and then rebooted. See my edited question of the results. Thanks. (23 Jan '11, 08:30) ant2009 What does Audacity menu Help|Audio Device Info show ? (23 Jan '11, 11:44) Jaap ♦ Hello Jaap, I have edited my answer with the device info. Thanks. (24 Jan '11, 07:16) ant2009 |
Thanks for your help. Just unfortunate that is no final solution.
Ehm, no, it's not a final solution. What would be is (in order of preference):
All of which requires developer cycles.