Unicasting a Live ASF Stream

Use the following steps when setting up a unicast of a live ASF stream from the Real-Time Encoder. Setting up a unicast in this way allows the client to receive only one ASF stream. If you want clients to receive a series of streams, set up the unicast using a channel.

Note The NetShow unicast service uses port 1755 to establish communication between a client and the server. To allow unicasts, this port must not be disabled in Windows NT Server.

The illustration shows the Real-Time Encoder, NetShow Server, and HTTP server on separate computers. While all software can run on a single computer, in most cases you should run the system as shown. Because the Real-Time Encoder places heavy demands on the processor, dedicating a computer to run it can ensure performance. If you plan to use NetShow Server's unicast HTTP streaming, you must run your HTTP server on a separate computer.

1. On the computer used to run the NetShow Real-Time Encoder, connect the audio or video source to the appropriate input on the server's sound or video card.
2. Set up the NetShow Real-Time Encoder on the computer you are using as a source for the stream.

   For more information, see the NetShow Tools Guide.

3. On NetShow Server, start NetShow Administrator, connect to the server you want to manage, and use Set Publishing Points to create a publishing point that references the Real-Time Encoder, and, optionally, the port. Specify the path using the MSBD protocol:
   msbd://servername:portnumber

   It is necessary to specify a port only when you have changed the default port used by the Real-Time Encoder.

   For more information, see Creating a Publishing Point.

4. In NetShow Administrator, use Set Properties to set the limits on the number of clients, bandwidth usage, and bit rate.

   For more information, see Setting Unicast Server Properties.

5. Start feeding the source stream and start the Real-Time Encoder.
6. Clients can connect to the NetShow server and play the file using either the stand-alone or embedded NetShow player.

   To connect using the stand-alone player, specify the URL for the NetShow server and publishing point alias using the MMS protocol. For example:
   mms://servername/pubpointalias

   To set up the embedded player to connect, specify the URL in either the object information or the scripting code for the control.

   Clients can also connect using an announcement. Clients must use an announcement to connect if they are connecting using a Web page link to reach the stream and will then use the stand-alone player to play it. To use an announcement:

   • Create an announcement for the unicast. Using a text editor, create an announcement that points to the NetShow unicast server. Save the announcement as an .asx file.

     For more information, see Using Unicast Announcements.

   • After you have created an announcement, you can distribute it in a variety of ways: store it on the HTTP server where clients using the embedded player or stand-alone player can access the file through a Web page; store it in a public directory on a LAN where clients using the stand-alone player can open it; or distribute it through e-mail to clients using the stand-alone player.

     Clients can connect to the server and play the file using either the stand-alone or embedded NetShow player. To connect using the stand-alone player, specify the .asx file. To set up the embedded player to connect, specify the .asx file in either the object information or the scripting code for the control.

© 1997 Microsoft Corporation. All rights reserved. Terms of Use.