[ https://issues.apache.org/jira/browse/FELIX-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613220#action_12613220 ]
Stefano Lenzi commented on FELIX-630: ------------------------------------- So the problem seems to be related to the CyberDomo stack that the base driver uses. I will check your patch and later I will update the CyberDomo stack. > The UPnP base driver does not conform to the UPnP spec, and thus will not > work with some devices > ------------------------------------------------------------------------------------------------ > > Key: FELIX-630 > URL: https://issues.apache.org/jira/browse/FELIX-630 > Project: Felix > Issue Type: Bug > Components: UPnP Subproject > Environment: Windows/Linux/MacOS > Reporter: Bruce Jackson > Assignee: Stefano Lenzi > Attachments: Device.java > > > The underlying Cyberlink code in the UPnP base driver does not respond > correctly to all Discover: Search with M-SEARCH searches. > The UPnP specification (UPnP Device Architecture 1.0) page 21 states that a > device should respond to an M-SEARCH message with ST set to urn:device-UUID > with a response which must also be urn:device-UUID. > The Cyberlink driver actually responds by appending ::upnp:rootdevice to the > ST header, breaking compatibility with some devices (notably, the Xbox 360). > This can be fixed by commenting out the append in Device.java, line 1428, as > shown below: > // MLC 10-Jul-08 > // if (isRootDevice == true) > // devUSN += "::" + USN.ROOTDEVICE; > However, this still leaves the case of a response to an M-SEARCH where the ST > is set to upnp:rootdevice, as this does not appear to be handled by the base > driver at all at present. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.