Closed pleqtron closed 9 years ago
AMS is using a handshake routine which is unknown to Red5; the first two lines in your log dump allude to this. Until the routine is known, we won't be able to support this type of connection.
According to Mondain, It is not possible to connect with RED5 from Adobe media server. Am I right ?
For testing, I'm using the dockerized version of AMS http://codesi.nz/docker/2015/09/17/dockerizing-adobe-media-server.html https://github.com/opreaadrian/docker-adobe-media-server
Successfully tested connecting to AMS 5.0.8 from Red5 Client and from AMS Server to Red5. The Red5 version used was 1.0.7-SNAPSHOT without any special modifications. The only issue I see at this time is in the initStream call made from AMS when creating a NetStream and until that is resolved, I'll keep this issue report open.
Similar Stackoverflow post that I made back in April 2015 http://stackoverflow.com/questions/29810697/adobe-ams-to-ams-initstream-method-call
I've updated red5 to handle the new methods called by AMS and have found that the play method uses some unknown object instead of the standard NetStream.play params we all know, so to work around this, you simply need to set AMF0 encoding on your server-side netconnection like so:
application.mobilenc = new NetConnection();
application.mobilenc.objectEncoding = 0;
I am currently streaming (with my custom application, server-side as well as client.side) on an Adobe Media Server (formerly Flash Media Server). In my server-side actionscript I try to connect to my additional Red5 Server to push the stream to this instance as well.
I am doing the following in my main.asc:
I can see the connection incoming to the red5 Server. So far so good. But directly after sending first bytes I will get some errors:
If I connect via the Flash Media Live Encoder directly to the red5 Instance, everything works like a charm. Where is the difference? What am I doing wrong?
Best, Patrick