PDA

View Full Version : Live stream - Pull support for Http?



avad
07-13-2010, 09:20 PM
In Tricaster Studio, when you setup a live stream in Windows Media format (pull), is the stream available in mms or Http or both?

The stream server I am using is capable of Pulling the live feed from an encoder or, in this case, Tricaster.

Any help is appreciated.

bbeanan
07-13-2010, 09:30 PM
you would just put in the static ip address of your TriCaster with your streaming host... that would be it

avad
07-14-2010, 08:40 AM
I meant to say that my stream server can pull the live feed ONLY on http.
For example, http://<tricaster IP address>

I read in the Tricaster help that Windows media was streamed from the Tricaster in MMS. My questions are:

1. Can the Tricaster make the live feed available in HTTP?
2. If so, how can I enable this?

TIA

joseburgos
07-14-2010, 02:09 PM
When you are sending the stream to another media server, it would be a push. Pull is when the users are logging in directly to the stream original, which would be the TriCaster in this case.
As to using HTTP for a pull, it never works and I would just use mms:

Good luck,

avad
07-15-2010, 08:39 AM
It seems the documentation is a little off! The Tricaster does makes the windows media live feed available as a http link by default.

@ joseburgos, I beg to differ. When you have a dedicated media server, it can either Pull or have the live feed pushed to it from the encoder (in this case, Tricaster acts as the encoder). Some media servers only support 'pulling' the feed from the encoder (like the one I am using) and some media servers (like Wowza) mandates the live feed be pushed to it.

Thanks

SBowie
07-15-2010, 08:46 AM
When you have a dedicated media server, it can either Pull or have the live feed pushed to it from the encoder (in this case, Tricaster acts as the encoder). Some media servers only support 'pulling' the feed from the encoder (like the one I am using) and some media servers (like Wowza) mandates the live feed be pushed to it.This is correct - some CDNs use Pull. (I think this is in the manual, actually.) Push may be more common though ...

joseburgos
07-15-2010, 08:54 AM
It seems the documentation is a little off! The Tricaster does makes the windows media live feed available as a http link by default.

@ joseburgos, I beg to differ. When you have a dedicated media server, it can either Pull or have the live feed pushed to it from the encoder (in this case, Tricaster acts as the encoder). Some media servers only support 'pulling' the feed from the encoder (like the one I am using) and some media servers (like Wowza) mandates the live feed be pushed to it.

Thanks

I never knew that as the CDN's I used when I was encoding to WME always used Push. I learned something new :)

rbartlett
07-15-2010, 09:51 AM
Plus, it is viable for a pull to be http, that then delivers an asx/wmx (with associated MIME type headers) that then kicks off further pull connectivity on non-http (non TCP80) ports.

Firewalls usually need to know the direction of initiation and the (protocol) ports or their pairings. Streaming entirely on http (TCP80) is viable with WMEncoder and also with FMS, afaik.

Best that you ensure you don't enable RTSP, RTMP, RTMPE or SSL options in any of the compression servers on the NewTek unit.

Testing with a browser or media player from the outside of your network (maybe via your cellphone etc) is usually helpful to establish whether your pull server is going to be able to start up just with an http type access.