Hi, The default server ip address is the localhost, and that can be overridden from the query string, for instance you can use the cloud-dleyna live pages using the ip address of your dleyna+cloudeebus server instead of 127.0.0.1 http://01org.github.io/cloud-dleyna/index.html?host=127.0.0.1&port=9000 However, it seems more practical (you are the second person to ask for it) to just use the http server ip address as the default. I just pushed the change on the cloud-dleyna github. Note that you can still override this in the query string as in the url above) if dleyna+cloudeebus and your http server are on two different machines. B.R. Luc From: dLeyna [mailto:dleyna-bounces@lists.01.org] On Behalf Of Mike akael Sent: Tuesday, November 19, 2013 1:12 AM To: dleyna(a)lists.01.org Subject: [dLeyna] cloud-dleyna Hi all, I've just installed and made first tests with dleyna. Seems very promising after just a quick look! I'm trying to test the cloud-dleyna test application but when opening the file index.html (served by a tornado webserver (also tried lighttpd) ,on an headless arm processor) i've got the message : Connection could not be established. This after launching ./cloudeebus.sh of course On port 9000 I can see authobahn is working. ALso I've tested rendererconsole.py and this work as expected, I can discover dlna devices and communicate with. I've installed dleyna renderer and server from Debian Jessie repository and made the cloudeebus install with setup.py. What can cause this issue (well many reason I guess but...)? or is the index.html exemple already served on another port when launching ./cloudeebus.sh ?? Thanks for help Mike

Hi Mike, About the cloud-dleyna test GUI: http://01org.github.io/cloud-dleyna/index.html?host=127.0.0.1&port=9000 Can you just tell me what should normally be displayed on id="mediaContent" window? Is that for image display, video also? It's for all of that, provided your navigator can display it in a "media" tag. The "Local Rendering" checkbox must be selected for the navigator to render media. If you select a remote renderer in the "Renderers" list, the media will be sent to that renderer instead. There is a controller UI more or less designed for smartphones in the "mobile-dmc" branch, that you can access also online http://01org.github.io/cloud-dleyna/dmc/index.html?host=127.0.0.1&por... For this version, the default behavior is to browse media servers and control renderers, but you can still see the media in another tab of your navigator if you hit the "preview" button I'm actually running dleyna from debian repo (v0.1.0-1) but I will install the latest versions from sources. Are there special requirement ? When I run autogen.sh I get the error : Libtool library used but LIBTOOL is undefined. What should I do to resolve this? I usually only deal with whatever is north of dbus here, but I suspect you should just install autotools: sudo apt-get install autotools-dev automake Cheers Luc 2013/11/19 Yriarte, Luc <luc.yriarte@intel.com<mailto:luc.yriarte@intel.com>> Hi, The default server ip address is the localhost, and that can be overridden from the query string, for instance you can use the cloud-dleyna live pages using the ip address of your dleyna+cloudeebus server instead of 127.0.0.1 http://01org.github.io/cloud-dleyna/index.html?host=127.0.0.1&port=9000 However, it seems more practical (you are the second person to ask for it) to just use the http server ip address as the default. I just pushed the change on the cloud-dleyna github. Note that you can still override this in the query string as in the url above) if dleyna+cloudeebus and your http server are on two different machines. B.R. Luc From: dLeyna [mailto:dleyna-bounces@lists.01.org<mailto:dleyna-bounces@lists.01.org>] On Behalf Of Mike akael Sent: Tuesday, November 19, 2013 1:12 AM To: dleyna@lists.01.org<mailto:dleyna@lists.01.org> Subject: [dLeyna] cloud-dleyna Hi all, I've just installed and made first tests with dleyna. Seems very promising after just a quick look! I'm trying to test the cloud-dleyna test application but when opening the file index.html (served by a tornado webserver (also tried lighttpd) ,on an headless arm processor) i've got the message : Connection could not be established. This after launching ./cloudeebus.sh of course On port 9000 I can see authobahn is working. ALso I've tested rendererconsole.py and this work as expected, I can discover dlna devices and communicate with. I've installed dleyna renderer and server from Debian Jessie repository and made the cloudeebus install with setup.py. What can cause this issue (well many reason I guess but...)? or is the index.html exemple already served on another port when launching ./cloudeebus.sh ?? Thanks for help Mike