Re: need help with RSTP

I have a question related to this topic, so I thought I'd stick it here...

Currently, our WMS is configured to only stream through port 80 using TCP.
Our Engineers were concerned about opening up all the ports for RTSP and MMS,
so they just used port 80. It's working, except I'm starting to get
complaints about live streams taking too long to start in embedded players on
our website. Will opening up the other ports to our WMS reduce the startup
time for videos in the embedded players on our site? Any thing else I can do
to decrease the buffer and load times?

"Mike Lowery" wrote:

If you want to force RTSP, yes. Or you can use HTTP to stream to the listeners.
http://www.microsoft.com/windows/windowsmedia/forpros/serve/firewall.aspx#ProtocolRollover

"jeff" <doc2485@xxxxxxxxxxx> wrote in message
news:OF58uF%23ZHHA.3612@xxxxxxxxxxxxxxxxxxxxxxx
AHHH, ok then, I guess my best practice is to use the http protocol to get to
the live encoders and then in my asx files pointing to the WMS is to use the
RTSP protocol to stream out to the listeners????


thx
jeff




"Mike Lowery" <selfspam@xxxxxxxxxxxxxxxx> wrote in message
news:uOPuj19ZHHA.4948@xxxxxxxxxxxxxxxxxxxxxxx
WME only supports HTTP, not RTSP. You have to use WMS for RTSP streams. FYI,
you can specify RTSPT for TCP and RTSPU for UDP if you want to force one over
the other.

Also, you can always test connection to TCP ports by telnetting to them:
telnet <server> <port>.

"jeff" <doc2485@xxxxxxxxxxx> wrote in message
news:ukqbyu8ZHHA.3996@xxxxxxxxxxxxxxxxxxxxxxx
Rich, i feel stupid on the misspelling! I tried it with RTSP and now i get
a connection failed error?

I am forwarded ports:
tcp - 554 in to encoder
udp - 5005 in to encoder
tcp - 1755 in to encoder


The streaming server is behind a small dlink router also......... i am doing
a pull from the encoder, does the ports have to open there also?

jeff


"Rich C" <no@xxxxxxxx> wrote in message
news:45f9f6b3$0$17135$4c368faf@xxxxxxxxxxxxxxxxx
jeff wrote:
I have a windows 2003 streaming server running and I am trying to start a
publishing point with the source being something like this:

rstp://streaming.abc.com:2929

each time i try to start the point i get some wierd error like:
"cannot start because of an enumeraton error....."

if i put in:
http://streaming.abc.com:2929
it works fine??????

I thought RSTP was a better streaming protocol for audio and video
streaming?????

advice?
jeff


Try RTSP...not RSTP. ;)

Rich C.









.

Relevant Pages

  • Re: need help with RSTP
    ... they started to feed video in 1-2 seconds... ... our WMS is configured to only stream through port 80 using TCP. ... Our Engineers were concerned about opening up all the ports for RTSP and MMS, ... udp - 5005 in to encoder ...
    (microsoft.public.windowsmedia.server)
  • Re: need help with RSTP
    ... our WMS is configured to only stream through port 80 using TCP. ... Our Engineers were concerned about opening up all the ports for RTSP and MMS, ... RTSP protocol to stream out to the listeners???? ... udp - 5005 in to encoder ...
    (microsoft.public.windowsmedia.server)
  • Re: trouble with RealPlayer files on iPaq 1940
    ... I have .ram files which wont stream, they just download. ... doesn't open up the ports used by the PocketPC client. ... router, while my PPC can't with this router. ...
    (microsoft.public.pocketpc)
  • Re: need help with RSTP
    ... AHHH, ok then, I guess my best practice is to use the http protocol to get ... you can specify RTSPT for TCP and RTSPU for UDP if you want to force ... you can always test connection to TCP ports by telnetting to them: ... udp - 5005 in to encoder ...
    (microsoft.public.windowsmedia.server)
  • RE: Server not actually streaming without full path to file
    ... the publishing point does include 'mediafiles'. ... I had my firewall setup to open the right ports, but that didn't seem to do the trick. ... I'll walk through that again and if that doesn't work, I'll stream via HTTP Server Protocol. ...
    (microsoft.public.windowsmedia.server)
Loading