tcp port number...

[simoncn]

(25-07-2012 15:40)psme Wrote:  minimServer has a setting for the tcp port number to use, default is 9790 I think. All song and album art are served through this port.

But, it seems, on startup, minimServer is randomly using a tcp port 5xxxx for it's device description xml URL. I checked foobar upnp, Asset upnp and Twonky, they all use the same tcp port for both device description xml and audio/picture links.

I understand currently minimServer doesn't support remote streaming, but the random tcp port seems specifically against remote access!

If possible, please consider using a static port for the device description. TIA!

ps: for remote streaming, I use foobar upnp. In PlugPlayer, I input foobar upnp device description xml address, and enjoy my music library on the road!

MinimServer supports the UPnP standard, in which a device sends out UPnP advertisements containing the URL for a dyamically generated device description. It sounds like PlugPlayer is using a different approach, where the device description is stored statically. I'll take a look at how this works.

I don't think it will be possible to use the same port for all requests, because some of these requests are handled by ohNet (on a listening port that it controls) and some are handled by MinimServer (on a different listening port). It might be possible for MinimServer to allow both of these ports to be assigned different static numbers for people who want to do remote streaming.