home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Unable to watch live TV Mediaplayer 2.1 Final
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1224806" data-attributes="member: 82144"><p>I'm not sure why you're asking me! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p></p><p>I suggest you check the UPnP specs:</p><p><a href="http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf" target="_blank">http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf</a></p><p><a href="http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf" target="_blank">http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf</a></p><p></p><p>Read section "1.2.2 Device available - NOTIFY with ssdp:alive". It explicitly describes each header.</p><p></p><p>The way I read the specs:</p><ul> <li data-xf-list-type="ul">none of the 3 headers are defined for UPnP 1.0<br /> </li> <li data-xf-list-type="ul">bootid.upnp.org and configid.upnp.org are required/mandatory for UPnP 1.1</li> <li data-xf-list-type="ul">searchport.upnp.org is optional for UPnP 1.1</li> </ul><p>Therefore if a device claims to be UPnP <strong>1.0</strong> compliant, MP2's library should not attempt to parse those headers. I think that part is already done correctly.</p><p>The problem is that this particular device seems to claim to be UPnP <strong>1.1</strong> compliant ("SERVER: POSIX/1.0 UPnP/<strong>1.1</strong> UPnP Stack/v1.00"). Therefore it should at least be providing the bootid and configid headers.</p><p></p><p>That UPnP stack version number seems weird to me though. It's as if the device is trying to claim partial UPnP 1.1 compliance.</p><p></p><p></p><p>In my opinion the library should be as standard-compliant as possible. Based on my interpretation of the standards (I'm not very familiar with them, so I could easily be wrong!) the library should not allow those headers to be null. It would cause difficulty in properly detecting and notifying about configuration changes and device reboots.</p><p></p><p>[edit: I suggest that the person check for software/firmware updates for the device. Maybe they will make it compliant. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite11" alt=":rolleyes:" title="Roll Eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /> ]</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1224806, member: 82144"] I'm not sure why you're asking me! :D I suggest you check the UPnP specs: [URL]http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf[/URL] [URL]http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf[/URL] Read section "1.2.2 Device available - NOTIFY with ssdp:alive". It explicitly describes each header. The way I read the specs: [LIST] [*]none of the 3 headers are defined for UPnP 1.0 [*]bootid.upnp.org and configid.upnp.org are required/mandatory for UPnP 1.1 [*]searchport.upnp.org is optional for UPnP 1.1 [/LIST] Therefore if a device claims to be UPnP [B]1.0[/B] compliant, MP2's library should not attempt to parse those headers. I think that part is already done correctly. The problem is that this particular device seems to claim to be UPnP [B]1.1[/B] compliant ("SERVER: POSIX/1.0 UPnP/[B]1.1[/B] UPnP Stack/v1.00"). Therefore it should at least be providing the bootid and configid headers. That UPnP stack version number seems weird to me though. It's as if the device is trying to claim partial UPnP 1.1 compliance. In my opinion the library should be as standard-compliant as possible. Based on my interpretation of the standards (I'm not very familiar with them, so I could easily be wrong!) the library should not allow those headers to be null. It would cause difficulty in properly detecting and notifying about configuration changes and device reboots. [edit: I suggest that the person check for software/firmware updates for the device. Maybe they will make it compliant. :rolleyes: ] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Unable to watch live TV Mediaplayer 2.1 Final
Contact us
RSS
Top
Bottom
