Default RTP Multicast Address

[Sven]

Hello,

We use pulseaudio in our LAN and we've noticed that the default Multicast IP Address (ie 224.0.0.56) used by the module-rtp-send and module-rtp-recv seems to be part of the "well-known" Multicast adresses. As a result, some switches (HP Procurve in our case) won't filter the igmp traffic, but will broadcast it to all ports. I attached a documentation from HP Procurve Networking with better explanations about this on page 100, (4-22).

We had to change the multicast IP address to resolv that issue. It seems that the 239.255.x.x range is dedicated to local multicast diffusion. We use 239.255.1.56 and it now works perfectly. My request is to have the default multicast IP address changed so that multicast diffusion works in all case with all network materials.

I would be glad to provide more information,
Best regards
Sven Marquilly

[coling]

NB Original comment from malaiwah reposted here:

Configuration file snippet (/etc/pulse/default.pa)

### On the SENDER side
load-module module-rtp-send source=rtp.monitor destination=239.255.1.56

### On the RECEIVER side
load-module module-rtp-recv sap_address=239.255.1.56

[coling]

HP Procurve switching traffic management documentation (from Sven)

[jon]

Hi, what we would like here is to change the default multicast address so that the HP switch can filter the pulse audio packets.

We made a small script that (de)activate using :

gconftool-2 -s /system/pulseaudio/modules/rtp-recv/args0 -t string "sap_address=239.255.1.56" gconftool-2 -s /system/pulseaudio/modules/rtp-recv/enabled -t bool "true" gconftool-2 -s /system/pulseaudio/modules/rtp-send/args1 -t string "source=rtp.monitor loop=1 destination=239.255.1.56" gconftool-2 -s /system/pulseaudio/modules/rtp-send/enabled -t bool "true"

It's more a paprefs issue than how the pulse audio modules are loaded. (I changed the component of this ticket to paprefs).

[mkbosmans]

Hmm, not sure what's best, but undoubtedly we can decide in the 1.0 time frame.

[Ford_Prefect]

Ping?