Topic: UPnP for Media Receivers (Read 10080 times)

John Gateley · « **on:** January 12, 2005, 05:12:19 pm »

UPnP v1.0.4 is now ready. This should still be considered an alpha. It is in build 11.0.173

j

syserror · « **Reply #1 on:** January 12, 2005, 07:36:23 pm »

NOTIFYs being sent now (5 of them - root, GUID, MediaServer, ConnectionManager, ContentDirectory). NOTIFY format not recognized by SMC or Intel though. One of NOTIFY's:

NOTIFY * HTTP/1.1
Connection: close
Server: JRiver UPnP 1.0
Cache-Control: 1800
Nt: urn:schemas-upnp-org:service:ContentDirectory:1
Host: 239.255.255.250:1900
Content-Length: 0
Nts: ssdp:alive
Usn: uuid:uuid:3E027E3A-AE14-4C9B-931C-4254240ECDEA::urn:schemas-upnp-org:service:ContentDirectory:1
Date: Thu, 13 Feb 2005 01:28:13 GMT
Location: http://192.168.3.150:0/DeviceDescription.xml

Spec format:

NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age = seconds until advertisement expires
LOCATION: URL for UPnP description for root device
NT: search target
NTS: ssdp:alive
SERVER: OS/version UPnP/1.0 product/version
USN: advertisement UUID

Need upper case, 'max-age' in cache control header, 'UPnP/1.0' in server header, possibly dupe uuid in usn header.

syserror · « **Reply #2 on:** January 12, 2005, 07:42:48 pm »

Haven't tried M-SEARCH with root or MediaServer yet. Response on ContentDirectory seems consistent now though. Format still not recognized by SMC or Intel. M-SEARCH response:

HTTP/1.1 200 OK
EXT:
DATE: Thu, 13 Feb 2005 01:37:39 GMT
ST: urn:schemas-upnp-org:service:ContentDirectory:1
CACHE-CONTROL: maxage=1800
CONNECTION: close
MYNAME: offsite1 (Media Center)
USN: uuid:uuid:3E027E3A-AE14-4C9B-931C-4254240ECDEA::urn:schemas-upnp-org:service:ContentDirectory:1
LOCATION: http://192.168.3.150:1278/DeviceDescription.xml
SERVER: JRiver UPnP 1.0
Content-Length: 0

Spec format:

HTTP/1.1 200 OK
CACHE-CONTROL: max-age = seconds until advertisement expires
DATE: when response was generated
EXT:
LOCATION: URL for UPnP description for root device
SERVER: OS/version UPnP/1.0 product/version
ST: search target
USN: advertisement UUID

Case good, need 'max-age' in cache control header, 'UPnP/1.0' in server header. Date format appears RFC1123 compliant, but 2/13/05 is definitely wrong (my time is set correctly).

bshock · « **Reply #3 on:** January 12, 2005, 10:52:08 pm »

It looks like we're getting closer. Here's my UPnP plug-in console dump:

01/12/05 23:49:11 - Starting...
01/12/05 23:49:12 - Running
01/12/05 23:49:29 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::upnp:rootdevice
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::upnp:rootdevice
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:device:MediaRenderer:1
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:device:MediaRenderer:1
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:RenderingControl:1
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:RenderingControl:1
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:ConnectionManager:1
01/12/05 23:49:30 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:ConnectionManager:1
01/12/05 23:49:31 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:AVTransport:1
01/12/05 23:49:31 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:Omnifi-DMS1-000000000000001460503562-1000000449-29::urn:schemas-upnp-org:service:AVTransport:1

Valisystem · « **Reply #4 on:** January 13, 2005, 12:40:48 am »

I'm not quite there yet. I've now got a Netgear MP101 running over a wireless connection. It works fine with the Netgear media server, installed on a different computer than MC. When I'm testing, I shut down that second computer to make sure the Netgear server is not interfering, then restart MC and power cycle the MP101.

With the previous version of the MC UPNP server, the MP101 could not find the MC server and there was no indication in MC that there were any inquiries.

