GNOME.org
 

Re: Fwd: GuPNP Tools - av-cp fails trying to access media renderer:2

Hi,

gupnp-av-cp works well with Rygel, I test the two with each other regularly. Electrocompaniet managed to configure Rygel in a way that it does not prepend the USN with "uuid:" - which TBH I thought wasn't possible. But the USNs are really invalid, they have to start with "uuid:"

Searching for the most basic spec version (:1) is fine. the devices are supposed to answer anyway, and GUPnP can handle that transparently for you (As properly certified by UPnP and DLNA some time ago). The other thing I'm wondering about is why Rygel is configured to do a version downgrade there.

gssdp-discover works because it does not do any USN validations. USN's are only standardized format in UPnP context, in SSDP you can put there whatever you want as long as it's printable ASCII.

On Mi, Jul 24, 2019 at 11:19 AM, Marc Dufresne via gupnp-list <gupnp-list gnome org> wrote:

Hello,

 

I am trying to use gupnp-av-cp are a test bed between my WD NAS EX2 running Twonky as a MediaServer:1 and my Electrocompaniet EC Living TANA SL1 wireless speaker running the RYGEL MediaRenderer:2

I get this error msg:

** (gupnp-av-cp:17185): WARNING **: 17:27:03.622: Invalid USN: cfe3ba95-5bb6-4404-92b0-ac676f0006d6::urn:schemas-upnp-org:device:MediaRenderer:1

(gupnp-av-cp:17185): gssdp-client-WARNING **: 17:27:04.115: Error sending SSDP packet to 239.255.255.250: Error sending message: Can't assign requested address

(gupnp-av-cp:17185): gssdp-client-WARNING **: 17:27:04.115: Error sending SSDP packet to 239.255.255.250: Error sending message: Can't assign requested address

** (gupnp-av-cp:17185): CRITICAL **: 17:27:58.038: gupnp_device_info_get_udn: assertion 'GUPNP_IS_DEVICE_INFO (info)ÿ failed

The UDN part the USN above is correct, but not the device which should be :2

The main program hard codes the server and renderer with a :1 suffix.

#define MEDIA_RENDERER "urn:schemas-upnp-org:device:MediaRenderer:1"
#define MEDIA_SERVER "urn:schemas-upnp-org:device:MediaServer:1"

uPNP architecture supports 4 types of mediaServers and 3 types of Mediarenderers

I believe that the gupnp-av-cp should be able to adjust itself automatically  to the type of servers and renderers it discovers.

Note that gssdp-discover  will retrieve the complete device description correctly:

resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6::urn:schemas-upnp-org:device:MediaRenderer:2
resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6
resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6::urn:schemas-upnp-org:service:AVTransport:2
resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6::urn:schemas-upnp-org:service:RenderingControl:2
resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6::urn:schemas-upnp-org:service:ConnectionManager:2
resource available
  USN:      cfe3ba95-5bb6-4404-92b0-ac676f0006d6::upnp:rootdevice


the xml descriptor for the device is attached:


It would be great if you could make these changes.

Best regards 

Marc Dufresne
+33 620 30 8788


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]