[Live-devel] test*Streamer push

[David Skiba]

Ross,

Here are a few more details. I have a client that is expecting an RTP
video connection using UDP on a specified port. Would you expect that
I should be able to use the test*Server unicast mode to get test*Server
to send video to this client? I change the ip address to the one my client
is running on and the port from 8888 to the correct client port.

I know you can't speak for my client but I am wondering if the client side
is "standard" then you think this should work.

Thanks,
Dave

-----Original Message-----
From: live-devel-bounces at ns.live.com [mailto:live-devel-bounces at ns.live.com]
On Behalf Of Ross Finlayson
Sent: Friday, June 18, 2004 5:17 PM
To: LIVE.COM Streaming Media - development & use
Subject: Re: [Live-devel] test*Streamer push


>I am not sure which sample I should model my app on for what I am trying 
>to do.
>If I have machine A waiting on socket port 2345 for a video RTP 
>connection, can
>I use a modified test*Server app on machine B to connect to that socket 
>and push RTP, assuming
>a match on the video format being streamed.

You can use one of the "test*Streamer" applications (or a modification of 
one of these, if your video format is different).  See 
<http://www.live.com/liveMedia/faq.html#unicast>.

>  I think this is just a slight modification of the unicast scenario and 
> making the correct type of socket connection.
>I may be simplifying things too much but does it make sense to wait for 
>machine A to be ready before initializing the
>Groupsock connections.

Yes, because RTP streaming uses UDP, not TCP.  So, there is no 'connection' 
made between the two machines.

>Then instead of the bind() call do a connect() to specifically connect to 
>port 2345
>on machine A?

No, because you're using a datagram socket, you don't need to call 
connect().  Instead, just call bind() on the port number (2345) that you 
wish to listen to.

(Note: By convention, you should really use an even-numbered port - i.e., 
not 2345 - for  sending/receiving RTP packets.  Odd-numbered ports are 
conventionally used for RTCP.)

But anyway, if you were to use one of the "test*Receiver" applications (or, 
even better, a RTSP client), then all of this would be taken care of for
you.


	Ross Finlayson
	LIVE.COM
	<http://www.live.com/>

_______________________________________________
live-devel mailing list
live-devel at lists.live.com
http://lists.live.com/mailman/listinfo/live-devel