Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wifi speaker detected, ip correct, portnumber wrong #74

Open
time4breakfast opened this issue Mar 29, 2020 · 4 comments
Open

Wifi speaker detected, ip correct, portnumber wrong #74

time4breakfast opened this issue Mar 29, 2020 · 4 comments

Comments

@time4breakfast
Copy link

Hello,

I'm trying to use a wifi speaker via the pulseaudio raop module. My speaker is correctly recognized, yet the port is wrong.
Modul #29 Name: module-raop-sink Argument: server=[192.168.178.49]:7000 sink_name=raop_output.Sonos-347E5C3C237C.local sink_properties='device.description="Arbeitszimmer (192.168.178.49:7000)"' protocol=UDP encryption=none codec=ALAC Nutzungszähler: 0 Eigenschaften: module.author = "Colin Guthrie" module.description = "RAOP Sink" module.version = "11.1"

I already tried to unload the module and reloading it with the correct port number.
pactl load-module module-raop-sink server=[192.168.178.49]:1400 sink_name=raop_output.Sonos-347E5C3C237C.local
pactl load-module module-raop-sink server=192.168.178.49:1400 sink_name=raop_output.Sonos-347E5C3C237C.local
But everytime I try this, I only get an error: 'initialization of module failed'

Is there a possibility to keep all the settings but just change the port number?
Thanks in advance
Liz

@piit79
Copy link

piit79 commented Mar 29, 2020

Hi, sorry if I'm not immediately helpful, but I'd start with a tcpdump to see what the speaker is announcing. Perhaps it's some kind of quirk in the announcement...

@StefanBruens
Copy link

StefanBruens commented Apr 4, 2020

As raop is announced using dns-sd/mdns, the port is announced there.

Use avahi-browse -a -r, for me it prints (using a Pioneer VSX-924):

= wlp2s0 IPv4 745E1C791C9A@VSX-924                          AirTunes Remote Audio local
   hostname = [VSX-924.local]
   address = [192.168.180.27]
   port = [1028]
   txt = ["fv=s9691.5003.1116" "am=VSX-924" "vs=141.9" "vn=65537" "tp=UDP" "ss=16" "sr=44100" "sv=false" "pw=false" "md=0,1,2" "ft=0x44F8A00" "et=0,4" "da=true" "cn=0,1" "ch=2" "txtvers=1"]

Port in this case is 1028.

@time4breakfast
Copy link
Author

The tcpdump doesn't look that different from the rest.

Interestingly, with the avahi-browse -a -r command I see the device listed twice, once with the correct IP and port and once with the incorrect one:
= wlp1s0 IPv6 347E5C3C754C@Arbeitszimmer AirTunes Remote Audio local
hostname = [Sonos-347E5C3C754C.local]
address = [192.168.178.49]
port = [7000]
txt = ["vs=366.0" "vn=65537" "tp=UDP" "sf=0x4" "am=SYMFONISK" "md=0,1,2" "fv=p20.55.1-74250" "ft=0x445F8A00,0x1C340" "et=0,4" "da=true" "cn=0,1"]

= wlp1s0 IPv4 sonos347E5C3C754C _spotify-connect._tcp local
hostname = [sonos347E5C3C754C.local]
address = [192.168.178.49]
port = [1400]
txt = ["CPath=/spotifyzc" "VERSION=1.0"]

I have deactivated the 'make Apple AirTunes devices available in local network" within pulseaudio and the device is shown in the audio settings but I still can't hear anything.

@StefanBruens
Copy link

The two entries are two different protocols, one is "AirTunes Remote Audio" aka RAOP, the other one is something related to Spotify.

For RAOP, you want to enable AirTunes.

Why do you think the port is wrong, at all?

Can you provide a wireshark trace? Set the filter to 'ip.addr == 192.168.178.49'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants