0
Завершен

UPNP discovery

rocfusion 7 лет назад в iRidium Script обновлен Sergey (expert) 7 лет назад 3
Hi,

The reason behind no discovery is quite apparent from the following, I made 3 different packet captures of the discovery process. First with iRidium client, next with the original Sonos app and finally with an UPNP Developer Tool. Both the Original Sonos app and the UPNP Developer Tool could find the Sonos Devices on my network immediately every time. Whilst the iRidium client discovery can "sometimes" take a minute or 2. I repeated this 3 times just to be sure. It would be great if the iRidium client could copy what the UPNP Developer tool is broadcast so that we can use this device with all UPNP devices.

Iridium Client Sends one broadcast.

M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 3
ST: upnp:rootdevice


The original Sonos App, 2 broadcasts are sent 2 seconds apart targeted specifically at the sonos household and two different broadcast addresses are used.

M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 1
ST: urn:schemas-upnp-org:device:ZonePlayer:1
X-RINCON-HOUSEHOLD: Sonos_XXXXXXXXXXXXXXXXXXXXXXXXX

M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 1
ST: urn:schemas-upnp-org:device:ZonePlayer:1
X-RINCON-HOUSEHOLD: Sonos_XXXXXXXXXXXXXXXXXXXXXXXXX


UPNP Developer Tool send two broadcasts less than 1 second apart, note the MX record gives all the devices to respond within 5 seconds

M-SEARCH * HTTP/1.1
ST: upnp:rootdevice
MAN: "ssdp:discover"
MX: 5
HOST: 239.255.255.250:1900
Content-Length: 0

M-SEARCH * HTTP/1.1
ST: upnp:rootdevice
MAN: "ssdp:discover"
MX: 5
HOST: 239.255.255.250:1900
Content-Length: 0



Thanks,


Roger
Ожидает ответа пользователя
Hello Roger,

Thank you for the idea. We plan to change UPNP driver in V.3.x.

Sincerely yours,

Oksana Storozheva
iRidium mobile Team

Сервис поддержки клиентов работает на платформе UserEcho