With today's build, the Netgear can find the MC UPNP server and shows, Connecting, followed by, Failed to connect. I think this is the portion of the MC log that applies:

01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:58D4430E-A340-4361-8857-580823A60569::upnp:rootdevice
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: uuid:58D4430E-A340-4361-8857-580823A60569, USN: uuid:58D4430E-A340-4361-8857-580823A60569
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaServer:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:device:MediaServer:1
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ContentDirectory:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:service:ContentDirectory:1
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:service:ConnectionManager:1
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:58D4430E-A340-4361-8857-580823A60569::upnp:rootdevice
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: uuid:58D4430E-A340-4361-8857-580823A60569, USN: uuid:58D4430E-A340-4361-8857-580823A60569
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaServer:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:device:MediaServer:1
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ContentDirectory:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:service:ContentDirectory:1
01/12/05 21:18:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:58D4430E-A340-4361-8857-580823A60569::urn:schemas-upnp-org:service:ConnectionManager:1

For what it's worth, MC is also generating "Unknown SSDP server method: NOTIFY" messages about every 45 seconds or so relating to a network color laser printer.

Also for what it's worth, my home network is running Small Business Server 2003. I think someone else with problems also mentioned that. I have no idea why that would matter - this traffic shouldn't go near the server. Windows Firewall is partially controlled by group policy from the server, but UPNP Framework is open on TCP 2869 and UDP 1900.

When I can, I'll bring the MP101 up here and see if it connects over a wired connection. . .

John Gateley · « **Reply #5 on:** January 13, 2005, 09:46:48 am »

Syserror - thanks. I made all the changes you suggested, and they'll be out in the next buiild (any minute now).

We have to argue about the header case though

. If I remember right, HTTP headers MUST be case insensitive and SHOULD be lower case with the first letter of each word capitalized. I didn't check the RFC to verify. The Intel UPnP book shows most headers following the first letter capital format except for the UPnP headers which are all upper.

If it still doesn't work with the SMC, can you get me a sniff of the SMC with a working server?

j

John Gateley · « **Reply #6 on:** January 13, 2005, 09:49:02 am »

bshock - we're not too close

The OmniFi is behaving quite differently than the MP101, so I'm not sure what is going on. It should work, it just wont be the next day or two.

j

John Gateley · « **Reply #7 on:** January 13, 2005, 09:57:12 am »

Valisystem,

The UPnP Server will not report unknown NOTIFY's for it's own NOTIFY messages. You are still getting unknown NOTIFY messages. To make sure they are not from the JRiver UPnP server, use regedit and look at the key:

HKEY_LOCAL_MACHINE\SOFTWARE\JRiver\Media Center 11\Plugins\Interface\UPnP Server
and look for "Media Center UUID" (there will be two very similar, the other is "Media CenterUUID").

Make sure that the UUID string in the registry is different from the UUID string in the unknown NOTIFY message.

If they are the same, it's a bug in my code. If they are different, you still have a different UPnP server running on the same machine. I'm not sure this should be a problem, but it's something I haven't tested.

If the MP101 is connecting to JRiver's UPnP server, you should see the following messages:

date - Received request for device description
date - Soap Message: Browse BrowseDirectChildren 0

Are you getting these?

j

Oh yeah - don't worry about the laser printer NOTIFYs. It's just an informational message

syserror · « **Reply #8 on:** January 13, 2005, 10:17:11 am »

Quote from: John Gateley on January 13, 2005, 09:46:48 am

We have to argue about the header case though . If I remember right, HTTP headers MUST be case insensitive and SHOULD be lower case with the first letter of each word capitalized. I didn't check the RFC to verify. The Intel UPnP book shows most headers following the first letter capital format except for the UPnP headers which are all upper.

You are correct about true HTTP. I'm not fond of it either, but UPnP SSDP took HTTP-ish headers and added the case sensitivity on the headers they specify.

