Bug 480195 - Enable portaudio (and thus the rtp player)
Summary: Enable portaudio (and thus the rtp player)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-15 17:17 UTC by Jakob Hirsch
Modified: 2009-01-19 13:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-19 12:55:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jakob Hirsch 2009-01-15 17:17:44 UTC
Description of problem:

Wireshark is able to play RTP audio, but only with the portaudio lib. Now that portaudio works with PulseAudio (see #445644), it should be enabled in wireshark, so one can play rtp audio when analyzing VoIP calls.

Version-Release number of selected component (if applicable):

wireshark 1.0.5-1
portaudio 19-6.fc10

How reproducible:

Steps to Reproduce:
1. Open a captured VoIP call
2. Click Statistics/VoIP Calls
  
Actual results:

"Player" button is not shown

Expected results:

"Player" button is shown

Additional info:

wireshark's configure script detects if portaudio is installed, so it's sufficient to add 
BuildRequires:  portaudio-devel
and
Requires:	portaudio
to the spec file. I rebuild the SRPM with these changes and the rtp player works.

Comment 1 Radek Vokál 2009-01-19 12:55:58 UTC
The support has been added to latest rawhide build - 1.1.2-0.pre1 .. Can you please verify that it works (I'm having some sound issues recently, button is there but I get no sound)

Comment 2 Jakob Hirsch 2009-01-19 13:11:59 UTC
Thanks for the quick response. Unfortunately, I have only a plain F10 system, and the wireshark packages from rawhide also needs updates for openssl and python (which need even more updates). Is there any chance that the F10 packages will be rebuild?

If not, my own wireshark packages run fine here, so it wouldn't be a big thing.


Note You need to log in before you can comment on or make changes to this bug.