FAQ  •  Register  •  Login

LG BD-390

<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Dec 03, 2009 8:00 pm

LG BD-390

Alrighty, I just hooked up my LG BD-390. It discoveres Serviio without a hitch, but cannot connect.
It gives a connection error, here's the output form the log:
  Code:
20:55:17,132 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:17,152 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:17,665 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:17,682 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:22,690 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:22,705 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:23,212 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:23,231 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:23,739 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:23,758 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:43,768 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:43,785 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:55,797 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:55,800 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:55:55,818 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:55,821 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:55:56,329 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:56,331 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:55:56,349 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:56,351 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:55:56,864 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:56,867 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:55:56,884 WARN  [EventDispatcher] Error 412 received from event subscriber
20:55:56,887 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:56:04,897 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:04,900 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:56:04,918 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:04,921 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:56:24,931 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:24,934 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:56:24,949 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:24,952 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:56:44,970 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:44,973 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:56:44,989 WARN  [EventDispatcher] Error 412 received from event subscriber
20:56:44,992 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:57:05,002 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:05,005 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:57:05,021 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:05,024 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:57:25,034 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:25,037 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:57:25,057 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:25,060 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:57:45,072 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:45,075 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:57:45,092 WARN  [EventDispatcher] Error 412 received from event subscriber
20:57:45,095 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:58:05,104 WARN  [EventDispatcher] Error 412 received from event subscriber
20:58:05,107 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:58:05,127 WARN  [EventDispatcher] Error 412 received from event subscriber
20:58:05,130 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires
20:58:25,143 WARN  [EventDispatcher] Error 412 received from event subscriber
20:58:25,146 WARN  [EventDispatcher] Couldn't send event message for subscription f7c1695c-cfa8-4012-8ceb-29d1101ee7e5, will try until subscription expires
20:58:25,164 WARN  [EventDispatcher] Error 412 received from event subscriber
20:58:25,167 WARN  [EventDispatcher] Couldn't send event message for subscription a2f0ddfe-7f5e-44e2-b17c-5acb7fcd1fda, will try until subscription expires

I tried to connect a few times - no difference.
I didn't set up a profile because I don't know the SQL commands yet ;)
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Thu Dec 03, 2009 8:04 pm

Re: LG BD-390

There are some fixes in the upcoming 0.3 that might fix this. For profile you don't need any SQL, they are stored in XML file.
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Dec 03, 2009 8:13 pm

Re: LG BD-390

Geebus, do you ever sleep? ;)
Aight. Am I right guessin' the profiles won't fix a discovery error?
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Thu Dec 03, 2009 8:19 pm

Re: LG BD-390

I'm on UK time ;-)

Yes, profile are there for resource retrieval, media mime-types, subtitle support etc. Discovery should be generic for all devices (following UPnP spec).
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Dec 03, 2009 8:36 pm

Re: LG BD-390