Thanks for the quick build. Date and UPnP/1.0 look clean, dupe uuid is out. Intel device sniffer at least can now identify what type of NOTIFY packet it is (with .173 it considered them unknown). Intel SDK AV Media Controller and SMC EZ-Stream still don't accept the NOTIFY or response though; ie., neither fetch the device description.

Only thing off hand that looks wrong in the headers is maxage without hyphen. I'm pretty confident at this point that if you can get MC working with the Intel AV Media Controller SW that the SMC will accept it as well.

SSDP NOTIFY for ContentDirectory from Intel AV Media Server (which SMC recognizes - immediately fetches its device description after seeing this):

NOTIFY * HTTP/1.1
LOCATION: http://192.168.0.1:61464/
HOST: 239.255.255.250:1900
SERVER: Windows NT/5.0, UPnP/1.0, Intel CLR SDK/1.0
NTS: ssdp:alive
USN: uuid:9fc50a32-2c28-4fd2-88a7-cfdf9dbbb78b::urn:schemas-upnp-org:service:ContentDirectory:1
CACHE-CONTROL: max-age=1800
NT: urn:schemas-upnp-org:service:ContentDirectory:1
Content-Length: 0

Aaron

MartinD · « **Reply #9 on:** January 13, 2005, 10:28:13 am »

Hi,

I've just tested build .174 with Terratec's Noxon: Server log:

01/13/05 17:22:30 - Starting...
01/13/05 17:22:30 - Running
01/13/05 17:25:05 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/13/05 17:25:06 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/13/05 17:25:06 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/13/05 17:25:07 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/13/05 17:25:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 17:25:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 17:25:08 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 17:25:08 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 17:25:08 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 17:25:09 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 17:25:10 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 17:25:10 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 17:25:11 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
01/13/05 17:25:11 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1

-Martin

John Gateley · « **Reply #10 on:** January 13, 2005, 10:41:40 am »

Oops on the maxage. I fixed it, you can get the latest at:

http://www.jriver.com/~gateley/server_upnp.mjp

Hope this works with the SMC now...

j

xerodiac · « **Reply #11 on:** January 13, 2005, 04:43:37 pm »

In case this means something you..

01/13/05 23:43:37 - Starting...
01/13/05 23:43:37 - Running
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 23:44:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 23:44:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 23:44:38 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 23:44:39 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:AVTransport:1
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:device:MediaRenderer:1
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:RenderingControl:1
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:ConnectionManager:1
01/13/05 23:44:40 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe004fce::urn:schemas-upnp-org:service:AVTransport:1

...that's what the plug-in says if I let my Streamium SL400i search for UPnP media servers. It won't find the MC server though.

John Gateley · « **Reply #12 on:** January 13, 2005, 05:21:59 pm »

Quote from: xerodiac on January 13, 2005, 04:43:37 pm

In case this means something you..

01/13/05 23:44:36 - ...FEEDBABE-5AFE-F00D-0090-3efffe004fce::upnp:rootdevice...

that's what the plug-in says if I let my Streamium SL400i search for UPnP media servers. It won't find the MC server though.

It means someone has a sense of humor, and is not very careful about generating unique IDs

Actually it just means that the Streamium is a MediaRenderer which I don't handle yet, but will soon.

j

Valisystem · « **Reply #13 on:** January 13, 2005, 08:06:30 pm »

Yowzah! The MP101 is up and running.

First - I had installed MC 11.0.173 yesterday. In the registry just now the version number for the UPNP plugin was 1.0.3. I clicked on the link in this thread and now it's at 1.0.4. Maybe I hadn't gotten the latest version of the plugin with MC 11.0.173, eh?

Second - you're right - the UUID I was seeing was NOT the MC server. Apparently one of my other computers was still running some remnant of the Netgear or MusicMatch software I've experimented with recently - not the MC computer but another one on the network, I think. I shut down all the computers but MC; the errant Unknown SSDP Server messages stopped turning up and the MP101 connected up to MC immediately and started generating Soap Messages and working quite nicely.

I'll go scrub the others of all references to other possible UPNP servers and see what happens. Thanks!

