Question / Help seeking some advice for an rtmp server

[Greendweller]

Goodmorning,

I am buisy with configuring red5 as a local rtmp server and would like to ask some advice here if someone knows the solution.

(im already waiting for a few days for the red5 google discussion group to be accepted to but so far not luck, thats why im turning over to here.)

I downloaded the latest version of red5 (1.0.1) and the java sdk and installed /configured it so that i get the initial red5 webpage that says that i have set up the server correctly. And the demo's indeed work properly so far as i can see/judge. (configured it on a laptop for now)

My goal is to setup a local server on my lan to host a lan party.
Every single computer on the lan runs obs and sends it to the lan rtmp server. ( have a gigabit lan so no worries there)

Now i want the server to capture those streams and let them rotate lets say every 10 seconds on a single webpage.
Then i want to capture that webpage with obs and stream it to twitch.(on the same rtmp server)

Now the first problem that i encounter is streamkeys. Were can i find/generate/create those in red5?
And how do setup red5 with the plan that i outlined earlier?

Is there anyone who can point me in the right direction?

 

[dodgepong]

I don't know about setting up Red5, but if Red5 is anything like the nginx + RTMP server, then you "invent" a stream key when you stream to the server (i.e. you don't get a stream key from the server and then stream to it, but you just stream to the server using a stream key of your choosing).

 

[Greendweller]

Thanks for your quick responce.
Does a key need to have a specific syntax that you perhaps know of or a certain amount of digits?

(i already tried something totally random but it doesn't seem to accept that tbh)
obs keeps reconnecting and i see no buffering going on.

 

[Greendweller]

I got a tiny bit furter with configuring that red5 server
(will make a guide when i actually got it to work properly)

But i'm still not able to connect to it, However the error message changed wheni'm trying to connect now and perhaps someone know this issue?
When i try to connect now with obs to my rtmp server i get the message after 2 seconds:

Could not connect to the server
RTMP_Connect0, failed to connect to socket. could not make connection because the target computer refused the connection (10061).

Before anyone tells me it's a firewall thing: i have tested my open rtmp ports at:http://www.therealtimeweb.com/index.cfm/2004/10/2/fms-port-tester?CFID=3070163&CFTOKEN=10205845
and it shows that they are all open.

Now i have probably found the configuration file for red5 server settings and i came across this part of code:

# Socket Policy
policy.host=0.0.0.0
policy port=843

do i also need to open that port on my firewall? and what ip should i fill in there for the host ip adress?
(already tried 127.0.01 but that didn't work.)

 

[Greendweller]

Okay i managed to get around that issue by reinstalling red5 and instead of giving the 127.0.0.1 when asked for an ip during the installation i have set my (static) lan ip and now im able to open up webpages from the red5 server from within my network from different computers.

But ofcourse i have encounterd another issue now and i guess that is actual programming work
When i now try to connect to red5 with obs i almost immediately get the following errors:

14:13:38: librtmp error: RTMPSockBuf_Fill, remote host closed connection
14:13:38: librtmp error: RTMP_Connect1, handshake failed.
14:13:38: Connection to rtmp://192.168.1.99:5080 failed: Kan geen verbinding maken met de server
14:13:38:
14:13:38: RTMPSockBuf_Fill, remote host closed connection
14:13:38: RTMP_Connect1, handshake failed.

Im not sure tho but i guess that red5 now needs a piece of script to handle the stream that obs offers.

 

[Greendweller]

Pff some things can be simple just like this one :)

Turns out that it (not sure if it's red5 or obs) somehow doesnt like to have the port specified in the server url.
Guess its some sort of protections or something?
Anyways the server receives now my stream :D

And im able to view myself with the software/app that came with the server installation.
Guess it's now just a case of fiddeling around with the code of that page so it displays several streams and stuff..


Getting closer to my goal step by (tiny) step :)