I just fired up serviio on my windows boxen, disabled any lingering firewalls and checked a couple of times - it only showed up on the LG once. I couldn't connect. Now it's gone. No joy. But that might have to do with Win7 x64 :(

I'll try to up the loglevel on my NAS and see if I can squeeze mor out of it.


edit:
alrighty, here goes the debug output....

btw 192.168.1.129 is my LG BD-390, .1.114 is my windows boxen. No clue what it ponders on uPNp *sigh*

  Code:
21:45:21,940 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:24,933 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:28,362 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:31,060 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:33,988 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:37,106 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:InternetGatewayDevice:1 from address /192.168.1.114:63183
21:45:46,129 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:48607
21:45:46,408 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:48607
21:45:46,548 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:48607
21:45:47,103 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:45:47,103 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:45:47,104 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:45:48,637 DEBUG [WebServer] Incoming connection from /192.168.1.129:51202
21:45:48,637 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 2c34c28c-6c25-3641-9736-66b299635fe4 from Linux/2.6.24.7.0909171-REL UPnP/1.0 DLNADOC/1.50 INTEL_NMPR/2.0 LG_DLNA_SDK/1.5.0
21:45:48,642 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Generic DLNA profile'
21:45:48,798 DEBUG [WebServer] Incoming connection from /192.168.1.129:51203
21:45:49,122 DEBUG [ServiceDescriptionRequestHandler] ServiceDescription request received for service ConnectionManager
21:45:49,128 DEBUG [ServiceDescriptionRequestHandler] Sending ServiceDescription XML back
21:45:49,413 DEBUG [WebServer] Incoming connection from /192.168.1.129:51204
21:45:49,697 DEBUG [ServiceDescriptionRequestHandler] ServiceDescription request received for service ContentDirectory
21:45:50,020 DEBUG [ServiceDescriptionRequestHandler] Sending ServiceDescription XML back
21:45:58,394 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:44829
21:45:58,394 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:45:58,495 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:44829
21:45:58,496 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:45:58,596 DEBUG [DiscoverySearchListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.129:44829
21:45:58,597 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s)
21:46:02,825 DEBUG [WebServer] Incoming connection from /192.168.1.129:51219
21:46:02,825 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 2c34c28c-6c25-3641-9736-66b299635fe4 from Linux/2.6.24.7.0909171-REL UPnP/1.0 DLNADOC/1.50 INTEL_NMPR/2.0 LG_DLNA_SDK/1.5.0
21:46:02,827 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Generic DLNA profile'
21:46:02,840 DEBUG [WebServer] Incoming connection from /192.168.1.129:51220
21:46:02,840 DEBUG [ServiceDescriptionRequestHandler] ServiceDescription request received for service ConnectionManager
21:46:02,841 DEBUG [ServiceDescriptionRequestHandler] Sending ServiceDescription XML back
21:46:02,867 DEBUG [WebServer] Incoming connection from /192.168.1.129:51221
21:46:02,869 DEBUG [ServiceDescriptionRequestHandler] ServiceDescription request received for service ContentDirectory
21:46:02,870 DEBUG [ServiceDescriptionRequestHandler] Sending ServiceDescription XML back
21:46:11,125 DEBUG [WebServer] Incoming connection from /192.168.1.129:51222
21:46:11,125 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ConnectionManager
21:46:11,125 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription registered (uuid=f3e39be7-e865-478e-aafd-0368474ab074) for service urn:upnp-org:serviceId:ConnectionManager reporting to http://192.168.1.129:45618/
21:46:11,184 DEBUG [WebServer] Incoming connection from /192.168.1.129:51223
21:46:11,184 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ContentDirectory
21:46:11,185 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription registered (uuid=c46ab9c2-2e19-4cdd-aa13-23573152e64f) for service urn:upnp-org:serviceId:ContentDirectory reporting to http://192.168.1.129:45618/
21:46:11,603 DEBUG [EventDispatcher] Sending event notification #0 for subscription c46ab9c2-2e19-4cdd-aa13-23573152e64f
21:46:11,607 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:11,618 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:11,618 DEBUG [EventDispatcher] Sending event notification #3 for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5
21:46:11,618 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:11,621 WARN  [EventDispatcher] Couldn't send event message for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5, will try until subscription expires
21:46:11,621 DEBUG [EventDispatcher] Sending event notification #0 for subscription f3e39be7-e865-478e-aafd-0368474ab074
21:46:11,622 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:11,639 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:11,639 DEBUG [EventDispatcher] Sending event notification #3 for subscription 9f98a601-9a1a-4001-958d-56b10379961a
21:46:11,639 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:11,641 WARN  [EventDispatcher] Couldn't send event message for subscription 9f98a601-9a1a-4001-958d-56b10379961a, will try until subscription expires
21:46:11,709 DEBUG [WebServer] Incoming connection from /192.168.1.129:51224
21:46:11,709 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ConnectionManager
21:46:11,710 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=f3e39be7-e865-478e-aafd-0368474ab074) for service urn:upnp-org:serviceId:ConnectionManager reporting to http://192.168.1.129:45618/
21:46:11,717 DEBUG [WebServer] Incoming connection from /192.168.1.129:51225
21:46:11,717 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ContentDirectory
21:46:11,717 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=c46ab9c2-2e19-4cdd-aa13-23573152e64f) for service urn:upnp-org:serviceId:ContentDirectory reporting to http://192.168.1.129:45618/
21:46:12,142 DEBUG [EventDispatcher] Sending event notification #1 for subscription c46ab9c2-2e19-4cdd-aa13-23573152e64f
21:46:12,142 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:12,149 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:12,149 DEBUG [EventDispatcher] Sending event notification #3 for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5
21:46:12,150 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:12,152 WARN  [EventDispatcher] Couldn't send event message for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5, will try until subscription expires
21:46:12,152 DEBUG [EventDispatcher] Sending event notification #1 for subscription f3e39be7-e865-478e-aafd-0368474ab074
21:46:12,153 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:12,170 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:12,170 DEBUG [EventDispatcher] Sending event notification #3 for subscription 9f98a601-9a1a-4001-958d-56b10379961a
21:46:12,171 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:12,173 WARN  [EventDispatcher] Couldn't send event message for subscription 9f98a601-9a1a-4001-958d-56b10379961a, will try until subscription expires
21:46:12,223 DEBUG [WebServer] Incoming connection from /192.168.1.129:51226
21:46:12,224 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ConnectionManager
21:46:12,224 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=f3e39be7-e865-478e-aafd-0368474ab074) for service urn:upnp-org:serviceId:ConnectionManager reporting to http://192.168.1.129:45618/
21:46:12,229 DEBUG [WebServer] Incoming connection from /192.168.1.129:51227
21:46:12,230 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ContentDirectory
21:46:12,230 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=c46ab9c2-2e19-4cdd-aa13-23573152e64f) for service urn:upnp-org:serviceId:ContentDirectory reporting to http://192.168.1.129:45618/
21:46:12,673 DEBUG [EventDispatcher] Sending event notification #2 for subscription c46ab9c2-2e19-4cdd-aa13-23573152e64f
21:46:12,674 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:12,682 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:12,682 DEBUG [EventDispatcher] Sending event notification #3 for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5
21:46:12,682 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:12,685 WARN  [EventDispatcher] Couldn't send event message for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5, will try until subscription expires
21:46:12,685 DEBUG [EventDispatcher] Sending event notification #2 for subscription f3e39be7-e865-478e-aafd-0368474ab074
21:46:12,686 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:12,702 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:12,702 DEBUG [EventDispatcher] Sending event notification #3 for subscription 9f98a601-9a1a-4001-958d-56b10379961a
21:46:12,702 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:12,711 WARN  [EventDispatcher] Couldn't send event message for subscription 9f98a601-9a1a-4001-958d-56b10379961a, will try until subscription expires
21:46:18,701 DEBUG [WebServer] Incoming connection from /192.168.1.129:51228
21:46:18,702 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ConnectionManager
21:46:18,702 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=f3e39be7-e865-478e-aafd-0368474ab074) for service urn:upnp-org:serviceId:ConnectionManager reporting to http://192.168.1.129:45618/
21:46:18,707 DEBUG [WebServer] Incoming connection from /192.168.1.129:51229
21:46:18,708 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent subscription request received for service ContentDirectory
21:46:18,708 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription reused (uuid=c46ab9c2-2e19-4cdd-aa13-23573152e64f) for service urn:upnp-org:serviceId:ContentDirectory reporting to http://192.168.1.129:45618/
21:46:18,712 DEBUG [EventDispatcher] Sending event notification #3 for subscription c46ab9c2-2e19-4cdd-aa13-23573152e64f
21:46:18,713 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:18,720 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:18,720 DEBUG [EventDispatcher] Sending event notification #3 for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5
21:46:18,721 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:18,723 WARN  [EventDispatcher] Couldn't send event message for subscription dfb8bb80-624d-4b6f-8e78-65bbd3aec4e5, will try until subscription expires
21:46:18,723 DEBUG [EventDispatcher] Sending event notification #3 for subscription f3e39be7-e865-478e-aafd-0368474ab074
21:46:18,724 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:45618
21:46:18,740 WARN  [EventDispatcher] Error 412 received from event subscriber
21:46:18,740 DEBUG [EventDispatcher] Sending event notification #3 for subscription 9f98a601-9a1a-4001-958d-56b10379961a
21:46:18,741 DEBUG [RequestExecutor] Sending HTTP request to 192.168.1.129:40873
21:46:18,743 WARN  [EventDispatcher] Couldn't send event message for subscription 9f98a601-9a1a-4001-958d-56b10379961a, will try until subscription expires
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Sat Dec 05, 2009 1:42 pm