syserror · « **Reply #14 on:** January 13, 2005, 09:02:46 pm »

With new code from your link, I saw a request for device description in log - had to be from the SMC so it must accept the SSDP now.

Only RDPing to PC right now, will be able to try really using it soon though.

John Gateley · « **Reply #15 on:** January 13, 2005, 09:12:49 pm »

Valisystem, Syserror: COOL!

Anyone else install 11.0.173 and not have the UPnP plugin upgrade to 1.0.4? Valisystem - is it possible you installed 10.0.173? The titles could be confusing.

Also, after thinking about it, in spite of the other UPnP server, it still should have worked ok. The MP101 should have reported 2 servers found, and given you the choice. The JRiver server should have worked. I'll have to try this, but in the meantime any more info you can give me would be great.

j

syserror · « **Reply #16 on:** January 13, 2005, 09:20:35 pm »

Some more info:

1) SMC is finding the device, gets device description and lists my computer name with "Media Center" as an available server.

2) Intel AV tools are actually more finicky than SMC; they get device description but then try to get scpd.xml too so fail to find MC. Not an issue unless real devices need the service description.

3) SMC appears to time-out servers quicker than the MC SSDP NOTIFY period - it periodically drops MC from its list then rediscovers it sometime later. Don't know the exact period.

4) Unfortunately, SMC doesn't get any further since actually Browse'ing MC doesn't work. At first glance this looks like an SMC bug instead of MC though. Will get some details for email since packet caps will get kind of ugly.

Aaron

Valisystem · « **Reply #17 on:** January 13, 2005, 11:41:56 pm »

