[mythtv-users] Accessing Mythbackend via UPNP

[David Hampton]

Hi,

I'm trying to use UPNP for the first time, and am unable to locate my
myth backend via the UPNP protocol.  When I run wireshark on my local
machine I see frequent MDNS and SSDP messages from a file server, but I
only ever see an occasional MDNS message from the myth backend.  I tried
enabling upnp logging (-v none,upnp --loglevel debug) on the backend,
and myth believes its sending SSDP notification messages, but wireshark
never sees those messages hit the wire.  Here a log excerpt from a
startup with only upnp logging enabled:

2015-02-12 23:07:04.750213 I  SSDP::EnableNotifications() - sending NTS_byebye
2015-02-12 23:07:04.750269 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : upnp:rootdevice : uuid:::upnp:rootdevice
2015-02-12 23:07:04.903074 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : uuid: : uuid:
2015-02-12 23:07:04.923967 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 :  : uuid:::
2015-02-12 23:07:05.010700 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1 : uuid:::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
2015-02-12 23:07:05.026723 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:schemas-upnp-org:service:ConnectionManager:1 : uuid:::urn:schemas-upnp-org:service:ConnectionManager:1
2015-02-12 23:07:05.101670 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:schemas-upnp-org:service:ContentDirectory:1 : uuid:::urn:schemas-upnp-org:service:ContentDirectory:1
2015-02-12 23:07:05.111431 I  SSDP::EnableNotifications() - sending NTS_alive
2015-02-12 23:07:05.111446 I  Starting TaskQueue Thread...
2015-02-12 23:07:05.111554 I  TaskQueue Thread Started.
2015-02-12 23:07:05.111565 I  SSDP::EnableNotifications() - Task added to UPnP queue
2015-02-12 23:07:05.111570 D  UPnp::Start - Returning
2015-02-12 23:07:05.111841 I  TaskQueue Thread Running.
2015-02-12 23:07:05.111942 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : upnp:rootdevice : uuid:::upnp:rootdevice
2015-02-12 23:07:05.123822 I  MediaServer:Init:End
2015-02-12 23:07:05.167536 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : uuid: : uuid:
2015-02-12 23:07:05.286496 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 :  : uuid:::
2015-02-12 23:07:05.439684 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1 : uuid:::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
2015-02-12 23:07:05.481091 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:schemas-upnp-org:service:ConnectionManager:1 : uuid:::urn:schemas-upnp-org:service:ConnectionManager:1
2015-02-12 23:07:05.534329 I  UPnpNotifyTask::SendNotifyMsg : 239.255.255.250:1900 : urn:schemas-upnp-org:service:ContentDirectory:1 : uuid:::urn:schemas-upnp-org:service:ContentDirectory:1

Comparing these to messages from my file server, these messages are all
missing the actual UUID value.  I poked around, but I don't see where
this is defined.  I do see the following message when searching other
myth log files with normal logging enabled:

2015-02-09 02:22:54.860839 E [12434/12434] CoreContext upnputil.cpp:51
(LookupUDN) - LookupUDN()- bad device type '', not enough tokens

Looking at the LookupUDN function it appears to be aborting before
generating and saving a UDN for the device, because the device type is
NULL.  The question now is why is the device type null?  I think I'm on
the right track, but I haven't chased it back further than this.  It
seems like maybe I'm missing something in my configuration?  This is a
backend that was installed sometime in 2007 and has been upgraded over
the years, so its entirely possible something may have gotten dropped or
left out along the way.

Any help would be appreciated.  TIA.

David