Re: LG BD-390

Ok, so I did some packet sniffing to find out why ushare, mediatomb, etc work so nice while serviio doesn't. I might have learned a thing or two about UPnP, too. ;)

Here's the UPnP response of the LG BD-390:
  Code:
DGET /description.xml HTTP/1.1
HOST: 192.168.1.2:49152
DATE: Wed, 11 Jun 2008 00:00:19 GMT
USER-AGENT: Linux/2.6.24.7.0909171-REL UPnP/1.0 DLNADOC/1.50 INTEL_NMPR/2.0 LG_DLNA_SDK/1.5.0
friendlyName.dlna.org: BD300


I captured a connection establishment with uShare that worked, and a failed attempt with Serviio on the same box.
The XML that's being transmitted looks fine to me.
However, there is a HTTP/200 being sent from serviio to the BD-390, followed by a TCP/port unreachable message from the BD-390 to Serviio.
That's the payload:
  Code:
HTTP/1.1 200 OK
CACHE-CONTROL: max-age = 1800
LOCATION: http://192.168.1.2:8895/deviceDescription/2c34c28c-6c25-3641-9736-66b299635fe4
EXT:
DATE: Sat, 05 Dec 2009 13:40:35 CET
SERVER: Linux UPnP/1.0 Serviio 0.2
ST: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:2c34c28c-6c25-3641-9736-66b299635fe4::urn:schemas-upnp-org:device:MediaServer:1


