rtmp live stream

800 views
Skip to first unread message

ahmed hussain

unread,
Apr 13, 2015, 8:00:52 AM4/13/15
to mists...@googlegroups.com
Hi, frnds iam getting confuse at connecting with live stream. so guide me how to check live stream in mistserver.

Balder Vietor

unread,
Apr 13, 2015, 8:22:29 AM4/13/15
to mists...@googlegroups.com
Hello Ahmed,

At what step are you getting confused with live streaming? It's a rather broad subject so unless you specify where you're stuck we might not be able to help you easily. The mail will get a bit long from here on, but feel free to ask if you're getting confused at any part of the instructions below.

The hardest part of live streaming is getting the host, port, application and stream correct on both MistServer and your device pushing towards MistServer. It's important to remember both MistServer and your pushing application need the address of each other, just remember they need to communicate with eachother and it will start making more sense.

Regardless of how you'll push towards MistServer the MistServer settings will stay the same. You can set up a live stream in two steps. First you need to set the RTMP port, then you need to create a live stream and give it a stream name you can remember. Viewers of live streams will automatically connect to the point as close to live as possible for the protocol, some protocols can be more live than others.

1.Protocols
 If you have activated every protocol (the standard option) you can skip this step. If you haven't activated any protocols you can open them at protocols within your MistServer Management Interface. The standard port for HTTP is 8080, RTMP uses 1935.
Protocols are responsible of how MistServer can communicate with other devices, adding or editing the protocols tells MistServer how to behave. Currently MistServer only supports RTMP pushing, so make sure you've one enabled if you want to attempt live streaming.

2. MistServer Settings 
To create a live stream, go to streams and create a new stream. Set up a stream name and use push://ip.address as a source.
Do remember that you'll probably have to fill in the stream name for each device pushing towards MistServer, so we recommend something short and easy to remember. 

Stream name
This is the name used by both MistServer and any device pushing to MistServer to connect correctly. MistServer handles a limit of 100 characters for your stream name, names are not case sensitive and will decline special characters.

Source
Here you can tell MistServer whether the stream is a live stream and from what locations it should accept a push and set a password* (*MistServer Pro only). The source is fully compatible with both ip addresses and host names, please make sure the ip addresses or host names you fill in are correct.

Examples
push://ip.address      Live stream accepting pushes only from the set location.
push://hostname       Live stream accepting pushes only from the corresponding hostname.
push://                       Live stream accepting pushes from any location.

3. Pushing 
Currently MistServer only supports RTMP ingest, luckily RTMP ingest suffices for nearly any use case. A RTMP url exists of a host, port, application and stream. This looks like rtmp://host:port/application/stream.
Most software will let you change all of these, though some software will call them differently.

First remember that MistServer and your live source application need to communicate. So your application will need the information to connect to MistServer, proper use of host, port, application and stream will decide your succes.

host              This will be your MistServer address.
port               If you're using the standard port you can omit this from your url, otherwise you'll need to use specify the port after the host.
application   This is used as another identifier, if you're using MistServer Pro you can use it as a password. If you haven't set it you can use anything as application.
stream          This needs to correspond with the stream name you've set in MistServer


Some examples of host, port, application and stream, as live is the most commonly used application name we'll use that as well:

Pushing to MistServer, standard RTMP port, no password.
rtmp://MistServer.ip.address/live/StreamName

Pushing to MistServer, custom RTMP port, no password.
rtmp://MistServer.ip.address:CustomPort/live/StreamName

Now sometimes host, port, application and stream are called differently depending on what you're using to push towards MistServer. If you're getting confused about what they're called please share what you're using and i'll do my best to help you. Incase you need it you can find some examples per application here: http://mistserver.org/wiki/Push_Guide

With kind regards,

Balder Viëtor
Product Management & Head of testing

Amphoraweg 5 
2332ED Leiden 
The Netherlands
mistserver.org
ddvtech.com
+31 10 8080 619 (NL) 
+1 408 677 5212 (USA)

On Mon, Apr 13, 2015 at 2:00 PM, ahmed hussain <ahme...@gmail.com> wrote:
Hi, frnds iam getting confuse at connecting with live stream. so guide me how to check live stream in mistserver.

--
You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ahmed hussain

unread,
Apr 13, 2015, 1:27:49 PM4/13/15
to mists...@googlegroups.com


On Monday, April 13, 2015 at 5:30:52 PM UTC+5:30, ahmed hussain wrote:
Hi Balder Vietor, iam getting like in this view. i want to check live stream in same machine in which i have misterver.
where i can get this port and host.? 
 

ahmed hussain

unread,
Apr 13, 2015, 1:35:38 PM4/13/15
to mists...@googlegroups.com

--
You received this message because you are subscribed to a topic in the Google Groups "Mistserver.org" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mistserver/7uPueZEKM3g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mistserver+...@googlegroups.com.
Screenshot from 2015-04-13 22:50:41.png

ahmed hussain

unread,
Apr 14, 2015, 4:05:31 AM4/14/15
to mists...@googlegroups.com
Hi I'm trying to check live stream, but i followed that mist server guide, is my configuration problem.
1. protocol: 1935
2. source:push://0.0.0.0


