Red5 + Open Broadcast Software (OBS) Setup Help

[Greg Fotiades]

Hi, I'm new to Red5 (and OBS, for that matter).  I am trying to get them to play nice together so I can stream directly (internal LAN) to a mobile device over RTMP.

I took version 1.0 of Red5 and installed it on my machine (Win7 x64).  I got prompted 2x during setup, 1 for IP, which I put my local host (127.0.0.1), and once for the port, to which I put 4444 (just a number that popped into my head).

If I go to http://127.0.0.1:4444 I get the Red5 HTTP page in browser, but I can't connect to it from OBS to stream.  I see in the Red5 config file that the port is different for RTMP, it's 1935, so I tried that, but no luck.

In "Broadcast Settings" of OBS, I'm using "Custom" type, and the address is: rtmp://192.168.1.100:1935 (the internal address of my computer) - I've also tried 127.0.0.1 with no luck.  The error I'm getting is that the pass key / channel path is invalid and the handshake failed.  I cannot figure out where to control this in the Red5 config.  I left this field blank in OBS.

Information seems to be scarce on the matter, and the few people with Red5 problems I find on OBS forum and stuff essentially get told to piss off...

Anybody have any info on setting the duo up to work together or simply what's wrong with the pass key / where to set it?

[Mondain]

By setting 127.0.0.1 during the install you have told the server only to listen on "localhost"; connecting to any other IP on the box will not work as it is not even bound to your NIC. Change the IP to 0.0.0.0 in your red5.properties file for every entry that contains 127.0.0.1 and then restart your server; that's all you should need to do.

--

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

[Greg Fotiades]

Mondain,

Thanks for your help!

Okay, I changed the IP address that it's listening on to 0.0.0.0 but the error persists.

I screen capped the error messages which OBS gives me.  I can't figure out how to set the pass key in red box, so I left it blank, and I believe that's what it is complaining about.

Error pop-up from OBS:
http://i.imgur.com/gyWUVQF.png

Connection settings:
http://i.imgur.com/cOWT3ln.png

That IS how I should be connecting to it, right?

I feel like the problem is not setting this pass key deal..

Thanks,

Greg

[Mondain]

I'm not familiar with OBS, but I think you're missing the application in the "FMS URL" box. Try this there: rtmp://127.0.0.1/live and leave off the port (1935) which should be the default when specifying the rtmp protocol. Then put your stream name in the "Stream key" box.

[Greg Fotiades]

Mondain,

Ok, I will try the address with /live when I get home.

The stream key is what I cannot find in Red5.  I know where to put it in OBS, it's fairly obvious given the previous screen shot, but I do not see any options in the Red5 config for setting the stream key or 'channel' - or where even '/live' comes from.  Where are all of these options in Red5?  I need to locate this key in Red5 if I'm going to enter it in OBS.

Thanks,

Greg

[Mondain]

I assume stream key means stream name; there is no key in red5 unless you create it. The server is wide-open unless you configure or develop for it otherwise.

[Greg Fotiades]

Mondain,

I'm actually away from home so I haven't had a chance to look, from what I recall in the config file I didn't see anything about a stream name - did I just miss it or is it named something a little odd?  You said to try it with '/live' - like is that in the config, or is that a default?

Thanks,

Greg

[Mondain]

"live" is a default app that comes with red5; look in your red5/webapps/ directory and you should see it and others such as root.

[Greg Fotiades]

Okay, I got OBS to connect by trying what you suggested:
In the FMS URL field, I put:  rtmp://127.0.0.1/live

This wasn't enough though, I also had to put in the "Play Path / Stream Key":  live

Then OBS and Red5 seemed to be playing nice together.

No RTMP clients (ie. VLC) seem to work, however.  The IP would be the same, right, in an RTMP player (on local LAN) I would just put in "rtmp://<local LAN IP addr>/live" - correct?

It seems that OBS is streaming to Red5 okay and that Red5 is hosting the stream ok, but I'm also confident that these RTMP clients work properly.  Not sure if I'm perhaps using the wrong address.

Thanks,

Greg

[Jason Powell]

When using VLC/ffmpeg/et al you need to specify the name of the stream in the URL, ie:

rtmp://<rtmp server>/live/<published stream name>

The published stream name will be whatever you entered in OBS' "Play Path/Stream Key" field (I usually paste it in to be sure since OBS treats this as a masked password field)

[Jason Powell]

Sorry for the double reply, just noticed something else.

OBS/XSplit/etc treat the key as the name of the stream to use for broadcasting. By using just the Red5 server's URL and entering 'live' in the play path/stream key field you're telling OBS to broadcast on a stream named 'live' in Red5's root scope instead of the "live" application.

To broadcast on a stream named "mytest" in the "live" application, your OBS settings should look like:

Server: rtmp://<red5>/live

Play Path/Stream Key: mytest

On Tuesday, December 2, 2014 3:04:19 AM UTC-5, Greg Fotiades wrote:

[Mondain]

Thanks for clarifying that, it's what I assumed since there's no "stream name" box.

[Greg Fotiades]

Jason,

Thanks for the clarification, that seems to resolve my connection issue, so in recap, in VLC (or MX Player, or whatever) I'm putting as the stream path:

rtmp://192.168.1.100/live/live

On OBS I'm putting for the URL:

rtmp://192.168.1.100/live
Channel Key:

live

Now it seems to work correctly....seems to have an extremely high latency leading to like 10 seconds of frozen picture, but I can see something on all devices on network now and that's way more than I was able to do last night.  I'll see if I can see where the bottleneck is tonight.

Thank you very much for your help!

[Mondain]

The current and most accurate information on this subject is at https://www.red5.net/docs/protocols/third-party-publishers/obs/

In addition to RTMP, Red5 also supports WHIP via OBS.