192.168.1.2 being serviio's IP. The source port is 1900, the destination port is 59124. After one retry, the destination port is changed to 47396, which then seems to work.
Don't know if thats ok, but it seems worth noting.

When the BD-390 wants to subscribe to Serviio this takes place:
  Code:
<?xml version="1.0"?>
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<SystemUpdateID>7</SystemUpdateID>
</e:property>
</e:propertyset>


Then the BD-390 replies with:
  Code:
HTTP/1.1 412 Precondition Failed
SERVER: Linux/2.6.24.7.0909171-REL UPnP/1.0 DLNADOC/1.50 INTEL_NMPR/2.0 LG_DLNA_SDK/1.5.0
CONNECTION: close
CONTENT-LENGTH: 58
CONTENT-TYPE: text/html

<html><body><h1>412 Precondition Failed</h1></body></html>

This certainly doesn't happen with uShare.

Serviio marches on:
  Code:
<?xml version="1.0"?>
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<SinkProtocolInfo></SinkProtocolInfo>
</e:property>
<e:property>
<SourceProtocolInfo>http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVHIGH_FULL;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-ms-wmv:*,http-get:*:video/x-ms-asf:DLNA.ORG_PN=VC1_ASF_AP_L2_WMA;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_SD_AC3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/x-ms-wma:*,http-get:*:video/mp4:DLNA.ORG_PN=MPEG4_P2_MP4_ASP_AAC;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_MP_HD_720p_AAC;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_SD_MPEG1_L3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_SD_AAC_MULT5;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-mkv:DLNA.ORG_PN=MATROSKA;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_SM;DLNA.ORG_OP=00;DLNA.ORG_FLAGS=00D00000000000000000000000000000,http-get:*:audio/L16;rate=44100;channels=1:DLNA.ORG_PN=LPCM;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:image/jpeg:*,http-get:*:audio/L16;rate=48000;channels=1:*,http-get:*:audio/mp3:*,http-get:*:audio/L16;rate=44100;channels=2:*,http-get:*:audio/L16;rate=48000;channels=2:DLNA.ORG_PN=LPCM;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMA_BASE;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_TN;DLNA.ORG_OP=00;DLNA.ORG_FLAGS=00D00000000000000000000000000000,http-get:*:video/divx:DLNA.ORG_PN=AVI;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-ms-asf:DLNA.ORG_PN=VC1_ASF_AP_L1_WMA;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_MED;DLNA.ORG_OP=00;DLNA.ORG_FLAGS=00D00000000000000000000000000000,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_MP_SD_MPEG1_L3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVMED_FULL;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-ms-asf:DLNA.ORG_PN=VC1_ASF_AP_L3_WMA;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/L16;rate=44100;channels=1:*,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_HD_AAC_MULT5;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_HD_AC3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http.c-get:*:video/vnd.dlna.mpeg-tts:*,http-get:*:audio/L16;rate=44100;channels=2:DLNA.ORG_PN=LPCM;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG1;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mpeg:*,http-get:*:video/x-msvideo:DLNA.ORG_PN=AVI;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/avi:*,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_MP_HD_1080i_AAC;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_HP_HD_AAC;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVMED_BASE;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_PS_PAL;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/x-matroska:DLNA.ORG_PN=MATROSKA;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/L16;rate=48000;channels=1:DLNA.ORG_PN=LPCM;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_LRG;DLNA.ORG_OP=00;DLNA.ORG_FLAGS=00D00000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_EU;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/mp3:DLNA.ORG_PN=MP3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:vide.co/mp4:*,http-get:*:video/x-matroska:*,http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMA_FULL;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=AVC_TS_MP_HD_MPEG1_L3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_MP_SD_AAC_MULT5;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000,http-get:*:audio/L16;rate=48000;channels=2:*,http-get:*:video/mp4:DLNA.ORG_PN=AVC_MP4_MP_SD_AC3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000</SourceProtocolInfo>
</e:property>
<e:property>
<CurrentConnectionIDs>0</CurrentConnectionIDs>
</e:property>
</e:propertyset>