Re: versions. It was an odd sequence, which I believe involved v.11 at all times. (I think. Really, I try to be careful and I think I've had my hands on v.11 each time. Honest. But I'm installing straight from the forum link and not saving a local copy, so I can't quite be absolutely sure.)

For no particular reason, I had uninstalled the UPNP plugin from 11.0.168. I installed 11.0.173 on top of .168, but there was no UPNP plugin after the new build was in - just library server and Tivo server. I scratched my head, uninstalled MC, immediately reinstalled it. There was the UPNP plugin, I turned it on and experimented with the MP101 last night. Today when I checked, the registry showed 1.0.3 as the version number for the UPNP plugin. If that's an impossible sequence then I'm perfectly willing to believe something else happened that I should have noticed, like installing the wrong MC version or something.

Re: conflict with Netgear Media Server.

Prior to last night, with MC 11.0.168, I got no indication from the MP101 or from MC that the MC server existed, regardless of whether the Netgear server was running. No entries in the MC log at all - not even the network printer messages I'm seeing now.

Last night, with 11.0.173 and whatever version of UPNP server I had:

If the Netgear software was running on the 2d computer, the MP101 found the Netgear server and wholly ignored the MC server.

If the Netgear software was shut down, the MP101 found the MC server but couldn't connect. Interestingly, I got the Unknown SSDP messages quoted last night - apparently from the Netgear software - at the exact times the MP101 was identifying and trying to connect to the MC server. That doesn't make sense unless the Netgear software leaves something running in memory even after its server reports that it has shut down.

If the 2d computer was completely shut off, the MP101 still couldn't connect to the MC server - but I don't recall with certainty if I got "server not found" or "MC server found, can't connect."

Today with 11.0.173 and UPNP 1.0.4, the MP101 works fine with MC. I honestly don't know if I tried 1.0.4 today while the Netgear software was running to see if the MP101 would find both. Now I've uninstalled the Netgear software so I can't test that easily - getting ready to leave for a few days.

Is there any way to identify UPNP devices on the network to match up a UUID in the MC log with a device or piece of software? There was nothing in the registry of the 2d computer matching the UUID in the message last night.

Sorry to be so vague on some of the details! If I see anything interesting in the future other than success, I'll try to keep closer track . . .

salsbst1 · « **Reply #18 on:** January 14, 2005, 02:14:32 pm »

Any chance of MC being a Media Renderer itself (to play music from either itself or another Media Device) someday?

John Gateley · « **Reply #19 on:** January 14, 2005, 04:02:41 pm »

Quote from: salsbst1 on January 14, 2005, 02:14:32 pm

Any chance of MC being a Media Renderer itself (to play music from either itself or another Media Device) someday?

Use Library Server to play music from another Media Center. Otherwise, I don't see the purpose.

j

salsbst1 · « **Reply #20 on:** January 14, 2005, 06:45:53 pm »

I'm working on a software implementation of a UPnP control point. I'd like to play MC files from that control point using MC's decoders.

MartinD · « **Reply #21 on:** January 15, 2005, 09:40:49 am »

Hi John,

I've tried MC .174 with the NOXON again. I've started MC's UPnP-Server, then plugged in the Noxon (power off & on is not enough to make it scan the network). MC is listed right after it receives the request for device description, but I can't browse any data. This is the Log:

01/15/05 16:34:35 - Starting...
01/15/05 16:34:35 - Running
01/15/05 16:34:46 - Received request for device description
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/15/05 16:34:49 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
01/15/05 16:34:50 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/15/05 16:34:52 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
01/15/05 16:34:54 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/15/05 16:34:56 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
01/15/05 16:34:56 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/15/05 16:34:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
01/15/05 16:34:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/15/05 16:35:00 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
01/15/05 16:35:02 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/15/05 16:35:03 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
01/15/05 16:35:08 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
01/15/05 16:35:09 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1

Please let me know if I can check something else (e.g. with Intel's UPnP tools).

Thanks for your work!

-Martin

John Gateley · « **Reply #22 on:** January 15, 2005, 12:42:03 pm »

Quote from: salsbst1 on January 14, 2005, 06:45:53 pm

I'm working on a software implementation of a UPnP control point. I'd like to play MC files from that control point using MC's decoders.

I think the current UPnP server does what you want. It's a Media Server device, serving out content.

j

John Gateley · « **Reply #23 on:** January 15, 2005, 12:44:16 pm »

Quote from: MartinD on January 15, 2005, 09:40:49 am

Hi John,

I've tried MC .174 with the NOXON again. I've started MC's UPnP-Server, then plugged in the Noxon (power off & on is not enough to make it scan the network). MC is listed right after it receives the request for device description, but I can't browse any data. This is the Log:

01/15/05 16:34:35 - Starting...
01/15/05 16:34:35 - Running
01/15/05 16:34:46 - Received request for device description
<snip>

Please let me know if I can check something else (e.g. with Intel's UPnP tools).

Thanks for your work!

-Martin

Hi Martin,

You can try restarting the UPnP server to make the NOXON rescan for servers. I'm not sure it will work, but when the server shuts down, it broadcasts byebye's to the network.

Do you have a packet sniffer available? A sniff of a successful connection would help me a lot.

j

MartinD · « **Reply #24 on:** January 16, 2005, 07:11:04 am »

Hi John,

ok, I've installed Ethereal. This is what I get when I try to browse MC from Noxon:

POST /ContentDirectory/control/DeviceDescription.xml HTTP/1.1
Host: 192.168.1.15:2071
SOAPACTION: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse"
CONTENT-TYPE: text/xml ; charset="utf-8"
Content-Length: 467

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>0</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>*</Filter>
<StartingIndex>0</StartingIndex>
<RequestedCount>10</RequestedCount>
<SortCriteria />
</u:Browse>
</s:Body>
</s:Envelope>

And this is the Response:

HTTP/1.1 501 Server Error
CACHE-CONTROL: no-cache
CONNECTION: close
CONTENT-LENGTH: 0
DATE: Sun, 16 Jan 2005 12:48:52 GMT

Again, thanks for your efforts!

-Martin

John Gateley · « **Reply #25 on:** January 16, 2005, 10:47:31 am »

Hi Martin,

This looks like the same thing I'm working on with Syserror. Try the version at:

http://www.jriver.com/~gateley/server_upnp.mjp

and see if you get farther.

j

MartinD · « **Reply #26 on:** January 16, 2005, 04:55:01 pm »

Hi John,

this looks good: I can choose from "Audio" and "Playlists". When I select "Audio" I get "Full albums", "All (68)" and the genre list. Scrolling down seems to work fine most of the time (I was transported back to start sometimes but I cannot reproduce this right now - I'll check this again later).

Right now, I can't step to the next level (result items have set the attribute childCount="0"). And I cannot play anything, maybe because there is no protocolInfo-attribute?

-Martin

John Gateley · « **Reply #27 on:** January 16, 2005, 07:34:32 pm »

Can you do a sniff with ethereal and mail me the results (for the childCount attribute failure)? It's gateley @ jriver.com, you can just mail the tcpdump format.

Thanks!

j

xerodiac · « **Reply #28 on:** January 17, 2005, 06:41:39 am »

John, would you mind showing the current plug-in version in the log? I know I can look it up somewhere in the menu but that's so inconvenient

syserror · « **Reply #29 on:** January 17, 2005, 11:52:59 am »

Quote from: MartinD on January 16, 2005, 07:11:04 am

POST /ContentDirectory/control/DeviceDescription.xml HTTP/1.1

I might have to move to Ethereal instead of MS' sniffer if it has good ability to piece together the TCP traffic.

The POST URL is very bizarre; it appears to be a URL mangling exactly like what the SMC EZ-Stream does - merging the control URL and the device description URL. Either it uses the same underlying stack with the same bug as the EZ-Stream, or maybe there's a very subtle aspect of UPnP spec that could explain that URL formation as somehow a legit interpretation.

Aaron

syserror · « **Reply #30 on:** January 17, 2005, 11:56:30 am »

Quote from: MartinD on January 16, 2005, 04:55:01 pm

this looks good: I can choose from "Audio" and "Playlists". When I select "Audio" I get "Full albums", "All (68)" and the genre list. Scrolling down seems to work fine most of the time (I was transported back to start sometimes but I cannot reproduce this right now - I'll check this again later).

Right now, I can't step to the next level (result items have set the attribute childCount="0"). And I cannot play anything, maybe because there is no protocolInfo-attribute?

You've got exactly the same behavior as I do with the EZ-Stream using John's dev version of plug-in now too. Do you have a sniff of the Noxon's NOTIFY packets? I'm curious to see what it says its server+UPnP are to see if EZ-Stream and it are essentially identical. I'll grab a sniff of inner-level browse on the EZ-Stream tonight too.

Aaron

John Gateley · « **Reply #31 on:** January 17, 2005, 03:05:19 pm »

Hi Y'all,

I'm closing this thread and starting a new one because there's a new version of the UPnP server ready to go.

I put in a real fix for the URL mangling problem.

I fixed the 0 childcount problem (it was my bug).

I added the version to the log.

I've made lot's of internal changes over the weekend, these could possibly make things work better, but also could break stuff that was working before.

I'm guessing that NOXON and SMC used the same UPnP code (probably from a third party like Digital5), that's why the same behavior is showing up. Though it could be some detail in the spec I've overlooked too.

Aaron - I've used ethereal for a while and I'm pretty happy with it. I can't compare it to windows sniffers though, haven't used any. I do like the "follow TCP" option that shows you the text for an entire connection in a window, The filtering is bizarre (two separate filter languages, depending on what you are doing), but it's usable. It doesn't do quite everything I'd like: I'd like to filter the entire data set for an IP address (the set top box), and then be able to look at TCP connections without losing the original filter. (After I view a connection and clear it, it reverts back to ALL traffic, not just traffic with the set top box).

Let me know how this new version works,

j

JimH · « **Reply #32 on:** January 17, 2005, 04:23:27 pm »

Here's a link to the next thread:
http://yabb.jriver.com/interact/index.php?board=3;topic=25599.4#msg177655

INTERACT FORUM

Author Topic: UPnP for Media Receivers (Read 10080 times)