Unreal Media Server v. 2.5
http://www.umediaserver.net/install.html


1. Media Server and Client.

After you have downloaded and run the installation program for Unreal Media Server, the service called
UMediaServer should be running and listening on TCP port 5119. If you have Microsoft IIS running on the 
computer, then it is suggested to install IIS extension for streaming (UHTTPProxy). During the 
installation please do not change the name of the virtual folder. After the installation please make 
sure that the IIS virtual folder UHTTPProxy allows anonymous access. When you have installed 
IIS extension for streaming, the Media Server will be able to stream media content via HTTP.

The installation program sets up a sample video clip by creating a virtual folder called 
MediaRoot (this is not IIS folder, but MediaServer's one), mapping this folder to the program 
installation directory ("Program Files\Unreal Streaming\MediaRoot" by default) and placing file
"test.avi" in the latter directory.

Streaming Media Player needs to be installed in order to see streaming media.
Start the player and enter IP address or machine name of the Media Server computer. If you choose TCP as
a transport protocol, make sure there are no firewalls between client and server machines, that block 
port 5119. If this particular port is blocked, use Media Server Configuration tool, which is a part of 
Media Server installation, to change this port number. If all TCP traffic is blocked, your only choice 
is to connect via HTTP. Once the client computer can reach the server computer, you should be able to 
stream the test file.

Using Media Server Configuration tool, you can create virtual folders and map them to the different 
physical locations on the server machine. Alternatively, the physical location can be anywhere in the 
server machine's LAN. To make this work, several steps should be done.

Win 2000: You will need to map network drive, such that the remote folder will be treated as a local folder. 
Win XP: Browse to network folder.
The security should be setup such that the account under which UMediaServer runs, has access to this 
network drive. By default, UMediaServer runs under local system account. You will need to have an account
that can access this network drive, and make UMediaServer service run under this account. Use "control 
panel - services - UMediaServer properties" to change the account. Once virtual folder is accessible by 
MediaServer, the files in this folder can be streamed to the clients. Users will need to specify this 
folder in Streaming Media Player. Virtual folder can be configured to require internal or session-based
authentication.


2. Live Source Server

Live source server should be installed on the computer that has live media sources attached to it. Live 
media sources include: digital cameras, microphones, analog video sources (analog camera or TV) connected 
to Video card or to FrameGrabber card that supports DirectShow interface. There can be multiple live 
sources attached to a single computer. Download and run the installation program for Unreal Live Server. 
The service called ULiveServer should be running and listening on TCP port 5120. It's very important to 
understand that the requests to this server will be coming from Media Server computer, not from the client 
computers. Therefore Live Server machine should be reachable from Media Server machine. The request from 
Media Server to Live Server can only be made by TCP via port 5120. Use Live Server configuration tool to 
add and configure a source for your live media content, such as camera/microphone/other. The clients 
should be able to see live source, provided they know the IP address/machine name of Live Server and 
Media Server machines, and the media source ID.

Using Media Server Configuration tool, you can create aliases for live sources. Clients can  then use the 
alias to get live stream.


3. Creating a link to media resource

The most comfortable way for the users to access remote media is to click on a link in the Web browser. 
Setup of Streaming Media Player registers a custom URL protocol on user's machine. This is a UMS protocol, 
allowing to launch Streaming Media Player directly from the hyperlink on the Web page. The person who 
configures the Media Server, is responsible for creation of these links and putting them to the web pages.

The link can refer only to File or Alias of the live source. Direct access to the live source is not 
allowed in the link.
Link should consist of 4 parts:

"ums:\\" or "ums://". 
Transport protocol followed by semicolon - TCP or HTTP. 
Media Server IP address followed by backslash. If no port is specified, default port corresponding to the 
transport protocol will be used for the connection. Default TCP port is 5119, default HTTP port is 80. 
Actual media name. In no slash or backslash is found in the name, the name will be treated as the Alias of 
the live source. Otherwise the name will be treated as a filename. 


The hyperlink on the web page might look like this:
< A HREF="ums:\\TCP:65.68.17.44:5127\Media\Myfile.avi">Myfile.avi</A>.
Or like this: 
< A HREF="ums:\\HTTP:207.68.171.244\MyWebCam">My Web Camera</A>.
The part shown in brown color is the actual link.
This link can alternatively be used on the local user's machine in two ways:
   Passing it as a parameter to Streaming media player: StreamingMediaPlayer.exe ums:\\TCP:65.68.17.44:5127\Media\Myfile.avi
   Running the link alone: ums:\\TCP:65.68.17.44:5127\Media\Myfile.avi
In all the described cases Streaming media player will launch and start playing the remote media.