The BD-390 gives error 412 again:
  Code:
HTTP/1.1 412 Precondition Failed
SERVER: Linux/2.6.24.7.0909171-REL UPnP/1.0 DLNADOC/1.50 INTEL_NMPR/2.0 LG_DLNA_SDK/1.5.0
CONNECTION: close
CONTENT-LENGTH: 58
CONTENT-TYPE: text/html

<html><body><h1>412 Precondition Failed</h1></body></html>


The above steps are repeated a few times, but it's always the same.

edit:
And as the upnp specification suggests, the reason might actually be an unknown uuid.
I've got two uuids from serviio. It seems the uuid changes after the BD-390 subscribes with the callback. The callback has a different uuid, hence the 412.

And as I am a total noob to UPnP, this may all very well be mumbo-jumbo too. So take it with a big grain of salt, obviously. ;) :D
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Sun Dec 06, 2009 1:45 am

Re: LG BD-390

<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Sun Dec 06, 2009 3:35 pm

Re: LG BD-390

Actually, when the event subscription comes Serviio generates the UUID and sends it back with the event that has been subscribed. So at this point it's the first time your device comes across this UUID, hence it cannot be missing. There is a differnet problem. There were a couple of bugs issued against the http header names andformat of date which might cause this error.

I'll PM you with a beta to test if it's ok ;-)
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Sun Dec 06, 2009 9:01 pm

Re: LG BD-390

Just to confirm again, the beta you sent me works with the LG BD390. :)
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Sun Dec 06, 2009 9:06 pm

Re: LG BD-390

nice one, this one was hard to get to work...
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Mon Jan 11, 2010 7:01 pm

Re: LG BD-390

0.3.1 still works nicely, but now I'm pretty sure some features don't work as expected, probably due to the DLNA-client.