please guide me with proper steps.
 Regards:
Ahmed Husssain 

Balder Vietor

unread,
Apr 14, 2015, 5:08:03 AM4/14/15
to mists...@googlegroups.com
Hello Ahmed,

I think I can see your problem: You're using "push://0.0.0.0" as a source this can't be a valid address, you'll need "push://localhost" or "push://127.0.0.1" as you've send in your screenshots.

Easiest is probably using "push://localhost" if you're streaming on the same device as you're running MistServer. If you'd like to try it out with another device later on i'd suggest using "push://" while testing to make sure the address isn't the problem in your MistServer settings. Do not use this in an actual live situation as it's lacking on the security this way. 

As for the protocol, are you using 1935 for RTMP? and is it allowed? You can view the RTMP protocol in the Protocols window and it should be able to tell you whether it's online or not. 

Once you're done with these settings make sure you push towards MistServer using the proper port, stream name, application and address. 
To give you proper instructions on this i'll need to know what you're using to push towards MistServer. Common used programs are: ffmpeg, FMLE, VMix, OBS. 

Going back to your screenshots you'll need to send on the following addresses:

rtmp://localhost:1935/live/live

rtmp://localhost:1935/live/live12

rtmp://localhost:1935/live/vid1

So use the following information in your push application:

Port: 1935 (or empty as it's standard)
Application: live (or empty as it'll probably take live as standard)
Address: localhost or 127.0.0.1
Stream Name: live or live12 or vid1

Afterwards you should be able to see your stream through the preview window. If this isn't working the logs in MistServer should be able to tell you what's wrong. If you're not seeing logs try putting the debug information to level 4 and reboot MistServer.

With kind regards,

Balder Viëtor
Product Management & Head of testing

Amphoraweg 5 
2332ED Leiden 
The Netherlands
mistserver.org
ddvtech.com
+31 10 8080 619 (NL) 
+1 408 677 5212 (USA)

You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.

ahmed hussain

unread,
Apr 14, 2015, 8:55:08 AM4/14/15
to mists...@googlegroups.com
where i have to configure this ffmpeg. iam using linux o.s ,so how can i get this.

Balder Vietor

unread,
Apr 14, 2015, 9:40:25 AM4/14/15
to mists...@googlegroups.com
Hello Ahmed,

As ffmpeg has a different install way for each flavor of Linux I'll send you the website: http://ffmpeg.org/

It would be best if you'd more information about ffmpeg if you want to use it as it has a very detailed information page/community you can access with any questions you have on the usage of ffmpeg. As for the "standard" usage it would be something like the following:

ffmpeg -i INPUT(url or file) -acodec copy -vcodec copy -f flv rtmp://mistserverip/live/streamname

Edit anything that's indented to what you'd like to use.





With kind regards,

Balder Viëtor
Product Management & Head of testing

Amphoraweg 5 
2332ED Leiden 
The Netherlands
mistserver.org
ddvtech.com
+31 10 8080 619 (NL) 
+1 408 677 5212 (USA)

ahmed hussain

unread,
Apr 15, 2015, 11:00:32 AM4/15/15
to mists...@googlegroups.com
Hello Balder Vietor,
I'm trying to live stream using wowza gocoder(Android App),Iam getting these errors.



Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|2052||Socket 6 closed
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|2052||Handshake type is 0, encryption is off
Wed 15 Apr 2015, 20:29:05MEDIUMMistOutRTMP|2052||Client scheme validation 1 failed
Wed 15 Apr 2015, 20:29:05MEDIUMMistOutRTMP|2052||Client scheme validation 0 success
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|2052||Handshake version is 3
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|2052||ServerSocket 5 closed
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|1855||Socket 6 closed
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|1855||Forked new process 2052 for socket 6
Wed 15 Apr 2015, 20:29:05HIGHMistOutRTMP|1855||IPv6 addr [::ffff:192.168.1.6]
Wed 15 Apr 2015, 20:29:02MEDIUMMistOutRTMP|2048||MistOut client handler shutting down: conn_closed, want_request, not_parsing_data
Wed 15 Apr 2015, 20:29:02MEDIUMMistOutRTMP|2048||MistOut client handler started
Wed 15 Apr 2015, 20:29:02HIGHMistOutRTMP|2048||Handshake success!

Balder Vietor

unread,
Apr 16, 2015, 4:54:17 AM4/16/15
to mists...@googlegroups.com
Hello Ahmed,

We've looked at the Wowza Gocoder and MistServer: We've found that the Wowza Gocoder application is only compatible with Wowza (due to an encryption they've added in the RTMP handshake). So you'll have to use another application if you'd like to use MistServer or use Wowza Streaming Engine if you want to use the Gocoder. 

With kind regards,

Balder Viëtor
Product Management & Head of testing

Amphoraweg 5 
2332ED Leiden 
The Netherlands
mistserver.org
ddvtech.com
+31 10 8080 619 (NL) 
+1 408 677 5212 (USA)

Reply all
Reply to author
Forward
0 new messages