The contents of "last viewed" are always empty, and the episode watched indicator on TV series never showed in 0.3.1.
When I use my N810's builtin UPNP client, the videos don't show up in "last viewed" either.

I think it counts as "viewed" as soon as streaming is started, right?


edit:
scratch that, the N810's browser does silly caching. It showed the TV episode under "last viewed" just fine after an application restart.
So it's down to the BD390 once again. :x
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Mon Jan 11, 2010 7:20 pm

Re: LG BD-390

This works on my Samsung and XBox (Last viewed and Series indicator) - can you post log (with DEBUG) when you attempt to browse to the Last Viewed folder?
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Tue Feb 23, 2010 8:57 pm

Re: LG BD-390

*bumpidy*

Ok, so just to make sure I'm still on track with this...
Is last viewed a per-client feature? Because when I play stuff on my N810 I see it in last viewed on my N810. I should see it in last viewed on my BD390 too, right?

What exactly do you need to amend this? :?
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Tue Feb 23, 2010 9:32 pm

Re: LG BD-390

No, it's not on per-client basis. So you should see it. Is the folder completely empty? Do you see any errors in the log?
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Feb 25, 2010 4:44 pm

Re: LG BD-390

Not recently. But I had to tune down the logging because it filled up my disk a couple of times. :?

I can see the contents in my BD390 when I watch stuff on my N810. So the problem really is that content watched on the BD390 doesn't get recognized as "watched"?
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Thu Feb 25, 2010 5:04 pm

Re: LG BD-390

Yes, that could be the problem. It's quite difficult to recognize when an asset is watched, because some devices send many requests for the same asset (byte range for example), some only 1. So the counter of number the asset has been watched is not that precise across devices.

Your player probably only issues requests with Range header which are ignored by the 'mark as viewed' functionality. I'll see if I can figure out some better way of doing this.
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Feb 25, 2010 5:14 pm

Re: LG BD-390

Ok. What can I do to verify this is the case?
Or can I find out exactly what kind of requests the player is sending when I access a content item?
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

zip

User avatar

Serviio developer / Site Admin

Posts: 17215

Joined: Sat Oct 24, 2009 12:24 pm

Location: London, UK

Post Thu Feb 25, 2010 5:31 pm

Re: LG BD-390

You can see the HTTP headers when you enable debug logging. It will look something like GET /xxxxxxx HTTP1.1 [header1=yyy, header2=yyyy]. Some devices also send HEAD requests first, but those are not considerer for marking the content as read.
<<

fizze

Serviio lover

Posts: 88

Joined: Wed Dec 02, 2009 8:27 am

Location: Austria

Post Thu Feb 25, 2010 5:33 pm

Re: LG BD-390

Alrighty, I'll try to get you a nice log, then. :)
Intel SS4200 - Ubuntu Server 8.04
LG BD - 390
<<

sdt1

Streaming enthusiast

Posts: 25

Joined: Thu Feb 25, 2010 11:25 pm

Post Thu Feb 25, 2010 11:34 pm

Re: LG BD-390

Hello @Petr. I am so happy to have found Serviio! I too, have an LG BD-390, and have had nothing but trouble with all other media server software written for Mac (e.g., Playback, EyeConnect, Majestic, Rivet, Wild Media, MediaLink, etc.). Serviio seems to play the best with the LG BD-390 running ver. 0.3.1. I am seeing one niggle, however, and wondering if there is a fix? The niggle is that when a file comes to an end playing, the BD-390 kicks out a "network error" message, rather than returning to the folder tree. Sometimes, it even displays a endless spinning wheel. In the first case, I have to refresh the server list on the BD-390, and reconnect to the folder tree; in the latter case, I have to power (force quit) the BD-390 and start over. If I can provide you with debug data, let me know how, and I will be happy to do so. If there is a beta that addresses this issue with this device, that would be great. Keep up the great work! Cheers.
Next

Return to User experiences

Who is online

Users browsing this forum: No registered users and 15 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.